Yesterday we told you about our loose-ends survey. Today the biggest finding gets fixed, along with a wave of things you will feel every day.
The button that finally does something
ShiftSee is a marketplace: businesses post shifts, shifters work them. And yet, posting a shift from the website did not actually work. The button existed. The page behind it did not. Businesses managed from their phones.
That ends today. Post a Shift on the web opens a proper page: pick broadcast (everyone you are connected with can race to claim it) or send it straight to one shifter, set the date, times, and rate with real pickers, add notes, and post. The other side landed too: shifters get a real Open Shifts page in the browser with one-tap claiming.
Notifications, live
The bell in the header now earns its place: a live panel of your latest updates, an unread dot that clears across devices, and background refresh while your tab is open. Under the hood we shipped a new sync engine that tells any ShiftSee app what changed in the last few seconds, cheaply enough to ask every 15 seconds. The upcoming mobile app polls it continuously, so shift claims, connection requests, and schedule changes show up while you are looking at the screen, no push notification required.
Sessions that cannot be replayed
Security work rarely makes headlines but this one matters: sign-in tokens are now single use. Each renewal retires the old token; a stolen token that gets replayed revokes every session on the account automatically. Signing out now means signed out, and a password change ends every session everywhere. Deleting your account also became real, with a 7 day grace window in case you change your mind.
And one for the AI-curious
ShiftSee now speaks MCP, the protocol that lets AI assistants use tools. Point Claude, Cursor, or any MCP client at your personal API key and ask it to check your schedule, post Friday's shift, or claim open work. Payments stay human-only by design. More on this soon.