AutoJev
Download

Alternative

A CC Switch alternative that routes every request

CC Switch makes it easy to flip which provider a tool uses. AutoJev takes a different approach: your agents stay connected to one local gateway, and each request is routed to the right model. You can bring your CC Switch providers with you in one import.

  • Import Claude Code and Codex providers from CC Switch
  • Routes with load balancing and intelligent selection
  • Scheduled speed tests on your own machine
  • Free and open source (MIT license)
Download AutoJevStar on GitHub

Routes

Create reusable routes and bind your agents to a route ID.

+ Add route

fast

autojev/fast

quality

autojev/quality

cheap

autojev/cheap

balanced

autojev/balanced

lb

autojev/lb

Why people look for a CC Switch alternative

CC Switch is a capable, popular tool. Its model is simple: each tool has an active provider, and you switch it with one click. That works well when you use one provider at a time.

It gets harder when you want several models in play at once — a cheap model for routine edits, a stronger one for hard problems, a local model when you are offline — or when you want the choice to depend on how fast each model actually is today. That is a routing problem rather than a switching problem, and it is the problem AutoJev is designed around.

Some people also just want a smaller tool: AutoJev does not manage MCP servers, Skills or prompts. It does one thing — connect agents to models through a local gateway — and shows you exactly what each request did.

How AutoJev differs

One endpoint, many models

Agents connect once to http://127.0.0.1:9527/v1 and request a route such as autojev/fast. Change the models behind a route without touching agent configs again.

Strategies, not toggles

Weighted load balancing with priority groups, or intelligent selection with balanced, lower-cost, higher-quality or lower-latency preferences. To pin one model, call <provider>/<model_id> directly.

Measured, not guessed

Speed tests record first-content latency and tokens/s for each model on a schedule. The lower-latency preference decides locally from those numbers.

Logs per request

See the agent, route, chosen model, upstream attempts, tokens, first-byte time and estimated cost for every request. Prompts and keys are not stored in logs.

At a glance

CC Switch facts from its GitHub README, as of October 2026.

CapabilityAutoJevCC Switch
Core modelRoute each request to a modelSwitch the active provider per tool
Routing strategiesWeighted load balancing, intelligent selection (single models via <provider>/<model_id>)Active provider; per-tool failover queue
Speed testsScheduled latency and tokens/s— (check their docs)
Protocol conversionChat ⇄ Responses ⇄ Messages; Gemini bridgeMessages, Chat, Responses, Gemini Native
Provider presets6 presets + any compatible endpoint90+ presets
MCP, Skills, promptsNot includedBuilt in
Usage and costPer-request logs; usage by agent/model/providerUsage dashboard by provider and model
LicenseMIT, freeMIT, free

For the full table see AutoJev vs CC Switch.

Move from CC Switch to AutoJev

Most of the setup carries over. Plan on about ten minutes.

  1. 1

    Install AutoJev

    Download the installer for macOS, Windows or Linux from the download page and open the app. The gateway starts on 127.0.0.1:9527.

  2. 2

    Import your providers

    Go to Providers → Import from CC Switch. AutoJev opens ~/.cc-switch/cc-switch.db read-only and imports Claude Code and Codex provider connections — endpoint, key and the model you had set. Duplicates by endpoint are skipped; CC Switch’s own data is not changed.

  3. 3

    Add models and prices

    For each provider, add the model IDs you want to route with their upstream API type and price per 1M tokens. Run a provider test to confirm the key works.

  4. 4

    Build routes

    Create routes such as fast, quality and cheap. Pick a strategy and preference, and let speed tests collect data.

  5. 5

    Hand the agents over

    In CC Switch, stop managing the agents you are moving. Then in AutoJev → Agents, select a route and click Connect. AutoJev backs up each config file before writing it.

What Codex ends up using

After connecting, Codex requests a route from the local gateway. Ask the gateway which models and routes it exposes:

List models and routes
curl http://127.0.0.1:9527/v1/models

Keep CC Switch for MCP and Skills if you like

MCP servers, Skills, prompts and usage history are not imported. You can keep CC Switch for those and let AutoJev handle model routing — just make sure only one app manages each agent’s model settings.

Trademarks

CC Switch, Claude Code, Codex and other product names are trademarks of their respective owners. AutoJev is not affiliated with or endorsed by them. Competitor details are summarized from public documentation as of October 2026 and may have changed.

Frequently asked questions

What is the best CC Switch alternative?

It depends on why you are switching. If you want per-request model routing, speed tests and load balancing across providers, AutoJev is built for that. If you mainly need MCP and Skills management, CC Switch remains a good choice.

Will importing change my CC Switch setup?

No. AutoJev opens the CC Switch database read-only and copies provider connections into its own database at ~/.autojev/autojev.db.

Which CC Switch providers are imported?

Claude Code (and Claude Desktop) providers with an Anthropic base URL, and Codex providers from their config. Entries without a usable endpoint are skipped, and providers whose endpoint already exists in AutoJev are de-duplicated.

Does AutoJev support the same agents as CC Switch?

There is a lot of overlap — Claude Code, Codex, Gemini CLI, Grok Build, OpenCode, OpenClaw and Hermes. AutoJev also supports Kimi Code, oh-my-pi and custom agents. It does not configure Claude Desktop.

Are my API keys safe in AutoJev?

Keys stay on your machine in ~/.autojev/autojev.db and are sent only to the provider they belong to. Note they are currently stored unencrypted, so protect your user account and disk as usual.

Is AutoJev free?

Yes. AutoJev is free and open source under the MIT license, with no account and no markup on model usage.

Keep exploring

CompareAutoJev vs CC SwitchPer-request model routing and speed tests versus one-click provider switching with MCP, Skills and prompt management.FeaturesProvider managementAdd OpenAI, DeepSeek, OpenRouter, Ollama or any compatible endpoint once, or import from CC Switch and Termany.FeaturesSmart model routingExpose routes like autojev/fast to every agent. Load-balance models or let Jev pick by cost, quality, speed or balance.FeaturesOne-click agent setupConnect Codex, Claude Code, Gemini CLI, OpenCode and more. AutoJev edits each native config, backs it up and restores it.

Updated 2026-10-14

Give every agent the right model.

Install AutoJev, add the providers you already pay for, and connect your agents in one click. Everything stays on your machine.

Download AutoJevStar on GitHub

Free & open source · macOS · Windows · Linux