Your team.
One shared board.
See who is working on what. Message any run, leave notes for each other, or start a swarm. Keep the work on your team's server.
Message a run someone else controls
Every live run on the server is open to the whole team. 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.
- To control the run yourself, hold Take control for a few 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 run'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 runs from the start. Aether records it instead of preventing it: Activity lists every message, approval and change of control with the member who did it, in that member's colour.
- Teammates who message a run become its co-authors: commits Aether 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 runs edit the same file, both are marked with the file and the other run. Nothing is locked.
- Runs in one workspace can message each other through their agents, and any member can read what they said.
Choose each person's access
Viewers watch runs and read Activity. Collaborators, the default, launch runs and can message, control and stop anyone's. Admins also manage members, workspaces, budgets and settings.
- Protect a run 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 your Profile and a teammate can launch runs on your subscription: useful when they have no subscription of their own, or have used up its quota.
- Their runs stay theirs: their own environment, home and GitHub login.
- A run near its quota can move to an account shared with its owner.
- Revoking the share stops new launches on your account.
Swarms and budgets
- Swarms
Hand a swarm one objective
A swarm's Integrator splits the objective into tasks and starts worker runs for them, on the agents you allowed when you created it. Nobody approves its plan: it asks you only when it needs an answer. The member accountable for the swarm, or an admin, can cancel it.
Launching a swarm - Spending limits
Limit new work, not progress
An admin can give each workspace a spending cap in US dollars. At the cap new runs are refused unless the override is on, and runs already going finish. Recorded spend is a floor: runs whose agent reports no usage are not counted, and deleting a run keeps its cost.
Budgets
Check the security boundary
Read how processes, credentials and permissions are separated.
Read about security