Continue CLI
Operating the Continue CLI (cn) on workers — login or configuration, print mode, and why tasks cannot choose its model.
Install
npm install -g @continuedev/cliThe worker looks for cn on the worker user's PATH.
Sign-in
Sign in to cn once as the worker's user, or set up its configuration. Without either a run ends with an error
that names no cause ("The request failed and the interceptors did not return an alternative response"); the
worker reports it as authentication required.
How it runs
cn -p --auto --format json <prompt>
--autoallows all tools.--modeltakes a hub slug, not a model id, so the worker does not pass a model: Continue's assistant decides.
Add-on models
Continue 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 Continue 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 Continue CLI 1.5.47 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.