Track your Claude Code activity
Caldera tracks Claude Code activity two ways. The Obsidian plugin reads Claude Code's local logs and shows tokens by model and day on your profile (counts only, never prompts or file names), and a small Claude Code hook shows each running agent as a drone over the repo it is working in on your GitHub city.
Updated 2026-10-18 · by mjonesone, LLC
Token usage from local logs
- Install the Caldera plugin in Obsidian on the computer where you code.
- The plugin reads Claude Code (and Codex) logs on that machine.
- Your page shows an AI usage section: total tokens, a daily chart, and shares by model and provider.
More machines or tools can be added through Caldera/activity.json. See Track AI token usage.
Agents live on your city
Copy the agent setup prompt from Settings and paste it into Claude Code. It installs a hook so each session appears over its repo: a beam while it edits, circling while it thinks, and parked at Agent HQ blinking amber when it is waiting on you. Task text stays private to you.
What is never published
- Prompts and responses
- File names and code
- Costs
Questions
Does it send my prompts anywhere?
No. Only token counts by model and day are published.
Does it work with Codex?
Yes, Codex logs are read too. Other tools can be added as counts.
Do I need Obsidian?
For token usage from local logs, yes. Agent drones work for GitHub sign-ups too.
Is it free?
Yes.