Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading to v2026.5.12, Control UI WebChat does not live-update while observing a Feishu-originated run in the same direct-chat session. The agent run itself works and the Feishu reply is delivered, but the Control UI only shows the new assistant/tool activity after the response has fully completed and chat.history is reloaded.

Important clarification: sending a message directly from Control UI WebChat streams correctly. The problem is specific to Control UI acting as a live observer of a channel-originated run, in this case Feishu DM.

Steps to reproduce

1. Install OpenClaw v2026.5.12.
2. Open Control UI WebChat and select the same Feishu direct-chat session.
3. Send a message to the agent from Feishu DM, not from Control UI.
4. Observe the selected session in Control UI while the Feishu-triggered run is in progress.
5. Expected: Control UI should receive live session updates / streaming updates for the active session.
6. Actual: Control UI does not update during the run. The response appears only after the Feishu-triggered run has fully completed and chat.history is reloaded.
7. Send a message directly from Control UI WebChat as a control test: direct WebChat-originated streaming works correctly.

Expected behavior

Control UI should live-update for the selected session regardless of whether the run was initiated from WebChat or from a connected channel such as Feishu. If a Feishu DM triggers a run in the currently selected session, Control UI should show assistant/tool progress during the run.

Actual behavior

• Feishu dispatch succeeds and the final reply is delivered.
• The run is persisted correctly; chat.history returns it after completion/reload.
• Control UI does not show incremental updates while observing the Feishu-originated run.
• Sending directly from Control UI WebChat streams correctly.
• This suggests the issue is not model generation itself, but the live session update/subscription path for channel-originated runs.

OpenClaw version

2026.5.12 (f066dd2)

Operating system

macOS Tahoe 26.4.1 (arm64)

Install method

npm global

Model

Observed with openai/gpt-5.5. Also tested after switching runtime/model path away from Codex; the Control UI observer issue persisted for Feishu-originated runs. Direct WebChat-originated messages stream correctly.

Provider / routing chain

Feishu DM -> OpenClaw Gateway -> selected agent session -> Control UI WebChat observing same session

Additional provider/model setup details

• The original suspicion was that this was related to the v2026.5.12 openai-codex/gpt-5.5 -> openai/gpt-5.5 + agentRuntime.id migration.
• Further testing showed the important distinction is origin surface:
  • Control UI WebChat sends: streaming works.
  • Feishu DM sends while Control UI observes the same session: Control UI does not live-update.
• Therefore this should be treated as a Control UI/session subscription issue for channel-originated runs, not as a generic WebChat streaming failure.

Logs, screenshots, and evidence

Gateway logs show Control UI connects and can load history:

[ws] webchat connected conn=... client=openclaw-control-ui webchat v2026.5.12
[ws] res OK sessions.list ...
[ws] res OK chat.history ...

For the Feishu-originated run:

[feishu] feishu[default]: dispatching to agent (session=agent:main:feishu:direct:...)
[feishu] feishu[default]: dispatch complete (queuedFinal=true, replies=1)

Additional observation from logs:

• On an initial Control UI connection, sessions.subscribe appears.
• After later WebChat reconnects, logs show agents.list, models.list, sessions.list, and chat.history, but no new sessions.subscribe.
• When this happens, Control UI appears to rely on history reloads instead of receiving live session updates.

Impact and severity

• Affected: users who interact through Feishu while using Control UI as a live monitor for the same session.
• Severity: High for long-running tool-call turns, because users cannot monitor progress from Control UI.
• Frequency: reproducible in the described Feishu DM + Control UI observer workflow.
• Direct WebChat usage is not blocked because WebChat-originated streaming still works.

Additional information

The earlier issue text incorrectly described the reproduction as "send a message using Control UI WebChat". That is not accurate. The correct reproduction is "send from Feishu DM, observe from Control UI WebChat".