Quick Start

This guide assumes you have the CLI installed and a Waypoint server available. If not, start with Installation.

Step 1 — Init a repo

cd your-project
waypoint init

You'll see:

✓ Updated CLAUDE.md
✓ Updated .gitignore
✓ Registered Stop hook in .claude/settings.json
✓ Installed /pr-summary slash command
✓ Server already configured (https://waypoint.yourcompany.com)

Waypoint is ready. Start a Claude Code session and work normally.
Sessions are recorded automatically after each turn.

Step 2 — Work in your agent

Open the project in your agent (Claude Code, VS Code Copilot, or any MCP-compatible agent) and have a session — write some code, fix a bug, ask the agent to refactor something. Work normally; Waypoint runs in the background.

When the session ends, the Stop hook fires automatically:

[waypoint] Recording waypoint for session abc12345 → def6789012
[waypoint] Posted to server https://waypoint.yourcompany.com
[waypoint] Done

Step 3 — Query context in the next session

Open the project again. Because your CLAUDE.md now includes the Waypoint instruction, the agent will call get_waypoint_context before editing files you worked on previously.

You can also call it directly:

get_waypoint_context("src/auth/middleware.ts")

The tool returns the sessions that touched that file — the decisions made, the approaches tried, and the events from each session.

To see what was worked on recently across the whole repo, call:

list_waypoints()

Step 4 — Generate a PR description

When you're ready to open a pull request, type /pr-summary in your agent. Waypoint reads the session history for the current branch and writes a PR description based on what actually happened — the intent, the decisions, the things that didn't work, and the test outcomes.

You're set up. Sessions record automatically. The agent gets context automatically.

Next: Session Recording — understand exactly what gets captured and how.