Bug type

Behavior bug (incorrect output/state without crash)

Summary

On macOS with OpenClaw 2026.3.12, the Control UI can still render a broken/blank chat area when a session reaches 100% context used, even if the known .context-notice CSS regression is already patched locally.

This appears to be more than the oversized warning icon bug.

In this case:

• the warning pill itself looked normal after a local CSS hotfix
• the chat area still broke when the session hit 100% context used (user report: 206.4k / 200k)
• session data continued to append normally on disk

So the failure looks like a Control UI render/state bug on the context exhaustion boundary, not session corruption.

Steps to reproduce

1. Run OpenClaw 2026.3.12 on macOS.
2. Open Control UI in Chrome.
3. Use a long-running main session until the UI reports 100% context used.
4. In the same period, let model fallback/compaction activity happen normally.
5. Observe that the chat pane can render incorrectly or appear blank, even though the session still exists and continues to append messages.

Expected behavior

• Context exhaustion should show a bounded warning.
• The chat history should remain visible.
• Input should either stay usable or be explicitly disabled with a clear action such as "Compact Session".
• If compaction fails, the UI should show a normal error state instead of collapsing the chat area.

Actual behavior

• The chat pane becomes visually broken/blank at the 100% context used boundary.
• In this repro, the context warning pill itself was already normal due to a local CSS hotfix, so the failure was not just the oversized icon overlay.
• Session data was still intact and continued updating on disk.

OpenClaw version

2026.3.12

Operating system

macOS

Install method

npm global

Model

Primary: anthropic/claude-opus-4-6

Fallback seen during repro: gemini/gemini-3.1-pro-preview

Provider / routing chain

local gateway loopback

Config file / key location

~/.openclaw/openclaw.json

Additional provider/model setup details

This machine is already using a local Control UI hotfix bundle because the installed 2026.3.12 bundle still lacks .context-notice CSS selectors.

Override in use:

gateway.controlUi.root = /Users/lucifinil_chen/.openclaw/runtime-overrides/control-ui-hotfix-20260314/dist/control-ui

Because the issue still reproduces with that override active, this looks like a second bug beyond the known CSS regression.

Logs, screenshots, and evidence

Relevant gateway log lines during the same repro window:

2026-03-14T14:07:34.497+08:00 [compaction] Full summarization failed, trying partial: Summarization failed: 429 {"error":{"message":"API 密钥额度已用完，请联系管理员充值","type":"quota_exceeded"},"type":"error"}
2026-03-14T14:07:47.434+08:00 [compaction] Partial summarization also failed: Summarization failed: 429 {"error":{"message":"API 密钥额度已用完，请联系管理员充值","type":"quota_exceeded"},"type":"error"}
2026-03-14T14:07:58.289+08:00 [compaction] Full summarization failed, trying partial: Summarization failed: 429 {"error":{"message":"API 密钥额度已用完，请联系管理员充值","type":"quota_exceeded"},"type":"error"}
2026-03-14T14:08:08.940+08:00 [compaction] Partial summarization also failed: Summarization failed: 429 {"error":{"message":"API 密钥额度已用完，请联系管理员充值","type":"quota_exceeded"},"type":"error"}

Session-store evidence that data remained intact:

• session file: agents/main/sessions/d0e51a49-1ea3-426a-b4dd-4416aa4018c5.jsonl
• compaction record exists at 2026-03-14T06:08:08Z
• a new user message exists at 2026-03-14T06:09:06Z
• a new assistant reply exists at 2026-03-14T06:09:34Z

That makes this look like a UI/render issue rather than session loss.

Related issues:

• [Bug]: UI Bug: Context limit warning icon scales abnormally and blocks chat view in v2026.3.12 #44906
• Control UI: Context warning blocks screen on refresh with incorrect values #45230
• [Bug]: Control UI - Chat input hidden behind warning overlay when context exceeds limit; token count mismatch in sessions view #45513

This report is specifically about the chat pane still breaking even when the .context-notice CSS path has already been patched locally.

Impact and severity

High for long-running sessions in Control UI. The conversation appears broken at the exact moment the user most needs recovery/compaction controls.

Additional information

The active runtime is also using memory-lancedb-pro@1.1.0-beta.8, but this issue does not appear to be related to the memory plugin. The failure is reproducible in the Control UI/render path.