docs(agenteye): add OpenClaw and Hermes session capture pages

CHANGELOG.md

@@ -22,6 +22,7 @@
 ### Docs
 - Add a Codex session capture page for AgentEye: what the collector picks up from local OpenAI Codex sessions (CLI, IDE, desktop app), how to turn it on with an `events:add` key, and where captured sessions show up. Value/contract level only, no implementation detail. (#592)
 - Note in the AgentEye overview that the dashboard and CLI are backed by a REST API callable with a scoped key, so prospects can see a programmatic API exists. Gist/contract level only — no endpoint signatures; the exhaustive HTTP API reference stays in the enterprise docs. (#593)
+- Add OpenClaw and Hermes session capture pages for AgentEye, and cross-link all three capture pages so a reader landing on any one finds the others. The collector gained both integrations in FailproofAI/agenteye#462 alongside the existing Codex capture, but that PR deferred the public half to "a separate failproofai PR" which was never opened — so befailproof.ai/agenteye has named Codex as the only capturable agent ever since, while the enterprise docs for both shipped correctly. Same value/contract level as the Codex page (#592): what the collector picks up, enabling it with an `events:add` key, where sessions surface, and the privacy caveat — no paths, env vars, or config keys, which stay enterprise-only. Hermes additionally notes that the originating channel (Slack, Telegram, CLI, scheduled run) is recorded, since telling those apart is the reason to capture it. Both registered in the `en` "SDK and CLI" nav group; `bun` could not run in the authoring sandbox, so nav↔file resolution was asserted in both directions across all 27 pages by hand — the file→nav direction being the one `mintlify validate` does not check, and the reason an unregistered page ships with green CI and no sidebar link. (#594)
 
 ## 0.0.14-beta.3 — 2026-07-20
 

docs/agenteye/codex-capture.mdx

@@ -7,6 +7,8 @@ Your engineers already run OpenAI Codex every day. Codex session capture brings
 
 A small background collector reads Codex's local session transcripts as they are written and ships them to AgentEye. One collector per machine captures every local Codex surface at once — there is no per-surface setup.
 
+The same collector captures other agents too — see [OpenClaw](/agenteye/openclaw-capture) and [Hermes](/agenteye/hermes-capture). Enable each one you run; a single collector can capture several at once.
+
 ---
 
 ## What it captures

docs/agenteye/hermes-capture.mdx

@@ -0,0 +1,49 @@
+---
+title: "Hermes session capture"
+description: "Bring your team's Hermes gateway sessions — Slack, Telegram, CLI, and scheduled runs — into AgentEye as ordinary sessions and events."
+---
+
+[Hermes](https://hermes-agent.nousresearch.com) answers your team from wherever they already work — Slack, Telegram, the CLI, scheduled runs. Hermes session capture brings all of it into AgentEye as ordinary sessions and events, so the assistant your team talks to every day is as observable as the agents you write yourself.
+
+A small background collector reads Hermes's local session store as it is written and ships sessions to AgentEye. It works the same way as [Codex](/agenteye/codex-capture) and [OpenClaw](/agenteye/openclaw-capture) capture, and one collector can capture several at once.
+
+---
+
+## What it captures
+
+Every Hermes session on the machine is captured, whichever channel it came from. Each one becomes an AgentEye [session](/agenteye/sessions); its user and assistant messages, tool calls, and tool results become the matching [events](/agenteye/event-stream).
+
+The channel a session started from — Slack, Telegram, CLI, or a scheduled run — is recorded on the session, so you can tell them apart and filter to one at a time.
+
+---
+
+## Turn it on
+
+Capture is off until you enable it. Install the collector with an API key that has the `events:add` permission (see [API keys](/agenteye/api-keys)), and turn on Hermes capture:
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/FailproofAI/agenteye-collector/main/install.sh \
+  | sh -s -- --key <YOUR_API_KEY> --hermes-enabled
+```
+
+That installs the collector, registers it as a background service, and starts capturing. Confirm it is running:
+
+```bash
+agenteye-collector health
+```
+
+Capturing more than one agent on the same machine? Add each one's flag to the same command — for example `--hermes-enabled --codex-enabled`.
+
+On first run, your existing Hermes sessions are backfilled once and new activity then streams within seconds. Hermes's own data is only ever read — never modified or deleted — and each message is shipped exactly once, even across restarts.
+
+---
+
+## Where it shows up
+
+Captured sessions appear in **Sessions**, and their events in the **Events** stream, the same as any other agent you observe — so [session replay](/agenteye/sessions), [search](/agenteye/queries), [evaluations](/agenteye/evaluations), and [alerts](/agenteye/alerts) all work on them. Filter by the Hermes agent to see them on their own.
+
+---
+
+## Privacy
+
+Hermes sessions contain the full transcript — including command output, file contents, and anything the agent read or wrote — and can contain secrets. Captured sessions are shipped as-is, so enable capture only where centralizing that content in AgentEye is appropriate, and give the collector a key scoped to `events:add` only. See [Security](/agenteye/security) for how your data is kept isolated.

docs/agenteye/openclaw-capture.mdx

@@ -0,0 +1,49 @@
+---
+title: "OpenClaw session capture"
+description: "Tail your team's local OpenClaw sessions into AgentEye as ordinary sessions and events — with no change to how OpenClaw runs."
+---
+
+If your team runs [OpenClaw](https://docs.openclaw.ai), OpenClaw session capture brings those sessions into AgentEye as ordinary sessions and events, so you can search, replay, and evaluate them next to everything else you observe. It complements the [Python SDK](/agenteye/python-sdk): the SDK instruments agents you write, while this captures the OpenClaw work your team already does — with no change to how they run it.
+
+A small background collector reads OpenClaw's local session transcripts as they are written and ships them to AgentEye. It works the same way as [Codex capture](/agenteye/codex-capture), and one collector can capture both at once.
+
+---
+
+## What it captures
+
+Every agent configured in a machine's OpenClaw setup is captured by that machine's collector — there is no per-agent setup.
+
+Each OpenClaw session becomes an AgentEye [session](/agenteye/sessions); its user and assistant messages, tool calls, and tool results become the matching [events](/agenteye/event-stream).
+
+---
+
+## Turn it on
+
+Capture is off until you enable it. Install the collector with an API key that has the `events:add` permission (see [API keys](/agenteye/api-keys)), and turn on OpenClaw capture:
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/FailproofAI/agenteye-collector/main/install.sh \
+  | sh -s -- --key <YOUR_API_KEY> --openclaw-enabled
+```
+
+That installs the collector, registers it as a background service, and starts capturing. Confirm it is running:
+
+```bash
+agenteye-collector health
+```
+
+Capturing more than one agent on the same machine? Add each one's flag to the same command — for example `--openclaw-enabled --codex-enabled`.
+
+On first run, your existing OpenClaw sessions are backfilled once and new activity then streams within seconds. OpenClaw's own files are only ever read — never modified, moved, or deleted — and each session is shipped exactly once, even across restarts.
+
+---
+
+## Where it shows up
+
+Captured sessions appear in **Sessions**, and their events in the **Events** stream, the same as any other agent you observe — so [session replay](/agenteye/sessions), [search](/agenteye/queries), [evaluations](/agenteye/evaluations), and [alerts](/agenteye/alerts) all work on them. Filter by the OpenClaw agent to see them on their own.
+
+---
+
+## Privacy
+
+OpenClaw transcripts contain the full session — including command output, file contents, and anything the agent read or wrote — and can contain secrets. Captured sessions are shipped as-is, so enable capture only on machines and for teams where centralizing that content in AgentEye is appropriate, and give the collector a key scoped to `events:add` only. See [Security](/agenteye/security) for how your data is kept isolated.

docs/docs.json

@@ -65,6 +65,8 @@
                   "agenteye/python-sdk",
                   "agenteye/python-sdk-skill",
                   "agenteye/codex-capture",
+                  "agenteye/openclaw-capture",
+                  "agenteye/hermes-capture",
                   "agenteye/cli",
                   "agenteye/cli-skill",
                   "agenteye/cli-recipes",