Cline
Use Cline through AnyAgent: what you can ask for, how it behaves, and the endpoint underneath.
The cline adapter drives the Cline CLI over ACP (cline --acp), detected as the cline binary on PATH; import cline from anyagent-js/cline. The Cline CLI is Apache-2.0 open source and bring-your-own-key (BYOK): configure a provider once with cline auth -p openai -k your_api_key_here (openrouter, anthropic, openai, and gemini all work).
What you can ask for
model and resume work on the endpoint’s own channels; readOnly, systemPrompt, and schema are provided by AnyAgent. effort, mcp, attachments, and model listing are undeclared and throw. authStatus() reads the provider settings file and never runs the CLI, whose config subcommand needs a TTY. The full grid is on the support matrix.
Good to know
Pin a model. A session that leaves model unset inherits Cline’s stored choice, which need not be a model the signed-in provider serves, and the turn then ends with no output.
- Every turn runs on a live connection, so sessions steer; the session id lands on
result.sessionIdand is whatresumetakes back. readOnly: trueis enforced by denial rather than by a mode: Cline’s own plan mode still runs shell commands, so AnyAgent rejects every permission request for a tool that could change the machine.- Runs report no token usage: the endpoint answers a prompt with its stop reason alone.
Under the hood
Every session launches cline --acp and configures it over the protocol; the prompt travels as a content block. Run options become:
| Option | Channel |
|---|---|
model | config option model, in Cline’s own vocabulary |
cwd | the cwd of the new session, and of the endpoint process |
resume | session/load with the session id |
readOnly: true | a denial of every permission request for a tool that could change the machine |