Theme
AI Resources
Her Claude Code Session Detective
Her is a Hugging Face Space for reading Claude Code session JSONL traces and turning them into a plain-English view of what happened during a coding-agent run.
The Hugging Face blog describes Her as a small hackathon-style trace reader that reconstructs sessions, surfaces production/config/secret-related activity, shows tool and token usage, and answers questions with turn references. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.
What it is
Claude Code session trace reader
Her is built around Claude Code session files: the JSONL traces that can contain user turns, tool calls, token usage, subagent activity, skills, MCP servers, and other run details.
Why it stands out
Session story instead of raw JSON
The value is readability. The blog says Her reconstructs what happened in plain English, links findings back to turns, and lets readers ask questions about why a tool or action appeared in the trace.
Availability
Public Space and blog writeup
The project is presented through a public Hugging Face Space and a Build Small Hackathon blog post. Treat it as a first-look trace reader rather than a finished audit or governance system.
Why it matters
What makes it useful
Coding-agent traces are often too long to understand from raw JSONL alone. Its value is the readable layer: session reconstruction, tool and token usage, notable-action surfacing, and turn-linked questions, while still requiring readers to check the raw trace for decisions that matter.
What to know
Where it fits
This belongs in the agent-observability and trace-reading layer. It is more relevant to people using Claude Code or reviewing coding-agent runs than to readers looking for a general chatbot, model, or agent framework.
Notable points
What stands out
The blog says the findings engine is deterministic and that Nemotron-Mini-4B-Instruct is used for prose and softer suggestions. LifeHubber treats that as a source claim to inspect, not as an independent validation.
Before using
What to review
Whether the Claude Code trace contains private code, prompts, file paths, secrets, account details, production settings, or customer data before uploading it anywhere.
The Space and blog handling notes, including the author's description of run namespaces, deletion behavior, and model/API use.
Whether the project is mature enough for the reader's workflow, since the blog frames it as something built over a weekend for a hackathon-style context.
The actual turn references and raw trace when decisions matter, rather than relying only on generated prose.
Reader fit
Who may find it relevant
Claude Code users who want a quicker first pass over long session traces.
Teams comparing coding-agent observability, token usage, tool usage, and post-run review ideas.
Less relevant for readers who do not use Claude Code or do not have session JSONL traces to inspect.
Editorial note
Why LifeHubber lists it
Her is included as a practical example of the tooling forming around coding agents: not another agent, but a way to read what an agent already did and inspect the trace behind the story.
Source links
Source materials
Reader note
Before relying on this entry
LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.
What to explore next
Continue from one trace to broader session evidence.
Her reconstructs what happened in a Claude Code session. Continue with a local coaching view across several coding harnesses or a focused report of token use, models, sessions, and estimated cost.
More in AI Agents
Keep browsing this category
Explore more AI agent projects.
Paperclip
paperclipai/paperclip
A self-hosted server and dashboard for coordinating agent teams through companies, goals, roles, issues, heartbeats, budgets, approvals, and persistent activity records.
Ponytail
DietrichGebert/ponytail
An MIT-licensed instruction and plugin pack that steers coding agents toward understanding the task, reusing existing code and native features, and writing the smallest solution needed, with rules that tell agents not to simplify away validation, security, data-loss handling, or accessibility.
Gemma 4 Browser Extension
nico-martin/gemma4-browser-extension
An independent Chrome extension experiment for running an on-device browser agent with Transformers.js, WebGPU, Gemma 4, page RAG, tab tools, and semantic history search.
For project maintainers
Listed here? You can use the badge.
If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.
