A Qoder credit balance answers capacity, not cost
Budgets and usage logs answer different questions. Deciding which you need saves an argument.
·3 min read
A Qoder credit balance is a budget figure, and budgets behave differently from usage logs. The number tells you whether work can continue, not what the work cost in model terms. For a team lead or a solo developer deciding whether to start a long agent run, that is exactly the right question. The UsageAtlas guide explains where the counters come from.
Where the balance lives
| Surface | What it reports | When to use it |
|---|---|---|
/usage in the CLI |
Credit counters for the signed-in account | Before starting work |
| Settings then Usage on the site | Personal and shared pools | Periodic review |
| A desktop connection | Mirrored counters beside other tools | Cross-tool comparison |
The first two are Qoder's own reports and remain the authority. The third is a convenience, and it should be treated as such.
Personal versus shared, again
It is worth repeating because it is the most common misread. A personal balance and a shared balance are separate numbers describing separate budgets. If four people share a workspace, the shared figure can fall while every personal figure looks untouched.
The website exposes both. A CLI check may show only what your account reports, so a periodic look at the site is worth the extra click.
Why credits are not tokens
A token is consumed by a model call. A credit is defined by the provider and may cover a variable amount of work. The two move together loosely.
That has a practical consequence for measurement. Comparing last week's credits with this week's tells you relative consumption, not which task was expensive. If you need the latter, a token-level history from a tool that writes local logs is the right source, and Qoder's credit view is not.
Connecting a desktop view
The connection uses your own signed-in session rather than a programmatic key, which is why the setup looks unusual.
- Open the account Usage page while signed in.
- In developer tools, open Network and reload.
- Copy the
Cookierequest-header value from the usage request. - Paste it into the tracker's Qoder connection.
- Select the region that matches the account, then save and check.
Keep the value private. It authenticates your account, and the app stores it encrypted and sends it only to the chosen region.
Reading an empty view
An empty balance view means one of two things, and neither is a bug in the tracker.
Region mismatch. Global and China are separate services. A cookie from one will not read the other.
Expired session. Cookies end. Sign in again, copy a fresh value, and re-save.
Try the region first when the view is blank, and the session when it is stale.
Using the number well
Write a simple rule and keep it visible: below a certain remaining balance, long runs wait for the reset. That single line converts a counter into a decision, which is the only reason to check it.
For shared credits, add an owner. A pool nobody owns is a pool everybody assumes is fine.
FAQ
Does the connection import token history?
No. It reads reported credits, not per-request tokens or session statistics.
Can I see which project spent credits?
Not through this view. Qoder's own surfaces are the place for activity detail.
What happens when the session expires?
The counters stop updating. Replace the cookie in the Qoder connection to restore them.
The short version
Check both pools, treat credits as capacity rather than cost, and keep the region and session in mind when the numbers disappear.