Join a session and get your own lane.
The room
- Any session card opens into the room. Join to add your column and work the same plan on the same branch; watch to follow along read-only.
- Everything streams live: every lane’s conversation, the plan, the diff, who is present.
- Joining checks the practical things in the background: your role, a free seat, push access, an available agent. If something blocks you, you are told the one thing that matters and how to fix it.
Possible overlap is visible before a prompt runs.
Coordination context
- Amoeba compares the current branch, open file paths, planned file paths and task descriptions with active sessions. Same-file activity is marked as overlapping; related plans or task descriptions can be marked as adjacent.
- A warning includes teammate and session context so the team can join, split or coordinate the work.
- Exact-path locks tell connected agents to refrain from editing a held file. They are advisory and scoped to the session, not a filesystem write barrier.
- If the local hook or Brain is unavailable, the prompt continues and may use cached context. Confirm ownership directly when a warning is missing or stale.
One plan per session, with owners on every step.
Shared by design
- Steps have owners and statuses everyone can see, and the progress on a session card comes from the plan, never from a guess.
- See a teammate eleven steps deep? Select steps and offer to take them. Unstarted, unowned steps transfer instantly; anything started asks its owner first.
Say it on the exact line you mean.
Anchored
- Attach a note to the session, a transcript moment, a file range or a diff hunk.
- A comment can become a plan step, a suggestion, or a prompt to your own agent, and it stays linked to whatever it caused. A comment alone never consumes provider usage.
- Resolving never deletes. If the code a comment pointed at moves on, the comment is labeled, not thrown away.
Work continues. It never restarts.
The baton
- Hand a session to a teammate deliberately, or let takeover handle the involuntary cases: a usage limit, a closed laptop, a vacation.
- The taker gets the branch as of the last successful sync, the plan with statuses, and the fresh memories. History records the baton pass.
- Assignment works for non-engineers too: hand a board item to someone with no agent and they can hold it, finish it, or hand it back with a note.
Run the latest build
Download for macOSDownload for Windows
Back to the site