Skip to content
Search

Mindwalk

lastmod 2026-07-20created 2026-07-201 edits

A visualization tool that replays coding agent sessions on a 3D map of the codebase

About

  • Session logs record what the agent did, but not how it understood the task (which areas it judged relevant, where it searched, whether it stayed within the task scope), and reading the raw JSONL does not reveal this
  • Draws the repository as a night map where the places the agent searched/read/edited light up and the rest stays dark, so the agent's understanding of the task can be seen at a glance
  • A single Go binary reads Claude Code and Codex session logs, and the viewing process runs entirely locally
  • Tree/Terrain views render the repository as a radial tree or a flat treemap; the more deeply and often a file is touched, the brighter it glows
  • Per-file touch states are color-coded — seen (green), read (blue), edited (amber), unvisited (dark)
    • Files the session touched but that no longer exist in the repository remain as wireframe ghosts
    • The HUD groups friction signals such as error rate, churned files, and edits since the last verify
  • The Playback deck lets you scrub/replay the session over a bucketed histogram; observation (search/read/run) is placed cool and mutation (edit/verify) warm, so editing stretches stand out
    • Supports exporting the whole replay to .webm entirely on the client side
  • Timeline marks show context compaction (◇), subagent runs (○), and user turns (›), and clicking one jumps to that point
  • Agent lenses replay the traces of subagents the session launched on the same map, with a way back to the main trace
  • The session evaluation feature asks the local CLI for verdicts on exploration/scope/wandering/verification, and every finding is anchored to a clickable timeline event
    • Only when an evaluation is run, a session summary (message text, file paths, one-line event summaries) is sent to the model behind the claude/codex CLI on the user's account; other sessions are not included
  • Internally, it deliberately separates three artifacts: trace (a normalized stream of file touch events), citymap (a deterministic repository layout), and report (evidence-based findings from the LLM judge)
    • A local Go server combines them and serves them to a React/Three.js frontend
  • MIT License

See also

Favorite site

author Zer0 sitemap