Session Review: Find the Origin of Changes
The Engineer's Dilemma: Daily conversations across Claude Code, Codex, and Cursor easily scatter. When unexpected code changes or regressions appear, engineers often struggle to remember which session, prompt, or tool call introduced the crucial requirement or modified that file.
01
Select Registered Project & Agent Provider
Choose a registered local repository in the macOS client. Vela automatically monitors and associates local JSONL log streams generated by Claude Code (
~/.claude/projects/) and Codex (~/.codex/sessions/), alongside read-only import support for exported Cursor sessions.
02
Evidence-Based Search & State Filtering
Conduct fast lexical searches across engineering sessions via the global search bar. Session lists show inferred states (Running, Idle, Needs Approval) derived strictly from log event timestamps. When liveness evidence is missing, sessions are marked as unknown rather than fabricating live process probes.
03
Inspect Actual Messages & Tool Call Invocations
Select a session to view the complete conversation timeline and tool invocation events. Inspect input arguments and return outputs for commands like
file.write, bash, or environment checks to verify the underlying evidence for every change.
04
Promote to Project Memory or Export Neutral Checkpoint
When valuable engineering constraints emerge from a session, promote them to Candidate memories with one click, preserving the exact source session and message indexes. Or export neutral Markdown checkpoints containing the current Git HEAD and pending tasks for agent handoffs.
macOS native development build interface (commit 91d34e2) · Synthetic data · Not included in the preview.2 installer
Boundaries & Known Limitations
- Development Build Interface & Version Boundary: The complete workspace, precise source tracking, and memory proposal workflows shown in this screenshot reflect the current development branch (commit 91d34e2); the 0.1.0-preview.2 installer includes core log ingestion and session state inference.
- States are Strictly Inferred: Operational states are inferred purely from the most recent write events in local log files, not from background daemon probes. They do not constitute OS-level process liveness guarantees.
- Bounded Ingestion Policy: Initially scans up to 60 recent session files per provider, reading a 256 KB tail window and a 32 KB header window. Vela does not perform unbounded historical backfills or live cross-provider context migration.
- Cursor Format Evolution: Cursor's internal storage formats vary frequently across releases. Unadapted formats must be imported via exported JSON.