What the limits window shows
Each limit is one card: the provider, its window (5 hours or Weekly), the share used, a bar with a tick at the ideal pace for today and the time until it resets. A model with its own weekly limit gets its own card. Updated just now or Updated 5m ago says how fresh the reading is, the refresh button asks again, and a reading that could not be refreshed is marked Last known value. Open VibeiDE at the bottom brings the app forward.
What under pace and over pace mean
The ideal pace is the share of the window that has already passed: two days into a seven-day week it sits at about 29%. The card compares it with the share you have used. A weekly Claude limit at 47% with 61% of the week gone reads 14% under pace, so at today’s rate the allowance lasts until the reset. Click a card for a chart of your average usage against the ideal pace, with an estimate of where you will end, or, when you are over pace, how long before the reset the allowance runs out at this rate.
Choose what the icon shows
Click the icon to open the limits window; right-click it for its menu (on Linux the menu opens on a click). The icon can follow your highest limit or one limit you choose, and you can hide limits you do not want to see. On macOS it shows bars, the percentage or both; on Windows and Linux, bars or the percentage. The same choices live in Settings, General, Status bar, where Show limits in the status bar turns the icon on or off.
How it compares to /usage and /status
As of November 2026, Claude Code shows plan usage bars in /usage inside a session, and Codex shows rate limits in /status. Each answers for one provider in the terminal you have open. The limits window shows every Claude Code and Codex limit VibeiDE has read in one place, which helps when several agents and projects share the same accounts.
What it does not do
The limits window draws the usage VibeiDE already reads for the app; the icon itself never reads a provider, a credential or a task. It cannot raise an allowance or bypass a provider limit, and slots in VibeiDE only control how many processes run at once. Limits appear once Claude Code or Codex is signed in. OpenCode limits are not shown.
Sources: Claude Code costs and /usage, Codex slash commands.
Related guides
All articles- Claude Code alternatives: 7 tools compared (November 2026)
- TokenEconomizer: how it cuts coding agent tokens
- Claude Code dashboard: usage, analytics and live sessions
- Claude Code weekly limit: when it resets and how to plan
- Claude Code cost: what you pay and how to spend less
- Claude Code statusline: show context, cost and limits