openclaw - 💡(How to fix) Fix Status bar ctx% shows 0% when context is mostly cached [1 comments, 2 participants]

Bug: The per-message status bar in Control UI shows 0% ctx even when the actual context window usage is ~10% (100k/1M), because the calculation only counts non-cached input tokens and ignores cache-read tokens.

Expected: ctx% should reflect the true context window occupancy, including cached tokens.

Root cause: In control-ui/assets/index-*.js, function EC():

// n = sum of usage.input (non-cached new tokens only)
// i = sum of usage.cacheRead (cached tokens)
// t = contextWindow (e.g. 1000000)
let l = t && n > 0 ? Math.min(Math.round(n / t * 100), 100) : null;

The formula uses only n (non-cached input), but the actual context window usage is n + i (input + cacheRead). When prompt caching is active (88%+ cache hit rate is common), n is tiny (e.g. 3 tokens for user message) while i is large (e.g. 98k), resulting in 0% displayed vs ~10% actual.

Reproduction:

1. Start a session with a large system prompt and bootstrap files (typical setup uses ~100k context)
2. After a few turns, cache hit rate reaches 80-100%
3. Status bar shows 0% ctx while session_status correctly reports 10% ctx

Fix suggestion: Change the formula to include cache-read tokens:

let total = n + i; // input + cacheRead
let l = t && total > 0 ? Math.min(Math.round(total / t * 100), 100) : null;

Or alternatively, use the last turn's input + cacheRead instead of cumulative sum, since ctx% conceptually represents current context window fill level, not cumulative consumption.