mustafacagri / vibe-usage

**English** · Türkçe · Deutsch · Español · Français · Italiano · Português · Nederlands · Polski · 日本語 · 한국어 · 简体中文 · Русский
# Vibe Usage
**Every AI coding subscription you pay for, in one menu-bar window.**
See how much quota Claude Code, Codex, Cursor and Antigravity have left, and keep working when a limit runs out:
your session continues on another account or tool, without re-explaining the task.
Windows tray · macOS menu bar · 13 languages · no passwords, no tokens stored
**Download for Windows and macOS** · Terminal: `npm install -g vibe-usage-cli`
 Watch in full resolution (MP4) 
## Why
If you code with several AI tools, you hit the same wall over and over: the 5-hour limit runs out mid-task, you open
another tool, and you start explaining the task from scratch. Each provider shows its usage somewhere different, if at
all.
Vibe Usage reads the sessions already signed in on your machine and shows every limit side by side: how much is left
and when it resets. When one tool is running low, it starts the next one with verified quota in your project folder,
and writes a briefing of the current session so the new tool can continue where the old one stopped.
## Features
### Quota at a glance
Every limit of every account: 5-hour and weekly windows, per-model scopes, spend pools. Countdowns show when each one
resets, and a limit that will run out before it resets says when, at the current pace. The last 7 days are one click
away as a chart. If a refresh fails, the last reading stays visible and is clearly marked as stale. Unknown numbers are
never shown as a full quota. The tray icon is a ring that fills with what your first tool has left; hover it for every
tool. Show each tool's accounts side by side, order the tools as you like, and switch to a compact view with one line
per account.
### Keep working when a limit runs out
When Claude Code or Codex stops because its account hit the usage limit, the session continues where there is room:
on the same tool's account with the most quota left, then, if you allow it, on the next tool in your fallback order.
Opt in and it happens on its own; otherwise it is one click. The trigger is the tool's own "usage limit reached"
record, never a percentage, so two agents never work on the same folder at once. A Claude Code session moves to your
other Claude account **whole** and goes on by itself; other tools get a handover brief (kept out of `git status`).
An account running low offers the same move early, and warns if its session is still running. When the first account
has quota again, bringing the work back is one click.
If the computer goes down (a restart, a crash, a power cut) while Claude Code sessions are open, they open again where
they left off, on the account they belong to, and a turn that was cut off goes on. Suggested by default, or on its own
if you choose. Sessions you closed yourself stay closed.
### Smart Launch
Picks the first tool in your priority order whose quota is **verified** to have roo