Continue On: Export Your Dev Context to Any AI Tool

You are mid-session in Claude Code. You have saved a checkpoint, touched a dozen files, and mapped out the next step. Then you need to switch to ChatGPT because it handles a specific task better. Or you move to your laptop and want to pick up in Gemini. Or a teammate wants to help using Copilot.

The context is all there, sitting in your .keepgoing/ directory. But the other tool does not know about it.

Continue On fixes that. It gathers your KeepGoing session data and formats it as a markdown prompt you can paste into any AI tool.

What gets exported

Continue On reads the same .keepgoing/ directory that every KeepGoing integration writes to and assembles a structured prompt with:

Project metadata: Project name and current git branch
Current status: When you last worked, what you were focused on
Last session: Summary, planned next step, any blockers, and which files you touched
Active sessions: Any concurrent agent tasks currently running (useful if you have Session Awareness)
Recent decisions: The last few high-signal architectural decisions
Recent commits: Commit messages since your last checkpoint (up to 10)

At the bottom of the prompt, the receiving AI tool gets a clear instruction: “Please help me continue this work. My next step is: …” using the next step from your last checkpoint.

The result is a complete context handoff. The receiving tool does not need to search through your codebase or guess what you were doing. It gets a structured briefing and a clear starting point.

What does not get exported

No raw source code leaves your machine. Continue On exports session metadata, summaries, and commit messages. It does not copy file contents, environment variables, or secrets. The prompt is safe to paste into any tool without leaking proprietary code.

How to use it

CLI

The fastest path. Run keepgoing continue and the prompt is copied to your clipboard:

keepgoing continue

Target a specific tool and auto-open it in your browser:

keepgoing continue --target chatgpt --open

Supported targets: chatgpt, gemini, copilot, claude. Each one opens the appropriate URL after copying the prompt.

If you want the raw data for scripting or piping:

keepgoing continue --json

MCP tool

If you are working in an MCP-capable environment (Claude Code, Cursor, Windsurf), the continue_on tool is available directly:

“Export my context so I can continue in ChatGPT”

The MCP server returns the formatted prompt as text. You can copy it from the tool output and paste it wherever you need.

VS Code

Open the command palette and run KeepGoing: Continue On. The prompt is copied to your clipboard, ready to paste.

What the prompt looks like

Here is a simplified example of what gets generated:

# Project Context: my-app

I'm continuing work on a project. Here is my development context from KeepGoing.

## Current Status
- **Branch:** feat/auth-flow
- **Last worked:** 2 hours ago
- **Focus:** Implementing OAuth token refresh logic

## Last Session
- **Summary:** Added token refresh service with mutex guard
- **Next step:** Write integration tests for the refresh flow
- **Files touched:** src/services/tokenRefresh.ts, src/middleware/auth.ts

## Recent Decisions
- authentication: Switch from session cookies to JWT with refresh tokens

## Recent Commits
- feat: add token refresh service with mutex guard
- refactor: extract auth middleware from route handlers

---
Please help me continue this work. My next step is: Write integration tests for the refresh flow.

Paste that into ChatGPT, Gemini, or any other tool, and it has full context to help you move forward.

Why this matters

AI tools are getting better fast. Most developers already use more than one. You might prefer Claude for architecture decisions, ChatGPT for debugging, Copilot for inline completions, and Gemini for research. The problem is that each tool starts from zero every time you switch.

KeepGoing already solves the “resume after a break” problem within a single tool. Continue On extends that across tools. Your development context becomes portable. It follows you wherever you go, not because of a cloud sync or a proprietary integration, but because it is plain text on your clipboard.

Local-first by design

The clipboard flow never sends data to any server. KeepGoing reads local files, formats a string, and copies it. That is the entire data path. No network requests, no telemetry, no third-party APIs.

A URL-based sharing flow is coming soon for cases where you want to send context to a teammate or a different device. Those links will expire after one hour and contain only the same session metadata, never source code.

Free for everyone

Continue On is not a Pro feature. It works with the free version of KeepGoing, across all integrations: VS Code, CLI, MCP server. If you have session data, you can export it.

To get started, install KeepGoing, save a checkpoint, and run keepgoing continue.

Your context should follow you, not your tools.