Capture
Captured agent Turns become a local session record.
Visual Waypoint turns captured AI coding sessions into a navigable Timeline and evidence trail—then lets you preserve durable anchors to important code as private or project-shared Waypoints.
Current-source Product Tour demo · maps are navigation surfaces, not verdicts.
Capture the work while it happens, understand it at the right level, and keep durable anchors back into the code.
Captured agent Turns become a local session record.
Work Spans reveal how the session unfolded.
Save the code and Notes worth keeping.
Claims stay separate from what was captured.
Return to the exact file or changed range.
Follow captured agent Turns in Work Spans, filter to changed code or evidence gaps, inspect a Turn in context, then open the corresponding Review item.
Focused crop of the Midnight Product Tour Timeline · open the image for the full thirteen-Turn view. Demo contents are not usage metrics.
Save a caret or exact code range, add a Quick Note or formatted Note, organize it, search it, and return to the code later.
Private by default. They stay in Visual Waypoint’s local data and do not write to the repository.
Explicit opt-in. Shared anchors and Note sidecars travel with the repository under .visualwaypoint.
Quick Notes and formatted Notes autosave during normal editing and flush when focus or selection changes.
Folders, point and range bookmarks, formatted Notes, Quick Notes, and anchored file locations stay organized by ownership.
Review Work Spans and Turns with guidance, changed regions, AI statements, receipts, and not-captured states kept visibly distinct. Review progress comes from explicit human action.
Story Spine, Signal City, Night City, and City Islands are alternate ways to explore the same captured session. They provide alternate navigation and spatial-memory views; they do not declare the code correct.
Visual Waypoint supports human review. It does not replace human review, declare correctness, or treat global workstation activity as review evidence.
Session data and private Waypoints stay in the local product workflow. Repository sharing is deliberate.
Opening or hovering is not approval. Review state changes through explicit user actions.
The Handoff Pack uses an allowlisted artifact set and excludes raw source and raw transcripts by default.
Rebuild context after an interruption and keep private anchors into a client or production codebase.
Move from Work Spans and evidence gaps to exact files and ranges before making a decision.
Understand scope, review progress, and where human attention is still required.
Zero qualifying failures across the extended headless campaign. Focused suites intentionally overlap; live-provider and remaining public-release gates sit outside this total.
Help shape a review and navigation workflow built for human understanding. Visual Waypoint is starting with Visual Studio and .NET developers working in substantial, long-lived codebases.
