Downloading now

Your download has started. Open the installer when it finishes.

start the download again

Docs / Admin and security

Run the workspace.

Roles, permissions, where your code lives, what Amoeba costs, and how pilots work.

Members and roles

01

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.

Permissions

02

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-first

03

Your code stays on your machines.

Architecture

  • Agents run locally under each member’s own login. The coordination server holds sessions, plans, presence and memory: metadata, not source.
  • Code syncs machine to machine over git, under your own credentials, in your own repository. We never store your model API keys or your repo credentials.
  • Transcripts are encrypted at rest, visibility is scoped to the workspace, and nothing is ever public.

Usage

04

Bring your own agent. We never meter tokens.

What you pay for

  • Every tier is bring-your-own-agent: your provider subscription stays between you and your provider, with no markup and no metering from us.
  • Plans govern capacity: people per session, concurrent sessions, active agents per session. The session host’s plan sets the rules, fixed when the session is created, so limits never change under the people inside it.
  • During early access, the builds on this site are free.

Pilots

05

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