Start tracking Muse Code
- Use Muse Code locally so it writes supported session history.
- Download UsageAtlas and check Muse Code under Settings → Sources.
- Refresh usage and select Muse Code in Today or History. No provider credential or UsageAtlas account is required.
Check the log location
The default session store is ~/.local/share/muse/sessions, with dated folders containing session.jsonl. Custom installations can use MUSE_SESSIONS_DIR or XDG_DATA_HOME. Start UsageAtlas with the matching environment if your files live elsewhere. The reader documentation describes supported schema-v1 events.
Understand the totals
The reader counts supported completed inference and automated-review events. Valid input, cache, and output counters contribute to token totals. It does not turn machine telemetry or child rollups into extra requests. Missing or unsupported records can make history incomplete, so compare the coverage status as well as the total.
Questions, answered
Why is Muse Code cost unavailable?
The integration does not assign monetary costs to Muse usage. A missing cost is unknown, not a statement that those tokens were free.
Can UsageAtlas alert me before a Muse limit resets?
No. This Muse integration reads local history and does not collect subscription allowances or reset times.