Amp
Operating Amp on workers — AMP_API_KEY or login, the settings file that switches confirmations off, and why a missing login waits.
Install
npm install -g @sourcegraph/ampThe worker looks for amp on the worker user's PATH.
Sign-in
Run amp login once as the worker's user, or put AMP_API_KEY in the task's environment profile. Do one of
them before the first task: without a login Amp starts a browser login and waits. The worker reports
authentication required as soon as that line appears, but the process ends only when the hang timeout stops
it.
How it runs
amp --settings-file <file> --no-notifications --no-ide --no-color --stream-json -x <prompt>
- Amp has no flag to switch command confirmations off. The worker passes a settings file of its own for the
run with
amp.dangerouslyAllowAll. - Because that settings file replaces your own for the run, settings from your
settings.json(such as MCP servers) are not loaded. - There is no model flag: the model follows Amp's agent mode, so a task's model choice is not applied.
Add-on models
Amp cannot use add-on models or providers configured on the worker. When it reaches its limit, the task moves to another compatible agent, or waits, as the fallback policy says.
Sessions
Resume is not claimed for Amp: no resume command could be verified without an account. After a crash, recovery starts a fresh session from the checkpoint.
What was verified
Checked against Amp 0.0.1791244891 on 2026-10-06: its --help, and a real run without credentials through the
worker's session runtime. A task with the vendor's account has not been run.