Pick Up Where You Left Off in Cursor

Cursor can read your codebase and ask about your code. What it can't know is your intent: what you were building toward, what you planned next, and where you left off. KeepGoing gives it that.

Cursor Chat

You:

Help me pick up where I left off and suggest what to do first.

Cursor:

You last worked on this project 5 days ago. You were refactoring the auth middleware to support JWT rotation. You updated auth.tsand middleware.tsbut still need to implement the verifyRefreshToken helper.

I'd suggest starting with the verifyRefreshToken helper in auth.ts since the middleware is already updated.

What you can do with Cursor + KeepGoing

Cursor becomes more useful when it knows what you were trying to accomplish, not just what the code looks like.

Ask Cursor "what was I doing?"

Instead of scrolling through git log, just ask. Cursor reads your KeepGoing data and answers with your last focus, branch, and suggested next step.

Context-aware AI suggestions

When Cursor knows what you were working on and what you planned next, its AI suggestions align with your actual intent, not just the current file.

Bridge the gap between sessions

Open Cursor after a week away. Ask for a re-entry briefing and get a synthesized summary of where you left off and what to do first.

Shared context across all your AI tools

KeepGoing data is shared between Cursor, Claude Code, and the CLI. Switch AI tools without losing your momentum.

How it works

1

Add KeepGoing via MCP

One click with the quick-install button, or add it manually to your Cursor MCP config.

2

Capture context as you work

Use the CLI or MCP server to save checkpoints. The VS Code extension also writes to the same data if you use both editors.

3

Ask Cursor anything

Cursor discovers the KeepGoing tools automatically. Ask about your momentum, history, or next steps.

The difference session continuity makes

Without KeepGoing

  • - Ask Cursor "what was I working on?" and it guesses from open files.
  • - Cursor AI suggests code that ignores decisions you made last week.
  • - You paste context into every new chat session to get useful answers.
  • - Close Cursor, reopen it. The AI starts from a blank slate.

With KeepGoing

  • + Ask Cursor "what was I working on?" and it answers from your checkpoint data.
  • + Cursor reads your session history and builds on your previous decisions.
  • + Your context loads automatically. No copy-pasting needed.
  • + Close Cursor, reopen it. The AI picks up where you left off.

Manual setup

If you prefer to configure manually, add the KeepGoing MCP server to your Cursor config.

Option 1: Quick install (recommended)

Add to Cursor

Opens Cursor and installs KeepGoing automatically.

Option 2: Edit ~/.cursor/mcp.json

~/.cursor/mcp.json
{
  "mcpServers": {
    "keepgoing": {
      "command": "npx",
      "args": [
        "-y",
        "@keepgoingdev/mcp-server"
      ],
      "type": "stdio"
    }
  }
}

Restart Cursor after saving the file.

Frequently asked questions

Does Cursor support MCP?

Yes. Cursor has built-in MCP support. You can add KeepGoing with one click using the quick-install button, or manually edit ~/.cursor/mcp.json.

Do I need the KeepGoing VS Code extension too?

Not required. You can save checkpoints manually via the CLI or MCP server. The VS Code extension adds automatic context capture from commits and branch switches, and writes to the same .keepgoing/ directory that Cursor reads.

What can Cursor access from my project?

Only the data in your .keepgoing/ directory: checkpoint summaries, next steps, branch names, and file lists. No source code is exposed through the MCP server.

Can I use both Cursor and Claude Code with KeepGoing?

Yes. Both tools read from the same .keepgoing/ directory. Checkpoints saved by one are visible to the other. They complement each other well.

Is KeepGoing free?

Yes. The MCP server and all core features are completely free. Optional Pro add-ons for power users are available separately.

Works great with

Combine integrations for the best experience. Each tool reads from the same local data.

VS Code

Passive context capture in VS Code. A ContextSnapshot appears in the status bar on every branch, and the sidebar shows your full re-entry briefing when you return.

Learn more

Claude Code

Give Claude Code session continuity across conversations. The MCP server feeds your momentum, recent progress, and next steps directly into every session.

Learn more

GitHub Copilot

Connect KeepGoing to GitHub Copilot via MCP. Copilot gains access to your project momentum, session history, and suggested next steps.

Learn more

JetBrains

Re-entry briefings when you open a project after days away. Works with IntelliJ IDEA, WebStorm, PyCharm, and all JetBrains IDEs.

Learn more

Windsurf

Windsurf (by Codeium) AI coding editor. Connect KeepGoing via MCP so Cascade maintains session continuity and knows your next steps.

Learn more

CLI

Run keepgoing glance for instant context in under 50ms. Integrates with Starship and tmux. Shell hook fires on cd so context is always there.

Learn more

Desktop Tray

Glance across every project: what's hot, what's warm, what's cold. Global hotkey pulls up your full briefing from anywhere, no editor needed.

Learn more

Starship

Show your current KeepGoing context in your Starship prompt. One-line glance output appears automatically in every initialized project.

Learn more

tmux

Show your KeepGoing context in the tmux status bar. Single project or multi-project view, refreshed automatically.

Learn more

Shell Prompt

Embed KeepGoing context directly in your Bash, Zsh, or Fish prompt using built-in shell hooks. No extra tools required.

Learn more

Give Cursor the context it needs

One click to install. No accounts, no setup wizards.