Skip to content

[Bug] Context indicator disappears after sending message and count mismatch #89662

Description

@snsczssl

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The context usage indicator at the top of the webchat disappears after sending a message and does not reappear after the agent response completes. Additionally, when visible, the indicator shows a lower token count than /status reports.The context usage indicator at the top of the webchat disappears after sending a message and does not reappear after the agent response completes. Additionally, when visible, the indicator shows a lower token count than /status reports.

Steps to reproduce

  1. Open Control UI webchat
  2. Context indicator is visible (showing token usage %)
  3. Type and send a message
  4. Indicator disappears
  5. Agent response completes
  6. Indicator does not reappear until page refresh (F5)

Expected behavior

Indicator should remain visible or reappear after the response completes, showing updated context usage that matches /status output.

Actual behavior

  • Indicator disappears after sending and stays hidden until page refresh
  • /status reports 3.9k/180k (2%) while indicator shows 1.8k/180k (1%) — ~2k token discrepancy

OpenClaw version

2026.6.1-beta.2

Operating system

Windows 11 (10.0.26200, x64)

Install method

npm global

Model

Huihui-Qwen3.6-27B-abliterated-ggml-model-Q6_K (local llama.cpp)

Provider / routing chain

Custom local provider (openai-completions API)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

Severity: Annoying (does not block workflow)
Frequency: Always reproducible
Consequence: Cannot visually track context usage without refreshing or running /statusSeverity: Annoying (does not block workflow)
Frequency: Always reproducible
Consequence: Cannot visually track context usage without refreshing or running /status

Additional information

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.bugSomething isn't workingclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions