Auto and Approve
Choose who decides the scope before the agent starts.
Auto
replume init
Replume forms the contract from the first prompt, tells the agent about problems during work, runs tests at Stop, and writes a report. Use it when you want the agent to continue without a scope approval step.
Approve
replume init --approve
You draft and review the contract before work, then confirm it. Use it when you want to approve exactly which paths the agent may edit and which checks must pass.
The Approve path
After replume init --approve, ask for a draft, inspect .replume/contract.yaml (especially allow), and confirm it before the agent works. After the change, commit it, verify it, and accept only a PASS.
$ replume draft --task 'Fix src/add.js so the add test passes'
final allow: src/add.js, test/**
This draft is NOT policy yet: the hooks ignore that draft until you confirm it. Review the file, then run `replume confirm`.
$ replume confirm
✓ confirmed .replume/contract.yaml (task-2026-10-22-001, status: confirmed)
$ replume verify --isolation worktree
Verdict: PASS — the checks that ran passed
$ replume accept --isolation worktree
✓ accepted df02ae4 for task task-2026-10-22-001 after a fresh PASSThis output is from a temporary Git repo with a declared add scenario and a changed source commit. Task IDs and commit hashes vary. The worktree run also printed not a security sandbox; trusted repositories only. Without a scenario, a PASS needs the test command to pass and hooks to record the changed files.
Switch modes
Run either init command again in the repository root. It writes mode: auto or mode: approve in .replume/config; other config keys remain. New tasks use the current mode.
$ replume init --approveIn Approve mode, the 0.2.0 CLI prints the draft/confirm path. In Auto mode, start the agent with your task. Neither mode guarantees that every tool action was captured if hooks are disabled or unsupported.