Workspace Usage, Credits, and Rolling Windows
How the workspace usage tab reports Codex request counts and token totals, how those numbers relate to your AI credit balance, and what rolling windows tell you about recent activity.
Workspace Usage, Credits, and Rolling Windows
Where you see this in the app
This page documents the Workspace usage tab that appears on workspace-enabled posts. It is the workspace-session view of AI usage, not the broader account settings usage page.
Users may see a mix of:
- wallet balance information,
- request counters,
- token counters,
- recent request rows,
- rolling usage windows.
Wallet balance and credits
The wallet card explains how much AI credit is currently available for the session owner or billed account.
Common labels:
| Label | Plain-English meaning |
|---|---|
AI credits available | The current pool of spendable credits |
Balance | Your usable credit balance right now |
Starter buffer | Temporary starter credit or cushion, if the app grants one |
Add credits | Shortcut to top up before more usage is blocked |
This tab is meant to help users understand whether workspace activity is still affordable or approaching a spend limit.
Request and token counters
The usage tab reports activity in request counts and token counts.
Typical counters:
| Counter | What it tracks |
|---|---|
Requests | How many model calls were recorded for the session |
Total tokens | Combined token volume across the tracked requests |
Input tokens | Tokens sent into the model |
Output tokens | Tokens returned by the model |
Cached tokens | Tokens reused from cache when supported |
Reasoning tokens | Extra reasoning-token usage when the model reports it |
These numbers are operational counters. They are useful for understanding cost and intensity, but they are not a promise that every token type affects billing in the same way.
Recent requests and rolling windows
Recent requests is the event-style view. It helps users answer practical questions such as:
- did the workspace actually make a request,
- did a spike happen recently,
- did usage rise after a specific prompt or automation run.
Rolling windows compress that story into recent time ranges so users can judge whether usage is cooling down or still climbing.
Use the tab this way:
| UI area | Best use |
|---|---|
Recent requests | Inspect individual bursts of activity |
Rolling windows | Judge short-term trends and rate spikes |
| Wallet card | Decide whether top-up action is needed |
What this tab does not mean
This tab should not be read as a full accounting ledger for every app feature.
Important limits:
- it is focused on workspace/Codex activity,
- it is not the same as your full account billing history,
- zero recent requests does not always mean the workspace is broken,
- a healthy wallet does not guarantee the workspace can start if other limits block the session.
If users need broader account-wide context, they should also read the account-side usage documentation.
Related docs
Related docs
See it in action
Previous
Workspace Terminal, Helix, and Codex Tool Access
How the live preview and embedded workspace tools differ, what read-only viewer mode means for Terminal, Helix, and Codex, and how sessions and Codex shortcuts fit into edit-mode work.
Next
Workspace Manual Runs and Run History
How one-off manual runs differ from reusable rules, what queued or failed runs mean, and how to read the Runs tab when automation results look stuck or incomplete.