CLI backends (fallback runtime)
Clawdbot can run local AI CLIs as a text-only fallback when API providers are down, rate-limited, or temporarily misbehaving. This is intentionally conservative:- Tools are disabled (no tool calls).
- Text in → text out (reliable).
- Sessions are supported (so follow-up turns stay coherent).
- Images can be passed through if the CLI accepts image paths.
Beginner-friendly quick start
You can use Claude Code CLI without any config (Clawdbot ships a built-in default):Using it as a fallback
Add a CLI backend to your fallback list so it only runs when primary models fail:- If you use
agents.defaults.models(allowlist), you must includeclaude-cli/.... - If the primary provider fails (auth, rate limits, timeouts), Clawdbot will try the CLI backend next.
Configuration overview
All CLI backends live under:claude-cli, my-cli).
The provider id becomes the left side of your model ref:
Example configuration
How it works
- Selects a backend based on the provider prefix (
claude-cli/...). - Builds a system prompt using the same Clawdbot prompt + workspace context.
- Executes the CLI with a session id (if supported) so history stays consistent.
- Parses output (JSON or plain text) and returns the final text.
- Persists session ids per backend, so follow-ups reuse the same CLI session.
Sessions
- If the CLI supports sessions, set
sessionArg(e.g.--session-id) orsessionArgs(placeholder{sessionId}) when the ID needs to be inserted into multiple flags. - If the CLI uses a resume subcommand with different flags, set
resumeArgs(replacesargswhen resuming) and optionallyresumeOutput(for non-JSON resumes). sessionMode:always: always send a session id (new UUID if none stored).existing: only send a session id if one was stored before.none: never send a session id.
Images (pass-through)
If your CLI accepts image paths, setimageArg:
imageArg is set, those
paths are passed as CLI args. If imageArg is missing, Clawdbot appends the
file paths to the prompt (path injection), which is enough for CLIs that auto-
load local files from plain paths (Claude Code CLI behavior).
Inputs / outputs
output: "json"(default) tries to parse JSON and extract text + session id.output: "jsonl"parses JSONL streams (Codex CLI--json) and extracts the last agent message plusthread_idwhen present.output: "text"treats stdout as the final response.
input: "arg"(default) passes the prompt as the last CLI arg.input: "stdin"sends the prompt via stdin.- If the prompt is very long and
maxPromptArgCharsis set, stdin is used.
Defaults (built-in)
Clawdbot ships a default forclaude-cli:
command: "claude"args: ["-p", "--output-format", "json", "--dangerously-skip-permissions"]modelArg: "--model"systemPromptArg: "--append-system-prompt"sessionArg: "--session-id"systemPromptWhen: "first"sessionMode: "always"
codex-cli:
command: "codex"args: ["exec","--json","--color","never","--sandbox","read-only","--skip-git-repo-check"]resumeArgs: ["exec","resume","{sessionId}","--color","never","--sandbox","read-only","--skip-git-repo-check"]output: "jsonl"resumeOutput: "text"modelArg: "--model"imageArg: "--image"sessionMode: "existing"
command path).
Limitations
- No Clawdbot tools (the CLI backend never receives tool calls). Some CLIs may still run their own agent tooling.
- No streaming (CLI output is collected then returned).
- Structured outputs depend on the CLI’s JSON format.
- Codex CLI sessions resume via text output (no JSONL), which is less
structured than the initial
--jsonrun. Clawdbot sessions still work normally.
Troubleshooting
- CLI not found: set
commandto a full path. - Wrong model name: use
modelAliasesto mapprovider/model→ CLI model. - No session continuity: ensure
sessionArgis set andsessionModeis notnone(Codex CLI currently cannot resume with JSON output). - Images ignored: set
imageArg(and verify CLI supports file paths).