Zum Inhalt springen

← All commands

chimera solve-batch

Solve 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.

Arguments

  • TASKSstrrequired

    Tasks to solve in parallel, each isolated.

Options

  • --workspace, -wstrdefault: '.'

    Workspace root (a git repo, to isolate).

  • --model, -mstr

    Override the model slug.

  • --max-stepsintdefault: 6

    Max tool-calling steps per task.

  • --context-budgetfloat

    Fraction of the model's window to spend on the prompt before compacting (e.g. 0.6).

  • --max-attemptsintdefault: 2

    Max verify-or-revert attempts per task.

  • --max-workersintdefault: 4

    Max concurrent isolated workers.

  • --fuseboolean

    Route deep-reasoning turns through fusion.

  • --taintboolean

    Arm each worker's adaptive allowlist (dangerous-when-tainted tools require approval). The cross-agent collusion monitor runs regardless — it's always on for fan-out.