Every flag, key and field

Flags #

Config keys #

The nine runtime knobs above also read from ./.revmux/config and ~/.config/revmux/config, under the same name as the flag, in INI format. Command line wins, then project, then user, then the default, merged per key. Every other flag is command line only.

--task and --run are not config keys: a config file naming the round to write would make the same command review different context in different directories.

Subcommands #

All print JSON on stdout and exit before any review starts. None of them ever exits 1.

Environment #

Front matter #

task.md

All four are optional and are stored and reported, never resolved. revmux runs no git command against branch or base and fetches nothing from url.

Model string #

<binary>[/<model>][:<effort>]

claude                   claude, its own default model and effort
claude/opus:high         fully specified
codex/gpt-6.1-sol          effort falls back to the profile's, then the binary's
codex:high               codex's default model at high effort
claude/                  refused: a second spelling of `claude`
claude/opus:hgih         refused: not an effort

Parses on the first / and the last :. A stage resolves through its stages: override, then the stage file's own model:, then the profile's. An entry naming a different binary than the profile brings its own model rather than inheriting one belonging to the other; effort carries across, since it belongs to neither model. Ask revmux config for what a given invocation resolves to.

Profiles #

Lenses #

reviewing a change

reading a filed item

Prompt variables #

The vocabulary is closed. A prompt file naming anything else fails at load. Every context variable expands to a path, never to the file's contents.

Prior rounds are appended to every composed prompt as a block rather than a variable, because a variable would be opt-in per file and any prompt omitting it would silently lose the history.

Colors #

A roster entry's color sets its prefix color in both the TUI and the plain renderer. In the TUI's combined pane it also colors the entry's log text. Omitted, it is filled from a palette by roster position. Accepted values are the ANSI-16 names (red, bright-blue and so on) or #RRGGBB. An unknown value is a startup error.

Report JSON #

Empty lists are emitted as arrays rather than null. The three side arrays are not filtered by --min-confidence and do not affect the exit code.

Verdicts #

Exit codes #

Task layout #

<tasks-dir>/<task>/
├── task.md              optional front matter about the task
└── <run>/               a round
    └── input/           caller-written
        ├── scope.md     required
        ├── goal.md      optional
        ├── profile.md   optional
        └── context/     optional directory

Take these paths from revmux new rather than joining them: the layout is revmux's own detail, and a caller that reimplements it breaks silently when it changes.

Run archive #

<tasks-dir>/<task>/<run>/
├── manifest.json      resolved roster, prompt provenance and hashes, requested vs actual model,
│                      timings. Created empty as the run starts and filled in when it finishes,
│                      so it doubles as the marker claiming the round
├── prompts/agents/    the composed prompt each agent received, post-substitution
├── prompts/stages/    synthesis and one file per verify group
├── prompts/input-profile.md  the project profile's bytes, when the round inherited one
├── stages/            1-found.json, 2-synthesized.json, 3-verified.json
├── events.jsonl       stalls, retries, degrades, stage transitions
├── agents/            verbatim tees: <agent>.jsonl, <agent>.log, <agent>.retry.jsonl
└── report.md, findings.json

A failed archive write fails the run. The one exception is a per-agent tee under agents/, which degrades that one source instead.

Name rules #

• No path separator, no .., not absolute, not starting with a dot.
• Containment is re-checked on the resolved path, because a symlink defeats the lexical test.
• A round may not be called task.md.
• Roster agent names carry the same rule, applied when the profile loads.
• A task name for revmux cleanup must be one task directly under the tasks root: a path, a .., a round name or a typo is an error and nothing is removed.

TUI keys #