Usage node
Local usage snapshots from installed agent CLIs on the canvas.
The Usage tool node shows normalized usage snapshots from agent CLIs that are enabled under Settings → Agents. It is a singleton per project.
What it is (and is not)
| Usage is | Usage is not |
|---|---|
| Local collection from installed CLIs | A cloud billing dashboard |
| RAM-only snapshots (refreshed live) | Persisted history inside .blxcanvas |
| Scoped to enabled agents | A list of every CLI ever discovered |
Only node metadata lives in the canvas file. After restart, data is fetched again.
Open and refresh
- Canvas Tools → Usage, Command Search, Global Agent
usage_node_control, or Notification Center Agent stats shortcut - Loads immediately with progressive skeletons per provider
- Auto-refreshes about every five minutes while mounted and visible
- Manual refresh available in the node UI
Collection is bounded (concurrent providers, capture size, timeouts) so one slow CLI does not freeze the whole snapshot. Failed providers appear as isolated errors; others still render.
Requirements
- Agents installed and enabled in Settings → Agents
- Project open (workspace path is part of the cache key)
- Network/local runtime as required by each CLI’s usage query
Disabled agents and their executable overrides are excluded before collection.
Related
- Agents — discovery and enablement
- Notifications — live agent phase/stats deep link
- Canvas nodes