i 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

the flow:

* 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.

user:	serkanhaslak
created:	July 26, 2014
karma:	1