Crew
Agents that keep the job, not just the chat.
A crew member is an agent with a charter you approved, its own memory and an inbox. Every use starts a fresh session that already knows the job, so you never explain it twice, and what your chats ask of it waits for your approval.
- Claude Code
- Codex
- Grok
- Devin
- Cursor
Charter
Describe the job once: you approve the charter.
Ask any chat for a crew member. The agent drafts its charter, project, device, model and access, and you see all of it on one card before anything is saved.
- Bind a member to one project, or to none.
- Pick its agent and model: Fable 5.1 on Claude Code, GPT-5.6 on Codex, Grok 4.7 and the rest.
- A member can propose a change to its own charter; it applies only when you approve it.
Memory and handoffs
A fresh session every time: it already knows the job.
Each use starts a new session instead of resuming an old chat. Studio hands it the charter, the member's memory, the notes earlier sessions left and its inbox before your first word.
- Memory belongs to the member, not to one chat.
- Every session leaves a short handoff note for the next one.
- Expand a member to see its sessions, inbox, charter and memory side by side.
Inbox
Your chats can hand work over: you approve it in one batch.
Every chat sees a short list of your crew and can leave a request in a member's inbox. Requests gather for a moment, then wait for you on one card; approve them and they run together in one session.
- Requests come from chats, other crew members and automations, each with its sender.
- Nothing runs on a request before you approve it, unless you let that member approve eligible ones itself, up to a limit per hour.
- Notices need no approval: the member's next session reads them.
Scheduled work
Put a member on a schedule: every run is its session.
An automation can target a crew member, so Disk Cleanup runs at 03:00 with its own charter, memory and model. You approve the automation once, and each run is a session you can open like any other.
- A run never gets more access than the member has, and you can cap it lower.
- A run that finds the member busy is skipped and recorded, not stacked.
Its own machine
Runs where its work is: and stays out of your chat list.
A member's sessions run on its host, the device of its project. Put it on your server and it keeps working while your Mac sleeps; the rail shows who is working and who needs you.
- A blue ring means a session is running, amber that it waits for you.
- Crew sessions never appear in your project chats, the archive or search.
You approve first
Members, charter changes and requests wait for your approval; automations you approved run on their own.
Limits on handoffs
Requests between members stop after two hops, and every chat and member has an hourly send budget.
Your own subscriptions
Every member runs on the agent and provider account you pick for it.
Build your first crew: free on your Mac.
Download Studio, open any chat and ask it for a crew member.