Session memory for Claude Code. Auto-saves checkpoints, shows what you were working on when you return, and tracks progress across sessions.

Once installed, KeepGoing runs automatically in the background:

• Session start: Shows your last checkpoint and what you were working on
• While coding: Tracks file edits and session activity
• Session end: Auto-saves a checkpoint so nothing is lost

/plugin marketplace add keepgoing-dev/claude-plugin
/plugin install keepgoing@keepgoing-dev

Full install guide: https://keepgoing.dev/setup/claude-plugin

If you previously configured KeepGoing via keepgoing init or setup_project, your settings.json already has KeepGoing hooks. The plugin provides those hooks too, so you'll have duplicates.

To clean up: remove the KeepGoing hook entries from your .claude/settings.json or ~/.claude/settings.json, then run keepgoing setup claude from your terminal to restore the rules file and statusline.

As of v0.1.3, the MCP server key was renamed from keepgoing to session to avoid naming conflicts. If your config references the old key name, update it to session.

With the plugin installed, Claude has direct access to all KeepGoing tools during your session:

• save_checkpoint - Save the current state
• get_reentry_briefing - Get structured context (supports tier and model params)
• get_momentum - Current session and branch status (supports tier and model params)
• get_session_history - Full session history
• get_decisions - Key architectural decisions (Pro)
• get_whats_hot - Recently active files and branches (Pro)
• continue_on - Export context for other AI tools (the underlying tool called by /keepgoing:handoff)

Note: The /keepgoing:handoff [target] slash command calls the continue_on MCP tool under the hood.

get_decisions and get_whats_hot (and detailed decision tracking) require a KeepGoing Pro license. Basic session recall, briefings, and checkpoints are free. Visit keepgoing.dev to learn more.

This package has no build step. It is a static bundle of JSON config files and Markdown skill definitions.

• To add or modify a skill, edit (or create) skills/<name>/SKILL.md.
• To change hook behavior, edit hooks/hooks.json.
• To update plugin metadata, edit .claude-plugin/plugin.json and keep the version in .claude-plugin/marketplace.json in sync.
• MCP tool references in skill allowed-tools must use the mcp__plugin_keepgoing_session__ prefix (the MCP server key is session).

If you rename or add MCP tools in apps/mcp-server, update the skill allowed-tools lists here to match.