Install Amoeba and open a shared workspace
A first-run guide using Welcome and Setup, GitHub sign-in, Claude Code or Codex detection, an existing workspace connection, and team invitations.
What you need
Use the desktop Welcome and Setup flow. Amoeba does not publish end-user commands for login, repository connection, session creation, or invitations.
- An Amoeba installer for macOS or Windows.
- A GitHub account and a local clone of the repository your team will use.
- Claude Code or Codex installed locally.
- 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.
Complete Welcome and Setup
- Download and open Amoeba.
- Select “Continue with GitHub” and finish sign-in.
- Review the disclosure. Provider CLIs and the checkout run on this machine, while the Brain stores shared coordination data and encrypted transcript chunks.
- Choose Claude Code or Codex. If the CLI is missing, install it and return to Setup.
- Complete provider sign-in if Amoeba reports that it is needed.
- Select the workspace connected to the repository’s local clone.
- Choose “Set it up for me” to install the provider adapter.
- Invite a teammate by GitHub username.
- Start the guided first session or open Mission Control.
Check the shared workspace
Each teammate repeats local provider setup on their own machine and uses their own provider account. Start with a small task on a disposable branch, then verify that session context, file activity, and the final Git diff appear where expected.
- Mission Control shows the correct workspace and repository.
- Claude Code or Codex is connected on this machine.
- Teammates appear under their GitHub identities after joining.
Data path and troubleshooting
Repository content stays in local checkouts and code moves through the configured Git remote under your credentials. Provider inference is a network operation. The Brain stores coordination records and encrypted transcript chunks, and Anthropic can process prompt-derived context for overlap checks and summaries. Amoeba encrypts transcript chunks and stored GitHub tokens before they are written to the database, and other workspace records rely on our database provider’s storage encryption. Amoeba holds the keys, so this is not end-to-end encryption.
Transcript chunks follow the organization’s configured transcript-retention period. Other workspace records do not share that automatic expiry. Workspace deletion removes workspace-scoped Brain data; local Amoeba state, Git objects, and provider histories are managed separately.
- Provider not detected: verify that Claude Code or Codex is installed, then reopen Setup.
- No workspace appears: ask the teammate who invited you or your Amoeba administrator for the workspace setup path.
- A teammate cannot join: confirm the GitHub username, workspace membership, and repository access.
- The agent works but coordination is missing: check the local connector and Brain connection. The provider can continue solo while coordination is unavailable.
Download AmoebaGetting startedConnect Claude Code or CodexTroubleshooting