Get API Key Get API
Docs

Using OpenVeer in CC-Switch

A detailed guide on configuring and using OpenVeer API services in CC-Switch, enabling you to access multiple AI models for assisted programming with simple configuration.

Introduction

CC-Switch is an open-source desktop application that unifies the management of API provider configurations across multiple AI coding CLI tools such as Claude Code, Codex, and Gemini CLI.
It turns tedious configuration file editing into just a few clicks in a GUI — once a provider is added, you can switch between API services instantly, with no need to edit configuration files by hand.

By connecting OpenVeer through CC-Switch, you can easily configure the OpenVeer service for Claude Code and Codex, and switch freely between multiple providers.

Prerequisites

Before you begin, make sure you have:

  1. Installed a supported CLI tool
    At least one supported CLI tool installed, such as Claude Code or Codex CLI

  2. Obtained an OpenVeer API Key
    Log in to the OpenVeer Console to get your API key (starts with sk-)

Note

If you don't have an OpenVeer account yet, please register at OpenVeer first and obtain your API key.

Step 1: Install CC-Switch

Choose the installation method based on your operating system:

macOS

Install via Homebrew (recommended):

brew tap farion1231/ccswitch
brew install --cask cc-switch

You can also download the .dmg installer from GitHub Releases. CC-Switch is signed and notarized by Apple, so it can be installed directly (requires macOS 12 or later).

Windows

Download the .msi installer or the portable .zip from GitHub Releases.

Requires Windows 10 or later.

Linux

Download the appropriate package from GitHub Releases:

  • Debian / Ubuntu: .deb package
  • Fedora / RHEL: .rpm package
  • Universal: .AppImage format
  • Arch Linux: paru -S cc-switch-bin
Note

When CC-Switch is launched for the first time, it automatically detects CLI tools installed on your machine and can import existing configurations as the default providers.

Step 2: Add the OpenVeer Provider

At the top of the CC-Switch main window you can switch between different CLI tool groups. Refer to the steps below based on the tool you want to configure.

Configure for Claude Code

1. Switch to the Claude Code group

Select Claude Code at the top of the main window.

2. Open the Add Provider panel

Click the + button at the top-right corner of the main window.

3. Fill in the provider details

Fill out the form as follows:

Field Value Description
Name OpenVeer Custom label for easy identification
Endpoint URL https://api.openveer.com OpenVeer API base URL
API Key sk-xxxxxxxxxxxx Your OpenVeer API key
API Format Anthropic Messages Keep the default Anthropic-native format

4. Save the configuration

Click Add to save. OpenVeer will appear in the provider list.

Configure for Codex

1. Switch to the Codex group

Select Codex at the top of the main window.

2. Open the Add Provider panel

Click the + button at the top-right corner of the main window.

3. Fill in the provider details

A Codex provider is configured through two blocks:

Fill in the API key in the auth.json block:

{
  "OPENAI_API_KEY": "sk-xxxxxxxxxxxx"
}

Fill in the provider config in the config.toml block:

model = "gpt-5.5"
model_provider = "openveer"

[model_providers.openveer]
name = "OpenVeer"
base_url = "https://api.openveer.com/v1"
wire_api = "responses"
requires_openai_auth = true

4. Save the configuration

Name the provider (e.g., OpenVeer) and click Add to save. CC-Switch will automatically validate both the JSON and the TOML.

Note

About the endpoint URL: Claude Code uses the Anthropic-native format with the URL https://api.openveer.com (no /v1); Codex uses the OpenAI-compatible format with the URL https://api.openveer.com/v1 (with
/v1). Do not mix them up.

Step 3: Switch Providers

Once added, you can switch between OpenVeer and other providers at any time:

Switch in the main window

  1. Select OpenVeer in the provider list
  2. Click the Enable (or Use) button
  3. A "Switched successfully" toast confirms the change

Switch from the system tray

CC-Switch stays in the system tray, so you can switch without opening the main window:

  1. Click the CC-Switch icon in the system tray
  2. Click the target provider name in the menu — it takes effect immediately
Note

About activation: Claude Code supports hot switching — new sessions pick up the new configuration automatically. After switching for Codex, you need to restart the terminal or Codex for the change to take effect.

Supported Models

After switching to the OpenVeer provider, you can use a variety of models in the corresponding CLI tool:

Model ID Strengths Recommended Use Cases
claude-opus-4-6 Strongest overall Complex architecture, hard debugging
claude-sonnet-4-6 Balanced perf & speed Day-to-day coding, code generation
gpt-5.5 Excellent coding skills Complex engineering tasks
gpt-4o High performance, fast Everyday coding, fast iteration
Tip

In Claude Code, use the /model command to switch models; in Codex, use the /model command as well. For the full model list, see the Claude Code guide and the Codex CLI
guide
.

FAQ

Q1: Switching providers doesn't take effect?

  • Claude Code: Supports hot switching — start a new session; if it still doesn't work, restart Claude Code
  • Codex: After switching, restart the terminal or Codex

Q2: API key reported as invalid?

  1. Make sure the API key starts with sk- and is copied in full with no extra whitespace
  2. Go to the OpenVeer Console to confirm the key is active
  3. Check that the endpoint URL is correct (Claude Code uses https://api.openveer.com, Codex uses https://api.openveer.com/v1)

Q3: Format error when adding a Codex provider?

CC-Switch validates auth.json (JSON syntax) and config.toml (TOML syntax). Check that:

  • Brackets, quotes, and commas in the JSON are complete
  • No full-width / smart quotes are used
  • Field names in the TOML are spelled correctly

Q4: Which files does CC-Switch modify?

CC-Switch writes to the configuration files of each tool:

  • Claude Code: ~/.claude/settings.json
  • Codex: ~/.codex/config.toml and ~/.codex/auth.json

CC-Switch automatically backs up these files before switching, so you don't need to edit them by hand.

Q5: How do I view API usage and billing?

Log in to the OpenVeer Console to view API call statistics, token consumption details, and cost trends.

Support and Help

If you run into any issues while using CC-Switch:


Get Started with OpenVeer

Sign up for OpenVeer now, grab your API key, and manage multiple AI coding tools effortlessly in CC-Switch!

This documentation is built and hosted on Mintlify, a developer documentation platform.