Qoder credits: read both pools before a long run
A healthy personal balance says nothing about the shared pool, and the reset time says when it changes.
2 min read
Qoder credits come in two pools that look alike and behave differently: personal and shared. A developer who checks one and assumes the other is fine will eventually be surprised mid-task, which is why the account's own usage page and the CLI's /usage command both separate them. The UsageAtlas guide describes the same split.
What the two pools mean
| Pool | Typical owner | What it limits |
|---|---|---|
| Personal credits | Your account | Your own work |
| Shared credits | The workspace or team | Everyone drawing on it |
Neither is a token count. Credits are a provider-defined unit, so they answer "can I continue" rather than "which model consumed what".
Checking before a long run
Qoder documents /usage in its CLI, and its credits guide points to Settings then Usage on the website. Either is enough for a quick look, and the CLI is usually the more current because it queries rather than renders.
Two habits make the check useful:
- Read both pools, not just yours.
- Note the reset time if one is shown, so a later drop is not a mystery.
A desktop mirror, and its setup
UsageAtlas can show the reported counters beside your other tools. The connection uses your own account session rather than an API key, which makes the setup a little more manual.
- Open the Qoder account Usage page in a browser.
- In developer tools, open Network and reload.
- Copy the
Cookierequest-header value from the usage request. - In the app, go to Settings, then Sources, find Qoder, expand Connect.
- Paste the cookie, choose Global or China to match the account, then Save and check.
Paste only the cookie value. A copied cURL command or URL will not work, and the value authenticates your account, so keep it private.
What it reports, and what it skips
The connection shows credits used, allowance, remaining balance and any reset time. It does not import CLI session statistics, per-request tokens, models or project history.
That limitation is worth accepting rather than working around. A balance view and an activity log answer different questions, and the tool that answers one well usually does not answer the other.
Reading a credit balance sensibly
Credits are a budget, not a measurement. Two weeks can consume the same credits for very different amounts of work depending on what ran, so a week-to-week comparison is more honest than a per-task one.
The useful pattern is a threshold: decide in advance that a certain remaining balance means "no long agent runs today", and check the figure before starting one.
When the connection goes quiet
Two causes cover almost every case.
Expired session. Cookies do not last forever. Sign in again and replace the value.
Wrong region. Global and China are separate, and a cookie from one will not read the other. If the numbers are empty rather than stale, check the region first.
FAQ
Does the integration read my Qoder conversations?
No. It reads current account credits, not session statistics or message content.
Is the cookie sent anywhere else?
The app sends it to the selected Qoder region and encrypts it locally. It is never uploaded to a UsageAtlas account.
Can I track credits without any connection?
Yes, with /usage or the website. The desktop view is a convenience for people already tracking several tools.
The short version
Read both pools, note the reset, and use credits for capacity planning rather than cost analysis. When the connection stops, suspect the session or the region.
FAQ
Does the integration read my Qoder conversations?
No. It reads current account credits, not session statistics or message content.
Is the cookie sent anywhere else?
The app sends it to the selected Qoder region and encrypts it locally. It is never uploaded to a UsageAtlas account.
Can I track credits without any connection?
Yes, with /usage or the website. The desktop view is a convenience for people already tracking several tools.
Originally published on claudegpt.si