Show Claude's context breakdown (what /context shows) from the context meter

[spiky02plateau]

What I'm missing

In a Claude thread, typing /context does nothing useful, because it's a Claude Code CLI built-in and T3 talks to Claude through the Agent SDK. The context meter gives me one number. On long sessions the number alone doesn't tell me what to do about it. Whether I compact, turn off an MCP server, trim memory files or start a fresh thread depends on what is filling the window.

What already exists

The Agent SDK version in the lockfile (0.3.170) exposes query.getContextUsage(). It returns the same data /context renders: totalTokens, maxTokens, percentage, per-category token counts (system prompt, tools, MCP tools, memory files, messages and so on), plus memoryFiles, mcpTools, agents and skills with their own token counts. T3 doesn't call it anywhere on main today.

Proposal

When the context meter popover opens on a Claude thread with a live session, the server asks that session for getContextUsage() and the popover lists the categories with their token counts under the existing total. It's on demand only: no polling and nothing persisted. With no live session, the popover stays exactly as it is now. Claude only, behind the existing context meter setting.

Optionally, typing /context in a Claude thread opens the same popover, so the habit from the CLI keeps working.

Questions

1. Is an on-demand request from the web client to the live provider session an acceptable shape here, or would you rather the server attach the breakdown to usage updates it already sends?
2. Popover only, or popover plus the /context shortcut?

If the direction works for you, I'm happy to send the PR.

[josephv123]

+1. I think this and #12074 are one feature. Fetch the breakdown from getContextUsage() on demand, show it in the meter popover, and have /context in a Claude thread render the same breakdown as a compact card in place of the raw tables. Claude Code Desktop already renders it this way (described in #12074).

On your second question: popover plus the /context shortcut. People will keep typing /context out of habit, and right now that dumps hundreds of table rows into the thread (#14690).