Module cli_backend 

CLI-spawn backend registry.

One row per coding CLI MUR can drive. The registry is data, not code paths: Gemini CLI was replaced by Antigravity inside a year, and the design records that hardcoding per-CLI flags guarantees rewriting this on the next replacement.

A row exists only when every field is known. agy’s home env var and the codex / agy streaming envelopes are still open questions in docs/superpowers/specs/2026-09-16-cli-spawn-backends-design.md, so those rows are absent rather than half-filled — an unknown field here would be read as fact by every consumer.

Nothing in this module spawns a process or reads the user’s CLI config.

Structs

BackendAvailability

A backend whose binary was found, plus whether MUR may drive it.

CliBackend

One CLI-spawn backend, as data.

Enums

Activation

Whether MUR may actually drive this backend.

McpMount

How a backend’s MCP configuration reaches the CLI.

Constants

AGY

agy, measured at 1.2.3 by running it (#1339, #1340).

CLAUDE

claude, measured at 2.1.273 by running it, not only by reading --help.

CODEX

codex, measured at 0.154.0 by running it (#1339).

ISOLATION_FLAGS

The flags that make a spawned CLI see MUR’s tools and nothing else.

PROVIDER_PREFIX

Marks a model registry provider as naming the CLI-spawn track.

REGISTRY

Every backend whose record is complete. Absence is a statement: a CLI missing here has an unanswered probe, not a missing implementation.

Functions

available

Which backends the user actually has, given a binary resolver.

backend

Look up a backend by key.

ensure_home

Create this backend’s private home if absent and return the environment variable that points the CLI at it.

from_provider

The backend a registry provider names, if it names one.

home_dir

<mur_home>/cli-homes/<key>/ — this backend’s private CLI home.

mcp_config_json

The --mcp-config document for one turn.