Project Context in Your Shell Prompt
One command sets up your Bash, Zsh, or Fish shell to show what you were working on every time you cd into a project. No manual config, no dependencies.
% keepgoing hook install
KeepGoing hook installed in ~/.zshrc.
% cd ~/code/my-project
⚡ Working on auth refactor → write tests (2h ago)
%
Why embed context in your prompt
The simplest integration is often the most effective one.
No extra tools required
Uses only built-in shell hooks: PROMPT_COMMAND for Bash, precmd for Zsh, fish_prompt for Fish. Nothing to install beyond the KeepGoing CLI.
Works with Bash, Zsh, and Fish
Native snippets for all three major shells. Each uses the shell's own hook mechanism so context updates before every prompt render.
Keeps your prompt clean everywhere
The `.keepgoing` directory check skips the glance call in uninitialized directories. Your prompt stays fast and uncluttered everywhere else.
Instant visibility on every prompt
Context updates before each prompt is drawn. Open a terminal, cd into a project, and your last checkpoint is already visible.
How it works
Install the KeepGoing CLI
Run the one-line installer: curl -fsSL https://keepgoing.dev/install.sh | bash. Or install directly with npm install -g @keepgoingdev/cli. Then run keepgoing init in any project you want to track.
Run keepgoing hook install
Auto-detects your shell (Bash, Zsh, or Fish) and adds the hook to your config file. No manual editing needed.
Reload and cd into a project
Run source ~/.zshrc (or equivalent) and cd into any initialized project. Your context appears automatically.
What changes with prompt context
Without KeepGoing
You open a new terminal in your project and spend the first few minutes recalling where you stopped. You check git log and scan recent files.
With KeepGoing
Your prompt already shows the summary and next step from your last checkpoint. You know what to do before you type anything.
Without KeepGoing
You need a separate command like keepgoing momentum or a sidebar to see your context. That means an extra step every time you return.
With KeepGoing
The glance output appears in your prompt automatically on every render. Zero extra keystrokes.
Without KeepGoing
Your prompt clutters up with context information even in system directories or projects you do not track.
With KeepGoing
The .keepgoing directory check means context only shows up where it exists. Everywhere else stays clean.
Frequently asked questions
Will this slow down my prompt?
No. The glance command reads only from .keepgoing/ JSON files with no git calls or network requests. It completes in under 50ms. The directory check also skips the call entirely in uninitialized directories.
Does this conflict with Oh My Zsh or Prezto?
No. The Zsh snippet uses precmd_functions+=(_keepgoing_precmd), which appends to the existing hook array rather than replacing it. It works alongside Oh My Zsh, Prezto, and other frameworks.
What if I already use Starship?
Use the Starship integration instead. It provides the same glance output as a proper Starship custom module and fits naturally into your starship.toml.
Can I use this without the VS Code extension?
Yes. The CLI is fully editor-agnostic. Any tool that writes to .keepgoing/ works, including keepgoing save from the CLI itself.
How do I reload my shell config after adding the snippet?
Run source ~/.bashrc for Bash, source ~/.zshrc for Zsh, or open a new Fish shell. The hook takes effect immediately after reload.
What if I want to always show something, even when there is no checkpoint?
Remove the .keepgoing directory check from the snippet. The CLI outputs an empty string when there is no data and always exits 0, so removing the guard is safe.
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 moreCLI
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 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 moreOne command, instant context
Install the CLI, run keepgoing hook install, reload your shell.