Feature request: Track remote/cloud session usage

[ozymandiashh]

Feature Request

Hey! Love the app, just updated to v2.2.0 — great fix with import persistence.

Question / Request: Does the dashboard currently track usage from remote sessions (e.g. Claude Code remote agents, scheduled triggers, headless sessions)? If not, would it be possible to add support for that?

Right now it seems to only pick up local CLI sessions. It would be super useful to have a unified view of all usage, including remote/cloud sessions, in one place.

Thanks for the great work! 🙏

[658jjh]

Thanks for the kind words and the thoughtful ask, @ozymandiashh! 🙏

You've spotted a real gap. Today every data source the collector knows about is a local JSONL/log file scanner — Claude Code projects, OpenClaw, Claude Desktop's local agent mode, IDE extensions, Aider, Continue, etc. Anything that runs purely in Anthropic's cloud (remote agents, cloud-scheduled triggers, headless runs that never write a local session file) just doesn't leave a trail on your machine for us to pick up.

Closing that gap means a new kind of source: instead of scanning the filesystem, the app would hit Anthropic's Admin API (/v1/organizations/usage_report/messages + /v1/organizations/cost_report) using an Admin API key. Concretely, that's:

• Keychain storage for the Admin key (can't sit in ~/Library/Application Support in plaintext)
• A settings screen to paste the key + toggle remote sync
• An API client + normalizer to merge the daily aggregates into the existing sessions schema
• A note that "remote" entries are daily rollups only — the per-message detail modal won't apply to them (the API doesn't return per-message data)
• A clear opt-in, since adding a network round-trip departs from the current "100% local, zero telemetry" pitch

It's a real feature, not a quick fix — most likely v2.3.x territory. Marking this as enhancement and keeping it open so it's visible on the roadmap. If anyone wants to take a stab in the meantime, the integration point would be a new entry in src/collect-usage.js's sources array (currently at L667-675) returning the same session-day shape as the local scanners.

Will report back here when this moves up the queue.