PR #51536: fix(webchat): use totalTokens for context utilization display

• Repository: openclaw/openclaw
• Author: VipinSinghChauhan
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/51536

Description (problem / solution / changelog)

Fixes #51507

The context warning banner and /status command were reading session.inputTokens to compute context fill %, but inputTokens accumulates input tokens across ALL API sub-calls in a run (tool-use loops, retries, compaction). With models like MiniMax-M2.5 that chain many sub-calls, this number far exceeds the actual context size, causing premature 100% warnings and a blocked chat input.

The correct field is session.totalTokens, which the backend already derives from lastCallUsage (the final API call only) — the true prompt-size snapshot. This is the same value the TUI uses, which explains why TUI showed accurate context while WebChat did not.

Changes:

• ui/views/chat.ts: renderContextNotice uses totalTokens (not inputTokens)
• ui/chat/slash-command-executor.ts: /status Context % uses totalTokens
• ui/views/chat.browser.test.ts: update fixture to totalTokens so the existing context notice test continues to pass

Summary

Describe the problem and fix in 2–5 bullets:

• Problem:
• Why it matters:
• What changed:
• What did NOT change (scope boundary):

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #
• Related #

User-visible / Behavior Changes

List user-visible changes (including defaults/config).
If none, write None.

Security Impact (required)

• New permissions/capabilities? (Yes/No)
• Secrets/tokens handling changed? (Yes/No)
• New/changed network calls? (Yes/No)
• Command/tool execution surface changed? (Yes/No)
• Data access scope changed? (Yes/No)
• If any Yes, explain risk + mitigation:

Repro + Verification

Environment

• OS:
• Runtime/container:
• Model/provider:
• Integration/channel (if any):
• Relevant config (redacted):

Steps

Expected

Actual

Evidence

Attach at least one:

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

What you personally verified (not just CI), and how:

• Verified scenarios:
• Edge cases checked:
• What you did not verify:

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

• Backward compatible? (Yes/No)
• Config/env changes? (Yes/No)
• Migration needed? (Yes/No)
• If yes, exact upgrade steps:

Failure Recovery (if this breaks)

• How to disable/revert this change quickly:
• Files/config to restore:
• Known bad symptoms reviewers should watch for:

Risks and Mitigations

List only real risks for this PR. Add/remove entries as needed. If none, write None.

• Risk:
  • Mitigation:

Changed files

• ui/src/ui/chat/slash-command-executor.node.test.ts (modified, +3/-1)
• ui/src/ui/chat/slash-command-executor.ts (modified, +5/-1)
• ui/src/ui/views/chat.browser.test.ts (modified, +4/-1)