Description
When sending a message in the control UI, the input field clears as expected. However, once the AI's "thinking" / streaming response begins, the previously sent text briefly flashes back into the input field (sometimes as a fragment), then disappears again after the response completes.
Steps to Reproduce
- Open the control UI in a browser
- Type a message and send it
- Observe the input field clears
- When the streaming response starts (thinking indicator appears), the sent text briefly reappears in the input field or as a duplicate chat bubble fragment
- After the response finishes, it disappears again
Expected Behavior
Input field should stay empty after sending. Streaming state updates should not cause stale input values to flash back.
Likely Cause
Lit component re-render issue — when the streaming/thinking state updates trigger a parent component re-render, the input component briefly restores a stale value before settling.
Screenshot

Screenshot shows a "That" fragment appearing as a separate bubble — a piece of the user's prior message that briefly resurfaced during streaming.
Environment
- OpenClaw 2026.4.14 (323493f)
- Model: claude-opus-4-6
- Runtime: direct (Claude Code CLI)
- macOS Darwin 24.6.0
🤖 Generated with Claude Code
Description
When sending a message in the control UI, the input field clears as expected. However, once the AI's "thinking" / streaming response begins, the previously sent text briefly flashes back into the input field (sometimes as a fragment), then disappears again after the response completes.
Steps to Reproduce
Expected Behavior
Input field should stay empty after sending. Streaming state updates should not cause stale input values to flash back.
Likely Cause
Lit component re-render issue — when the streaming/thinking state updates trigger a parent component re-render, the input component briefly restores a stale value before settling.
Screenshot
Environment
🤖 Generated with Claude Code