If you’re looking at VibeProxy to use your plans in all your
coding agents, AutoRouter does that from the Mac menu bar too, and
also picks the model for each turn. It pools the AI subscriptions
you already pay for and adds itself to each app when you click
Enable, with no endpoint to point your tools at. VibeProxy is a
free, open-source menu bar app that runs a local proxy for the
accounts you connect; you point each tool at it and choose the
model there. This page covers how VibeProxy works, then how the
two compare.
Learn more
AutoRouterA Mac app that picks a model for each turn.$0/mo on your plansDownload
VibeProxyAn open-source menu bar app that runs a local
proxy.$0open source
Price
Free to start on your plans
Free, MIT licensed
Fee
on tokens
Provider’s price plus 10% on paid models
None, you pay your providers
Runs
on
Your Mac, macOS 14 or later
Your Mac, macOS 13 or later
Tools
Codex, Claude Code, Cursor, Claude Desktop, T3 and
Terminal
Any client you point at its local endpoint, with guides
for Factory Droid, Amp and Codex
Setup
Install, sign in, click Enable
Install, connect accounts, point each client at
127.0.0.1:8317
Your
plans
Claude, ChatGPT, Grok and Gemini plans, in any harness
Claude Code, Codex, Gemini, Kimi, Qwen and Antigravity
logins, plus a Z.AI GLM key
Model choice
Your rules, then a model that clears the quality bar
The model each client asks for
Each
request
Every turn shows its model, cost and why
Live connection status for each account
Requests go
Through AutoRouter’s servers to each provider
Through the proxy on your Mac, to each provider
A model picked for each turn, with no config to
write
Added to each app with one click, no endpoint to
set
What the app is, how setup works, and how your clients reach it.
A menu bar app around CLIProxyAPI
VibeProxy is a native SwiftUI menu bar app by Automaze, MIT
licensed, with more than 3,400 stars on GitHub. Its README
says it lets you use your existing subscriptions with AI
coding tools such as Factory Droids. It bundles
CLIProxyAPI, the
open-source proxy, and handles the OAuth logins, token
refresh and API routing for it (README).
How setup works
Download the zip for Apple silicon or Intel from the
releases page and drag the app to Applications. It’s signed
and notarized. Open Settings from the menu bar icon, and the
server starts. Click Connect for each account, which opens a
browser sign-in, or Add Account to paste a Z.AI GLM key.
Then point each client at the proxy. For Codex, the README
gives this line for ~/.codex/config.toml:
base_url = "http://127.0.0.1:8317/v1"
Accounts, failover and overrides
You can connect several accounts per provider; requests
rotate round-robin and fail over when one is rate-limited.
Turning a provider off hides its models at once. An option
routes Claude requests through Vercel AI Gateway, and
another opens the proxy to your local network. For anything
else, CLIProxyAPI settings go in
~/.cli-proxy-api/config.yaml, which VibeProxy
merges with its defaults and reloads live.
What it does well
It’s free and open source, so you can read the code that
handles your requests.
It turns CLIProxyAPI into a native Mac app with one-click
sign-ins, so there’s no YAML to start.
It covers a wide set of accounts, including Gemini, Kimi,
Qwen and Antigravity logins.
It pools several accounts per provider with round-robin
and failover.
Any client that speaks the APIs it serves can use it,
including Factory Droid and Amp.
It updates itself daily through Sparkle and can start at
login.
Where it gets harder
You choose the model. VibeProxy serves the model each
client asks for and doesn’t judge how hard a request is.
Each client needs its own settings pointed at
127.0.0.1:8317. The README notes that one of
Codex’s two config shapes breaks some of Codex’s own
ChatGPT features.
Its window shows which accounts are connected, not which
model ran each request or what it cost.
Settings beyond the app’s switches mean editing
CLIProxyAPI’s YAML.
Intel builds are marked untested in the README.
How AutoRouter differs
VibeProxy gives your clients a local endpoint and serves the model
they ask for. AutoRouter chooses the model for every turn, using
models it includes and the plans you already pay for.
It picks the model for each turn
AutoRouter shows up as one more model in the picker you
already use. While it’s selected, it works out how hard each
turn is and only considers models that clear the quality bar
for it. Hard work goes to the strongest model your plans
cover, and quick work to the one that costs you least. Your
own plain-English rules go first, such as “Use Claude Opus
5.5 for UI work.” Every turn shows its model, what it cost
and why.
Enabled in each app for you
There’s no endpoint to type into each client. You sign in,
sign in to your plans and click Enable for each app.
Enabling adds AutoRouter to Codex’s
config.toml and Claude Code’s
settings.json after saving a copy of each file,
and disabling it switches the app back. Frontier and
open-weight models come with AutoRouter, kept current by its
team, with no keys to add.
Your plans, stacked in any harness
You can connect the AI subscriptions you already pay for and
use them in any harness, such as a ChatGPT plan in Claude
Code. When one account reaches its limit, AutoRouter moves
to the one with the most room left before it spends any
credit. Free connects two subscriptions and Pro connects any
number.
Built for teams to roll out
Enterprise rolls AutoRouter out to every Mac through Jamf or
another MDM, with nothing for anyone to set up. Admins get
allowed models, team budgets and zero data retention in one
place, spend by team, project or ticket, and SSO, SCIM and
an audit log.
What it costs and what it can’t do
Routing across your plans is free, and paid models bill at
the provider’s price plus 10% (pricing). It needs macOS 14 or later, and it doesn’t give you a
raw local endpoint for your own scripts and other clients
the way VibeProxy does. It sometimes misjudges how hard a
task is. Requests pass through AutoRouter’s servers on their
way to each provider; see privacy for
what is kept.
Which one to choose
Choose VibeProxy if you want a free, open-source local
endpoint for clients such as Factory Droid or Amp, use
accounts like Qwen or Antigravity, or want requests to stay
between your Mac and each provider.
Choose AutoRouter if you want each turn in every coding
agent you use sent to the right model, with your plans used
first and nothing to point your tools at. For other options,
read
Model routers for Claude Code and Codex, compared.
Setup, side by side
The steps each one’s own docs give, as of November 19, 2026.
VibeProxy
DownloadThe zip for your Mac from the GitHub releases page, then
drag the app to Applications.
Start the serverOpen Settings from the menu bar icon, and the proxy
starts.
Connect accountsClick Connect for each account and finish the sign-in in
your browser.
Point your clientsSet each client’s base URL to
http://127.0.0.1:8317, for example in Codex’s
config.toml.
Sign inSign in or create a free account, then sign in to your
plans.
Enable your appsAllow Accessibility and click Enable for each app.
Pick AutoRouterIn a new session, choose AutoRouter from Codex’s model
menu, or with /model in Claude Code.
Questions
What people ask about VibeProxy.
What is VibeProxy?
A free, open-source macOS menu bar app by Automaze that runs
CLIProxyAPI on your Mac. It signs in to the accounts you
connect and gives your coding tools a local endpoint at
127.0.0.1:8317.
Is VibeProxy free?
Yes. It’s MIT licensed and free to download. You pay for the
accounts you connect, at their own prices.
Which accounts does VibeProxy support?
Its README lists sign-ins for Claude Code, Codex, Gemini,
Kimi, Qwen and Antigravity, plus Z.AI GLM by API key.
AutoRouter connects Claude, ChatGPT, Grok and Gemini plans.
How does VibeProxy relate to CLIProxyAPI?
VibeProxy bundles CLIProxyAPI and gives it a Mac interface
for sign-ins, server control and updates. Advanced settings
still go in CLIProxyAPI’s config.yaml. See
CLIProxyAPI vs AutoRouter.
Does VibeProxy pick a model for me?
No. It serves the model each client asks for and rotates
requests across your accounts for a provider. AutoRouter
picks a model for each turn by how hard it is, after your
own rules.
Does VibeProxy work with Codex?
Yes. Its README sets base_url in Codex’s
config.toml to the proxy, or adds a named
provider, and it has guides for Factory Droid and Amp.
AutoRouter adds itself to each coding agent you use when you
click Enable.
How is AutoRouter different from VibeProxy?
Both are Mac menu bar apps for the plans you pay for.
VibeProxy runs a local proxy you point each client at and
serves the model they ask for. AutoRouter adds itself to
each app, includes its own models, picks a model for each
turn with its reasons and cost, and rolls out to a team’s
Macs through MDM.
What does AutoRouter cost?
Routing across your plans is free, and paid models bill at
the provider’s price plus 10%. See
pricing, or estimate a month with and
without AutoRouter in the
savings calculator.
Your plans, every turn routed
Install the Mac app, sign in to your plans and click Enable.