# feat\(orchestration-v2\): show live context usage in the meter \(\#8144\) · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/b3af3efbf1d7b40bad5c4f3f944e6c1aa7d9e8a6)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: b3af3efbf1d7b40bad5c4f3f944e6c1aa7d9e8a6

Requested commit: b3af3efbf1d7b40bad5c4f3f944e6c1aa7d9e8a6

Commit: b3af3efbf1d7b40bad5c4f3f944e6c1aa7d9e8a6

Tree: a2c94b428c554c1469d9a5a85af369b31d725390

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
feat(orchestration-v2): show live context usage in the meter (#8144)

The v2 context meter could only show token counts after a compaction had
already happened — v2 had no live usage plumbing at all, so main's
compaction-threshold UX was invisible on v2 threads. Provider turns now
carry an optional tokenUsage report: the Codex adapter maps the
app-server's thread/tokenUsage/updated notification (total breakdown +
model context window) onto the active provider turn, ChatView picks the
newest report out of the projection, and the meter prefers it over the
compaction fallback — so usage and remaining-context percentages update
while the turn runs.

Claude's v2 adapter does not report usage yet; its meter falls back to
compaction items as before.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

- [21e63e4604c443de69b8f039afb26adc7489c9a0](https://git.cafe/pingdotgg/t3code/commit/21e63e4604c443de69b8f039afb26adc7489c9a0?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/b3af3efbf1d7b40bad5c4f3f944e6c1aa7d9e8a6?format=markdown)