Local session data
Handoffs and summaries live under .keepitmovin/, which gets its own gitignore.
Open source · MIT · one terminal
Agents hit limits. Your work doesn't.
keepitmovin runs your coding agents in one terminal, watches for rate limits, and hands the next tool a structured record of the goal, changes, blockers, and next step.
npm install -g keepitmovinThen run kim. A first-run wizard detects your installed tools and you pick a fallback order. Zero config to start.
$ kimStarting Claude Code — first in your fallback order⏺ Read(src/auth/refresh.ts)⏺ Update(src/auth/refresh.ts) ⎿ Updated 3 additions, 1 removal● Running tests… ✓ 24 passedClaude usage limit reached ∙ resets 3am╭────────────────────────────────────────────────────────────╮│ Switching tools │├────────────────────────────────────────────────────────────┤│ Claude Code hit its usage limit. Starting Codex… ││ Your context is packed — pick up right where you left off. │╰────────────────────────────────────────────────────────────╯> Reading .keepitmovin/current/handoff.md Picking up: finish the refresh-token rotation● Wired refreshed token into the request client ✓ 24 passed
Local by design
Your continuity stays with your project.
keepitmovin does not upload handoffs or session logs. Your coding tools still connect to their own providers under their own terms.
No extra model call
The active tool maintains the handoff during normal work. keepitmovin does not call another model.
Defensive redaction
Common credential formats are redacted before persistence. Treat local artifacts as sensitive anyway.
Open source
The CLI is MIT licensed. Read the code, audit the behavior, and keep using it for free.
Before you ask
Practical continuity, not a cloned chat.
Does it transfer the private chat session?
No. The next tool starts fresh and reads a live handoff containing the goal, decisions, changes, checks, blockers, and next action.
Is the handoff just another stale context file?
No. The working agent is prompted to revise it after each subtask, while keepitmovin refreshes repository state and recent changes during the session.
Does keepitmovin send my data anywhere?
keepitmovin itself does not upload handoffs or logs. The agents it launches still communicate with their own providers.
Can I switch before a limit is hit?
Yes. Press Ctrl+] to pack the current context and move to the next tool whenever you choose.
Does it commit or push code?
Never. keepitmovin watches, records local continuity, and switches tools. The launched tools retain their own permissions and behavior.
Works with
- Claude Code
- Codex
- Kimi CLI
- Google Antigravity
- opencode
- Grok Build
- Cursor Agent
- GitHub Copilot CLI
- Ollama
The handoff
The handoff is automatic.
When a tool hits its usage limit, keepitmovin detects the exact limit message and starts your next tool. No copy-pasting context, no lost thread, no "where was I".
- Limit hit
A tool hits its limit
keepitmovin watches the terminal and recognizes the exact limit message the moment it appears.
- Context packed
Your context is packed
The handoff file carries your goal, decisions, and recent changes — refreshed as the tool works.
- Next tool resumes
The next tool resumes
It launches with the handoff loaded and picks up where you stopped. You keep typing.
Switch on your own schedule: press Ctrl+] to hand off to the next tool anytime. Everything keepitmovin writes lives in.keepitmovin/ in your project.
The difference
One long session, not five short ones.
You already pay for these tools. keepitmovin chains their limits into one continuous working session.
With keepitmovin
- Hit a limit mid-taskThe next tool starts automatically, context included.
- Context carried overThe handoff file is refreshed as your tools work.
- Watching for failuresLimits, auth errors, and crashes are detected for you.
- Multi-tool setupOne setup wizard, zero config to start.
Running agents raw
- Hit a limit mid-taskYou copy-paste what you remember into a new session.
- Context carried overNothing — the new tool starts blank.
- Watching for failuresYou watch the terminal yourself.
- Multi-tool setupJuggle every CLI's flags and logins by hand.
Supported tools
Works with the tools you already use.
Nine tools supported today. keepitmovin detects what's installed; you pick the fallback order. Ollama sits last — a local fallback for advice and planning when every cloud tool is blocked.
The trade, stated plainly
When keepitmovin switches tools, the new tool starts a fresh session.
It gets the handoff file — your goal, decisions, and recent changes — not the previous tool's private chat history. No coding agent can transfer that today. That's the trade, stated plainly.
Free and open source
The CLI is free. Pro only happens if it’s useful.
Everything you need to keep agents moving is free forever. No trial, account, or usage cap from keepitmovin.
keepitmovin CLI
Everything you need to keep moving.
$0forever
- All nine supported tools
- Unlimited local sessions
- Automatic structured handoffs
- Local project files
- MIT licensed
npm install -g keepitmovinProduct research
Shape what comes next.
Pro isn’t for sale yet. Tell us where continuity still breaks and which advanced features would actually be worth paying for.
- Influence what gets built first
- Join early product conversations
- Get first access if Pro becomes real
Vercel Analytics measures anonymous pageviews and referrers. Privacy details →