Skip to content

Docs

Tokens, cost and rate limits

Right now shows what each agent's session used so far and how much of its rate limits is left, as Claude Code and Codex count it themselves.

Updated 13 October 2026

With several agents at work, the question is which one is about to hit its limit, and what the afternoon cost. Right now answers it from what each agent's own program wrote down: Hamloy counts nothing and prices nothing itself.

HERE NOW  2 sessions

claude   5-hour limit 84% used, starts over in 40m    weekly limit 41% used, starts over in 3 days
codex    weekly limit 2% used, starts over in 5 days   Plus plan

claude  working  active just now
  laptop · ~/code/pebble · on main
  43k tokens · $0.42 · claude-haiku-5-5

codex  idle  active just now
  laptop · ~/code/pebble · on main
  1.4M tokens · gpt-5.6-luna

This needs the hamloy program on the computer where the agents work.

What a session's row says

  • Tokens: everything the session used so far, in and out, with what was read again from the vendor's cache. Hover the line for the split.
  • Cost: only where the agent's program gives one.
  • The model its last answer came from.

The numbers are the session's own. They arrive when a turn ends, once a minute during a long turn, and when the session is over.

The limits strip

One line for each agent of each person: how much of its 5-hour and weekly limit is used, and when each starts over. A limit that is 80% used or more is red. A limit is yours with the vendor across every project, so the line takes the newest word from any of your sessions here in the past day, and drops a limit once its window has started over.

Claude Code and Codex

They write down different things, and Hamloy shows what each gives.

Claude Code Codex
Tokens and model from its transcript from its session file
Cost when Hamloy is in its status line Codex gives none
Rate limits when Hamloy is in its status line, on a Pro or Max plan from its session file, with the plan's name

Claude Code hands a session's cost and limits only to its status line. hamloy statusline on puts Hamloy's line there (--below keeps your own above it), and from then on the row has the cost and the strip has Claude Code's limits. Its cost is what Claude Code works out at list prices, so on a subscription it is what the session would have cost, not a bill.

An agent without the program (Cursor, Claude on the web) reports none of this.

Keeping it to yourself

hamloy config usage off keeps what your sessions use on your computer; the board still shows who works where. hamloy config usage on sends it again. Everyone on a shared project sees the same Right now, so they see what your sessions report.