Installation
Install the Waypoint CLI and connect it to your repo and team server.
Prerequisites
- Node.js 18+
- Git (any recent version)
- A Waypoint server — sessions are stored on the server, not in the repo. See Server Overview if your team doesn't have one yet.
- Claude Code or VS Code GitHub Copilot (other MCP-compatible agents also work — see Agent Compatibility)
Install the CLI
npm install -g @laserowl/waypointVerify the install:
waypoint --versionConnect to your server
Before initialising any repo, connect the CLI to your team's Waypoint server:
waypoint connect https://waypoint.yourcompany.comYou'll be prompted for your API key. Keys are issued by your admin from the server's admin panel. Config is saved to ~/.waypoint/config.json with 0600 permissions.
Config can also be set via environment variables, which take precedence over the file:
export WAYPOINT_SERVER_URL=https://waypoint.yourcompany.comexport WAYPOINT_API_KEY=wp_...Set up a repo
Run waypoint init from the root of any git repository:
cd my-projectwaypoint initinit does five things:
- Updates
CLAUDE.md— instructs the agent to callget_waypoint_contextbefore editing files andlist_waypointsat session start - Updates
.gitignore— excludes.waypoint/sessions/(sessions live on the server, not in git) - Registers the Stop hook in
.claude/settings.json— runswaypoint generateautomatically after every session - Installs the
/pr-summaryslash command in.claude/commands/ - Prompts for server connection details if not already configured
If a server isn't configured yet, init will prompt for your server URL and API key.
Note
Sessions are stored on the server — not in the repository. This keeps git history clean and makes context available to every developer on your team without any extra steps.
Verify
Start a session in your agent, do some work, and end it. You should see:
[waypoint] Posted to server https://waypoint.yourcompany.com[waypoint] DoneIf you see No server configured — session not saved, run waypoint connect to add your server details.