Amp
Install, authenticate, and resume Sourcegraph's Amp inside Daintree, including the @ampcode/cli package, OAuth tokens, AMP_API_KEY, and thread resume.
Amp
Amp is Sourcegraph's agentic coding tool. It runs as a process in its own Daintree terminal panel with full PTY emulation, like every other built-in agent.
| Command | amp |
|---|---|
| Shortcut | — (assignable in Keyboard settings) |
| Rendering | Alt-screen — Amp draws its own full-screen TUI |
| Resume | amp threads continue <id> (named thread) |
| Quit command | — (no slash-quit; Daintree sends Ctrl+C) |
| Permission bypass | --dangerously-allow-all |
| Platforms | macOS and Linux native; on Windows use the npm package or WSL |
Install & Authenticate
curl -fsSL https://ampcode.com/install.sh | bash
# or
npm install -g @ampcode/clinpm install -g @ampcode/cliNo native Windows binary is published. Use the npm package on Windows, or run the curl installer inside WSL.
curl -fsSL https://ampcode.com/install.sh | bash
# or
npm install -g @ampcode/cli@ampcode/cli. The older @sourcegraph/amp name was an alias and has been retired — if you have it installed, reinstall from the new package.Run amp once and it opens your browser to complete the OAuth flow, storing tokens in ~/.amp/oauth/ and refreshing them automatically. On headless machines and in CI, set AMP_API_KEY instead. Amp is a paid product, so this needs an active ampcode.com account. The installer drops the binary at ~/.amp/bin/amp with a symlink to ~/.local/bin/amp, and Daintree probes both paths because the symlink isn't always on PATH for a GUI-launched process.
Resuming Sessions
Amp resumes by thread rather than by session ID: Daintree relaunches it as amp threads continue <id> against the thread the previous panel was working in. Amp has no slash-quit command, so Daintree sends Ctrl+C as the graceful exit signal on shutdown. See Session Management for how resumable sessions are stored and pruned.
Launch flags, custom presets and display titles are covered in Agent Presets. What the working, waiting and exited badges on a running agent mean is covered in Agent States.
amp isn't detected after install, confirm it's on your PATH (which amp on macOS/Linux, where amp on Windows), then restart Daintree. Daintree also surfaces WSL installations in its availability diagnostics, so a Windows machine with Amp only inside WSL reports that rather than reporting nothing.