Qoder CLI
Operating the Qoder CLI on workers — sign-in, print mode, the session id, several repositories, and what it cannot do.
Install
npm install -g @qoder-ai/qodercliThe worker looks for qodercli on the worker user's PATH.
Sign-in
Run qodercli login once as the worker's user. Without a login a run ends with "Not logged in · Please run
/login".
How it runs
qodercli -p --output-format stream-json --dangerously-skip-permissions --session-id <uuid> [--model <model>] [--add-dir <dir>] <prompt>
--dangerously-skip-permissionsbypasses permission checks; without it a headless run waits.- The worker assigns each session its id.
- Projects with several repositories reach it: the other repositories are passed with
--add-dir.
Add-on models
Qoder CLI 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 Qoder CLI: 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 Qoder CLI 1.1.65 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.