Your Project Context, Right in the Terminal
You switch between projects all week. The KeepGoing CLI shows you exactly where you left off the moment you enter a directory. No editor required.
~ keepgoing log --today --oneline
a3f1c2 2h ago Refactored auth middleware to support JWT rotation
b7e4d9 5h ago Added rate limiting to API endpoints
c9a2f1 7h ago Fixed session expiry bug in token refresh
~ keepgoing momentum
KeepGoing · 2 hours ago
Summary: Refactored auth middleware to support JWT rotation
Next step: Implement verifyRefreshToken helper in auth.ts
Branch: feature/auth-refactor
Files: auth.ts, middleware.ts, routes/token.ts (+2 more)
Why use the CLI
Editor-agnostic project context that works wherever your terminal does.
Get a re-entry briefing
Run keepgoing briefing and get a full summary of where you left off: session history, recent commits, and your next step.
Save checkpoints from git automatically
Run keepgoing save and the CLI auto-generates a summary and next step from your recent git activity. Override with -m or -n for custom text.
Browse and search session history
Use keepgoing log to filter checkpoints by date, branch, file, or keyword. View grouped by session, in compact one-line format, or with file stats.
Scriptable and composable
JSON output, quiet mode, and keepgoing query for reading checkpoint data programmatically. Pipe data into other tools or build your own workflows.
How it works
Install the CLI
Run the one-line installer or install globally with npm. Then run keepgoing init to set up hooks and config in your project.
Check momentum, browse history, or save
Use keepgoing momentum for a quick pulse, keepgoing log to browse history, keepgoing briefing for a full re-entry summary, or keepgoing save to capture a checkpoint.
Add the shell hook (optional)
One command installs a cd hook that shows your context whenever you enter a project directory.
What changes with terminal context
Without KeepGoing
You cd into a project you have not touched in a week. You run git log, check TODO files, and try to piece together what you were doing.
With KeepGoing
You run keepgoing briefing and get a full re-entry summary: what you did, what changed, and where to pick up.
Without KeepGoing
You finish a coding session but forget to write down where you stopped. Next time, that context is gone.
With KeepGoing
You run keepgoing save. The CLI auto-generates a summary from your git activity in seconds.
Without KeepGoing
You need to find when you last worked on a specific file or feature, but your commit history is noisy.
With KeepGoing
You run keepgoing log --follow src/auth.ts or keepgoing log --search "auth" to find exactly what you need.
Frequently asked questions
Do I need the VS Code extension to use the CLI?
No. The CLI reads and writes the same .keepgoing/ data format independently. You can use it standalone or alongside any other KeepGoing tool.
What shells does the hook support?
Zsh, Bash, and Fish. The hook install command detects your shell and adds the appropriate snippet to ~/.zshrc, ~/.bashrc, or ~/.config/fish/config.fish.
How does auto-generated save work?
When you run keepgoing save, the CLI analyzes your recent git commits and changed files to generate a summary and next step automatically. You can override either with -m (summary) or -n (next step).
Can I use the CLI in scripts or CI?
Yes. The --json flag outputs raw checkpoint data, and --quiet outputs a single summary line. Both are designed for scripting and piping.
Is the CLI free?
Yes. The CLI and all core features are completely free. The decisions command requires a Pro license, but everything else works out of the box.
Where is my checkpoint data stored?
All checkpoint data is stored in a local SQLite database at .keepgoing/keepgoing.db in your project directory. Nothing is sent to the cloud. Run keepgoing doctor to check storage health or keepgoing migrate to import legacy data.
Does the CLI work with AI tools?
Yes. Checkpoints saved by the CLI are readable by Claude Code, GitHub Copilot, and any tool that uses the MCP server. They all share the same SQLite database at .keepgoing/keepgoing.db.
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 moreClaude Code
Give Claude Code session continuity across conversations. The MCP server feeds your momentum, recent progress, and next steps directly into every session.
Learn moreGitHub Copilot
Connect KeepGoing to GitHub Copilot via MCP. Copilot gains access to your project momentum, session history, and suggested next steps.
Learn moreJetBrains
Re-entry briefings when you open a project after days away. Works with IntelliJ IDEA, WebStorm, PyCharm, and all JetBrains IDEs.
Learn moreCursor
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 moreWindsurf
Windsurf (by Codeium) AI coding editor. Connect KeepGoing via MCP so Cascade maintains session continuity and knows your next steps.
Learn moreDesktop 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 moreStarship
Show your current KeepGoing context in your Starship prompt. One-line glance output appears automatically in every initialized project.
Learn moretmux
Show your KeepGoing context in the tmux status bar. Single project or multi-project view, refreshed automatically.
Learn moreShell Prompt
Embed KeepGoing context directly in your Bash, Zsh, or Fish prompt using built-in shell hooks. No extra tools required.
Learn moreTry it in 10 seconds
One command installs the CLI and runs the setup wizard.