It works through your tools — Gmail today, any remote MCP server your team adds, and your code editor. Anyone in the room can ask it, watch it, or stop it. Anything that sends, creates or changes waits for the person whose account it uses.
Follow-ups for this week
Team-visiblePriya · 09:14
Draft replies to the three oldest unanswered threads
Send an email from priya@acme.co
This action needs your approval
Everyone in the room prompts the same agent, and it knows who's asking.
Each step streams into the room as it happens — the search, what it read, what it's about to do.
Reads run on their own. A send, a create, an update waits for the person whose account it runs on, who can edit it before it goes.
A team thread sits next to the agent, and the agent never reads it.
Your accounts
Search, read, and send from your own inbox. Only in turns you start.
Your team's tools
Any remote MCP server an admin adds — for example, an issue tracker, a docs space, a database, or your own internal API. Read-only tools run on their own; everything else asks first.
Each one is a prompt someone types into a room. Everyone watches the work happen, and nothing that writes goes out without the right person's approval.
Gmail
“Draft replies to the three oldest unanswered threads.”
It searches and reads on its own, writes each reply, and waits for you before anything sends.
Documents
“Turn these notes into a one-page PDF summary.”
Reports, briefs and letters as Markdown, PDF or Word — saved in the room for everyone to download.
Images & video
“Create a hero image for the launch post.”
Generated through fal.ai, approved before it's made, saved in the room with its cost on record.
Issue trackers
“List the open issues and what's blocking the release.”
Through Notion, Linear, GitHub and other MCP servers your team adds. Reads run on their own.
Calendar & Drive
“What's on my calendar this week? Find last quarter's contract.”
Reading files and events runs on its own; creating or changing anything asks first.
VS Code
“Fix the keyboard navigation bug in the menu.”
A coding session in your editor, with the room around it — teammates watch, stop, and suggest mid-turn.
Coworkers for VS Code
Start a multiplayer coding session inside VS Code. The agent reads and edits the owner's machine only. Teammates join from their own editor to watch every step, stop it mid-turn, suggest the next instruction, and talk in a thread the agent never reads.
Every other coding agent is one person alone with a model. This one has a room around it.
Fix keyboard navigation in Menu
acme-web · fix/menu-a11y
Team-visible
You · owner · 09:14
Menu doesn't work with the keyboard — add arrow-key navigation and focus handling.
src/components/Menu.jsxAgent · Sonnet 5 · agent mode · 09:17
The menu renders as a plain ul with mouse handlers only. I'll add roving focus with aria-activedescendant, arrow-key movement, and an Escape path back to the trigger.
Suggestion from Priya · 09:19
watcherAlso give Escape a path that returns focus to the trigger button — that's the bug QA filed.
Fix keyboard navigation in Menu
acme-web · fix/menu-a11y
Team-visible
You · 09:14
Taking the Menu accessibility issue — session's open if you want to watch.
Priya · 09:19
Watching. QA's repro is Escape from a submenu, not the arrows.
You · 09:20
Good catch — sending that in as a suggestion.
Every edit is proposed as a diff. Nothing is written to anyone's disk until a person accepts it.
Who asked and who approved are recorded by the database, not by convention.
Personal connections only run in turns you start.
Private rooms are invisible to everyone else, including their history.