Context Usage tray shows breakdown but no "View Report" / Context Usage Report button (3.12.17, local Windows)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After updating Cursor, the Context Usage breakdown tray still works (context ring → category breakdown), but the previous View Report entry (top-right of that popup) is gone. I only see the close (X) button.
Previously on the same machine/environment I could open the interactive Context Usage Report (Canvas) from that tray and use Debug with Agent for optimization suggestions. Restarting Cursor did not restore the button.
This does not look like the known SSH limitation: I am on a local Windows workspace (E:\...), and Canvas itself still works in this project.

Steps to Reproduce

  1. Open a local workspace in Cursor 3.12.17 (not Remote-SSH / WSL / Dev Container).
  2. Use Agent chat and send at least one message.
  3. Click the context ring next to the input to open Context Usage.
  4. Observe the tray: usage % + category breakdown are shown.
  5. Look at the top-right of the tray for View Report / link to Context Usage Report Canvas.

Expected Behavior

A View Report (or equivalent) control that opens the interactive Context Usage Report in Canvas, with follow-up / Debug with Agent for reduction suggestions — as previously available and described in the 3.7 changelog (“Context usage report in canvas”).

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

  • OS: Windows 10/11 (win32 10.0.26200)
  • Cursor: 3.12.17 (user setup)
  • VS Code / Extension API: 1.128.0 (from About dialog)
  • Commit: 0fb762053c34788bb7760d5673f8a6d4c8589d50
  • Date: 2026-07-17
  • Workspace: Local disk path (not SSH remote)
  • Layout: Reproduced from Agent / Context Usage tray
  • Notes: Restarted Cursor fully; still missing. Canvas creation in this workspace still works.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report. You diagnosed it correctly on your side, and it’s not an SSH limitation.

Good news: there’s nothing to fix locally. The View Report button, the interactive Context Usage Report in Canvas, is temporarily disabled on our side server-side for performance reasons. It was turned off for all versions and platforms around the same time, and it just happened to line up with the 3.12.17 release. So it looks like a regression after the update, but it’s not related to the update. Reinstalling, restarting, or rolling back won’t bring it back.

The Context Usage indicator itself, the ring and category breakdown, uses a separate mechanism, so it stays fully functional for you. That’s expected.

The report will be back once we re-enable it on the server. There’s no exact ETA yet. I’ll post an update in the thread as soon as I have one.

Bummer, definitely missing this, since it helped me discover MCP-related waste in a project that wasn’t even using a plugin I had installed, but was flooding my context windows with enormous amounts of waste anyway.

Without this, is there any other way to get a breakdown of what’s actually occupying each category at some level of detail, even if locally?

Hey, thanks for describing your case. It helps to understand what you needed the report for.

The interactive Context Usage Report in Canvas is currently disabled server-side (details are earlier in the thread), and it was the only place with per-item details using Debug with Agent. Unfortunately, there isn’t another built-in way to get that same level of detail right now.

What still works is the tray you get by clicking the context ring next to the input box. It shows a category breakdown (System prompt, Tools/MCP, Files, Chat history, etc.) with percentages and tokens. It’s the same data source, just without the interactive Canvas overlay report. For your MCP scenario, this should be enough. Check the Tools category in the tray, it shows how much tool definitions take, and you can disable unused MCP servers in settings to free up context.

The full report will come back once we re-enable it on the server. There’s no exact ETA yet. When I have an update, I’ll post it here. I also passed your request for a more detailed breakdown to the team.