菜单
Run headless Hermes agent turns over the iii bus, deliver messages to 27+ chat platforms, and react to inbound platform/webhook events — with the agent carrying the live iii runtime context.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run Unix commands and structured filesystem ops from the iii engine: exec, background jobs, and a structured fs (ls/stat/mkdir/rm/chmod/mv/grep/sed/ read/write, jailed only if fs.host_roots is configured), all forwardable into a sandbox microVM.
Shared, adapter-backed key/value store addressed by scope and key, with a reactive `state` trigger so other functions can run on every create, update, or delete without polling.
Durable topic queues for iii: subscribe functions to topics, publish work asynchronously, retry failed deliveries with backoff, and inspect/redrive dead-lettered messages.
Mint isolated git worktrees for parallel agent work, track ownership in a cross-agent registry, and land finished branches back onto a target with a queued rebase, test gate, and atomic fast-forward merge.
Connect this engine to another iii engine over a long-lived WebSocket so functions call across the boundary. Wire stable ids with `forward:`/`expose:`; `bridge.invoke` is the ad-hoc escape hatch.
Drive Devin over the iii bus. Run the local Devin CLI agent (SWE-1.6) with the iii runtime context so it discovers and operates your mesh, or start and steer autonomous Devin cloud sessions through the REST API, with a passthrough to any Devin v1/v3 endpoint.
| name | hermes |
| description | Run headless Hermes agent turns over the iii bus, deliver messages to 27+ chat platforms, and react to inbound platform/webhook events — with the agent carrying the live iii runtime context. |
The hermes worker puts the Hermes agent on the iii bus. hermes::run runs one
headless Hermes turn carrying the iii runtime context, so the agent discovers
and drives the whole engine live. hermes::send delivers to any of Hermes's
27+ messaging platforms. Inbound platform messages and webhook events arrive on
the worker's HTTP sink (hermes::inbound) and republish so any iii worker can
react. Hermes becomes iii's omnichannel front door: chat-platform reach wired to
the entire function registry.
Requires pre-provisioned Hermes credentials (~/.hermes/.env). When a turn
needs a capability beyond Hermes, add another iii worker instead of bolting it
on here.
hermes::run with
prompt and cwd — the agent discovers and calls any registered function
through the iii CLI (engine::functions::list, iii trigger <fn> --help).hermes::send with {platform, message} for
Telegram, Discord, Slack, WhatsApp, Teams, and 20+ more.inbound_api_path; deliveries land on hermes::inbound and
republish for iii workers to handle.session_id again.hermes::run / hermes::send are not agent-callable without human approval
(privilege + outbound messaging); read-only introspection is allowed (see
iii-permissions.yaml).agent::events carries whole-turn
frames (turn_end, agent_end), not per-tool frames.shell, coder, web.hermes::run — one turn, wait, return {session_id, result, is_error};
accepts prompt or messages, plus model, cwd, iii_context.hermes::send — deliver {platform, message} to a gateway platform.hermes::sessions::list — sessions this worker has run.hermes::status — session state + live flag.hermes::stop — interrupt a live run.run::start_and_wait — alias for hermes::run.hermes::inbound (HTTP) — inbound gateway delivery sink; republishes events.