# AIUsage puts twelve AI subscriptions, their quotas and their proxies in one macOS window > AIUsage is a native SwiftUI app for macOS 14 and later that tracks quotas, costs and accounts across a dozen AI providers, and adds four local coding proxies plus a managed CLIProxyAPI gateway. It is Apache-2.0 licensed, actively versioned, and its README is as much a sponsorship page as a manual. **sylearn/AIUsage** — One dashboard to manage all your AI subscriptions — track quotas, costs, accounts, Claude Code proxy, and Codex proxy in one place. - Repository: https://github.com/sylearn/AIUsage - Stars: 732 · Forks: 56 - Language: Swift - License: Apache-2.0 - Published: 2026-10-21 · Updated: 2026-10-21 · Language: en - Canonical page: https://hysenlabs.com/projects/sylearn-aiusage ## Twelve providers, one window The problem is arithmetic. If you pay for a coding assistant, a chat subscription and a model API separately, you now have three dashboards, three refresh buttons and three different definitions of what you have left this month. AIUsage is a native macOS application that puts them side by side, and the README describes it as one dashboard for all your AI subscriptions, tracking quotas, costs and accounts across 10+ AI providers. The provider list in the feature table is the substance of the project. It names Codex, Copilot, Cursor, Antigravity, Kiro, Warp, Gemini CLI in its Code Assist Standard and Enterprise forms, Droid, Claude Code, OpenCode, Kimi and MiniMax, with a second row of accounts on top, since multiple accounts per provider are supported with independent refresh and one-click CLI switching. The multi-account part is the detail that decides whether this is useful. Teams that hold a work account and a personal account of the same tool, or that rotate between two subscriptions, get independent refresh rather than one merged view that lies about which account is which. The implementation language is Swift and the interface is SwiftUI, with a badge stating macOS 14 plus. The repository carries an Xcode project, AIUsage.xcodeproj, alongside the AIUsage directory of sources, a QuotaBackend directory, a scripts directory and a docs directory. There is also a Chinese README, README.zh-CN.md. So the audience is individual developers and small teams who hold several AI subscriptions and want the numbers in one place on a Mac. ## Where the usage numbers actually come from A quota tracker is only as good as its data source, and the README is specific about where the numbers originate. The usage stats feature describes a unified cost and token breakdown drawn from three places: the Claude and Codex proxy archives, token-only non-proxy Codex sessions, and OpenCode's local session ledger. That distinction matters. Where a proxy is in the path, the proxy sees every request and can attribute it exactly. Where no proxy is involved, the app falls back to session records that carry token counts but not the full request detail, which is why the README separates token-only non-proxy Codex sessions from proxied traffic and calls the aggregation source-aware. On top of the raw counts, the app offers per-model trends, time-period analysis and source-aware aggregation. In practice that means you can ask which model consumed the tokens and from which client they came, rather than seeing a single monthly number per subscription that tells you nothing about why it went up. The README also lists per-node usage attribution in the proxy sections, and per-model pricing in the OpenCode proxy, so the cost side is computed from per-model prices applied to attributed usage rather than from the provider's own invoice. That distinction between usage data and cost data is worth keeping in mind when you read any total the dashboard shows, since a per-model price applied locally is not the same calculation as a provider's billing. ## Four proxies that sit between your agent and the model The proxy half of the app is where it stops being a dashboard. Each proxy intercepts a coding agent's traffic and lets you point it somewhere else. The Claude Code Proxy lets you use Claude Code with DeepSeek, GPT, Ollama or any OpenAI-compatible model, and it supports Anthropic passthrough for usage logging, which is how the Claude side of the usage statistics gets its data. The Codex Proxy points the Codex CLI at any OpenAI-compatible upstream, with a unified switcher across subscription accounts and API nodes, and the README highlights a surgical `config.toml` merge. Merging rather than rewriting matters because `config.toml` is where the Codex CLI keeps its settings, and overwriting it would lose configuration the tool needs. The OpenCode Proxy switches OpenCode across upstreams through a managed `opencode.json` block, and it speaks the OpenAI-compatible, Anthropic and Responses protocols, with per-node usage attribution, per-model pricing and optional request logging. The Claude Science Proxy is the unusual one. It launches a local Claude Science without a Claude subscription and routes its inference to a third-party model, with a local virtual login and an isolated sandbox, and an optional adoption mode so that the double-clicked desktop app is login-free too. The README is emphatic that it never touches your real credentials. Each of these is a local process that sits in the request path. That is the mechanism that makes the cost attribution possible, and it is also the thing to think about before you point a coding agent at a third-party model. ## One endpoint per agent, and the CLIProxyAPI gateway The Global Proxy is the layer that ties the four proxies together. Its description promises one fixed local endpoint per agent, hot-swapping the active upstream node with zero CLI restart, per-node cost attribution and automatic cross-track port arbitration. The point of a fixed endpoint is that the agent's configuration does not change. When you switch from one upstream to another, the agent keeps talking to the same local address and the proxy changes what is behind it, so no restart is needed and no configuration file is rewritten. The port arbitration detail matters when several of these are active at once, since each wants a port. Separately, the CPA Gateway runs the official CLIProxyAPI as a managed local gateway. It gives you one OAuth account pool, live model discovery, multi-protocol APIs, optional LAN access and one-click connections to Codex, Claude Code or Science, and OpenCode. And then there is Unified API Providers, which is the configuration side of the same idea. You configure one upstream, with a Base URL, format, key and model library or pricing, once, and it is distributed to Codex, Claude and OpenCode at once. Linked nodes inherit from the master and sync on change, with per-field local overrides. In other words, changing the base URL in one place propagates to three tools, and a local override is available where one agent genuinely needs a different value. The README describes this whole surface in its own feature table, which is the clearest single view of what the app does. Two rows from it set the tone. The multi-account row reads "Multiple accounts per provider, independent refresh, one-click CLI switching", and the Codex Proxy row describes a "unified switcher across subscription accounts and API nodes" with a surgical `config.toml` merge. There is also a Claude Desktop Gateway, which connects the same node pool to Claude Desktop's official third-party mode, with model routes, per-model display names and 1M controls, localhost HTTPS, exact rollback and a verified connection state. The mention of rollback and a verified connection state is the kind of detail that appears when the author has seen people break their setup and wanted a way back. ## A macOS app with an update feed, not a cross platform tool AIUsage is a native macOS application, and the repository says so in the badges: macOS 14 plus, SwiftUI native. There is no Linux or Windows build mentioned anywhere, and the Xcode project at the root of the repository makes the toolchain obvious. This is a desktop app for people who work on a Mac. Distribution is through GitHub releases. The README links the releases page for both the download badge and the version badge, and the project publishes a new version frequently: v0.15.27 on 2026-10-20, v0.15.26 on 2026-10-12 and v0.15.25 on 2026-10-11, with the last push on 2026-10-20. A version number in the zero-fifteen range with releases days apart is a project in active daily development. Updates are handled through an appcast. There is an appcast.xml at the top level of the repository, which is the feed format used by the Sparkle framework for macOS applications, so the app can check for and apply new versions. Two files are worth a reader's attention for a different reason. THIRD_PARTY_NOTICES.md records the third-party components the app ships with, which matters here because the app embeds a proxy, a gateway and sandboxed components rather than being a single self-contained binary. And the QuotaBackend directory at the root, separate from the AIUsage sources, suggests the quota collection logic is a distinct layer from the user interface, which is how you would expect a project to be structured if you wanted to reuse the collection without the window. ## A README that is also a sponsorship page The README carries a sponsors section with a table of partners, and the entries are not decorative. Sidrune AI, API Models, Sucloud and BaiPiao each appear with a promotional code, a description of what they sell and a call to action. The API Models entry, for example, advertises access to models from OpenAI, Anthropic, Gemini, Grok, DeepSeek, GLM, Kimi and Qwen with referral rewards, and the Sucloud entry advertises 400 plus models across text, image, video and music. None of those companies are the AI providers the app tracks. They are API relay and reseller services, which places them in the same category as the third-party upstreams the proxies are designed to route to. That is worth noticing as a reader, not as an accusation: a project that helps you route a coding agent to a cheaper upstream is in a position where an upstream might want to sponsor it. The practical implication is that the README is not purely documentation. The feature table is genuinely detailed and is the best description of the app available, but the surrounding pages mix documentation, sponsorship and promotional copy, and the sections after the feature table in the published README continue past where the documentation was extracted here, with a preview section, an install section and sections for the CPA gateway, the proxies and call analytics. For anyone assessing the tool, the feature table and the releases are the parts to rely on. The sponsorship block tells you about the project's funding, which is information in its own right. ## Where AIUsage is the wrong tool The first wrong case is not being on a Mac. This is a native macOS 14 plus application. If your working machine is Linux or Windows, there is nothing to install, and the local proxy architecture, which depends on running processes on your desktop and on the agent running there too, does not translate directly. The second wrong case is having one subscription. If you use a single provider and know its own dashboard, the proxy layer is dead weight and the quota view duplicates what the provider already shows you, potentially with a different calculation. The third is a policy that forbids routing traffic to a third-party upstream. The proxies exist to send requests somewhere other than the account you pay for, which is the point, and for some organisations that is a rule rather than a preference. The Claude Science Proxy's claim that it never touches your real credentials is reassuring about credential handling and says nothing about whether an inference request may leave your account. The alternative approach for the same job is to keep using each provider's own dashboard for quotas and to configure a single upstream per agent by hand. The difference is that the manual route has no shared cost attribution and no hot swap, so you trade the ability to see everything in one place for fewer moving parts and a smaller attack surface on your machine. For one or two accounts on a laptop, that trade is often worth making. For a dozen accounts across a team, it is not. ## Conclusion Adopt AIUsage if you pay for several AI subscriptions at once and want their quotas, token spend and account state in one place, and if you want a local proxy so a coding agent can talk to a different upstream without re-authenticating. Do not adopt it if you work on anything other than macOS, since it is a native macOS 14 plus app, or if your setup needs nothing more than one provider. Before installing, read the feature table rather than the screenshots, check the sponsors list in the README against your own preferences, and read THIRD_PARTY_NOTICES.md, since the app bundles proxy components that carry their own terms. ## FAQ ### What is AIUsage and what does it track? AIUsage is a native SwiftUI macOS 14 and later application that tracks quotas, costs and accounts across 10+ AI providers, including Codex, Copilot, Cursor, Gemini CLI, Claude Code, OpenCode, Kimi and MiniMax, with multiple accounts per provider and independent refresh. ### Where does AIUsage get its usage and cost numbers? The README describes a unified cost and token breakdown from the Claude and Codex proxy archives, token-only non-proxy Codex sessions, and OpenCode's local session ledger, with per-model trends, time-period analysis and source-aware aggregation, plus per-node attribution and per-model pricing in the proxy sections. ### What do the proxies in AIUsage do? The Claude Code Proxy lets Claude Code run against DeepSeek, GPT, Ollama or any OpenAI-compatible model, the Codex Proxy points the Codex CLI at any OpenAI-compatible upstream with a surgical config.toml merge, the OpenCode Proxy switches upstreams through a managed opencode.json block, and the Claude Science Proxy launches Claude Science against a third-party model in an isolated sandbox. ### Can I install AIUsage on Linux or Windows? Nothing in the repository suggests so. The README badges state macOS 14 plus and SwiftUI native, the project is built from an Xcode project, and downloads are offered through the GitHub releases page for the macOS application. ### What is the CLIProxyAPI gateway inside AIUsage? The CPA Gateway runs the official CLIProxyAPI as a managed local gateway, with one OAuth account pool, live model discovery, multi-protocol APIs, optional LAN access and one-click connections to Codex, Claude Code or Science, and OpenCode. ## Sources - [Issues](https://github.com/sylearn/AIUsage/issues) - [License: Apache-2.0](https://github.com/sylearn/AIUsage/blob/main/LICENSE) - [README](https://github.com/sylearn/AIUsage/blob/main/README.md) - [Releases](https://github.com/sylearn/AIUsage/releases) - [sylearn/AIUsage on GitHub](https://github.com/sylearn/AIUsage) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/sylearn-aiusage