Team-wide Google Connectors, Zero CRM, and a Calmer Slack
Gmail and Google Calendar now cover your whole team without holding onto message bodies, and Slack finally shows you exactly what your assistant is working on.
Gmail and Google Calendar now work across your whole team. Each teammate connects their own Google account, and when you ask a question that spans the team — who's already talking to this customer, when everyone is free — reads fan out across every connected mailbox and calendar, with each answer attributed back to the person it came from. Writes work the other way on purpose: creating an event or sending an invite always binds to your own account, so nothing ever lands on a colleague's calendar by accident. Compose links open your mailbox, never someone else's.
Alongside that, we closed a privacy gap worth calling out. Gmail message bodies used to linger in saved chat history long after the conversation ended. Now every Gmail result is tagged so that saved transcripts keep only the subject line and a link back to the thread — the body itself is trimmed on the way to storage, in single-member and team workspaces alike. Our privacy policy has been updated to spell out exactly how Google data is read, retained, and never used for training, advertising, or sale. Gmail connections remain invite-only while Google's verification review runs.
There's a new Zero connector too, for teams using the AI-native CRM. It's read-only in this first release — records, activity history, synced email, and calendar — with an authorization flow that can't request write access at all, and availability limited to a small beta group while we watch it in the wild.
Slack got the biggest quality-of-life change. Your assistant's "working" indicator is now a single native status line instead of a pile of self-posted placeholder messages, typing GIFs, and duplicate narration. The line names the tool actually in use — "querying your database in Supabase" rather than a vague "still on it" — and it holds that identity through long tool calls instead of decaying into generic text. Status updates that used to be dropped mid-stream now land in order, the rotating copy stays in the assistant's own voice, and its avatar stays its own rather than being replaced by a connector logo. Long-running deep work drives the same status line, refreshed periodically so it doesn't quietly expire while a task is still running. And when an upstream model call hangs, the turn is now cut short and retried once within the same time budget instead of returning an empty reply — with failure details always recorded so our team sees problems the moment they happen, not weeks later.
A few smaller things round out the release. Workspace chat is easier to read: message text is larger, the conversation column is wider and aligned with the opening screen, and the deep-work proposal card header has been pared back to just its title and cost. In-chat file generation has been retired — chat and deep-work replies are text and links now, with branded slide decks remaining the one thing the assistant builds as a file. Everything generated previously is still in your Library and still downloads and previews exactly as before. Behind the scenes, published pages are now automatically submitted to search engines after each deploy, so new content shows up in results faster.
If your team lives in Slack or works out of Google, this is a good week to reconnect your accounts and see the difference. As always, tell us what still feels rough.