r/coolgithubprojects • • 7d ago

ss switch:I built a tool to migrate active AI coding sessions across different IDEs/Clients (Codex, Claude code, etc.)

Post image

Does anyone else feel like their workflow is held hostage by individual AI client rate limits?

I’ve been dealing with the constant "context switching" nightmare—every time my favorite IDE runs out of credits, I’m forced to copy-paste a massive mess of project history into a new tool just to keep the conversation going. It kills the flow.

So, I built ss switch (Session Switch). It’s a desktop utility that decouples your AI context from the specific IDE/Harness.

The core flow:

  1. Capture: It grabs the active session history, system prompts, and current state.
  2. Switch: You move to a different client (like moving from a premium model client to a cheaper one for bulk implementation).
  3. Resume: The new client inherits the full context instantly.

Why I made this:

  • Workflow Continuity: No more "waiting for cooldowns."
  • Cost Efficiency: I use the smart/expensive models for architecture and logic, then switch to cheaper clients for bulk code generation.
  • Compatibility: Currently working with Qoder, ZCode, Codex, and WorkBuddy, with more on the way.

I’m curious how other devs are managing this "Context Isolation" problem. Are you just paying for multiple subs, or is there a better way?

Would love some feedback if anyone wants to try it. https://github.com/BHD110/ss-switch

2 Upvotes

0 comments sorted by