New to KeepGoing? See the integration overview.
Claude Code that remembers where you left off
Install the KeepGoing plugin and Claude Code automatically knows your project momentum, recent sessions, and suggested next steps.
When you open a project with the session hook:
[KeepGoing] Last checkpoint: 3 days ago
Summary: Refactor middleware to support JWT rotation
Next step: Implement the verifyRefreshToken helper
Branch: feature/auth-refresh
Worked on 4 files on feature/auth-refresh
Tip: Use the get_reentry_briefing tool for a full briefing
What Claude Code can do
The MCP server exposes four tools that Claude Code can use to understand and track your project context.
get_momentum
Returns your last checkpoint timestamp, summary, next step, blockers, current branch, and files touched. Use this to understand where you left off.
get_session_history
Returns a chronological list of your recent checkpoints. Accepts a limit parameter (1-50, default 5).
get_reentry_briefing
Synthesizes a complete re-entry briefing from your session data, recent commits, and touched files. Designed to get you back up to speed in seconds.
save_checkpoint
Save a development checkpoint. Call this after completing a task or meaningful piece of work, not just at end of session. Each checkpoint helps the next session (or developer) pick up exactly where you left off.
Slash commands
Type /keepgoing: in Claude Code to see all available commands. All commands are namespaced so they never conflict with your project's own slash commands.
/keepgoing:reentry
Quick "where did I leave off?" briefing. Best when you open a project and want to get back up to speed in seconds.
/keepgoing:briefing
Full context reconstruction before a big session. Synthesizes your session history, recent commits, and touched files into a complete picture.
/keepgoing:save [msg]
Save a checkpoint manually with an optional message. Useful before switching branches or ending a session early.
/keepgoing:progress
Standup-ready progress summary across recent sessions, grouped by branch or feature.
/keepgoing:hot
See what's actively in-progress across all your sessions. Useful when juggling multiple branches or projects.
/keepgoing:handoff [target]
Export your session context to another AI tool: ChatGPT, Gemini, GitHub Copilot, and others. Hand off context without re-explaining everything.
Status line
With per-project setup, KeepGoing writes a statusLine entry to your .claude/settings.json. Claude Code uses this to show your current task and AI activity in its status bar in real time.
Idle, between tasks:
› Where did we leave off?
Based on your last session...
Active, while the AI is working:
› Fix the auth middleware
Looking at the middleware files...
Setup
Three ways to get started. The plugin is the fastest path for Claude Code users.
Option A: Claude Code Plugin recommended
One command installs the CLI, plugin, hooks, and rules file. No JSON editing required.
Run in your terminal
What gets configured automatically
- Claude Code plugin installed with MCP server, tools, and slash commands
- SessionStart hook loads your momentum when you open a project
- Stop hook auto-saves a checkpoint when you close a session
- Rules file written so Claude proactively saves checkpoints as it works
- Status line configured to show current task and AI activity in real time
Coming from the plugin marketplace? See the dedicated plugin install guide.
Option B: From VS Code
If you have the KeepGoing VS Code extension installed, open the command palette and run:
KeepGoing: Set up Claude Code MCP
This registers the MCP server and configures session hooks. You'll still need to run keepgoing setup project in Claude Code to complete per-project configuration.
Option C: Terminal setup
Register the MCP server directly. Choose global (all projects) or per-project scope:
Global Works across all your projects
claude mcp add keepgoing --scope user -- npx -y @keepgoingdev/mcp-serverPer-project Scoped to a single project, good for teams
claude mcp add keepgoing --scope project -- npx -y @keepgoingdev/mcp-serverThen configure hooks and instructions
Once the MCP server is registered, ask Claude Code to complete setup:
Global setup If you added the MCP server with --scope user
keepgoing setup project with scope user Per-project setup If you added the MCP server with --scope project
keepgoing setup projectShow manual JSON configuration
Session hooks
Add to ~/.claude/settings.json (global) or .claude/settings.json (per-project):
{
"hooks": {
"SessionStart": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "keepgoing momentum --hook"
}
]
}
],
"Stop": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "keepgoing save --hook"
}
]
}
]
}
}Do not configure hooks at both global and per-project scope, as they will fire twice.
CLAUDE.md instructions
Add to ~/.claude/CLAUDE.md (global) or your project's CLAUDE.md so Claude proactively saves checkpoints:
## KeepGoing
After completing a task or meaningful piece of work, call the `save_checkpoint` MCP tool with:
- `summary`: What you accomplished
- `nextStep`: What should be done next
- `blocker`: Any blocker (if applicable)How it works
The MCP server can both read and write checkpoints to .keepgoing/ in your project directory. Claude Code can call save_checkpoint directly, and the Stop hook provides an automatic safety net.
No VS Code extension required. No cloud, no accounts. Everything stays local.
If you also use the VS Code extension, it writes checkpoints from editor activity (saves, commits, branch switches, idle detection). Both sources share the same .keepgoing/ directory, so Claude Code always has the full picture.
Get started
One command sets up everything. Claude Code handles the rest.