OpenClaw 2026.4.14 Windows UI Regression: What's Broken and What to Do

OpenClaw 2026.4.14 introduced a significant chat UI regression on Windows. If you updated and your text is disappearing, replies aren't streaming live, or the typing indicator flashes once and goes blank — this is a known bug (GitHub #67035), not your setup.

What's Broken

The regression affects the web/dashboard UI on Windows (10 and 11). Reported symptoms:

• Typed input often doesn't appear in the chat input field immediately
• Some input text appears with a significant delay
• Some input text is dropped entirely and never appears
• Assistant replies don't stream live — content only appears after manually refreshing the page
• The "assistant is typing" animated indicator flashes once, then disappears, leaving a blank area
• The UI briefly shows activity and then goes blank

The issue was confirmed on OpenClaw 2026.4.14 (build 323493f) and is specific to Windows. Users on macOS and Linux are not reporting the same symptoms. It also appears independent of model choice — the bug affects setups using LM Studio, Ollama, and cloud providers.

Is This a Model Latency Issue?

No. The input field regression (text not appearing while typing) happens before any model is involved. That's a frontend render issue, not a slow model. If your replies aren't streaming, that's also a rendering regression — the content is being generated but the UI isn't updating. Refreshing the page reveals the content, which confirms it arrived, just wasn't displayed.

Workarounds While You Wait for a Patch

Option 1: Roll Back to 2026.4.13

If you can pin versions, roll back:

npm install -g openclaw@2026.4.13
openclaw gateway restart

The 4.13 build doesn't have the Windows UI regression. See our version pinning guide to stay on 4.13 until a fix ships.

Option 2: Use a Messaging Channel Instead

If you have Telegram, Discord, or WhatsApp connected to OpenClaw, these channels are unaffected by the browser UI regression. You can continue working through your messaging app while the dashboard bug gets patched.

Option 3: Hard Refresh / Clear Browser Cache

Some users report that a hard refresh (Ctrl+Shift+R) or clearing the browser cache temporarily restores normal behavior. This is not a permanent fix but can unblock you in a pinch.

Option 4: Try a Different Browser

The issue appears most consistently in Chrome on Windows. Firefox and Edge have been reported to behave better in some cases — worth trying if you're blocked.

Status

GitHub issue #67035 was filed April 15 and is open as of this writing. Given the severity (broken input on the primary UI surface), expect a patch release quickly — the OpenClaw team has historically turned around regression fixes within 24-48 hours.

Watch the releases page for 2026.4.15 which should include the fix.