One config, many providers: safely switching Claude Code, Codex and Gemini CLI between API endpoints

Description and use

Folkbench Switch enables safe switching between multiple AI coding CLI providers, preserving settings and workflow context.

Problem

Managing multiple AI coding CLI providers requires manual edits of disparate config files, leading to errors and lost context.

Outcome

Folkbench Switch enables safe, reversible provider switching across multiple AI coding CLIs, reducing manual errors and preserving user context.

Workflow

• 1. Define provider profiles (Base URL + key) in Folkbench Switch.
• 2. Select target CLI and provider profile.
• 3. Review the diff of the target config file.
• 4. Apply the profile – the app writes only connection fields and stashes OAuth if needed.
• 5. Verify provider health via folkbench.com uptime/latency data before switching.
• 6. Continue coding with the new provider without losing context or re‑authing.

Evidence

The tools themselves are great. Switching between providers is still mostly manual.

Source

Profiles, not file copies. You save providers as Base URL + key (several keys per provider, with notes). Applying a profile writes only the connection fields for the target tool.

Source

Show the diff first. Before it writes, you see exactly what will change in the target file.

Source

Stash what you'd lose. When Codex is switched to a third-party provider, the official OAuth credentials are stashed and restored when you switch back.

Source

If a write fails, only that write is rolled back. If the file was changed externally since it was read, the app stops instead of overwriting.

Source