Four roles, each one a real seat.
The roles
- Viewer: sees sessions, transcripts, diffs, plans, memories and history. Nothing else.
- Commenter: viewer, plus comments and suggestions, plus holding work: claim a board item, accept an assignment, hand it back, mark it done. No agent required.
- Editor: commenter, plus everything agentic: start and join sessions, prompt, steer their own turns, take over, spawn subagents, answer approvals, manage plans, assign work, invite to a session.
- Owner: editor, plus membership, roles, settings and deletion.
Enforcement
- Role changes take effect on the server immediately. A downgraded client’s next action is rejected even before its screen catches up.
Nothing gated runs without a named approval.
Approval cards
- Agents start in request-permission mode. A gated action produces an approval card: the exact action, the capabilities it touches, the agent asking and the human behind it.
- Approval authorizes that exact action, once. It is enforced on the machine that runs the action, not just in the interface.
Local provider CLIs work with a shared Brain and your Git remote.
Architecture
- Claude Code and Codex run locally under each member’s provider login. Provider requests follow that account’s data controls.
- Repository content stays in local checkouts and synchronizes through Git shadow refs on your configured remote. The Brain stores snapshot commit and ref metadata, not a repository copy.
- The Brain stores workspace and session records, plans, locks, memories, comments, activity and encrypted transcript chunks after built-in pattern-based secret redaction. Anthropic can process prompt-derived content for overlap checks and task summaries.
- Transcript chunks and stored GitHub tokens are encrypted by Amoeba before they are written to the database. Other workspace records are protected by our database provider’s storage encryption. Amoeba holds the encryption keys, so this is not end-to-end encryption.
- Transcript chunks follow the organization’s configured transcript-retention period. The default is 90 days. Other coordination records do not share that automatic expiry and can remain until removed or the workspace is deleted.
Bring your own agent. Managed usage is optional.
What you pay for
- Bring your own agent: your provider’s charges go to your provider and Amoeba adds no markup to them. Optional managed model usage is metered and billed at provider token cost plus 5%.
- During early access, the builds on this site are free.
We onboard pilot teams directly.
Run one
- Running Amoeba with your team? We set pilots up hands-on and stay close through the first weeks.
- The fastest way to start: contact us and tell us your team size and stack.
Run the latest build
Download for macOSDownload for Windows
Back to the site