LIFEHUBBER
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 useful angle 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

Why coding-agent users may care

Coding agents can leave long traces that are hard to read after the fact. A tool that turns those traces into a report can help readers understand where time, tools, context, and notable actions showed up in a run.

Reporting note

How the blog frames the engine

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 readers may want 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 it is included here

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

Official 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.

Sponsored

Sponsored

Related in LifeHubber

Keep the thread going

Follow the next layer with AI Resources for AI projects worth inspecting at the source, AI Guides for decision habits for messy AI choices, AI Access for free and low-cost ways to compare AI model access, AI Ballot for a clearer view of what readers are leaning toward, and AI Radar for AI stories that deserve a second look.