Your browser
The extension requests usage from Claude and ChatGPT using your existing signed-in session.
Your sessions stay yours.
Your juice stays local.
Juicebox needs to know your allowance.
Here’s exactly how it gets there.
A local bridge
Chrome sends normalized usage to Juicebox’s native helper, which writes a file on your Mac.
Your menu bar
The Mac app reads that local usage file and displays your remaining allowance.
No new login to remember.
You sign in on the providers’ own websites. Juicebox does not ask you to paste passwords or API keys. The extension uses the active browser session to request allowance data; the Mac app does not read your browser’s cookie jar.
Usage lives on your device.
The latest browser reading is cached in the extension’s local storage and sent to
~/.juicebox/usage.json
through native messaging. The Mac app itself opens no network connections to fetch your account data.
A fallback, close to home.
When browser readings are unavailable, Codex can read quota events from local session files. Muse and Kimi Code are detected through local configuration or session files; available Kimi quota blocks can also be read locally.
You’re always in charge.
Remove the extension through your browser and quit or remove the Mac app whenever you like. Launch at login is optional. The bridge only accepts the extension ID registered during setup.
This page describes the Juicebox app and extension. Your AI providers handle their own account data. This website’s hosting platform may handle connection and access information separately.