[Bug] Web interface does not auto-refresh conversations in real-time

[afonsoft]

Problem

New messages sent within a conversation in the OpenCode web interface are not appearing in real-time. Manual page refresh is required to see them.

Steps to Reproduce

1. Open the OpenCode web interface.
2. Start a new conversation or load an existing one.
3. Send a message (or have another participant send a message).
4. Observe that the new message does not automatically appear in the chat window.
5. Manually refresh the web page (e.g., using F5 or Cmd+R).
6. Observe that the new message now appears after the refresh.

Actual Behavior

The chat UI does not update dynamically; new messages are only visible after a manual page refresh.

Expected Behavior

The chat UI should update automatically in real-time as new messages are sent or received, without requiring a manual refresh.

Environment

• Browser: Chrome/Firefox/Safari
• OpenCode Version: Latest

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• The issue body appears to be AI-generated. It contains an extensive multi-section analysis including root cause breakdowns, 6 code fixes with before/after snippets, a 3-phase proposed solution, a full utility class implementation, automated test suites, and effort estimates. We do not accept AI-generated walls of text in place of genuine bug reports.
• A bug report should describe what you actually observed: what you did, what you expected to happen, and what happened instead. Please replace the current content with your own words describing the real problem you encountered.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

This issue might be a duplicate of existing issues. Please check:

• Mobile browser tab does not reconnect SSE stream after returning from another app #39030: Mobile browser tab does not reconnect SSE stream after returning from another app — same symptom of the web interface not showing new messages without a manual page refresh.

If you believe this was flagged incorrectly, please let a maintainer know.

[afonsoft]

Technical Details (for reference)

Based on analysis of packages/web/src/components/Share.tsx, the issue is likely caused by SolidJS Store reactivity problems with WebSocket message handling.

Possible Root Causes

1. Store Mutation Not Triggering Reactivity (lines 137-142)

setStore("messages", d.content.messageID, "parts", (arr) => {
  const index = arr.findIndex((x) => x.id === d.content.id)
  if (index === -1) arr.push(d.content)
  if (index > -1) arr[index] = d.content
  return [...arr]
})

The callback receives an array that may be undefined. If undefined, the update fails silently.

2. Race Condition: Parts Before Message (line 133)

d.content.parts = d.content.parts ?? store.messages[messageID]?.parts ?? []

If parts arrive before the message, store.messages[messageID] may be undefined.

3. Missing Connection Timeout (line 111)
No timeout on new WebSocket(wsUrl) - connection may hang without feedback.

Suggested Fix Direction

Use produce from solid-js/store for safe mutations:

import { produce } from "solid-js/store"

setStore("messages", d.content.messageID, "parts",
  produce((arr = []) => {
    const index = arr.findIndex((x) => x.id === d.content.id)
    if (index === -1) arr.push(d.content)
    else arr[index] = d.content
  })
)

Add connection timeout and heartbeat to detect dead connections.

Debugging Steps

1. Open DevTools → Network tab → filter WS
2. Verify WebSocket connection status (101 Switching Protocols)
3. Check console for WebSocket errors
4. Add temporary console.log in onmessage handler to verify messages are received

Reference: WebSocket endpoint is wss://[API_URL]/share_poll?id=[SESSION_ID]

[github-actions]

Thanks for updating the issue! The report now clearly describes the problem, steps to reproduce, and expected behavior. We appreciate you taking the time to revise it.