More
Usage and cost
What Claude Code and Codex used across all your machines, in tokens and in what it would cost on the API.
The Usage page (⌃5) adds up what your agents used on every machine: tokens, requests, and what the same work would cost through the API. It reads Claude Code’s and Codex’s own logs on each machine, so it covers sessions you started anywhere, not only in Muxen.
Reading the page
Pick a period at the top: Today, 7 days, 30 days or 90 days. Today counts from midnight on this computer.
- At API prices, Tokens, Requests and Most used: the totals for the period.
- Each day, at API prices: a chart, Claude Code and Codex in their own colors.
- By model: requests, output tokens, cache reads, all tokens and the cost for each model.
- By machine: which machines did the work.
- Busiest folders: the projects that used the most, with the machine and agent.
Muxen reads the logs when you open the page. Click the refresh button to read them again.
What the cost means
Costs are at Anthropic’s and OpenAI’s list prices for each model. If you use Claude Code with a Claude plan, or Codex with a ChatGPT plan, you don’t pay per token: the number is what the same work would have cost through the API. It’s useful for comparing models, machines and projects, and for seeing what a plan saves you.
A model Muxen doesn’t have a price for is counted in tokens only, and the page names it.
Cache reads are often most of the tokens. They’re much cheaper than fresh input, which is why a large token count can still cost little.
Where the numbers come from
Muxen’s agent on each machine reads the logs the agents already write. Nothing extra is recorded.
| Agent | Logs |
|---|---|
| Claude Code | ~/.claude/projects (or under $CLAUDE_CONFIG_DIR) |
| Codex | ~/.codex/sessions |
Only machines that are connected and reachable are counted. A machine that’s off or disconnected drops out until it’s back; its logs are still there.
Other agents (OpenCode, Gemini CLI, Amp) don’t show up here yet.
From the command line
muxen usage # the last 7 days
muxen usage --days 30
muxen usage --machine beacon
muxen usage --days 1 --json # for scripts
Agents get the same through the agent_usage tool, so you can ask yours “what did my agents use this week, by machine?”. See MCP for your agents.