Verboo Code: how to see how much of your limit is already used with /usage
Back to the blog
Articleverboo codetutorialhow todev toolsprodutividade

Verboo Code: how to see how much of your limit is already used with /usage

MafraNovember 16, 20266 min read

You are halfway through a big refactor and need to know whether there is room left. You open the terminal, type /usage, and the panel shows up. The problem is that it prints several similar lines, with hours, a percentage and a reset date, and almost nobody knows which one decides whether to start the work now or wait for the window to roll over.

This piece shows what /usage actually reads, what each line means, why its number does not match /cost, and why the command prints nothing when you run the CLI headless.

What does the /usage command do?

It opens the settings panel on the Usage tab and shows plan consumption, one line per limit window. It does not measure the current session: it asks the server and returns the percentage already spent in each window, the window duration in hours and when that window resets.

Flowchart: /usage opens the panel, each window shows hours and used percentage, plus the reset date; if a balance warning shows, check /login and the connection
The /usage path: open, read the window, see when it clears.

How do I open the panel and read each line?

Type the command inside a normal CLI session. If you have more than one limit window, the output repeats in blocks, one per group.

/usage

The output follows this shape, with numbers coming from your account:

Pro
24h: 38% utilizado
Renova em 16/11/2026, 09:00:00
168h: 12% utilizado
Renova em 21/11/2026, 14:30:00

Each pair of lines is one window: the first carries duration in hours and used percentage, the second carries when that window clears. The panel re-queries every 10 seconds while it stays open, so you can park it in a tmux pane and watch it during the task.

What you seeWhat it means
24h: 38% utilizadoA 24 hour window, 38% of that window's limit already spent
Renova em ...Local date and time when the percentage goes back to zero
A janela começa no próximo uso.No reset is scheduled: the count starts when you use it again
Sem limite de janela.The group shows up but has no per-window limit

Press Esc to close. There is no flag: the command does not accept /usage --json or a window argument. If you want the panel, that is it.

One caveat: the strings in this panel are hardcoded in Portuguese in the current build, regardless of your terminal language. So you will read utilizado and Renova em even on an English machine. The values are the part that matters.

Why do /usage and /cost show different numbers?

Because they measure different things. /cost sums what the current session consumed, with cost, API duration, wall duration and tokens per model. /usage shows what the plan already spent in the window, including everything you ran in other sessions, other projects and another machine.

In practice: a fresh session with /cost at zero can sit next to /usage at 80%. If the question is "is there room for more work now?", read /usage. If the question is "what did this task cost?", read /cost. The /cost tutorial is at how to read session duration and cost with /cost.

What does each panel warning mean?

The panel swaps the status line when the state is not normal. There are four messages, and each one asks for a different action.

Message in the panelWhat is happeningWhat to do
Não foi possível consultar o saldo. Tente novamente.The server query failed or timed outCheck /login and the connection, leave with Esc and reopen
Uso pausado até a confirmação das solicitações anteriores.The account is waiting for earlier requests to settleThis is not a limit hit: wait for accounting to close and reopen the panel
Limite de uso atingido. Aguarde a renovação.The window percentage hit 100%Check that window's reset date before retrying
Carregando consumo…Still waiting for the first responseIf it hangs, it is the first case

The headless trap. /usage is a command that opens UI, not a text command. Running the CLI headless, the command exists but prints nothing: the panel is never drawn and the output stays empty. If you need the number inside a script or an agent, query the data through the API instead of calling /usage and reading stdout.

Where does the number come from?

From the /api/me/usage-windows route, authenticated with your session token. The query has a 10 second timeout per attempt, tries up to three times and honours Retry-After on 408, 429, 500, 502, 503 and 504 responses, with a 35 second overall deadline. That is why the panel sometimes takes a few seconds to leave Carregando consumo… instead of failing on the first attempt.

If your account is in the free-token period, the panel adds an extra block: how many free tokens remain, how many were used out of the total (input plus output, no expiry) and a notice when some requests are still awaiting confirmation. When that block is absent, the panel points to the dashboard for a detailed view.

Can I see usage per model here?

No. /usage is per window, not per model. To see which models pulled the session's consumption, use /cost, which breaks down tokens and cache per model. To see what is filling the context, use /context. Three different questions, three different panels.

Quick questions

Does /usage count what I ran on another machine? Yes. The percentage belongs to the plan, not the machine, so sessions on another VPS or another project land in the same window.

Do I need to restart the CLI for the number to update? No. The panel re-queries every 10 seconds while it is open.

Does the percentage go back to zero when I close the terminal? No. The window lives on the server and resets on the date the panel shows.

Before starting the next refactor, open the CLI, run /usage and look at the shortest window. If it is near the top, the decision takes five seconds. If you are not on Verboo Code yet, you can start at verboo.ai and run the same command on day one.

Enjoyed this article?
Share knowledge with your network.
// Read also

Related articles