Hermes Agent 的代理自有工作流程图。 你的代理编写一个包含代理节点、扇出和门的JSON图;背景 Runner 在调用者进程树之外执行该任务，并将结果反馈回去 与它启动时相同的workflow工具。Hermes Desktop 绘制实时 DAG。

四张生产图，每张图有两行注释： docs/showcase.md。

为什么会有这样的存在

一个代理回合是一条漫长而脆弱的工作线：一个情境，一个 超时，无可恢复检查点。图将作业拆分为节点，满足 显式依赖——并行侦察通道、合成连接、对抗 Review Gate——每个节点都是一个独立的子会话，拥有自己的模型、预算和 类型失败。当某物死亡或你在飞行中改变主意时，只有 受影响节点重运行：已完成的工作会从其存储的指纹重播， 没有还款。

你得到了什么

Hermes Workflows

Agent-owned workflow graphs for Hermes Agent. Your agent authors a JSON graph of agent nodes, fan-outs and gates; a background runner executes it outside the caller process tree and hands results back through the same workflow tool it launched from. Hermes Desktop draws the live DAG.

Four production diagrams, glossed two lines each: docs/showcase.md.

Why this exists

A single agent turn is one long, fragile thread of work: one context, one timeout, no resumable checkpoints. A graph splits the job into nodes with explicit dependencies — parallel recon lanes, a synthesis join, an adversarial review gate — each node a separate child session with its own model, budget, and typed failure. When something dies or you change your mind mid-flight, only the affected nodes re-run: completed work is replayed from its stored fingerprint, not re-paid.

What you get