What you get:
→ Tamper-evident audit trail (not tamper-proof - honest about that)
→ Deterministic replay without LLM calls ($0 debug cost)
→ Structural comparison between two runs
Open source: https://t.co/FXHvyhvmxT
#SpanChain#AgentAudit#TamperEvident#Elixir
Logs tell you what your AI agent claimed to do.
We wanted to know what it actually did.
So we built the SHA-256 hash chain into the core of Span Chain.
Every span -every LLM call,tool use, decision -gets cryptographically chained to the previous one.
Append-only. Verifiable.
Can your AI agent prove it didn't tamper with its own logs?
Mine can.
107 spans · 4.6h · 0 broken hashes
SHA-256 hash chain, self-hosted, append-only.
https://t.co/FXHvyhvmxT
New video: How Span Chain keeps a verifiable record of every agent action.
Hash-chained spans, instant verification, deterministic replay, and a stress test with 10k spans / 0 corrupted.
Full explainer + self-host instructions: https://t.co/t2B6z8yO5g
Most LLM agents are still black boxes.
When they make an expensive mistake, you usually get just a polite “sorry” and a useless log.
I built something better: a flight recorder for agents.
One of the most useful features: run comparison.
You can take two different runs of the same agent and instantly see exactly where and how they diverged — step by step, including duration differences.
Super useful for debugging and audits.
Anthropic just shipped Dreaming, Outcomes, and multiagent orchestration.
I've been building the same thing manually for months.
Here's what that means 🧵
Best part? It’s open-source, self-hostable, and works 100% offline with Ollama.
I’m currently stress-testing it on a live project. Will report back on the results soon.
How are you guys managing context and token efficiency lately? 🛠️
AI without context knows nothing about the project you built 6 months ago. And let's be real—neither do you.
Ever felt the pain of opening a new session and having to dump tons of context just because the agent has no clue what you did last time?
Repowise solves this differently.
Why this matters: Every new session in Claude Code starts from zero. CLAUDE.md helps, but it misses the why—the auth logic or hidden file dependencies buried in git history.
Repowise makes these layers available without burning through your token limit. 📉