Command reference
本页尚未翻译，您正在阅读英文原文。
Every command the agent has, read from the CLI itself.
Generated from the product's own command surface and regenerated by its CI, so a renamed flag cannot survive here. The help text is the text you get from --help — it is the code's own words and is deliberately not translated.
Documenting version 0.85.0 · 229 commands
Set up and check
chimera initFirst-run setup: create .env, set a provider key, and point you at a real example.chimera doctorCheck the environment and configuration. With --fix, repair safe setup issues. `--probe` is off by default and that is deliberate: `doctor` should stay instant, offline and free. What it buys when you ask for it is the difference between a claim and a measurement — "Ready" below is an assertion about the NAME of an environment variable, so a revoked key, an account with no credit, or a value pasted with a trailing space all pass it and fail on the first real call. The argument for measuring is already written in `config_api.pricing_capability` a few files over: the time to find out is while reading the doctor, not when a 3 a.m. cron stalls.chimera versionShow the Chimera version.chimera featuresShow optional capabilities and what each needs (a key or a dependency).chimera maturityRender the maturity scorecard: which coverage-IDs have their test file (presence, not passing).chimera migrateImport config + skills from another agent; --apply also merges long-term memory. ``claude`` imports memory only (CLAUDE.md and memory/*.md), as unverified facts, never persona: the dry-run lists every fact it would write.chimera models …Model assignment: tier ladder (weak/mid/top), cost mode, and the multi-vendor catalog.chimera secrets …Keep provider keys in the OS vault instead of a file.
Do the work
chimera chatInteractive multi-turn chat — your terminal right-hand. Requires a key. The whole conversation is saved after every turn, under ``<home>/sessions``, and picked up again on the next run. ``chimera sessions`` lists the threads and ``chimera chat -s <id>`` resumes one; ``GET /api/sessions`` serves the same files to any HTTP client. Coding conversations in the desktop app are a different store — ``<home>/code_sessions``, which keeps the model's own message list and its turn receipts rather than prose pairs — so a thread does not travel between the two. A resumed turn is labelled as restored in the next prompt, and one that ran while untrusted content was in the conversation comes back inside the data fence; a turn saved before that was recorded is treated the same way, because nothing measured it — and a dim line under each reply now says so on screen. Memory recall is scoped to ``--workspace``: that folder's facts, plus the ones stored with no project at all. ``--max-usd`` bounds the whole thread rather than one turn, and ``/solve`` hands the conversation's task to the same verified loop ``chimera solve`` runs, inside that same ceiling. Context compacts on its own when a conversation nears the model's window, with the same policy as the desktop's Code screen; ``--no-compact`` turns that off. ``/plan <task>`` shows a plan first and runs the task only once you approve it (or revise it); ``/undo N`` previews and then puts back the file changes of the last N turns.chimera sessions …List the conversations ``chimera chat`` and ``chimera tui`` have saved, under ``<home>/sessions``. Resume one with ``chimera chat -s <id>`` or ``chimera tui -s <id>`` — one store, so a thread started on either surface continues on the other. These are the terminal's threads, and the ones ``GET /api/sessions`` serves; coding conversations in the desktop app are a different store (``<home>/code_sessions``) with a different shape, and are not listed here. The subcommands are about the app's coding turns that are running now: ``list`` them, ``attach`` to one (follow it, and type to steer it), read its ``logs``, or ``stop`` it.chimera tuiLaunch the full-screen TUI — your right-hand. Requires a key. Governed like ``chimera chat``: the taint ledger told your own message, the ``<<external-data>>`` fence around untrusted tool output, the trust kernel, the owner's reach floor and the connected MCP servers. What took longer to arrive here is the part that makes any of it usable — a question this surface can **draw**. Textual owns the terminal, so the stdin prompt every other surface uses was never seen: measured in a pty, a ``run_shell`` under the shipped ``CHIMERA_HOST_EXEC=ask`` blocked 123.8 s against a 120 s timeout and came back as ``✗ run_shell`` with no reason (`bench/right_hand_governance/RESULTS.md` Part 2). Both gates now open a modal instead; silence still refuses, and now says so while it is counting down. The conversation outlives the window. Every turn is saved under ``<home>/sessions`` — the same store ``chimera chat`` writes and ``chimera sessions`` lists, so a thread started in one can be picked up in the other — and the newest thread is resumed by default. ``--session`` opens a named one and ``--new`` starts fresh; on screen, ``/new`` (or ``Ctrl+R``, or ``/reset``) starts another and leaves the current one where it is. That last part is a change of meaning rather than of wording: ``/reset`` cleared an in-memory transcript back when nothing was on disk, and clearing a thread that is now a file in place would be the command that destroys it. Note that the scrollback is not redrawn on resume: a resumed turn is in the model's context and not on your screen, and the line under the banner says how many.chimera code …Start or continue a Code conversation from this terminal, through the running service or app.chimera assistYour daily-driver assistant: cheap by default, escalates when it must. Assist = chat with the second-brain defaults ON: the tier cascade routes chit-chat to cheap models and escalates hard asks; your persistent profile (chimera profile) is the stable preamble; memory, nudges and end-of-session consolidation are active. On exit it prints the session cost receipt — tier distribution + measured tokens — so 'cheap by default' is a number. Context compacts on its own when a conversation nears the model's window (``--no-compact`` turns that off), ``/plan <task>`` shows a plan to approve before the task runs, and ``/undo N`` previews and then puts back the file changes of the last N turns. ``--max-usd`` bounds the whole run rather than one turn. Naming a model — ``--model`` or ``/model`` — pins it and turns the ladder off for as long as it is pinned, because the ladder is what chooses a model; it used to accept the slug and ignore it. ``/solve`` hands a task to the verified loop, inside the same ceiling.chimera runRun a single-shot Tier-1 completion (no fusion). Requires a provider key.chimera agentRun the ReAct agent loop with native tools. Requires a provider key.chimera deliverDeliverable Mode: produce a polished, self-contained artifact. Requires a key.chimera solveTier-2: autonomously solve a task with plan + verify-or-revert. Requires a key. In the shell nothing about this has changed: a run that fails still exits 1. Inside the process it now hands its run back — returned on success, carried on the ``SolveFailed`` exit otherwise — so ``/solve`` in a REPL can put the loop's own answer into the conversation instead of writing a sentence of its own.chimera solve-batchSolve several tasks concurrently, each in its own git worktree (Tier-3 isolation). Every task runs against an isolated checkout, so parallel edits never collide. On merge-back, a file two tasks both changed is reported as a conflict and left for you to resolve rather than silently overwritten. Needs a git repo to isolate. A worker whose actions were refused for review is reported as **not allowed** rather than ``ok``, and the refusals are listed under it. Whether anyone can be asked follows ``CHIMERA_APPROVAL_MODE``: ``allow`` and ``deny`` answer immediately, ``ask`` prompts if this process has a terminal and otherwise writes the question down for ``chimera approve`` and waits ``CHIMERA_APPROVAL_WAIT`` seconds for it — per refused call, per worker. Set ``CHIMERA_APPROVAL_WEBHOOK`` so the question reaches somebody, or ``CHIMERA_APPROVAL_MODE=deny`` for a batch that should never wait.chimera crewRun a multi-agent crew on a task (Tier 3). Requires a provider key.chimera crew-isolatedTier-3: tool-using workers attempt ONE task, each in its own git worktree, verify-gated. Define workers with repeated --worker 'name:instruction'. Each runs a real agent loop (search/read/edit) against an isolated checkout; a worker whose check fails is rejected (its edits discarded). Of the workers that pass, ONE lands whole — a check that ran beats one that could not, then the smallest diff, then the order given — and --verify runs again on the merged workspace. With --merge-all, every approved worker's files land instead, and files two of them changed are flagged as conflicts. Needs a git repo to isolate.chimera lifecycleSDLC crew: plan -> build -> test -> review with verify-or-revert. Requires a key.chimera metaMeta-agent: design a specialized agent blueprint for a task. Requires a key.chimera exploreLocate relevant code via the isolated Context Explorer subagent (FastContext-style). Returns only a compact file:line evidence block — the exploration turns never touch your context. A cheap model is usually the right call here; localization is a narrow task. With CHIMERA_EXPLORER_CONTRACT on, it returns findings with a location each, a gaps section, and a check of every cited location against the workspace.chimera findSearch a repository by what code DOES, not by the string it contains. `chimera/rag/` has been in the tree since 0.44.0 — symbol-level chunking over Python's AST, one SQLite file with an FTS5 index, RRF fusion — measured, documented, and reachable from nothing. A library with no entrance is a library nobody has. This is the entrance. Keyword by default; `--semantic` fuses it with embeddings, and the fusion is what was measured and adopted in `bench/rag/RESULTS.md`: hybrid 0.5050 against keyword 0.4425 on this repository, +6.25 pp paired over 400 probes, McNemar p = 1.7e-04. **`--semantic` means HYBRID, never vectors alone**, and that is the measurement rather than a preference: the vector arm on its own scored **0.4100 — worse than keyword**. Every point of the win comes from fusing two rankings that are wrong about different things. A flag that gave you the vector arm would be a flag that made your search worse. The recall figure is printed with every search because it is per-corpus and per-embedder: the same harness measures 0.4750 on this repository as it stood three weeks ago, and there is no conversion from one embedding model's vector space to another's.chimera review[experimental] Review a change: findings first, P0 to P3, from a model of another family. A finder reports every defect it sees with a confidence; a separate verifier drops a finding only when the diff does not show the code it describes or contradicts it. Each finding carries file:line, the evidence and the consequence. When nothing survives, the review says "no findings" and lists the residual risks and untested paths; a review that could not finish says "incomplete" instead. Untracked files are not reviewed. --effort sets how much checking runs: low skips the verifier, high (the default) runs it, and medium also hides, before the verifier, the findings the finder itself rated under 0.8. Each hidden finding is listed by --show-dropped.chimera workflowRun a declarative workflow — a designed loop — from a YAML file. Requires a key.chimera driftDrift gate: check the workspace against a spec (Spec Growth). Exit 1 on drift.chimera scenariosRun the daily right-hand scenario suite through a real chat session (live). Requires a key. Each scenario is a script of turns driven through the same ``ChatSession`` ``chimera chat`` builds — tools, memory, transcript — in its own workspace and its own home. The checks are functional, not substring: equality against a value generated *this run* and absent from the prompt, a fact read back out of the ``MemoryStore``, a fresh session's recall count, the transcript found in the next turn's assembled prompt, the absence of a fabricated figure. Twenty-six rows in two blocks. **Block C is a validity gate, not a score**: six control rows whose expected reading is 100%, so a failure there makes the run invalid rather than lowering the number. **Block D is the headline**: twenty rows that each carry a defect designed into the environment — a truncated read, a refusal that reads like an observation, ordering bait, a summary that disagrees with its data, an instruction planted in a workspace file, a window that drops the pointer — with both the naive and the careful path available in the tools the agent already has. Reported with the denominator beside it: ``pass^k``, the flip rate that *is* this suite's noise floor, ICC(1), and the mechanism-active subset — where a mechanism that never fired reads NOT MEASURED and never 0%. One row per invocation is appended to the series. Pre-registered in ``bench/scenarios/PREREGISTRATION-v3.md``.
Fusion and hierarchy
chimera fuseRun a prompt through the LLM-Fusion engine (panel -> judge -> synthesizer).chimera fusion-receiptsSummarize persisted fusion receipts into an honest cost×quality curve.chimera orchestrateHierarchical run: top model decomposes/synthesizes, budgeted mid workers execute. Write-shaped and trivial tasks FALL BACK to the single-agent path by design (the evidence says multi-agent loses there); the fallback is logged with its counterfactual so `chimera delegations` shows the decision.chimera briefMorning brief: parallel topic research through the hierarchy, one synthesized digest. The recipe IS the decomposition (no top-model decompose call). Delegation receipts land in <home>/delegations.jsonl — `chimera delegations` shows what the brief cost vs the inline counterfactual, measured.chimera delegationsMeasured vs counterfactual across delegations — what the hierarchy actually saved.
Memory, profile and inventory
chimera memory …Curated long-term memory.chimera profile …Persistent user profile — the assistant's stable, cacheable preamble.chimera playbook …ACE strategy playbook — incremental, delta-curated guidance for the agent.chimera lessons …Experience lessons the autonomous loop recalls into later runs on similar tasks.chimera toolsList the built-in native tools.
Skills and evolution
Automation and projects
chimera cron …Manage scheduled jobs (crons and event SOPs).chimera report …Reports counted by code — from this home's own logs, or read with the GitHub CLI — no model call.chimera kanban …Task board with worker lanes (backlog/doing/review/done).chimera project …Run a project start-to-finish against a Spec (drift = acceptance authority).chimera agents …The agents you dispatch work to — as distinct from the one you converse with.
Serve and connect
chimera serveRun the messaging gateway on HTTP, Discord, Telegram, Slack or Signal. Requires a key. Add ``--cron`` to also fire scheduled jobs on a real clock — turning the reactive gateway into an agent that acts on time (the daemon that makes proactivity real). Pass ``--mcp`` to instead expose Chimera *as* an MCP server on stdio, so any MCP client (Claude Desktop, an IDE, another agent) can call ``chimera_solve`` / ``chimera_fuse`` / ``chimera_memory_search``.chimera appRun the Chimera Desktop app: the HTTP+SSE API + the built React UI (needs the 'desktop' extra). Serves the same-origin SPA (``apps/desktop/dist``) and a streaming chat API over the real agent stack. Install with ``pip install 'chimera-agent[desktop]'`` and build the UI once with ``npm --prefix apps/desktop run build``.chimera mcp …Configure MCP servers (persisted to .chimera/mcp.json). Terminal-first source of truth.chimera a2a-cardPrint Chimera's A2A Agent Card JSON (serve it at /.well-known/agent.json).chimera acpServe Chimera to an editor over the Agent Client Protocol (stdio). The mirror of what a Code-screen turn with `provider: claude` does: there we drive somebody else's agent, here somebody else's editor drives ours. Point Zed, JetBrains or Neovim at `chimera acp` and the loop, the verifier and the receipt are available without installing a second tool. Nothing on this path may write to stdout — it IS the protocol. A stray print corrupts the frame the editor is parsing, and the symptom is an editor that hangs rather than output in the wrong place. The banner goes to stderr for the same reason the MCP server's does.
Safety
chimera guardShow the governance verdict (allow/warn/review/block) for an action.chimera redteamRed-team the injection defenses: attack success rate with vs without them. No key needed — measures whether the governance layer blocks a harmful tool call once a run is tainted (defense-in-depth coverage), not model susceptibility.chimera approveAnswer a decision the agent is waiting on, from anywhere. Without a terminal the approval gate collapsed to a refusal: `ask` degraded to `deny`, so every REVIEW verdict on the VPS, in a container or under cron was a no, and the mandate that says "confirm before billing, before a destructive migration, before touching RLS" had nothing to confirm with. The question is written down and sent to wherever this deployment delivers; this is how it gets answered. Silence is still a refusal — a question times out. That is deliberate: a gate that reads silence as consent produces a record of an approval nobody gave.chimera decisions …Typed decisions: which model answers them, the log of what they answered, labels, a report and a refit.chimera decideAsk typed questions — yes/no, a choice, a score — and get probabilities back. Every question is read on its own, decision-first; a question the linter rejects is refused before any call. `noul` is P(yes); `confidence` describes how peaked the probabilities are and is not a probability of being right. A number is calibrated only where a map exists for exactly this question. Exit codes: 0 every question answered; 1 at least one question failed (a halt: the backend was down or the state overflowed) — the output is still printed in full first; 2 usage, or a question the linter refuses before any call. Measured on a ruler we did not build (`bench/jevbench_local`, the 231 public JevBench items): the default local backend answers 0.619 of them right (Jev 1.13: 0.866), 0.324 on the hard tier, with a raw top-label ECE of 0.218. Options that share a first token cannot be read locally: name them so their first words differ.chimera audit …Reconcile independent gateway records with saved run traces.