Docs / Help and reference

When something looks wrong.

The common fixes, the honest failure states, the shortcuts, and where to find us.

Troubleshooting

The three things people actually hit.

The Mac build needs Apple silicon (an M1 or newer). Both installers are signed; if your OS warns about an unidentified developer, re-download from this site.

The app updates itself. Builds at 0.1.17 or older cannot: install the latest build manually once, and updates are automatic from then on.

The window title always shows connection state. If the coordination server is unreachable, your agent keeps working solo and reconnects on its own. Presence and peer awareness come back by themselves.

Failure states are named, not hidden.

“Sync paused”: the session’s branch cannot push, usually credentials or a ruleset. Fix the credentials and retry from the banner; presence keeps working meanwhile.
“2 versions” of a file: a sync conflict. Both versions are preserved; open the session and pick.
“Outcome unknown”: an action was interrupted mid-flight. Amoeba never retries it automatically. The card shows what was dispatched and the evidence, and an editor records what actually happened.
“Workspace not set up on this machine”: the app is healthy but this machine holds no binding for the workspace. The screen offers setup directly.

The keyboard map fits in one breath.

Cmd or Ctrl K: the command palette, from anywhere.
Escape: closes whatever is open.
Enter dispatches the composer’s selected intent; Shift+Enter is a newline.
Shift+Tab cycles your agent’s permission mode in native mode. In terminal mode it passes through to the CLI untouched, which is exactly what your CLI expects.

Every build, in plain English.

The change log lists every release: what is new, what got better, what we fixed.
Downloads always point at the latest signed build for your platform.

The tools your agents use to coordinate.

Setup installs a small set of coordination tools into your CLIs over MCP: fetch the team’s live context, propose a work split, claim plan steps, assign board work, send a message to another agent, record a memory.
Your agent picks these up automatically; there is nothing to configure by hand. Each tool documents itself to the agent, including when not to use it.

A human answers. Usually a founder.