先看要改什么
默认先出 remediation 计划，而不是直接落笔改配置。你先看懂，再决定要不要执行。
M78Armor Hermes Core 计划优先的整改执行产品
M78Armor Hermes Core Plan-first remediation for Hermes Agent
Core 不是“点一下全自动修好”。它先给出计划，再在你确认后执行改动，先备份，再写入，需要时可恢复。重点不是花哨，而是把 Hermes 本地整改做得更稳。
Core is not a blind one-click fixer. It builds the plan first, applies changes only after confirmation, backs up before write, and gives you a restore path. The point is controlled remediation, not theatre.
Plan · Apply · Restore
Plan · Apply · Restore
为什么要买 Core
Why buy Core
先备份，再写入
任何修改前先生成 backup 和 manifest。真正出问题时，你有回头路。
不把运行边界交给外部
本地执行、零默认联网、零后台回调。它处理的是 Hermes 控制面，而不是把你的环境交给远端服务。
See the change plan before anything writes
Core starts with a remediation plan by default instead of editing config immediately. You see the path first, then decide whether to execute.
Backup before write
Every apply run creates backups and a manifest first. When something goes wrong, you have a real rollback path instead of guesswork.
Keep the runtime boundary local
Local execution, zero default network behaviour, and no background callbacks. It hardens the Hermes control plane without outsourcing trust to a remote service.
Core 会处理什么
What Core is built to handle
Gateway 与 approval 收口： 把 allow-all、YOLO、过宽 allowlist 之类的问题收回来。
Gateway and approval cleanup: pull back allow-all exposure, YOLO posture, and other over-broad approval shortcuts.
Terminal 隔离整改： backend、mount、forward env、container limits 这些会直接影响边界的项。
Terminal isolation work: backend choice, mounts, forwarded environment variables, and container limits that change the runtime boundary.
Secret 与 MCP 整理： 该去
.env 的值放回 .env，该收口的 MCP 面尽量收口。Secret and MCP cleanup: move the right values back into
.env and narrow the MCP surface where Core can do so safely.恢复能力： Apply 后不是“祝你好运”。Core 会保留 restore 路径，让你可以撤回。
Recovery path: after apply, it is not “good luck.” Core preserves a restore path so you can reverse the changes when needed.
执行方式
Workflow
1Plan
先读取当前状态，列出问题、工作量和预计可执行的整改动作。
2Apply
你确认之后再执行改动。先备份，再写入，并输出变更结果。
3Restore
需要回退时按 manifest 恢复，不靠回忆“我上次改了哪一行”。
1Plan
Read the current state first and show the findings, estimated effort, and the changes Core can execute.
2Apply
Core changes nothing until you confirm. It backs up first, writes second, and then reports what changed.
3Restore
When you need to roll back, use the manifest-backed restore path instead of trying to remember which line you edited.
Core 卖的不是“自动化很酷”。卖的是更短、更稳、更可恢复的 Hermes 整改路径。
Core is not selling automation theatre. It is selling a shorter, safer, recoverable Hermes remediation path.
成交入口
Buy path
M78Armor Hermes Core
M78Armor Hermes Core
¥88
一次性购买 · 永久使用
One-time purchase · Yours forever
- 计划优先的 remediation runtime
- Plan-first remediation runtime
- Apply 前自动备份
- Backup before apply
- Manifest 驱动的 restore 路径
- Manifest-backed restore path
- 本地运行 · 零默认联网
- Runs locally · Zero default network behaviour
继续查看
NEXT STEP
还在比较 Lite 和 Core
Still comparing Lite and Core
如果你还在判断是否该从只读检查升级到执行路径，先看差异。
If you are still deciding whether to move from read-only audit to execution, compare the two paths first.
查看对比Compare options先确认产品边界
Review the product boundary
先看这款产品明确承诺什么，不承诺什么，再决定是否适合你的环境。
Review what this product explicitly promises and what it does not before deciding whether it fits your environment.
查看边界View boundary购买前先看常见问题
Read the common questions first
付款、恢复路径、本地运行边界和升级判断的常见问题都在这里。
Questions about payment, restore path, local runtime boundary, and upgrade decisions are handled here.
查看 FAQRead FAQ