Auggie
Operating Auggie on workers — login or AUGMENT_SESSION_AUTH, print mode and indexing, and several repositories.
Install
npm install -g @augmentcode/auggieThe worker looks for auggie on the worker user's PATH.
Sign-in
Run auggie login once as the worker's user, or put AUGMENT_SESSION_AUTH in the task's environment profile.
Without either a run ends with "No auth provided".
How it runs
auggie --print --output-format json [--model <model>] [--add-workspace <dir>] --instruction-file <prompt file>
- Print mode skips the indexing confirmation, so the project is indexed by Augment without a prompt.
- The task is read from the instruction file.
- Projects with several repositories reach it: the other repositories are passed with
--add-workspace.
Add-on models
Auggie 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 Auggie: 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 Auggie 0.36.0 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.