plan-mode.yaml 5.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. name: plan-mode
  2. title: Plan mode
  3. repo: https://github.com/100yenadmin/hermes-plan-mode
  4. sha: ee4a245fbc2b2d874f3a5021963bef6c358d17fb
  5. description: 'Claude Code-style plan mode for Hermes: the agent explores and writes a plan, and edits nothing else until you
  6. approve it. It works on every interactive Hermes surface: /plan or /planmode on blocks mutating Hermes tools dispatched
  7. through pre_tool_call (writes outside .hermes/plans, terminal, code execution, delegation, MCP) while the agent
  8. explores, asks clarifying questions and writes a plan. The agent shows the complete plan, submits it with
  9. plan_mode(submit) and one approval card asks: approve and auto-accept edits, approve and review each file edit
  10. (when Hermes approvals are on, every write_file and patch then gets Hermes'' approval prompt with its path and a
  11. preview), or keep planning; Other sends feedback, and the revised plan says what changed since the last revision.
  12. Once approved, it implements in the same turn and tracks todo_list progress. To change the plan yourself, keep
  13. planning, run /planmode edit, save, then /planmode show and /planmode approve; the text you were shown is saved as
  14. an approved snapshot, so later edits to the file do not change the approval. The classic profile
  15. (plan_profile: classic), approval_card: false and surfaces without a card use Hermes'' own approval prompt
  16. (gateway buttons, the TUI/Desktop card, the CLI panel or /approve). When yolo or approvals.mode: off would
  17. auto-approve, it asks through clarify instead, so a person still decides. By default plans are compact and
  18. decision-complete, the lean profile asks at most three targeted questions, and the agent does not commit unless
  19. asked (plan_style, plan_profile, allow_commits and plan_skill settings). Classic CLI enforced on every supported
  20. Hermes; gateway, TUI and Desktop from Hermes v2026.9.24 (0.21.5), and refused on older builds; 0.21.6 recommended.
  21. On the interactive classic CLI, Hermes'' inline diff shows a new plan file in full, so the agent does not retype it
  22. (write_once). A report-a-problem skill drafts a bug report and files it with gh only after you approve the draft.
  23. Disclosure — plan-mode does not enforce Codex app-server exec/applyPatch or TUI /background and btw side agents.
  24. A plan is approved only on its approval card (a clarify question only the plugin issues and checks), through
  25. Hermes'' own approval prompt, or with /planmode approve. It reads nine groups of internal Hermes seams for session
  26. identity, workspace, profile, skills.inline_shell and the classic CLI''s inline diff, each guarded with a documented fallback. It creates
  27. .hermes/plans under the session working directory, reads plan files there, saves the approved text of an edited
  28. plan as a new file under .hermes/plans/approved, and keeps per-session state in plugin state. It adds a turn note
  29. while planning or executing, a ≤200-char system-prompt hint, and a one-line footer to short replies on chat
  30. platforms. When a turn ends while a submitted plan still awaits approval and no approval card was answered, it adds
  31. one line to that reply on any surface, whatever its length, saying how to approve (unless footer is off). When you
  32. pick "Always" on a plan approval or a per-edit review, Hermes core writes a
  33. plugin_rule:plan-mode entry to command_allowlist in config.yaml; each entry is keyed to one plan revision, so it
  34. cannot approve another plan. With allow_gateway_injection: true it queues one message to start work after a typed
  35. /planmode approve. On TUI, Desktop and hermes serve sessions (lean profile, plan_once) it reads the visible reply
  36. text from post_api_request while planning and saves its <proposed_plan> block as the plan file. On the interactive
  37. classic CLI (lean, write_once) it checks that Hermes printed a newly written plan file in full, then tells the agent
  38. not to retype it. Its report-a-problem skill has the agent file to the plugin repository with gh only after the user
  39. approves the exact saved draft. The plugin itself makes no network calls, launches no subprocesses and has no
  40. self-updater.'
  41. maintainer: 100yenadmin
  42. tier: community
  43. category: tools
  44. requires_hermes: '>=0.21.3'
  45. docs_url: https://github.com/100yenadmin/hermes-plan-mode#readme
  46. version: "1.0.0"
  47. image: https://raw.githubusercontent.com/100yenadmin/hermes-plan-mode/ee4a245fbc2b2d874f3a5021963bef6c358d17fb/docs/media/banner.png
  48. screenshots:
  49. - https://raw.githubusercontent.com/100yenadmin/hermes-plan-mode/ee4a245fbc2b2d874f3a5021963bef6c358d17fb/docs/media/cli-card.png
  50. - https://raw.githubusercontent.com/100yenadmin/hermes-plan-mode/ee4a245fbc2b2d874f3a5021963bef6c358d17fb/docs/media/cli-edit-review.png
  51. - https://raw.githubusercontent.com/100yenadmin/hermes-plan-mode/ee4a245fbc2b2d874f3a5021963bef6c358d17fb/docs/media/cli-card-implement.png
  52. - https://raw.githubusercontent.com/100yenadmin/hermes-plan-mode/ee4a245fbc2b2d874f3a5021963bef6c358d17fb/docs/media/cli-edit-approve.png
  53. platforms: []
  54. capabilities:
  55. provides_tools:
  56. - plan_mode
  57. provides_hooks:
  58. - pre_tool_call
  59. - post_tool_call
  60. - pre_llm_call
  61. - transform_llm_output
  62. - pre_approval_request
  63. - post_approval_response
  64. - on_session_finalize
  65. - on_session_reset
  66. - post_llm_call
  67. - transform_tool_result
  68. - post_api_request
  69. provides_middleware: []
  70. requires_env: []