Best possible solution:

Refresh the branch and drive the meter from the same freshness-aware context usage model as the existing notice, with explicit stale-token behavior and tests.

Do we have a high-confidence way to reproduce the issue?

Yes. Source inspection gives a high-confidence path: render an active session with totalTokens, contextTokens, and totalTokensFresh=false; this PR passes only raw totalTokens into the meter while current sibling context UI hides that stale state.

Is this the best way to solve the issue?

No. The visible meter is plausible, but the maintainable fix is to reuse or match the existing freshness-aware context model instead of adding a parallel raw-token calculation.

Full review comments:

• [P1] Reuse the freshness-aware context model — ui/src/ui/views/chat.ts:2296
  The new meter is driven by activeSession.totalTokens and threadContextWindow, but session rows can preserve totalTokens with totalTokensFresh=false. Existing web context UI, /usage, and the Android context meter do not present that stale value as live context usage, so drive the meter from the shared freshness-aware model or pass freshness through and add a stale-row test.
  Confidence: 0.9

Overall correctness: patch is incorrect
Overall confidence: 0.9

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 19707cce1d73.

Label justifications:

• P3: This is a bounded web UI enhancement with low blast radius, even though it has a merge-blocking display correctness issue.
• merge-risk: 🚨 session-state: The diff can render stale session token totals as current context usage in the chat composer.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🌊 off-meta tidepool and patch quality is 🧂 unranked krab.
• status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: The external-contributor proof gate does not apply to this member-authored, maintainer-labeled PR.

PR surface:

Source +58, Tests +44. Total +102 across 3 files.

What I checked:

• PR renders from raw token totals: The PR renders the new meter from activeSession.totalTokens and threadContextWindow without passing totalTokensFresh or using the existing freshness-aware context usage helper. (ui/src/ui/views/chat.ts:2296, 3b9121a97dd2)
• Current web context notice hides stale totals: Current main returns no context notice when session.totalTokensFresh is false, so the adjacent web UI does not present stale totals as live context usage. (ui/src/ui/chat/context-notice.ts:67, 19707cce1d73)
• Session contract defines stale totals: The session type documents totalTokensFresh=false as requiring consumers to treat totalTokens as stale or unknown for context-utilization displays. (src/config/sessions/types.ts:361, 19707cce1d73)
• Sibling Android meter follows freshness: The Android context meter returns no width when totalTokensFresh is false and has a regression test for that stale-token behavior. (apps/android/app/src/main/java/ai/openclaw/app/ui/chat/ChatScreen.kt:1003, 19707cce1d73)
• Current main lacks this meter: Current main has no token-meter or renderTokenMeter implementation, and the latest release tag also lacks the meter, so the PR is not obsolete or implemented elsewhere. (19707cce1d73)
• Live PR state requires refresh: GitHub reports the PR open with maintainer label, head 3b9121a, mergeable CONFLICTING, and mergeStateStatus DIRTY. (3b9121a97dd2)

Likely related people:

• BunsDev: Authored the persistent Control UI chat context usage indicator and earlier fresh-context behavior in the affected helper, tests, and styles. (role: context-usage behavior contributor; confidence: high; commits: 5a90179e8fdf, da773175f2eb; files: ui/src/ui/chat/context-notice.ts, ui/src/ui/chat/run-controls.test.ts, ui/src/styles/chat/layout.css)
• stainlu: Authored the merged stale totalTokens preservation work that introduced totalTokensFresh as a display-layer freshness signal. (role: stale-token contract introducer; confidence: high; commits: 24b915ed413e; files: src/config/sessions/types.ts)
• vincentkoc: Recently touched shared chat token formatting and adjacent context usage reporting paths used by the web UI. (role: recent context-token area contributor; confidence: medium; commits: 45f935887769; files: ui/src/ui/chat/context-notice.ts, ui/src/ui/chat/token-format.ts)
• Tosko4: Added the Android live chat context meter and stale-token test that share the same freshness invariant. (role: sibling context-meter contributor; confidence: medium; commits: 826ea2bf8513; files: apps/android/app/src/main/java/ai/openclaw/app/ui/chat/ChatScreen.kt, apps/android/app/src/test/java/ai/openclaw/app/ui/chat/ChatContextMeterTest.kt)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.