On the left, the connections you have brought in: each holds its own key, address and models. On the right, the places that use them: Vesper itself, Claude Code, Codex, Gemini CLI and OpenCode. The lines between them are what is wired to what, and when one connection fails, the next in line takes over.
Automatic backup every 24 hours, ten kept, encrypted. Export, import, or share a vesper:// link.
Used in
VesperDeepSeek → Kimi
Claude CodeDeepSeekMy relay
CodexDeepSeekMy relay
Gemini CLIKimi
OpenCodeLocal
TRY IT · THE SWITCHBOARD
Four places, all wired. Choose a connection or a place to follow its wires.DeepSeek went down — Kimi took over for Vesper and Claude Code.
An example with made-up wiring. In the app, each connection holds its own key, address and models.
HOW IT WORKS
Five parts of one board.
Connections, places, the relay, failover, and the records that let you trust it.
ConnectionsA catalog, a pasted relay, or a ChatGPT account
PlacesChange only what must change
The relayThrough Vesper, any format to any format
FailoverRest, probe, rewrite and retry
Records and backupsUsage, cost, extensions, backups
01
Bring in a connection.
The catalog groups providers into model makers, clouds and aggregators, and models that run on this computer, filtered by China, overseas or local. Each one is configured from its official documentation, so pasting the key is usually all it takes; local models need no key.
For a relay, paste its address and key, a config file, or a whole example curl command. Vesper finds the address, the key, the newest models and which API formats work, and sets up every place at once. A ChatGPT account can also be a key: you sign in on OpenAI’s own page and enter a short code.
02
Wire it to the places that use it.
Click a place and choose the connection it should use; one connection can feed several places. Click a connection to see where it is wired, test it, list its models, and check its balance and latency.
Wiring a tool changes only its address, key and model. Plugins, hooks, permissions, your environment variables and comments are left alone; the change is checked before it is written, the original is backed up the first time, and you can restore it whenever you like. Your ChatGPT sign-in for Codex is never touched.
03
Relay through Vesper.
With the relay on, Claude Code, Codex and Gemini CLI send their requests to Vesper on this computer, which forwards them in the order you set. It listens only locally and expects a token only Vesper knows.
Formats are converted on the way, between Anthropic Messages, OpenAI Chat, Responses and Gemini, so a tool can use a model its own format does not support. Quit Vesper and every tool goes back to its direct connection.
04
When one fails, the next takes over.
If a connection cannot be reached, returns a server error, is rate-limited or has an invalid key, the request goes to the next one. A connection that keeps failing rests for a while, then gets one test request to see whether it is back.
Some errors are known and fixable, such as a thinking block one provider signed that the next does not accept. Those requests are adjusted and retried on the same connection. Vesper’s own models follow the same order and rules.
05
Know what it cost, and keep a copy.
Every relayed request and every request Vesper makes is counted, without slowing anything down, and priced from a built-in table of official prices. Relays can have a price multiplier, and you can fill in prices for models that lack them. See cost, tokens and requests by day, by connection and by model, and the last 300 requests.
MCP servers, prompts and skills are kept in one list and synced to each tool. The whole setup is backed up every 24 hours, ten copies kept, encrypted, and can be exported or shared as a one-click link.
A WORKED EXAMPLE
A relay key, three tools, five minutes.
You bought access through a relay and want every coding tool to use it.
You say
Here is the curl example my relay sent me. Set up Claude Code, Codex and Vesper to use it, and fall back to Kimi if it breaks.
What happens
Reads the snippet
Address, key and the newest models are found; three API formats respond.
Wires three places
Only address, key and model are written; each original file is backed up.
Turns on the relay
Claude Code can now use a model the relay offers only in OpenAI format.
Puts Kimi second
When the relay rate-limits, requests move to Kimi and come back later.
Starts counting
A price multiplier for the relay makes the cost estimate honest.
What you get
WIRE
Three tools, one connection
Claude Code, Codex and Vesper on the relay, with Kimi behind it.
BAK
Originals backed up
Restore any tool to how it was before, in one click.
COST
A cost view
By day, by connection and by model.
WHAT IT DOES
The small things a switchboard should do.
A catalog of providers
Grouped by maker, cloud and local, filtered by region, configured from official documentation.
A ChatGPT account as a key
Sign in on OpenAI’s page with a short code; choose models and reasoning effort.
Balances and quotas
Balances for several providers, five-hour and weekly windows for coding plans, and custom checks for relays.
Prompts per tool
Kept in a library and written into CLAUDE.md, AGENTS.md or GEMINI.md when enabled.
Skills from GitHub
Installed once, synced to each tool, backed up before updates and removal.
Warnings without secrets
If your shell sets a variable that overrides the wiring, you see its name and line, never its value.
WHAT YOU KEEP
A setup you can restore, and a record you can read.
Nothing is changed that you cannot put back.
BAK
Backup sets
Wiring, MCP, prompts and skills as one set; switch whole sets in a click.
LOG
Usage and cost
By day, connection and model, with the last 300 requests.
CFG
Original config files
Backed up the first time each one was changed.
LINK
vesper:// links
Share a setup, or import one, in a click.
Your keys stay yours.
Keys are encrypted on this computer and shown only by their last digits.
The relay listens only on this computer and requires a token only Vesper knows.