March 23, 2026
KeepGoing now greets you when you start a session
The new global statusline and session start experience show what you were working on, what comes next, and where you left off. No searching, no scrolling, no lost context.
You open a terminal, start a session, and stare at the prompt. What were you doing? Which branch? What was the next step? You check git log, scan recent files, maybe grep for a TODO you half-remember leaving yourself.
That friction is gone now.
What changed
KeepGoing can now show your session context the moment you start working. Two things happen:
A statusline that stays with you. Claude Code’s status bar shows a one-line summary of your last meaningful checkpoint: when it was, what you did, and what comes next. Before you type anything, you already know where you are.
[KG] 2 days ago · Refactored auth module · → Add unit tests
While you work, the statusline updates to reflect your current task:
[KG] Fix login validation · editing
A session start greeting. When you open a project, KeepGoing prints your momentum data into the session context. Claude reads it and greets you with a summary: what you were working on, your suggested next step, and any blockers you noted. No tool calls needed on your part. It just happens.
How it works
KeepGoing uses Claude Code hooks and a statusline command, both configured in your settings:
- SessionStart hook: runs
npx -y @keepgoingdev/mcp-server --print-momentumwhen you open a project. This prints your last checkpoint summary, branch, and next step directly into the session. - Statusline: runs
npx -y @keepgoingdev/mcp-server --statuslinecontinuously. It reads your active session transcript to show what you are doing right now, or falls back to your last checkpoint when idle. - Stop and SessionEnd hooks: auto-save a checkpoint when you finish, so the next session always has something to show.
The statusline prefers manual checkpoints (ones you or your AI tool saved deliberately) over auto-saves. That way you see “Refactored auth module” instead of a generic “session ended” message.
All of this runs locally. No network calls, no cloud sync. The data lives in .keepgoing/ at your git root.
Setting it up
Install KeepGoing and configure hooks, rules, and the statusline in one step:
curl -fsSL https://keepgoing.dev/install.sh | bash -s -- claude
If you already have the CLI installed, run keepgoing setup claude to reconfigure.
The setup is idempotent. Running it again will not duplicate hooks or overwrite existing config.
Global by default
The previous version required per-project setup. Now you can configure KeepGoing once at the user level (~/.claude/settings.json) and every project inherits the hooks and statusline automatically. Open any repo, get your momentum. No per-project config files needed.
If you do want project-specific behavior, project-level settings still take priority.
What you actually see
Here is a typical session start. You open a project you haven’t touched in three days:
[KeepGoing] Last checkpoint: 3 days ago
Summary: Added pagination to the search results API
Next step: Wire up the frontend to use cursor-based pagination
Branch: feature/search-pagination
Worked on 8 files on feature/search-pagination
Tip: Use the get_reentry_briefing tool for a full briefing
Claude picks this up and greets you:
Welcome back! You were adding pagination to the search API. Your next step is wiring up the frontend to use cursor-based pagination. You were on the
feature/search-paginationbranch with 8 files touched.
From there, you are already in context. No archaeology required.
Beyond side projects
This feature works just as well when you are juggling multiple repos at work. Context-switch to a different service for a few days, come back, and the statusline tells you exactly where you left off. The cold start problem is not unique to side projects. It happens every time you step away from any codebase.
How to get it
The statusline and session start experience are free. Install or update to the latest version:
curl -fsSL https://keepgoing.dev/install.sh | bash -s -- claude
For the full re-entry briefing with decision history and cross-session intelligence, check out the Pro add-ons.
Your next session should start where your last one ended.