Pick Up Where You Left Off with GitHub Copilot

Copilot can read your codebase and suggest code in context. 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.

Copilot Chat

You:

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

Copilot:

You last worked on this project 10 days ago. You were adding dark mode support to the settings panel. You finished the theme toggle component but still need to persist the preference to localStorage and update the CSS variables in theme.ts

I'd suggest starting with the useTheme hook since the toggle is already wired up.

What you can do with Copilot + KeepGoing

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

Ask Copilot "what was I doing?"

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

Context-aware code suggestions

When Copilot 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 VS Code after a week away. Ask Copilot for a re-entry briefing and get a synthesized summary of where you left off and what to do first.

Shared context with your whole stack

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

How it works

1

Install the VS Code extension

KeepGoing captures your coding context silently as you work. This is the data source.

2

Register the MCP server

One command or a VS Code palette action adds the MCP server to your project.

3

Ask Copilot anything

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

The difference session continuity makes

Without KeepGoing

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

With KeepGoing

  • + Ask Copilot "what was I working on?" and it answers from your checkpoint data.
  • + Copilot reads your session history and builds on your previous work.
  • + Your context is loaded automatically. No copy-pasting needed.
  • + Close VS Code, reopen it. Copilot picks up where you left off.

Frequently asked questions

Does this work with GitHub Copilot Free?

Yes, as long as your version of VS Code and Copilot supports MCP servers. The KeepGoing MCP server is free regardless of your Copilot plan.

Do I need the KeepGoing VS Code extension too?

Recommended but not required. The extension auto-captures context from commits, branch switches, and idle periods. Without it, you can still save checkpoints manually via the CLI or MCP server.

What can Copilot 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 Copilot 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, VS Code extension, 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

JetBrains

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

Learn more

Cursor

AI-first editor with built-in Copilot. Connect KeepGoing via MCP so Cursor maintains session continuity, knows your next step, and respects recent decisions.

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 Copilot the context it needs

Install the extension to capture your context, then connect Copilot via MCP.