Quotio: a macOS menu bar front end for the CLIProxyAPI server

The account juggling problem Quotio targets

Anyone running Claude Code alongside OpenCode or Factory Droid eventually accumulates more than one credential for the same model family: a personal Claude subscription, a work Codex seat, a Qwen Code login. Each CLI tool keeps its own configuration, so switching between them means editing files or re-authenticating. Quotio's stated purpose is to sit between those tools and the providers. It presents itself as a macOS menu bar app that manages CLIProxyAPI, described in the README as "a local proxy server that powers your AI coding agents." The audience is narrow and specific: Mac-based developers who already pay for two or more AI coding subscriptions and want a single local endpoint plus a per-account quota view. It is not a general API gateway and not a chat client.

How the CLIProxyAPI architecture fits together

The data flow is a loop through your machine. Quotio runs CLIProxyAPI as a local server, you connect provider accounts to it through OAuth or by importing credentials, and then the Agents tab rewrites your CLI tools so their requests go to that local server instead of straight to the vendor. The proxy holds the accounts and applies a routing strategy when a request arrives. The README names two strategies, Round Robin and Fill First, selectable in Settings, and says the app supports "automatic failover strategies." Quotio also generates API keys for the local proxy, which is how the CLI agents authenticate to it. A separate Standalone Quota Mode lets you read quota and account data without starting the proxy at all, which is a sensible split: monitoring should not require a running server. One boundary worth noting is that Cursor and Trae appear only under IDE Quota Tracking, and the README is explicit that they "cannot be used as providers for the proxy." They are read-only inputs to the quota display.

Installing Quotio with Homebrew and configuring a first agent

The README states a requirement of macOS 14.0 (Sonoma) or later plus an internet connection for OAuth. Homebrew is the recommended path, and it uses a project tap rather than the default cask repository. Run these two commands in a terminal:

brew tap nguyenphutrong/tap
brew install --cask quotio

Alternatively, download the latest .dmg from the Releases page. The README notes that official release artifacts are signed with Developer ID and notarized by Apple, so no Gatekeeper bypass is required. Building from source is a different route: clone the repository, then open the Xcode project and run the Quotio scheme with Cmd + R.

git clone https://github.com/nguyenphutrong/quotio.git
cd Quotio
open Quotio.xcodeproj

On first launch the app downloads the CLIProxyAPI binary itself. After that, the README's usage sequence is four steps: click Start on the dashboard to initialize the local proxy server, open the Providers tab and authenticate a provider via OAuth or import credentials, go to the Agents tab and pick an installed agent, then click Configure and choose Automatic or Manual mode. Settings exposes the proxy Port, the Routing Strategy (Round Robin or Fill First), an Auto-start toggle, and notification controls. The README does not state which port is used by default, so read the value in Settings before pointing a tool at the proxy by hand.

Where Quotio stops being the right tool

The platform constraint is the first limitation and it is absolute: macOS 14.0 or later, with no Windows or Linux build documented anywhere in the README. The related search phrase for a Windows version has no answer here. The second constraint is the dependency on CLIProxyAPI. Quotio is a management layer, not the proxy, and the README does not document version pinning, checksum verification or a manual override for the binary it downloads on first launch. If that download fails or the proxy misbehaves, the app's own troubleshooting surface is limited to the Logs tab, which the README describes as raw request and response logs. There is also a credential concentration question the README does not address: connecting Claude, Codex, Qwen, Vertex AI, iFlow, Antigravity, Kiro and GitHub Copilot accounts to one local server means one process holds all of those tokens. The README says nothing about how credentials are stored on disk or whether they are encrypted, so treat that as unverified rather than safe. Finally, the auto-failover behaviour is described only as Round Robin or Fill First; the README does not explain what triggers a failover, how a cooling period is decided, or how an in-flight request is retried.

Quotio compared with CLIProxyAPI on its own

The honest alternative is running CLIProxyAPI directly without Quotio. The proxy is the component that actually routes traffic; Quotio wraps it with a SwiftUI interface, a menu bar item, quota charts, OAuth flows and one-click agent configuration. Choosing the bare proxy buys you headless operation, so it can run on a server or inside a container and serve machines other than your laptop, and it removes the macOS 14 requirement entirely. Choosing Quotio buys you the quota view per account, notifications for low quotas and cooling periods, and the Agents tab that rewrites Claude Code, Codex CLI, Amp CLI, OpenCode and Factory Droid configuration for you. The trade is convenience against portability, and it is a real trade: if your coding agents run on a remote box, the menu bar app cannot help them. If they run on your Mac and you are tired of hand-editing config files, the wrapper is the point.

Maintenance, releases and the MIT licence

The repository is not archived, and the last push was on 2026-08-25, which is recent enough to call this a project with current activity. The release cadence visible in the release list is tight: v0.29.0 on 2026-08-22, v0.29.1 on 2026-08-23, and v0.30.0 on 2026-08-25. Three releases in four days suggests either rapid iteration or rapid bug fixing, and the README does not explain which. Upgrade cost is low by design: the README lists a built-in Sparkle updater under Auto-Update, so the app can update itself outside Homebrew, and the Homebrew cask path gives you a second upgrade route. That also means two update channels can disagree, so pick one. The licence is MIT, which permits commercial use, modification and redistribution provided the copyright notice and permission notice are included. This is a description of the licence text, not legal advice; if you plan to redistribute a modified build, read the LICENSE file in the repository root yourself. Note that the MIT licence covers Quotio, not the CLIProxyAPI binary the app downloads, whose own licensing the README does not discuss.

Editorial conclusion

Adopt Quotio if you run several Claude, Codex or Qwen subscriptions on a Mac and want one place to see quota and switch agents over to a shared local proxy. Skip it if your team is on Windows or Linux, or if you need a headless server, since the README documents no non-macOS build. Before trusting it, verify what CLIProxyAPI binary is downloaded on first launch and where it is stored, then read the Port and Routing Strategy settings so you know which port your agents will point at.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes