# AI use cases for Hermes Plan Mode (100yenadmin/hermes-plan-mode) Repo: [100yenadmin/hermes-plan-mode](https://github.com/100yenadmin/hermes-plan-mode) | Use cases: 4 | Page: https://dedupedai.com/use-cases/100yenadmin-hermes-plan-mode/ A plugin for Hermes Agent that enforces a Claude Code-style plan mode: the agent explores read-only, writes a plan file, and makes changes only after you approve the plan. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Get a reviewed plan before the agent edits code: https://dedupedai.com/use-cases/100yenadmin-hermes-plan-mode/plan-before-code-change/ - Approve each file write before it applies: https://dedupedai.com/use-cases/100yenadmin-hermes-plan-mode/approve-each-file-edit/ - Edit the plan file yourself, then approve the exact text: https://dedupedai.com/use-cases/100yenadmin-hermes-plan-mode/edit-plan-file-before-approval/ - Approve or revise a plan from a messaging app: https://dedupedai.com/use-cases/100yenadmin-hermes-plan-mode/approve-plan-from-chat/ ## How to get a reviewed plan before the agent edits code with Hermes Plan Mode Repo: [100yenadmin/hermes-plan-mode](https://github.com/100yenadmin/hermes-plan-mode) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Use /plan so the agent reads the code, asks questions, and waits for your approval before changing anything. **Who it is for:** A developer who wants a change made in a repo but does not want the agent editing files before the approach is agreed. **The problem:** Core Hermes /plan is only a prompt, so the agent can still start changing files without a checkpoint. **The outcome:** The agent shows a written plan, you approve or revise it, and only then does it implement the change in the same turn with progress tracked in todo_list. ### Steps 1. Install the plugin with `hermes plugins install 100yenadmin/hermes-plan-mode --ref --enable`, replacing with the 40-character SHA from the latest release notes. (inferred, check the README) 2. Start a new Hermes session. 3. Ask for the change with `/plan add a --dry-run flag to the import command`, using your own request. 4. Answer any clarifying question the agent asks, then read the plan it shows. 5. Choose "Approve, auto-accept edits" to let the agent implement the plan, or "Keep planning" to request changes. ### Prompt to paste into your agent ```text In the Hermes session for the project, run /plan with the request: . Stay in planning until I approve, then implement the plan and report the files changed. Verify that no file was modified before approval. ``` ### Caveat Plan mode blocks only mutating tools dispatched through Hermes' pre_tool_call hook, so the README's known limitations still apply. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/100yenadmin-hermes-plan-mode/plan-before-code-change/ ## How to approve each file write before it applies with Hermes Plan Mode Repo: [100yenadmin/hermes-plan-mode](https://github.com/100yenadmin/hermes-plan-mode) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Choose "Approve, review each file edit" so every write or patch shows its path and preview first. **Who it is for:** A developer making a risky change in a shared codebase who wants to inspect every file write. **The problem:** Approving a whole plan at once means file writes happen without a look at each one. **The outcome:** Each write_file or patch shows its path and a preview, and you decide whether it is applied. ### Steps 1. Start planning with `/planmode on ` or `/plan `. (inferred, check the README) 2. Read the plan the agent submits. 3. Choose "Approve, review each file edit". This option appears only when Hermes approvals are on. 4. When each file write appears, check its path and preview, then approve or deny it. ### Prompt to paste into your agent ```text In the Hermes session for , start plan mode with /planmode on . After I approve with review each file edit, confirm that every write_file and patch triggers an approval prompt before it applies, and list the file paths that were applied. ``` ### Caveat The per-edit review option is offered only when Hermes approvals are on, and the classic profile uses Hermes' own approval prompt instead. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/100yenadmin-hermes-plan-mode/approve-each-file-edit/ ## How to edit the plan file yourself, then approve the exact text with Hermes Plan Mode Repo: [100yenadmin/hermes-plan-mode](https://github.com/100yenadmin/hermes-plan-mode) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Change the saved plan in your editor on a local surface, show it, and approve that exact revision. **Who it is for:** A developer who wants to adjust a plan's steps by hand before the agent implements it. **The problem:** Asking the agent to revise every detail takes several rounds, and an unchecked edit could be approved by mistake. **The outcome:** Your edited plan is shown in full and approved as a new revision, and implementation uses the reviewed text. ### Steps 1. Choose "Keep planning" on the approval card, or finish or dismiss any open approval first. 2. Run `/planmode edit` to get the absolute path of the plan file. 3. Edit and save the file in your editor. 4. Run `/planmode show` and read the complete text. 5. Run `/planmode approve` to approve the reviewed revision. ### Prompt to paste into your agent ```text In the Hermes CLI session, run /planmode edit, change the plan file as I describe: , then run /planmode show and report the first and last lines. Run /planmode approve only after I confirm the displayed text. ``` ### Caveat Editing a plan with exact approval works on local surfaces only, and files above 64 KiB do not arm approval. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/100yenadmin-hermes-plan-mode/edit-plan-file-before-approval/ ## How to approve or revise a plan from a messaging app with Hermes Plan Mode Repo: [100yenadmin/hermes-plan-mode](https://github.com/100yenadmin/hermes-plan-mode) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Answer the plan approval card with native buttons in Telegram, Slack or Discord from your phone. **Who it is for:** A developer who runs Hermes through the messaging gateway and wants to approve a plan away from the terminal. **The problem:** Plans that wait for approval stall until someone is back at the CLI. **The outcome:** The plan appears in chat with native buttons, and approving it starts implementation in the next turn. ### Steps 1. Run `hermes gateway restart` on the host that runs the messaging gateway. 2. Send `/plan ` from the chat platform. (inferred, check the README) 3. Read the plan and its approval card, then tap the approve or keep planning button. 4. If you approve by typing `/planmode approve`, send any message if the reply asks for one to start the work. ### Prompt to paste into your agent ```text Through the Hermes gateway on Telegram, send /plan with a short description of . Confirm that an approval card with buttons appears, and report the plan title and the number of steps. ``` ### Caveat On the messaging gateway plugin commands run only between turns, and Telegram was the only chat platform where the README reports clicking the buttons. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/100yenadmin-hermes-plan-mode/approve-plan-from-chat/