[Feature] No per-surface activity log for subscription usage
Status Open
Maintainer reply None cached
Activity 4 comments · opened Jun 10, 2026
Summary
Claude subscription plans (Max) have no per-surface breakdown of activity.
There is no log showing which interface (Claude Code, claude.ai chat, Claude
Design, API via subscription, etc.) consumed usage at what time.
Impact
- Cannot audit unexpected quota consumption across surfaces
- When a rate limit hits, there is no way to determine which surface caused it
- Claude Design was silently merged into the shared Max quota pool on ~2026-05-28
with no announcement; without a per-surface log, users had no way to detect this
- Contrast: API console (console.anthropic.com) shows per-model token usage with
timestamps for API key users
What would help
A usage log at claude.ai/settings/usage showing:
- Timestamp
- Surface (Claude Code / claude.ai / Design / etc.)
- Model used
- Approximate token/usage amount
Even a rolling 7-day history would be sufficient for the primary use case
(diagnosing unexpected rate limits).
Related
- #33978 — usage analytics consolidation issue (this is specifically about
per-surface historical log, not in-session metrics)
- #59951 — surface labeling in telemetry (backend; this is the user-facing equivalent)
Environment
- Claude Code v2.1.170, macOS 15.x
- Claude Max (5x) subscription
- Multiple surfaces in use: Claude Code, claude.ai, Claude Design
Showing cached comments. Read the full discussion on GitHub ↗
3 Comments
Periodic verification — July 2026
Checked against Claude Code v2.1.197 (latest release as of 2026-07-01).
Reproduction test: ℹ️ Not testable this run — this is a feature request (no timestamped per-surface audit log surface exists yet). The subscription activity-log API probe (
usage/activity,usage/sessions, etc.) requires an authenticated session key that isn't available in this automated environment.Release notes through v2.1.197: no mention of a subscription usage audit log per surface.
This comment is posted automatically every ~20 days to prevent stale-bot closure (threshold: 28 days). Reporter (@blwfish) will close upon confirming resolved.
Periodic verification — July 2026
Checked against Claude Code v2.1.216 (latest release as of 2026-07-21).
Reproduction test: ℹ️ Inconclusive this run — probing for a per-surface subscription activity-log endpoint requires an authenticated
claude.aiorg session that was not available to the automated check. No such endpoint is documented, and the feature request (a timestamped audit log per surface: CLI, web, Design, iOS) remains open on its merits regardless.Release notes through v2.1.216: no mention of a per-surface activity log.
This comment is posted automatically every ~20 days to prevent stale-bot closure (threshold: 28 days). Reporter (@blwfish) will close upon confirming resolved.
Periodic verification — September 2026
Checked against Claude Code v2.1.252 (latest release as of 2026-09-01).
Reproduction test: ✅ Still present — probed four candidate per-surface usage/activity endpoints on
claude.ai/api/organizations/<org>/:No endpoint returns a timestamped per-surface activity record. Separately, there are still no locally-written session records for the Design surface under
~/.claude/projects/— CLI sessions are auditable there, Design sessions are not, which is the asymmetry this request is about.Release notes through v2.1.252: no mention of a per-surface usage audit log.
This comment is posted automatically every ~20 days to prevent stale-bot closure (threshold: 28 days). Reporter (@blwfish) will close upon confirming resolved.