Downloading now

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

start the download again

Getting started.

From download to your first shared session in about ten minutes. No agent installed yet? You can still watch, comment and hold work.

Install

01

One installer per platform, signed on both.

Mac

  • Apple silicon (an M1 or newer). The build is Developer ID signed and notarized by Apple, so it opens with a normal double click.

Windows

  • x64. Signed and timestamped.

Updates

  • The app updates itself in place. One exception: builds at 0.1.17 or older cannot apply updates. Install the latest build manually once and everything after that is automatic. Details in the change log.

Sign in

02

Sign in and set up your team.

Steps

  • Amoeba stores GitHub access tokens, encrypted, to give you repository access; it does not store your local Git credentials or SSH keys. You can sign in with email, Google or GitHub.
  • Create an org for your team, or join the one a teammate made.
  • Open the local Git clone you want to use. You also need an Amoeba workspace connected to that clone. If your installation does not offer a way to connect one, ask the teammate who invited you or your Amoeba administrator before continuing.

Connect your tools

03

Bring the coding agents you already pay for.

Providers

  • Amoeba works with Claude Code and Codex. It detects the CLIs on your machine and offers one-click setup of the hooks and tools they need to coordinate.
  • Your agent runs on your machine under your provider login. The provider performs model inference under your account’s data controls. Amoeba also processes prompt-derived coordination context in the Brain, including overlap and task-summary processing by Anthropic.

No agent?

  • A supported seat, not a broken one. You can watch every session live, comment, and hold work from the board without any agent installed.

First session

04

Start one session and the board comes alive.

Do this

  • From Mission Control, start a session with a short task description. Amoeba can use a session branch and dedicated Git worktree for joined sessions and subagents, keeping their working-tree changes separate from the main checkout.
  • Prompt your agent. Your conversation streams live to Mission Control, where teammates see the task, the progress and the files being touched.

Invite the team

05

Sessions are better with people in them.

Invites

  • Invite teammates by GitHub username and pick their role.
  • A teammate who joins your session gets their own column with their own agent. You both see everything, live.

The manual

→

Everything else, by topic.

Read next

  • Core concepts: workspaces, sessions and lanes, Mission Control, ownership, the shared Brain.
  • Working with agents: providers, prompting, guiding and taking over, parallel subagents, recovery.
  • Team collaboration: live sessions, overlap warnings, plans, comments and handoffs.
  • Code and Git: repositories, worktrees, editor and terminal, reviewing changes, syncing.
  • Admin and security: members and roles, permissions, local-first architecture, usage, pilots.
  • Help and reference: troubleshooting, error reference, shortcuts, releases, MCP reference.

Run the latest build

Download for macOSDownload for Windows

Back to the site