Your team.
One shared board.
See who is working on what. Message any session and leave notes for each other. Keep the work on your team's server.
Message a session someone else controls
Every live session in a workspace is open to the members who reach that workspace. Teammates watch its terminal as a mirror while one person controls the agent. A message from anyone else waits up to 45 seconds for the controller to approve or deny it, and is delivered when the time runs out.
- Teammates watch the terminal as a mirror. One person controls the agent.
- A message from anyone else waits for the controller.
- When the time runs out, it is delivered.
Take control, send a message, leave a note
- To control the session yourself, hold Take control for three seconds. The controller can accept or deny, and with no answer control passes after seven seconds.
- The agent gets only the text of a message. People see who sent it.
- Notes in the session's Details are for the people on it. The agent never sees them.
Every act has a name on it
Collaborators can message, control and stop each other's sessions from the start. Cloudfield records it instead of preventing it: Activity lists every message, stop, approval and handoff with the member who did it, in that member's colour.
- Every act is recorded in its member's colour.
- Two sessions change the same file. Both get a warning, and nothing is locked.
- A session's commits name the teammates who messaged it.
Co-authors, overlapping work and agent messages
- Teammates who message a session become its co-authors: commits Cloudfield makes for it end with a Co-authored-by line for each of them, and the agent is told to add the same lines to its own.
- When two sessions change the same file, both get a warning that opens the shared files. Nothing is locked.
- Sessions in one workspace can message each other through their agents, and any member of the workspace can read what they said.
Choose each person's access
Viewers watch sessions and read Activity. Collaborators, the default, launch sessions and can message, control and stop anyone's, in the workspaces they were granted. Admins also manage the workspaces they own: settings, budgets and grants. A super admin manages members, roles and the server.
- Protect a session and only its owner and admins can message, control or stop it.
- A role change applies at once, even to connections already open.
Lend a teammate your agent subscription
Share your agent account from a teammate's row in Members and they can launch sessions on your subscription: useful when they have no subscription of their own, or have used up its quota.
- Their sessions stay theirs: their own environment, home and GitHub login.
- A Claude Code or Codex session whose account runs out of quota can move to another account its owner may use.
- Revoking the share stops new launches on your account.
Sorted by what needs you
Every session you can see is a card under Needs you, Working or Finished. A card says why it is waiting, such as the agent's question.
- The agent asks a question. The card moves to Needs you.
- You answer from the card, and it is Working again.
- It reports success. The card moves to Finished.
Subsessions and budgets
- Subsessions
Let an agent start subsessions
An agent can start a subsession for a large, independent part of its task: a session with a fresh context, on any agent you have installed and left on for subsessions. It appears under its parent, reports its result to the parent, and you can open, message, take over or stop it like any session. Subsessions go one level deep.
- Spending limits
Limit new work, not progress
A workspace's admin can give it a spending cap in US dollars. At the cap new sessions are refused unless the override is on, and sessions already going finish. Recorded spend is a floor: sessions whose agent reports no cost are not counted, and deleting a session keeps its cost.
Check the security boundary
Read how processes, credentials and permissions are separated.



