pub const CLAUDE: CliBackend;Expand description
claude, measured at 2.1.273 by running it, not only by reading --help.
stream_flags carries --verbose: since at least 2.1.281, -p with
--output-format stream-json and no --verbose exits 1 before any event
(“–output-format=stream-json requires –verbose”). Re-measured at 2.1.283;
the flag adds no events the stream parser does not already skip.
tool_disable_flags is --tools "", not --disallowedTools: the latter
is a named deny list, and denying Bash merely sent the model to Glob.
Both halves of the disable are required. --tools "" alone left 44 tools
mounted — every MCP server in the user’s own config — so the flags below
are the pair, and --strict-mcp-config is load-bearing. Verified from the
system init event’s tools array, which reported [].
Enabled as of the CLI-spawn backend. The reason moved three times before
it could be: the tool probe, then serving tools over MCP, then the spawn. The
probe is answered; MUR does now serve its tools over MCP (tools/list,
tools/call, and the shim that forwards to them). What is missing is the
other half: nothing writes the per-turn --mcp-config and nothing runs
the CLI, so this row describes a backend that could work rather than one
that does.
Keep this sentence true. A row whose stated reason outlives the thing it
described is worse than a bare false — it explains itself confidently
and wrongly, and a user reading the panel has no way to tell.