CURRENT COLLECTOR · CLAUDE CODE
Put Claude Code's multi-session work back on one map.
Wayfinder reads compatible Claude Code sessions locally and organizes voyages by workspace and goal, so attempts, branches, and validation no longer scatter across separate chats.
What it helps you review
- How one project continues across multiple Claude Code sessions.
- Which implementation directions failed, rolled back, or were rejected.
- Which original turn tool activity and file edits came from.
- Which tests or validation the final approach went through.
- Related work from different AI tools around the same goal.
Local boundary
Collection, grouping, and map generation happen locally. Wayfinder requires no Claude Code plugin and uploads no full sessions, file-change summaries, or voyage maps to a Wayfinder service.
Only genuinely successful edits in the source record become file changes; the app does not fabricate past diffs from the current workspace when no evidence exists.
Collection scope at a glance
| Reads from | Local Claude Code compatible session records |
|---|---|
| Grouping | Into voyages and branches by workspace and goal |
| File-change source | Only successful tool calls with real edit evidence |
| Plugin required | None |
| Incremental updates | A watcher processes only new or changed session records |
Getting started
Open Wayfinder and keep using Claude Code normally. First launch imports the available local history, after which the watcher processes only new or changed session records.
Primary source
Anthropic's official Claude Code documentation states that sessions are tied to project directories and saved continuously to local transcript files. Wayfinder's collection scope and evidence boundary above remain descriptions of the current public build.
Support status: Early Access · Updated: 2026-09-14