UNWINDING 000
A plugin for Hermes Agent

Record a Hermes session once. Then replay it with no model, no network and no tokens, and see exactly what Hermes does differently.

scroll
The problem

Every Hermes release changes how your agent thinks: the prompt, the tools, the hooks. You usually find out from a session that went wrong. Ariadne lets you find out first, offline, for free.

How it works
01 / RECORD

Keep the thread.

Turn recording on and use Hermes as usual. Every model call, tool call and turn is saved to a cassette on your machine, with secrets scrubbed. Nothing leaves your computer.

02 / REPLAY

Follow it back.

Ariadne answers every model call and tool call from the cassette, while the rest of Hermes runs for real. No model, no network, no tokens. If anything Hermes sends is different, you see the exact line.

03 / COMPARE

Two installs, one thread.

Replay one cassette on two Hermes installs side by side with compare. What differs between the machines cancels out; what Hermes changed does not.

04 / BISECT

Name the commit.

bisect replays across a Hermes checkout and names the first commit that changed your session. 358 commits, 10 replays, about a minute.

05 / FORK

Take another path.

Replay up to any turn, then hand the session to a live model from exactly that state. Tools stay frozen unless you allow them. Export the result as training data.

hermes ariadne record on
REC
IDENTICAL

A · v0.23.0

B · main

v0.23.0 → main · 358 commits
recorded turns · replayed offline original forked · live model turn 3
Before you update Hermes

Is it safe
to update?

One button. Ariadne installs the new Hermes in a private folder, replays your own sessions on both versions with your plugins loaded, offline, and answers in plain words: what changed, which tools, and whether a plugin broke. Your Hermes is never touched.

$ hermes ariadne upgrade-check
v0.23.0→v0.23.1
Safe to update
4 sessions · 114 s · 0 tokens
Plugin compatibility

Real catalog plugins,
on every Hermes.

Plugins from the Hermes catalog, at the exact commit the catalog pins, loaded into offline replays on each Hermes release and main. A cross means the plugin failed to validate, did not load, or one of its hooks crashed.

Loading the latest results…
Proof, not promises

It already found
a real Hermes bug.

0

Hermes commits searched between v0.23.0 and main

0replays

to name the commit that changed a recorded session

0tokens

spent on any replay. No model, no network, approvals denied

0rules

from Hermes's own hook docs, checked on every run

Finding 001

A truncated reply skipped post_api_request.

Hermes promises plugins that every pre_api_request ends with a post_api_request or an error. When a model reply was cut off at the token limit, it did neither. Ariadne's contract check caught it on a replay; the fix is a few lines with a test that fails before it.

Issue #150324 ↗ Fix #150333 ↗
CONTRACT REPORTreplay · length_stop
✓ pre_llm_call fires once per turn
✓ post_llm_call fires at most once per turn
✓ auxiliary calls do not fire api hooks
✗ api_pairs: pre_api_request #2 never ended
finish_reason = "length" → recover_from_truncation
post_api_request: not fired
✓ on_session_end fires once per turn
✓ subagent_start / subagent_stop pair
Hermes Desktop

Watch a replay land,
call by call.

The Ariadne page in Hermes Desktop showing a replay with an inline diff
●
One-click recording

A REC chip in the status bar. Recorded sessions get a small mark in your session list.

↺
Live replay

Each model call and tool call lights up as the replay reaches it. Differences open inline as a real diff.

⑂
Fork from any turn

Pick a turn, write a new message, and watch Hermes take the other path with your model.

For plugin authors

Your plugin,
on every Hermes.

Commit a few cassettes and add one step. Every push replays them on the Hermes you pin and on main, offline, and fails when Hermes changes what your plugin sees or breaks a hook promise.