Stop Losing Context on Your VS Code Side Projects

You reopen VS Code after two weeks. You check git log, grep TODOs, re-read your last PR. Twenty minutes gone before you write a line of code. KeepGoing eliminates that ramp-up entirely.

Install for VS Code v0.10.0 Read the setup guide

KeepGoing

KEEPGOING

Welcome back

Here's where you left off

🕐 2 weeks ago

🎯 Migrate UserProfile from class component to React hooks.

📋 Modified UserProfile.tsx, useProfile.ts, and 3 others

➡️ Wire up the refresh token endpoint

Next small step:

🟢 Wire up the useProfile hook in the settings page.

▶ Quick checkpoint Save with auto-generated summary

▶ Start new checkpoint Save your current progress

▶ View full history Browse all checkpoints

TS auth.ts

middleware.ts

Using GitHub Copilot in VS Code?

Add the KeepGoing MCP server so Copilot can read your session context. One click to install.

Add to VS Code (MCP) GitHub Copilot integration

Built for how you actually work

Side projects, context switching, long breaks between sessions. KeepGoing handles all of it.

Return after a vacation

You were deep in a refactor before two weeks of PTO. KeepGoing shows the exact file, function, and next step so you skip the "where was I?" phase entirely.

Juggle multiple side projects

Context-switch between three repos without losing your place. Each project keeps its own checkpoint trail, ready when you come back.

Hand off context to AI

Pair KeepGoing with Claude Code or GitHub Copilot. Your AI assistant reads your momentum data and picks up exactly where you stopped.

Weekend warrior workflow

Code on Saturday, come back next Saturday. KeepGoing bridges the gap so your weekly sessions feel continuous instead of starting from scratch.

How it works

Install the extension

One click from the VS Code Marketplace. No accounts, no configuration required.

Code as usual

KeepGoing watches silently. It checkpoints on commits, branch switches, and idle periods.

Resume with full context

Come back days or weeks later. KeepGoing shows your last focus, files touched, and suggested next step.

The difference one extension makes

Without KeepGoing

- Reopen VS Code after 2 weeks. Stare at the file tree.
- Run git log and git diff to piece together what happened.
- Grep for TODOs, re-read your last PR description.
- Open 4 files trying to remember which one matters.
- 20 minutes gone before you write a single line.

With KeepGoing

+ Reopen VS Code. A prompt shows your last focus and next step.
+ See exactly which files you touched and why.
+ Read a one-line summary of what you were trying to accomplish.
+ Open the right file immediately.
+ Start coding in 30 seconds.

Frequently asked questions

Is KeepGoing free?

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

Does it work offline?

Absolutely. KeepGoing stores everything in a local .keepgoing/ directory inside your project. No internet connection needed.

What data does KeepGoing collect?

None. KeepGoing has no telemetry, no analytics, and no cloud sync. Your session data never leaves your machine.

Does it slow down VS Code?

No. KeepGoing runs lightweight background tasks on commits, branch switches, and idle timeouts. There is no file watcher overhead or continuous polling.

Can I use it with other editors?

The VS Code extension is the primary writer. For other editors, the CLI and MCP server can read and write checkpoints. A JetBrains plugin and desktop tray app are also available.

How is this different from git stash or TODO comments?

Git stash saves uncommitted changes. TODO comments mark spots in code. KeepGoing captures your intent, focus, and next step across sessions, bridging gaps of days or weeks automatically.

Works great with

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

Start keeping your projects alive

Install from the VS Code Marketplace. No accounts, no setup wizards.

Install for VS Code v0.10.0 Read the setup guide 100% Free and Local