You have already run dozens of sessions this week and cannot say how many days in a row you have used the CLI, which model pulls the most tokens in your workflow, or whether your work happens in bursts or steadily. /stats answers that in a single panel, built from the transcripts already on your disk.
This article shows what each tab holds, which keys navigate the panel, why today's number can change during the day, and exactly where the command reads its data from.
What does the /stats command show?
Two tabs. Overview brings a GitHub-style activity heatmap, your favorite model, total tokens, session count, longest session, active days, longest streak and current streak. Models breaks usage down by model, with a tokens-per-day chart.
How do you open and navigate the panel?
Type the command inside a normal CLI session.
/stats
While data loads you see Loading your Verboo Code stats…. Then the panel opens and responds to five keys:
| Key | What it does |
|---|---|
Tab | Switches between Overview and Models |
r | Cycles the period: All time, then Last 7 days, then Last 30 days, and back |
↑ ↓ | Scrolls the model list on the Models tab |
ctrl+s | Copies a screenshot of the current panel to the clipboard |
Esc | Closes the panel |
The panel footer repeats the shortcuts: Esc to cancel · r to cycle dates · ctrl+s to copy. The interface labels stay in English in every language, so Last 7 days is the seven-day window and All time is everything on disk.
What does each Overview line mean?
Each line comes from a different calculation, which is why two of them can look contradictory on the same screen.
| Line | What it counts |
|---|---|
| Heatmap | One square per day, one column per week, up to 52 weeks. Intensity is relative to your own history: message-count percentiles define what a weak, average and strong day is |
Favorite model | The model with the most combined tokens (input plus output) in the selected period |
Total tokens | Input plus output summed across all models in the period |
Sessions | How many main transcripts exist in the period. Each session counts once, dated by its first message |
Longest session | Gap between the first and last message of the longest session, not time with the terminal open |
Active days | Days with at least one session, over the total days in the period |
Longest streak | Longest run of consecutive days with a session, inside the period |
Current streak | Consecutive days up to today. This number is always all-time, even with a filtered period |
Most active day | The day with the most messages in the period |
The heatmap ignores the period filter. It always draws your whole history, because its job is to show the long-term pattern. If you switch to Last 7 days and the heatmap stays full, that is correct: only the number lines below it change.
How do you read the Models tab?
The tab lists models sorted by token volume, largest first, with four visible at a time. Each entry shows the token total and a bar chart of that model's tokens per day.
Total tokens: 12,480,331
sonnet-4.6 8,120,004
▁▂▃▅▇▆▄▃▂▁▂▄▆▇▅▃▂
opus-4.6 3,204,112
▁▁▂▂▃▄▂▁▁▂▃▅▄▂▁▁
If the list is empty the panel shows No model usage data available. That happens when the selected period has no recorded model response, which is common in Last 7 days after a week without use.
Use this tab to answer one specific question: which model is consuming your workflow. A heavy reasoning model at the top with few sessions means you are using the expensive model for simple work. To switch models mid-session, the command is /model.
Why does today's number change during the day?
Because history is read from a cache and the current day is always recomputed live. The command keeps a stats-cache.json file in the CLI config directory with everything already aggregated up to yesterday. Each time you open the panel it reprocesses only today, which is still incomplete, and adds it to the cache.
In practice: opening /stats in the morning and again at night gives different numbers on the same day, and that is not a bug. Previous days stay stable, the current day does not.
The Last 7 days and Last 30 days windows do not use the cache: they re-read the session files and filter by date. That is why the first period switch can take a few seconds in a directory with many transcripts, and later switches are instant.
The resumed-session trap. A session that started last month and that you resumed today does not enter the seven-day window, even if it has messages from today. The filter looks at the session's first message date, so the session belongs to the day it was born. If a number does not add up, that is the first place to look.
Where does the data come from?
From local transcripts, not from the server. The command reads the main sessions directory, ~/.claude/projects by default or the path in VERBOO_PROJECTS_DIR, and also includes subagent transcripts, which live in {project}/{session}/subagents/agent-*.jsonl.
That explains three behaviors that usually confuse people:
- A subagent is not a session. Its tokens and tool calls count toward totals, but it does not add to
Sessionsor to the heatmap. - A session belongs to the day it started. A long session crossing midnight stays entirely on the day of its first message.
- A new machine starts empty. With no transcripts on disk, the panel opens with
No stats available yet. Start using Verboo Code!and nothing else. There is no history sync between machines.
For plan consumption, the right panel is another one: /usage shows what the account already spent in the limit window, including other machines. For the current session's cost and duration, use /cost. /stats is activity history, not billing.
Quick questions
Does /stats show data from another machine? No. It reads the local disk, so each machine has its own history.
Can I export the number? ctrl+s copies an image of the current panel to the clipboard. For text data, the source is the stats-cache.json file in the config directory.
Does deleting a project remove its history? Yes. The calculation starts from the transcript files, so a deleted transcript leaves the history on the next aggregation.
Why does the current streak not change when I switch periods? Because it is always computed over all history, on purpose, so that filtering the view does not flatter the number.
Open the CLI, run /stats and look at the heatmap before anything else. In five seconds you see whether your usage is steady or bursty, and that changes how you plan the week. If you do not use Verboo Code yet, start at verboo.ai and run the same command on day one.
![[CC] stuck with no response for 15 minutes: how to break out](/_next/image?url=https%3A%2F%2Fstorage.googleapis.com%2Fverboo-landing-page%2Fblog-uploads%2F1783232445352-verboo-code-cover.png&w=3840&q=75)
