Show HN:`npx continues` – resume same session Claude, Gemini, Codex when limited
github.comi kept hitting rate limits in Claude Code mid-debugging, then hopping to Gemini or Codex. the annoying part wasn't switching tools (copy-pasting terminal output doesn't bring tool-use context with it) — it was losing the full conversation and spending 10 minutes re-explaining what i was doing.
so i built *continues*. it finds your existing AI coding sessions across five tools (Claude Code, GitHub Copilot, Gemini CLI, OpenAI Codex, OpenCode), lets you pick one, and generates a structured handoff so you can continue in another tool without starting from zero.
npx continues # interactive TUI: pick a session, pick a target
continues scan # see what it finds (read-only)
continues claude # jump into your latest Claude Code session
continues resume abc123 --in gemini # hand off a specific session to Gemini
* scans the current directory first (so you see what's relevant), then shows everything
* you pick a session + a target tool
* it generates a handoff doc: recent conversation, cwd, files modified (best-effort), pending tasks
* launches the target tool with everything injected inline — no extra "go read this file" step
what it's not:
* not "true migration" — it's context injection. you get recent messages + metadata, not a full replay (pls come up with PR for full session reprod)
* rate limit detection is manual for now — you run it when you know you're blocked, no auto-detect yet
* session formats are mostly undocumented and can change anytime (this is the biggest maintenance risk)
* local file parsing only, no API calls — your data stays on your machine
curious if anyone else actually juggles multiple AI coding CLIs, or if most people just commit to one and wait out rate limits. would love to hear how you handle tool-switching + context today + feedbacks on context quality migrations and feedbacks are welcomed. Although I rarely hit my limit in my $20 a month Codex plan, I can imagine this would be very useful. The issue I have more often is that I will start a conversation in ChatGPT, and realize an hour later that I needed all that context to be in Codex, so I’ll generally ask ChatGPT to give me a summary of all facts and a copy‑paste prompt for Codex. But maybe there is a way to extract the more useful content from a chat UI to an agent UI. imo an agent learns way more by watching the raw agentic flow than by reading some sanitized context dump. you get to see exactly where the last bot derailed and then patched itself. give that a shot—handing over a spotless doc feels fake anyway. interesting idea. At first I just thought that it's sth like the "fg" command but for AI sessions. i.e. just resume the last AI session you "paused". honestly, that in itself would be valuable, though simple. This idea, i. e. actually "moving" context form one agent to another is even more interesting. yeah, thanks for sharing your thoughts! the original idea was to reproduce the exact same session on other coding platforms using the jsonl schema of each, but after seeing how the microsoft ai engineers on copilot-cli handle session continuity (major respect to them), i switched to single-message compression and it's been working very well for me. most of us are juggling between $20 chatgpt and $20 claude subscriptions, so being able to hop between them by copying stuff over properly is clutch. give it a shot and lmk what you think, or drop a pr if you’ve got tweaks! this is exactly what i needed. thanks for dropping it in npx ease - added it to my raycast snippets enjoy it! thats a great tool thx!