Open Source · Verify in your browser · Offline

Don't trust the audit trail.
Verify it yourself.

Capsule Explorer re-verifies any agent's session right in your browser: every SHA3-256 hash recomputed, every Ed25519 signature checked, every link confirmed. No backend, no account, nothing to trust but the math.

capsule-explorer·localhost:4840
128 capsules · all valid
Chains
CLAUDE-CODE128
sess_a1b2c3
CURSOR64
sess_9f0e1d
CODEX47
sess_4c5b6a
CLINE31
sess_7d8e9f
Timeline
#0AGENTSession start
#1TOOLread_file(src/app.ts)
#2TOOLedit_file(src/app.ts)
#3AGENTReasoning: apply patch
#4TOOLrun(npm test)
Capsule #2
Trigger
Context
Reasoning
Authority
Execution
Outcome
hash + sig + link OK
4
Agents Side by Side
0
Backends
3
Client-Side Checks
100%
Offline
Live Verification

Verify the chain.
Then break it on purpose.

Run all three checks on every capsule, then flip a single byte and watch verification fail at the exact record. This runs in your browser, the same way the real Explorer does.

verify.ts
5 capsules
#0AGENTSession start
sha3-256
ed25519
prev-link
#1TOOLread_file(config.yml)
sha3-256
ed25519
prev-link
#2TOOLedit_file(config.yml)
sha3-256
ed25519
prev-link
#3AGENTReasoning: ship change
sha3-256
ed25519
prev-link
#4TOOLrun(deploy.sh)
sha3-256
ed25519
prev-link

This demo animates the result. The real Explorer recomputes the actual bytes with audited libraries, no shortcuts.

Three Checks, Client-Side

Three things have to be true.
Your browser proves all three.

Verification is not a vibe. It is three concrete checks, run with audited, MIT-licensed libraries, entirely on your machine.

Hash

@noble/hashes

Recompute SHA3-256 over the capsule's canonical bytes and confirm it matches the stored hash. Flip one byte and the hash changes completely.

sha3_256(canonical) == stored_hash

Signature

@noble/ed25519

Ed25519 verify the signature over the hash hex string against the chain's published public key. No key, no valid signature.

ed25519.verify(sig, hash_hex, pubkey)

Link

pure check

Confirm each capsule's previous_hash equals the prior capsule's hash and that sequence numbers are consecutive. Insert or remove one and the chain breaks.

prev_hash == prior.hash && seq+1

Both libraries (@noble/hashes and @noble/ed25519) are independently audited, dependency-light, and MIT licensed. The whole verifier ships as static files.

Tool-Agnostic

A capsule is a capsule,
whatever produced it.

Claude Code, Cursor, Codex, and Cline all write the same hashchain format. Capsule Explorer shows every session side by side, each chain tagged with the tool that wrote it.

CLAUDE-CODE
CURSOR
CODEX
CLINE
chains
CLAUDE-CODEsess_a1b2c3
128
CURSORsess_9f0e1d
64
CODEXsess_4c5b6a
47
CLINEsess_7d8e9f
31
read from ~/.agent-capsule/chains/<tool>/*.db
Run It Locally

Three commands. Fully air-gapped.

Clone it, build the static export, and open it at localhost:4840. It reads the chains agent-capsule already wrote to your home directory.

then open http://localhost:4840

No network

Verification runs in the browser. Unplug the cable and it still works, byte for byte.

No backend

No server, no API, no account. The Explorer is static files plus your local chain databases.

Portable proof

Hand someone your chain JSON plus the public key and they can verify it with nothing but a browser.

The Explorer reads ~/.agent-capsule/chains/<tool>/*.db, the per-tool SQLite chains written by agent-capsule. Nothing else leaves your machine.

Open Source on GitHub

Read Every Line.

The verifier is open source under Apache 2.0. Clone it, audit the crypto, and host it yourself.

quantumpipes / capsule-explorer
TypeScript + Astro Apache-2.0 Offline verifier
Clone
$ git clone https://github.com/quantumpipes/capsule-explorer

Then npm install && npm run export && npm run dev to verify your own chains at localhost:4840.

quantumpipes / agent-capsule
The tool that writes the chains this explorer verifies.

Don't take our word for it.
Run the math yourself.

Capsule Explorer is open source. Clone it, read every line, and verify any agent's session in your browser with nothing to trust but the cryptography.

Offline No Account Apache 2.0