Usage
Read the totals and the consumption per assistant — and understand why this is not your bill.
Ajustes > Uso (Settings > Usage) shows what the app managed to measure of your work: a summary with the totals and a reading per assistant.
The totals
The summary brings three numbers:
- Assistants started
- Working time
- Pull requests opened
They give the dimension of the usage in the period read, not a productivity score.
Per assistant
The second part opens the consumption per assistant — Claude, Codex, OpenCode and Grok.
Each panel shows what the app managed to read from that provider.
The rule that avoids a scare
An empty counter is not an error.
The numbers depend on two things:
- On the local capture — what the app recorded on this machine.
- On the provider’s availability — what it exposes for reading.
When one of the two is missing, the panel stays empty or incomplete. That describes the reading, not your usage.
What these numbers are not
The app is not your bill. Elyra’s reading and the provider’s billing can diverge:
| Reason | Consequence |
|---|---|
| Different scope | The app may measure only what went through it |
| Different latency | The provider may consolidate later |
| Rounding | The totals are for reading, not for accounting |
To know how much you owe, check the provider’s account — not this screen.
Result
- You see the totals for the period and the consumption per assistant.
- You know when a panel is empty for lack of reading, and not for lack of usage.
Limits
- The totals are not equivalent to billing. No cost decision should rest on this screen.
- The coverage per provider varies. Not every assistant exposes consumption reading.