Keepgoing

Created By
keepgoing-dev3 months ago
Project memory for AI coding assistants. Auto-captures checkpoints on git commits, branch switches, and inactivity. When you start a new session, your AI assistant reads your last context instead of re-inferring everything from scratch. Local-first, no account required.
Overview

What is KeepGoing?

KeepGoing gives AI coding assistants persistent project memory. It auto-captures checkpoints on git commits, branch switches, and inactivity, so when you start a new session, your AI picks up exactly where you left off.

Why?

AI coding assistants start every session with zero context. They re-read files, re-infer intent, and miss what you planned next. KeepGoing fixes this by capturing session state automatically and exposing it via MCP tools.

Tools

ToolDescription
get_momentumLast checkpoint, next step, blockers, and branch context
get_reentry_briefingSynthesized re-entry briefing with focus and suggested next steps
get_session_historyRecent session checkpoints in chronological order
save_checkpointSave a checkpoint after completing meaningful work
setup_projectSet up KeepGoing in the current project with hooks and instructions
get_decisionsHigh-signal commits with category and rationale (paid add-on)
get_current_taskLive session tasks across concurrent AI agents (paid add-on)

Quick Setup

claude mcp add keepgoing -- npx -y @keepgoingdev/mcp-server

How It Works

  1. Install the KeepGoing VS Code extension
  2. Add this MCP server to your AI coding assistant
  3. Start coding. Checkpoints are saved automatically
  4. Come back anytime. Your AI calls get_momentum to pick up where you left off

All data is stored locally in a .keepgoing/ directory at your git root. No account required.

Server Config

{
  "mcpServers": {
    "keepgoing": {
      "command": "npx",
      "args": [
        "-y",
        "@keepgoingdev/mcp-server"
      ]
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
keepgoing-dev
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago