Configuration

The active product path is API-key setup plus the Amp manager launcher. Most users should not edit environment variables directly: run revue login, then revue.

Manager launcher

Setting	How it is set	Controls
Revue API key	`revue login` prompt	Workspace-scoped ingestion, bid, route, and manager-delegation authority
Revue API	Default service, or `revue login --api-url <url>`	Hosted `/api/v1` endpoint
Workspace	Inferred from the API key via `/principal`	Tenant for manager, child, Orb, and subagent state

The saved machine config lives under ~/.config/revue. Child and Orb launches receive adapter/read/route authority only; manager delegation tokens are scoped to the manager run and manager Amp thread.

Local runtime

The local runtime and TUI are fallback/dev surfaces.

Variable	Example	Controls
`REVUE_RUNTIME_PORT`	`47838`	Local HTTP port
`REVUE_RUNTIME_TOKEN`	random secret	Required token for runtime requests and the plugin
`REVUE_WAL_PATH`	`.revue/runtime.wal.jsonl`	Optional durable WAL path
`REVUE_SEED_DEMO`	`1`	Optional local demo state
`REVUE_ALLOWED_ORIGINS`	`http://127.0.0.1:3000`	Optional browser origins for a future local UI
`REVUE_AMP_TRANSPORT`	`pty`, `sdk`, or `execute-json`	How the runtime launches Amp when it owns a session

Amp plugin

Variable	Example	Controls
`PLUGINS`	`all`	Required for Amp to load plugins
`REVUE_RUNTIME_URL`	`http://127.0.0.1:47838`	Local runtime endpoint used by the plugin
`REVUE_RUNTIME_TOKEN`	same as runtime	Token sent as `x-revue-runtime-token`
`REVUE_AGENT_MODEL`	`openai/gpt-5.5`	Model for the `revue` mode; local setup writes this default
`REVUE_ENABLE_GLOBAL_APPEND_DELIVERY`	`1`	Set by local setup so user-level plugin installs can append routed answers

Advanced compatibility

Linear, Centaur, and self-hosted deployment settings remain advanced adapter/operator concerns. They are not part of the first-run path: the engineer should connect one API key and let Revue materialize the launch environment.