中文

SubsidyBar

SubsidyBar is a lightweight SwiftBar menu item for Codex users.

It displays the API-equivalent value of local Codex usage after subtracting the relevant subscription allocation.

SubsidyBar is designed for Codex usage that is not routed through third-party API providers or gateways. If your local Codex logs include third-party API usage, SubsidyBar cannot separate that from subscription usage.

-$201

That number means the current-period Codex usage would cost about $201 more than the allocated subscription amount if priced at API-equivalent rates.

This is an estimate for visibility and comparison. It is not a billing tool.

What It Tracks

SubsidyBar currently supports Codex only.

If you use multiple subscribed Codex accounts in the same local log set, enter the total monthly subscription amount across those accounts. SubsidyBar does not track accounts separately.

It reads local Codex usage through @ccusage/codex, using:

~/.codex/sessions
~/.codex/archived_sessions

Archived sessions are included by default. SubsidyBar creates a temporary merged CODEX_HOME for ccusage and does not modify your real Codex logs.

Install For SwiftBar

Install SwiftBar first.

Then run:

npx --yes subsidybar setup

During setup, SubsidyBar asks for:

SwiftBar Plugin Folder
Total monthly subscription USD
Weekly reset time

The default plugin directory is:

~/SubsidyBar

If you already use SwiftBar, enter your existing Plugin Folder. If not, press Enter and choose ~/SubsidyBar when SwiftBar asks for a Plugin Folder.

The installer generates:

~/SubsidyBar/subsidybar.5m.sh

That file is a small bash wrapper. Published npm installs call:

npx --yes -p subsidybar@<setup-version> subsidybar swiftbar

The generated wrapper is pinned to the SubsidyBar version used during setup. Re-run setup when you want to update the SwiftBar plugin command.

For a custom SwiftBar plugin folder:

npx --yes subsidybar setup --dir "/path/to/your/plugin-folder"

Local Development

From this repo:

./bin/subsidybar status
./bin/subsidybar details
./bin/subsidybar swiftbar
./bin/subsidybar config
./bin/subsidybar setup

The project currently requires Node.js 24+ because it runs TypeScript directly.

Configuration

Config is stored at:

~/.config/subsidybar/config.json

Show current config:

subsidybar config

Set your total monthly subscription:

subsidybar config set subscription 100

Set the reporting period:

subsidybar config set period quota
subsidybar config set period week
subsidybar config set period month

Set or reset the weekly Codex refresh time:

subsidybar config set reset "Mon 23:08"
subsidybar config set reset auto

quota uses your Codex weekly cycle. For weekly periods, the total monthly subscription is divided by 4. For month, the full total monthly subscription is used.

This weekly allocation is a simple estimate. For example, $100/mo is treated as $25/week, not annualized by calendar weeks.

Usage is aggregated from daily ccusage output. If your quota resets in the middle of a day, SubsidyBar starts counting from the next local date to avoid mixing pre-reset usage into the new cycle.

SwiftBar Menu

The menu bar shows the estimated subsidy number.

The dropdown keeps only the essential details:

Quota: Apr 28 - Apr 30
Vendor loss: -$201
API value: $226.00
Subscription: $25 ($100/mo)
Tokens: 278.00M
Reset: May 4 23:08

If the API-equivalent value is below the subscription allocation, the same line is shown as Unused allocation instead of Vendor loss.

You can change period and subscription from the dropdown.

Notes

SubsidyBar uses public API-equivalent pricing from ccusage. It is not an official OpenAI bill and does not reflect internal Codex subscription economics.

The subsidy number assumes your counted Codex usage comes from subscription quota. Third-party API usage should be kept out of the measured Codex log set.

If @ccusage/codex changes how it reads archived sessions, SubsidyBar may need a small update.