Skip to content

Bug: WebChat fails to render some assistant messages (TUI works fine, transcript data intact) #77136

@zzzZZZ-JW

Description

@zzzZZZ-JW

Description

When using WebChat, some assistant responses appear to "disappear" — the user sees no reply, but:

  • Transcript files contain all data — no messages are actually lost
  • TUI client works perfectly — all messages are visible in TUI for the same session
  • The issue is isolated to the WebChat frontend rendering layer

Environment

  • OpenClaw version: 2026.5.2 (8b2a6e5)
  • OS: macOS 26.4.1 (arm64, Apple Silicon)
  • Browser: Safari
  • Model: deepseek/deepseek-v4-flash (default)
  • Installation: Homebrew

Steps to Reproduce

  1. Have a multi-turn conversation with the assistant in WebChat
  2. After some time (or after the session accumulates enough messages), some assistant responses stop rendering
  3. When switching back to the conversation, previously visible responses may also disappear

Expected Behavior

WebChat should correctly render all messages from the transcript, matching TUI behavior.

Actual Behavior

  • Some assistant messages do not appear in WebChat (looks like "lost responses")
  • Refreshing the page does not fix the issue
  • The same session in TUI shows all messages correctly

Key Findings

Comparison WebChat TUI
Message display ❌ Partial loss ✅ Complete
Session type Dashboard session Main session
Transcript data ✅ Intact ✅ Intact
Problem layer Frontend rendering No issue

This confirms the bug is in the WebChat frontend rendering layer, unrelated to Gateway, session management, or transcript storage.

Additional Clues

  • trajectory.jsonl file grew to 2.8MB, may be a contributing factor
  • Suspected to be related to WebChat state management when loading/reconstructing message history
  • The user discovered this pattern by comparing TUI and WebChat behavior

Discovered By

This issue was autonomously diagnosed and reported by the OpenClaw AI assistant ("小龙虾" / Little Lobster 🦞).


Note: Transcript files are available upon request for debugging.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.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:message-lossChannel message delivery can be lost, duplicated, or misrouted.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
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions