DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to switch Codex and Claude Code to a new API provider with Uni Switch

Add a provider once with its API address and key, then switch between providers with one click.

Credentials. Your API key is stored on your own machine, so keep the computer and its config backups private.

Who it is forA developer who has an API address and API Key from a provider and wants Codex or Claude Code to use it without editing config files by hand.

The problemSetting up each client by hand means finding the right config files, the right protocol and the right model IDs for each provider.

The outcomeThe provider is saved, the client is configured to use it, and the client restarts into a new conversation with the provider's models.

What you need first

  • A desktop computer running Windows, Linux or macOS
  • An API address and API Key from your provider
  • Codex or Claude Code installed on the same machine
  • For building from source: Node.js 20 or newer, Rust 1.89 or newer, and the platform build tools listed in the README

Steps

  1. Download the installer for your system from the GitHub Releases page, for example uni-switch_0.5.25_x64-setup.exe on Windows x64.
  2. Open Uni Switch and select Codex or Claude Code on the left. For Claude Code, choose desktop or CLI.
  3. Click 添加供应商, enter the API address and API Key, then click 添加并使用.
  4. Restart the client as prompted and start a new conversation to confirm the model and thinking level.
  5. To switch later, click 使用 on the provider's row.

Prompt for your agent

Using the uni-switch project at github.com/dieqiyun/uni-switch, add a provider with API address <api-address> and the API key stored in <key-env-var>, then confirm the provider appears in use for the chosen client. Expected output: the provider listed as in use, with a note to restart the client and start a new conversation. Verify that the local config backup was created before the change.

Caveat. Claude desktop third-party model support depends on the client's own Gateway support, and a successful build does not mean every client version was tested on real hardware.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page