See what happened, in order.
Claude Code hooks and transcript events become a local session timeline. Open a session and follow its recorded activity from start to finish.
A LOCAL FLIGHT RECORDER FOR CLAUDE CODE
Come back to the whole story.
A diff tells you what changed. Dashcam records the sequence of a Claude Code session, so you can review events, inspect available screenshots, and return to the exact moment that matters.
Runs locally. Screenshot capture needs Playwright and a reachable dev server.
RECORDED SESSION
Trace the work, step by step.
01Session startedEvent
02File changedTool event
03Screenshot savedCapture
CAPTURE / 03
LOCAL CAPTUREReview the screen
at this moment.
Open the original, or keep an exact link to this capture.at this moment.
A simplified interface illustration. Your recorded sessions appear in the local dashboard.
THE REVIEW LOOP
From unattended work
to a clear account.
Dashcam keeps the order and context of a session intact. Start with the timeline, then follow the evidence that was actually recorded.
EVENT TIMELINE
Check the screen at key moments.
When Playwright and a reachable development server are available, Dashcam can capture screenshots after configured tool events. Review the image beside its session.
Keep a link to the exact capture.
A capture URL opens the same preview after reload. If that capture is unavailable in the session, Dashcam says so instead of showing unrelated evidence.
BUILT AROUND EVIDENCE
What the recording has.
Nothing invented.
Events and decisions
Inspect recorded activity. Stith decisions require an explicit local session binding.
Portable review
Export session data as JSON or a text-only HTML report for a written handoff.
Video is deferred
The current capture flow centers on screenshots when prerequisites are met.
READY TO REVIEW
Make the next session
easier to understand.
Start with local setup, then open the dashboard when Claude Code has recorded a session.