Enable the source and refresh
Open Settings → Sources and confirm the provider is enabled. Installing a coding tool alone does not create usage history. Use it once, allow it to write compatible records, then refresh UsageAtlas. Check the source's status before interpreting an empty chart as zero usage.
Check the selected account
For a key, token, or cookie connection, expand Connect and choose Save and check. Verify the region for Kimi Code or Qoder and the organization ID for Kilo Code. A saved credential takes precedence over environment values and supported local credentials. Restart the app after changing startup environment variables.
Check what that integration can report
Warp, Kimi Code, Kilo Code, GitHub Copilot, Factory / Droid, Amp, and Qoder currently provide allowances or balances. Look in Limits; they do not supply historical token charts. Antigravity CLI, Pi / OMP, and Muse Code read local files with specific supported formats. See local history coverage if one of those is missing.
Use the current app version
Download the current UsageAtlas release to get the supported integrations and parser fixes. UsageAtlas is free and open source. If the source still fails, report the provider name and redacted error on GitHub. Never include account keys, cookies, or raw session logs.
Questions, answered
Will signing up for UsageAtlas fix missing local files?
No. Local tracking needs no account. Cloud restore can recover previously saved history, but it cannot create activity that was never collected.
Does an unavailable cost mean my usage was free?
No. The source may omit costs or the model may lack a known price. UsageAtlas leaves those costs unknown.