Summary
Summary
Last week, clicking a request in Studio → Usage opened a per-request detail panel with cache reporting, cache hit rate, token breakdown, and effective cost. As of August 9, that panel and all of that information disappeared: clicking a request now does nothing, and I cannot find an equivalent view anywhere else in Studio.
A Command Code Discord support response pointed me to Studio documentation describing this same click-through detail view, but it does not currently open.
Why this matters
This is not only a missing convenience metric.
I previously used the per-request data to identify and report a billing/usage discrepancy, which was ultimately fixed. With the request-detail view unavailable, users cannot inspect a historical request closely enough to detect, describe, or verify a similar problem.
A total-cost figure alone is not an adequate substitute. It does not show whether a request was cached as expected, whether cache thrash or compaction occurred, whether a model/provider changed, or how the billed amount was derived.
Cache reporting is also necessary to independently evaluate claims such as high cache-hit rates and low effective token cost against a user's own real traffic.
Reproduction scope
I reproduced this in LibreWolf, Brave, and Firefox on mobile. The request-detail view worked in all three browsers last week, so this does not appear to be browser-specific.
Required restoration
Restore the documented per-request detail view in Studio Usage and restore the per-request cache/token/billing breakdown it previously exposed.
Whether this was caused by a UI regression, an implementation change, or an intentional product decision does not change the customer impact: removing the only practical way to inspect and verify the cache behavior and billed cost of an individual request is a material transparency downgrade.
An explanation for the removal would not replace the lost auditability. Studio must provide an equivalent, customer-accessible per-request record with cache, token, and billed-cost breakdowns for each request.
Expected Behavior
Clicking a request in Studio → Usage opens a per-request detail view. That view must provide a customer-accessible breakdown sufficient to audit that request’s billed usage and cost, including cache-related usage / hit-rate information, rather than only a total.
Actual Behavior
Clicking a request row does nothing. No detail panel, modal, or page opens. The previous per-request detail and cache-reporting information is no longer available anywhere in Studio Usage that I can find.
Steps to reproduce the issue
- Sign in to Command Code Studio.
- Open Studio → Usage.
- Locate any request row in the usage list.
- Click the request row.
Expected: a per-request detail view opens.
Actual: nothing happens—no panel, modal, navigation, or error is shown.
Command Code Version
1.22.0
Operating System
macOS
Terminal/IDE
iTerm2
Shell
zsh
Session file (optional)
No response
Fix prompt (optional)
No response
Additional context
OS: macOS Sequoia 15.7.3
Summary
Summary
Last week, clicking a request in Studio → Usage opened a per-request detail panel with cache reporting, cache hit rate, token breakdown, and effective cost. As of August 9, that panel and all of that information disappeared: clicking a request now does nothing, and I cannot find an equivalent view anywhere else in Studio.
A Command Code Discord support response pointed me to Studio documentation describing this same click-through detail view, but it does not currently open.
Why this matters
This is not only a missing convenience metric.
I previously used the per-request data to identify and report a billing/usage discrepancy, which was ultimately fixed. With the request-detail view unavailable, users cannot inspect a historical request closely enough to detect, describe, or verify a similar problem.
A total-cost figure alone is not an adequate substitute. It does not show whether a request was cached as expected, whether cache thrash or compaction occurred, whether a model/provider changed, or how the billed amount was derived.
Cache reporting is also necessary to independently evaluate claims such as high cache-hit rates and low effective token cost against a user's own real traffic.
Reproduction scope
I reproduced this in LibreWolf, Brave, and Firefox on mobile. The request-detail view worked in all three browsers last week, so this does not appear to be browser-specific.
Required restoration
Restore the documented per-request detail view in Studio Usage and restore the per-request cache/token/billing breakdown it previously exposed.
Whether this was caused by a UI regression, an implementation change, or an intentional product decision does not change the customer impact: removing the only practical way to inspect and verify the cache behavior and billed cost of an individual request is a material transparency downgrade.
An explanation for the removal would not replace the lost auditability. Studio must provide an equivalent, customer-accessible per-request record with cache, token, and billed-cost breakdowns for each request.
Expected Behavior
Clicking a request in Studio → Usage opens a per-request detail view. That view must provide a customer-accessible breakdown sufficient to audit that request’s billed usage and cost, including cache-related usage / hit-rate information, rather than only a total.
Actual Behavior
Clicking a request row does nothing. No detail panel, modal, or page opens. The previous per-request detail and cache-reporting information is no longer available anywhere in Studio Usage that I can find.
Steps to reproduce the issue
Expected: a per-request detail view opens.
Actual: nothing happens—no panel, modal, navigation, or error is shown.
Command Code Version
1.22.0
Operating System
macOS
Terminal/IDE
iTerm2
Shell
zsh
Session file (optional)
No response
Fix prompt (optional)
No response
Additional context
OS: macOS Sequoia 15.7.3