CURRENT COLLECTOR · CODEX
Turn Codex sessions into a reviewable project path.
Wayfinder reads available active and archived Codex sessions locally and organizes work that belongs to one project into voyages, instead of regenerating a chat summary.
What it keeps
- The provenance of goals, replies, and tool activity in a session.
- Related attempts and voyages within the same workspace.
- Both successful and failed paths, not only the final answer.
- File changes when the source clearly contains real edits.
- Available validation such as tests or checks.
What it does not do
Wayfinder does not invoke system Git, does not create hidden workspace snapshots, and does not infer a nonexistent historical diff from the final file state. Unfinished, failed, or out-of-bounds tool calls do not become file changes.
The complete history stays on the user's computer; the current version has no Wayfinder account, telemetry, cloud sync, or cloud analysis.
Collection scope at a glance
| Reads from | Local Codex active and archived session records |
|---|---|
| Grouping | Into voyages and branches by project/workspace |
| File-change source | Only successful tool calls with real edit evidence |
| Plugin required | None; use Codex as usual |
| Network | Only opens GitHub Releases when you check for versions |
Getting started
Install and open Wayfinder, then keep using Codex as usual. On first launch it backfills available local history, then updates the matching project voyage map incrementally in the background.
Primary source
OpenAI's official Codex CLI documentation states that Codex stores transcripts locally and can resume a specific session from records under ~/.codex/sessions/. Wayfinder's collection scope and evidence boundary above remain descriptions of the current public build.
Support status: Early Access · Updated: 2026-09-14