Get This Tool
mindwalk
Pricing
- Model
- Free
Summary
Raw JSONL agent logs tell you what ran — they don't tell you whether the agent wandered half the repo before touching the three files you actually cared about. Mindwalk renders those sessions as light moving through a 3D night-map of your codebase, so scope drift becomes visible instead of inferred.
The tool replays Claude Code or Codex session logs against a spatial model of your repository, showing file touch history, exploration paths, and where the agent's footprint diverged from the intended task boundary. Everything runs locally as a compiled Go binary — no server, no API key, no data leaving the machine. That local constraint is also the ceiling: Mindwalk reads and visualizes; it does not flag anomalies automatically or integrate into a CI gate. Teams using it for post-session audits get a fast, honest picture of agent behavior. Teams that need automated alerts or diff-level review stay in their existing toolchain.
Bottom line: Reach for Mindwalk when you need to show a teammate exactly where an agent strayed from scope during a session review; skip it when you need that check to fire automatically in a pipeline without a human pulling up the visualization.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Spatial replay of agent session paths, so you can see exploration-before-action at a glance instead of reconstructing it by reading hundreds of JSONL lines in sequence.
- Fully local Go binary with no external dependencies at runtime, which means session logs containing proprietary code never leave the machine — a requirement on most enterprise codebases.
- MIT license with build-from-source instructions, so teams can audit the binary, fork it, or embed it in internal tooling without negotiating a license.
- Visual file-touch history makes scope drift concrete — when an agent read files three directories outside the intended boundary, that shows up as light crossing the map rather than as a number buried in metadata.
- Targets the specific log formats produced by Claude Code and Codex, so there is no generic adapter layer to configure for the two most common coding-agent environments.
Cons
Sign in to edit- Visualization is purely retrospective: there is no API, no event stream, and no CI hook, so the tool cannot block a bad session from shipping — a team that needs automated scope enforcement has to build that check elsewhere and Mindwalk contributes nothing to it.
- Log format support is tied to what the schema directory describes; agents that produce non-standard or extended JSONL structures require a preprocessing step before Mindwalk can ingest them, and the docs do not describe a plugin or adapter interface for this.
- There is no anomaly detection or scoring — the visualization shows you what happened, but deciding whether the footprint was acceptable is entirely on the reviewer. Teams that audit dozens of sessions per day and need triage prioritization will hit this ceiling quickly and move to a purpose-built audit platform that can surface outliers automatically.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- macOS, Linux, Windows
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-07-22T13:34:41.903Z
Best For
Who it's for
- Developers debugging agent behavior
- Teams auditing coding-agent outputs
- Local analysis of Claude Code or Codex logs
What it does well
- Review coding-agent session paths and scope alignment
- Visualize agent exploration vs. intended task boundaries
- Inspect file touch history and friction signals post-session
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare mindwalk
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is mindwalk free?
- Yes — mindwalk is fully free to use. There is no paid tier.
- Is mindwalk open source?
- Yes. mindwalk is open source.
- Can I self-host mindwalk?
- Yes. mindwalk supports self-hosting on your own infrastructure.
- What platforms does mindwalk support?
- mindwalk is available on: macOS, Linux, Windows.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Mindwalk ingests the JSONL session logs produced by coding agents and renders them as a 3D spatial replay — the repository becomes a map, and the agent’s activity plays back as movement through it. The core workflow is local: install the Go binary via the provided script or build from source, point it at a log file, and the tool produces an interactive visualization showing which files were read, which were written, and in what sequence the agent explored before committing to action.
The differentiating design choice is the spatial metaphor. Rather than a flat timeline or a raw log diff, Mindwalk draws the repository as a night-city map and animates the session as light traveling through it. The vendor’s own framing — ‘where it explored before it acted, whether its footprint matched the scope you had in mind’ — captures what this unlocks: the gap between what an agent did and what you assumed it did becomes a geometric shape you can point at, not an inference you have to argue from line numbers.
Mindwalk fits a specific moment in the debugging workflow: after a session completes, before you decide whether to ship the output or re-prompt. It is a human review aid, not an automated gate. There is no API, no webhook, and no integration surface for CI pipelines. Teams that want anomaly detection or automated scope-boundary enforcement need a separate layer — Mindwalk does not provide it and the project does not describe plans to add it.
The tool is MIT-licensed and written in Go, with build instructions and a release script in the repository. Log support targets Claude Code and Codex session formats as described in the README. The schema directory in the repository suggests log format expectations are explicit, which matters if your agent produces a non-standard JSONL structure — the docs describe the expected format and deviations will require preprocessing.