Learns the multi-step tool routines your agent keeps repeating across conversations and, only after you review and approve each one, compiles it into a single deterministic tool that runs its steps without model round-trips in between. Proposals show the steps, data flow between them, permissions, input and output schemas, per-step side effects and a twelve-check offline validation (exact replay of recorded runs, held-out fit, injected failures and timeouts, secret scan, tool schema fingerprints). Approve, reject, disable, roll back and inspect run traces from /kata, `hermes kata` or a dashboard tab. Disclosure — records tool names, arguments and results (first 64 KB, secret-named keys and common credential formats redacted) plus model request timing and token counts to a local SQLite file under its plugin data directory, kept for 30 days by default; registers tools only after explicit approval and executes their steps through ctx.dispatch_tool; katas whose steps have external or unclassified effects escalate every call to Hermes's own approval prompt with a fresh rule key, so remembered approvals never repeat them and unattended runs follow Hermes's approval policy; side-effecting steps are never retried; makes no network, model or subprocess calls of its own.
Learns the multi-step tool routines your agent keeps repeating across conversations and, only after you review and approve each one, compiles it into a single deterministic tool that runs its steps without model round-trips in between. Proposals show the steps, data flow between them, permissions, input and output schemas, per-step side effects and a twelve-check offline validation (exact replay of recorded runs, held-out fit, injected failures and timeouts, secret scan, tool schema fingerprints). Approve, reject, disable, roll back and inspect run traces from /kata, `hermes kata` or a dashboard tab. Disclosure — records tool names, arguments and results (first 64 KB, secret-named keys and common credential formats redacted) plus model request timing and token counts to a local SQLite file under its plugin data directory, kept for 30 days by default; registers tools only after explicit approval and executes their steps through ctx.dispatch_tool; katas whose steps have external or unclassified effects escalate every call to Hermes's own approval prompt with a fresh rule key, so remembered approvals never repeat them and unattended runs follow Hermes's approval policy; side-effecting steps are never retried; makes no network, model or subprocess calls of its own.
This directory is the Hermes plugin. Install it with hermes plugins install kata.
Full documentation, safety model and screenshots: see the repository README.
README from the reviewed commit cc59b08; it updates when the author re-pins.
opeblow