Quickstart

This is the current Amp-first product path: connect once with a Revue API key, then run revue to launch the manager Amp session. The manager thread is the primary UI for child sessions, Orbs, subagents, and human decisions.

1. Install Revue

Install or update Revue from the repository:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/ethandaya/revue/main/scripts/install.sh)"

The command installs or updates Revue at ~/.local/share/revue/source, installs the Amp plugin and bidding skill once in your user config (~/.config/amp and ~/.config/agents), writes a ~/.local/bin/revue command shim, and prepares ~/.config/revue.

When working from a Revue checkout, the equivalent developer command is pnpm run revue.

2. Connect one API key

Use a workspace-scoped Revue API key:

revue login

Revue asks only for the API key, validates it with the hosted API, infers the workspace, and stores machine credentials under ~/.config/revue. For a non-default service deployment, use revue login --api-url <url>.

3. Launch the manager

From any workspace:

revue

Bare revue syncs the Amp plugin and skill, mints a short-lived manager delegation, and launches Amp in Revue manager mode. Keep that Amp thread open; it is the primary UI.

Ask the manager in chat:

launch an orb to investigate CI
launch a local child to write the regression test
show blocked decisions
answer the top decision with option B

4. Launch backup children from the CLI

The manager can launch children for you. If you need the CLI backup path:

revue child "Investigate CI and bid only for true human decisions" --where orb --launch
revue child "Review this diff" --where local --launch

--where orb uses Amp's Orb execute path. --where local starts a local Amp child. Revue defaults the manager context when you are outside the manager thread.

5. Verify the connection

revue doctor --remote
revue smoke

revue smoke registers a manager/child/subagent dogfood loop, seeds a child decision, answers it with manager delegation proof, and verifies route proof. Add --launch-orb only when you want to spend a real Orb run.

Fallback local UI

Amp manager chat is the primary UI. The older local TUI remains available as a fallback:

revue ui

The non-interactive commands still exist for scripts or debugging:

revue inbox
revue answer top "Use the recommended default."
revue watch

Shell autocomplete is generated by Incur; run revue completions --help for zsh, bash, fish, and nushell setup snippets.

Developer commands

revue rpc
revue threads
revue steer latest "Follow up on the completed task."
revue archive latest
revue demo

latest resolves to the most recent unarchived workstream, so you can follow up or archive without finding an Amp thread id.