Pick Up Where You Left Off in Windsurf

Cascade 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.

View setup Full MCP server docs

Windsurf / Cascade

You:

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

Cascade:

You last worked on this project 12 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 that helper in auth.ts.

What you can do with Windsurf + KeepGoing

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

Ask Cascade "what was I doing?"

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

Context-aware AI suggestions

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

Bridge the gap between sessions

Open Windsurf after a week away. Ask Cascade 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 Windsurf, Claude Code, and the CLI. Switch AI tools without losing your momentum.

How it works

Edit your Windsurf MCP config

Add the KeepGoing server to ~/.codeium/windsurf/mcp_config.json and restart Windsurf.

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.

Ask Cascade anything

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

The difference session continuity makes

Without KeepGoing

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

With KeepGoing

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

Setup

Add the KeepGoing MCP server to your Windsurf config file and restart Windsurf.

Edit ~/.codeium/windsurf/mcp_config.json

~/.codeium/windsurf/mcp_config.json

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

Restart Windsurf after saving. Cascade will discover the KeepGoing tools automatically.

Frequently asked questions

Does Windsurf support MCP?

Yes. Windsurf has built-in MCP support through Cascade. Add KeepGoing by editing ~/.codeium/windsurf/mcp_config.json and restarting Windsurf.

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 Windsurf reads.

What can Cascade 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 Windsurf 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.

Give Cascade the context it needs

One config file, then Cascade picks up where you left off.

View setup Full MCP server docs 100% Free and Local