Workspace
Context and cache
How full each agent's context window is, how long its prompt cache stays warm, and where agex gets those numbers.
The status bar, under the terminals and the right panel, shows how much of the context window the agent in front is using and how long its prompt cache stays warm. It always follows the tab in front, and stays empty when that tab isn't an agent.
The context meter
On the left of the status bar, the meter shows the agent's task, a bar colored by what fills the window, and the share in use with the token count:
21% · 212.8k / 1M
It follows each reply within a second.
Meters turn amber, then red, as the agent gets close to compacting its context. The thresholds are a share of the window before compaction:
| Setting | Default | What it does |
|---|---|---|
status_bar.context_warning_percent | 70 | Context use that turns meters amber. |
status_bar.context_danger_percent | 90 | Context use that turns meters red. |
Context details
Click the meter, or press ⇧⌘I, for the details. They're laid out like Claude Code's /context: a row per category, with its tokens and its share of the window. The categories are messages, system tools, system prompt, skills, MCP server instructions, MCP tools and memory files. After them come the autocompact buffer and the free space.
- Hover Messages to see what the conversation holds: your messages, replies and tool calls, tool results, and files.
- Unfold MCP tools to see them per server, loaded or deferred.
- Unfold Memory files to see each file.
Only Claude Code, Copilot CLI and Auggie say what fills their context. For every other agent, the details show a single In context row.
Prompt cache countdown
Next to the meter, a countdown shows how long the agent's prompt cache stays warm, to the second (4:07). Reply before it runs out and the agent reuses the cache.
- In the last minute it turns amber (
0:42). - Once the cache has gone cold, it shows a snowflake. The next request writes the whole context again.
The countdown appears for agents whose records say when the cache was last used. For Claude Code, that's 5 minutes from its last request, or an hour on plans that get it.
Sub-agents and threads
While the agent in front has sub-agents at work, a button says how many (3 sub-agents). Click it for the list: the sub-agents at work, with their kind, last action and time, then the ones that finished. Each shows how full its own context window is, with its share, a bar and its tokens.
When threads have branched off the agent's session, another button says how many (2 threads), with a spinner while one is at work. Click it for the list, latest first. Each thread shows its context's share and tokens, and a row to switch to the agent that has that thread open, or to resume it in a new tab.
See Sub-agents and threads for which agents report them.
Other agents
On the right of the status bar, a dropdown lists the project's other agents, both agex's and those running elsewhere, with their share and tokens. It reads like 2 other agents ▾, and turns amber or red when one of them is close to compacting. Click a row to unfold its categories.
Nothing in the dropdown changes what the left side shows.
Row meters
Every agent's row in the sidebar shows the same numbers as a small meter, like ▬ 34%, which turns amber and then red as compaction gets close. Click it to see that agent's details, if it's the agent in front, or its row unfolded in the dropdown, for any other agent.
Session panel
The Session panel moves all of this out of the status bar and into a Session view in the right panel, next to Source Control, Files and Search. It's off by default. Turn it on with status_bar.session_pane, or Session pane in Settings.
The panel shows one session in full:
- Its details: context by category, MCP tools and memory files.
- Its prompt cache.
- Its sub-agents: the ones at work, then the latest that finished.
- Its threads.
Under it are the project's other agents. Click one to show it instead.
The session shown is the one you picked, from its row in the sidebar, its meter, or its row in the panel, until you bring another agent's tab to the front. With nothing picked, it's the agent in front, or else the project's first agent.
⇧⌘I and the gauge in the top bar toggle the panel. The status bar keeps the coffee cup, and its toggles below still choose what the panel shows. Servers stay on the rows of the agents and terminals that started them.
Status bar settings
| Setting | Default | What it does |
|---|---|---|
status_bar.visible | true | Shows the status bar. |
status_bar.session_pane | false | Moves the agent's pieces into the Session panel. |
status_bar.context_meter | true | The context meter of the agent in front. |
status_bar.prompt_cache | true | The prompt cache countdown. |
status_bar.subagents | true | The sub-agents button and list. |
status_bar.threads | true | The threads button and list. |
status_bar.other_agents | true | The list of the project's other agents. |
Which agents are tracked
Context tracking works for the agents that write their token counts down, in agex or running elsewhere:
Claude Code, Codex, Copilot CLI, Gemini CLI, Qwen Code, OpenCode, Kilo Code, Crush, Cursor Agent, Kiro CLI, Droid, Auggie, Kimi, Junie, Qoder, Pi, Goose, OpenHands, Mistral Vibe, Cline, Trae Agent, Continue, and Amp (before threads moved to Amp's servers).
Three agents are estimated and marked ≈:
- Grok CLI and Amazon Q, whose records don't hold the context size.
- Aider, which rounds its counts.
Antigravity, Blackbox, Qodo and Jules keep nothing agex can read, so they aren't tracked.
Totals
The total is the agent's own count: the API's token count for its last request, or the share the agent reports itself (Kiro, Cursor and Qoder).
For Claude Code, the split by category is estimated from the transcript and calibrated against the first reply, which holds only the system prompt, the tools and your first message.
Window size
Agents that don't write down the size of their window get it from the model catalogs on your Mac (OpenCode's and Kilo's copies of models.dev, and Crush's provider list), or else from a table built into agex.