"View session" link + weekly usage bar graph below chat name

Feature request for product/service

Cursor IDE

Describe the request

Feature request for product/service

Cursor IDE — Agent chat header (Glass layout)

Describe the request

Problem: Usage/session context is hard to see while working in Agent. The usage summary is buried (bottom-right, often only near limits unless Settings → Agent → Usage Summary → Always). I want at-a-glance usage in the chat header without hunting.

Requested behavior

Directly below the session/chat name in the Agent header, show:

  1. “View session” — link/control to open session details (model, tokens/time for this chat, or full session panel)
  2. Weekly usage bar graph — compact 7-day bar chart (tokens or $, per day), using the same billing/usage data as the dashboard

Why it matters

  • Plan daily/weekly spend while coding
  • Correlate heavy sessions with usage spikes
  • Avoid surprise limit hits

Note: Settings → Agent → Usage Summary → Always helps today but is bottom-right only and has no weekly bar under the chat title.

Operating System

Windows 11

Operating System (if it applies)

Windows 10/11

Hey, thanks for the feature request. You explained everything clearly.

Part of your workflow is already supported today: Settings > Agents > Usage Summary > Always pins the usage summary in the chat pane. You can also find it by searching for “usage summary” in Settings. But I agree, that’s an account or plan-level indicator, not per-session details and not a bar chart under the chat title.

One note so it’s not confusing: there’s a known bug right now. If the Agents Window status bar is enabled (the row with environment and context %), Usage Summary won’t show even with Always. Workaround: turn it off via View > Status Bar, and the indicator should come back. No ETA for a fix yet.

Both parts of your request are not in the product today: per-session View session with model and tokens, and a weekly chart in the header. I’ve logged the request. Similar requests about showing usage directly in chat are already being tracked in a couple threads:

If there’s an update, I’ll reply here.