New Adapter: Hermes

Traces now supprts the Hermes from Nous Research. Your Hermes sessions show up in Traces alongside every other agent and Traces captures the full run: prompts, reasoning, tool calls, and results.

How Traces reads Hermes

Hermes keeps its session history in a local SQLite database at ~/.hermes/state.db, and Traces reads straight from it. SQLite is the single source of truth: Hermes can optionally write JSON snapshos too, but Traces never falls back to them, so what you see always matches Hermes's canonical store.

Because Hermes writes to SQLite in WAL mode, Traces watches the database and its -wal/-shm sidecars, so a live session streams into Traces as new messages land.

What gets captured

For each session, Traces normalizes Hermes's message rows into typed events:

• Your prompts. As user messages.
• The agent's reasoning. Hermes's reasoning content is surfaced as thinking, so you see how it worked, not just what it said.
• Tool calls and their results. So terminal commands and other actions are visible in context.

Hermes also has a rewind/undo feature (a soft-delete flag on messages); Traces respects it so a shared trace reflects the live conversation.

Share and resume

• Share. Run traces setup to install the share skill, then traces share to publish a session and get a link.
• Resume. Pick up any captured session where it left off. Traces hands the session ID back to Hermes via hermes --resume <id>.

Get started

1. Update your CLI
2. Run traces setup to install the Hermes integration.
3. Run traces shareto publish a session and get a link.