100yenadmin / hermes-plan-mode

# Hermes Plan Mode
Claude Code / Codex-style plan mode for Hermes, on every interactive Hermes surface (CLI, TUI, Desktop and the
messaging platforms), with no core changes. The agent explores with
read-only tools, asks clarifying questions, writes a plan file and shows it to you. You approve it on one card:
approve and auto-accept edits, approve and review each file edit, or keep planning (Other sends feedback). The classic
profile and surfaces without a card use Hermes' own approval prompt. Then the agent implements it in the same turn and
tracks progress. Until you approve, the plugin blocks mutating tools dispatched through Hermes' `pre_tool_call`
hook, except writes to the plan file.
`/plan` in core Hermes is a prompt only. This plugin turns it into an enforced mode.
## Quick start
1. Install it (see Install), then start a new Hermes session.
2. Ask for a change with `/plan`, for example `/plan add a --dry-run flag to the import command`.
3. The agent reads the code, may ask you a question or two, and shows you its plan. Until you approve, plan mode blocks
 changes made through Hermes' tool hook, apart from the plan file. Known limitations lists what
 that hook does not cover.
4. Approve the plan, or say what to change; the agent revises it and asks again. Most surfaces show a card with
 "Approve, auto-accept edits", "Approve, review each file edit" (when Hermes approvals are on) and Other for
 feedback. What you see on each channel lists the other forms.
5. After approval the agent implements the plan in the same turn and tracks its progress.
`/planmode status` shows where you are; `/planmode off` leaves plan mode without approving anything.
## How it works
1. Start planning with `/plan ` or `/planmode on [task]`. The agent can also enter on its own with the
 `plan_mode` tool.
2. The agent explores with read-only tools. For a choice only you can make, it asks with `clarify` before it writes
 the plan. With the default `lean` profile it prefers one question and asks at most three, each with 2–3 choices,
 recommended first.
3. It writes the plan as Markdown under ` /.hermes/plans`.
4. It shows the complete plan in its reply, then calls `plan_mode(action="submit")`.
5. With the default `lean` profile, plan mode asks one `clarify` card for plan revision N: "Approve, auto-accept
 edits" (recommended), "Approve, review each file edit" (only when Hermes approvals are on) or "Keep planning".
 `/planmode show` prints the plan (up to 64 KB, then a truncation notice). The classic profile, a custom `levers` list without `approval_card`, and
 ACP, API server, cron and webhooks keep Hermes' own approval prompt: buttons, a card, the CLI panel or `/approve`.
 If a turn ends while the plan still awaits approval and no card was answered, the reply ends with a line saying how to approve
 (unless `footer` is off).
6. Approve: plan mode turns off and the agent implements the plan in the same turn. It mirrors the steps into
 `todo_list` (with the default `lean`