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, Antigravity and GitHub Copilot 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 and the last 24 hours are one click away as charts, and Claude Code and Codex show the tokens they used (today, over the week, by model) counted from their own logs. When a tool's maker reports a problem on its status page, the card says so: a slow or failing tool may not be your limit. 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 room, then opens it in a new terminal in the project folder you choose. It names each tool it passed over and why (not signed in, quota spent, not read yet), and starts the tool on the model you prefer for it, else on the tool's own default. If no tool can be verified, it says so and starts nothing.

Handover

Choose a session from Claude Code, Codex, Cursor Agent or Antigravity. Vibe Usage summarizes it into VIBE_HANDOVER.md in the project folder: the goal, the latest request, the recent conversation, file references and Git branch/HEAD metadata. Working-tree changes are not scanned. Preview brief shows it before anything is written or started; recognizable secrets are redacted and the brief is marked as unverified context. Handing over then uses exactly the previewed session and starts the target tool with a prompt to read the brief. The physical source, account and version stay pinned to the preview, including sessions relocated into a worktree. A file of your own named VIBE_HANDOVER.md is never overwritten; tracked files or a failed Git exclusion stop the handover. Cursor keeps its own project-trust prompt.

Multiple accounts

Claude and Codex keep one sign-in per profile folder. Add account creates a new folder and opens the tool's sign-in there; ~/.claude-* and ~/.codex-* folders you made yourself are found automatically. Each account is shown by the e-mail it is signed in with, and every signed-in Antigravity account is tracked separately too. Pick the primary account, launch Claude Code with a specific account, and set the fallback order and the preferred model per tool. A sign-in not finished within ten minutes takes the account off again, and the next account reuses its folder.

Settings, history and diagnostics

• When a limit runs out (Settings): only suggest it, continue with the tool's other accounts, or then also with the other tools, in fallback order. When the main account has quota again, work that moved off it can go back (off, ask, or on its own once the session is idle). When the computer goes down, open Claude Code sessions can open again where they left off.
• Home order and fallback priority are separate: one is how tools are listed in the window and the tray, the other which tool takes over next. Preferred models set the model Smart Launch and handover start each tool with; left at Default, Smart Launch uses the tool's own default and handover the closest match to the session's model. The eye beside each tool in Home order hides it: it leaves the window and the tray, its quota is no longer read and it raises no alerts. Handover and the command line still use it. One tool always stays visible.
• Project preferences (Settings): give a folder its own tool, model, account and automatic continuation. They narrow what Smart Launch and continuation pick, never replace the verified-quota check, and a project set to off stays off even when continuation is on globally.
• Notifications: choose the low-quota line and quiet hours (they may cross midnight). Quiet hours skip notifications (they are not sent later); quota is still read, work still continues and suggestions wait in the window.
• Handover history lists each continuation with its project, route and outcome. A failed one can be tried again, checked against current quota first.
• Diagnostics shows, per tool, whether it is installed, each account's state and freshness, and the next step, plus the latest unexpected errors (what failed and the system's error code, never the error's text) and each time the window stopped responding for 2 seconds or more. Copy report gives a version without names, e-mail addresses or folders, ready for an issue.
• Backup and restore: export, import or reset the settings. Every save keeps the previous good copy; a damaged settings file is restored from it (and kept aside), and a file written by a