Desktop app: terminal content blank after upgrading to v1.4.0

[leoncheng57]

Description

After upgrading to v1.4.0, the desktop app terminal tabs render but the terminal content area is completely blank — no shell output appears. Only a cursor is visible. Downgrading to v1.3.17 resolves the issue.

Steps to Reproduce

1. Upgrade OpenCode Desktop from v1.3.x to v1.4.0
2. Open a project
3. Observe the terminal pane — tabs (Terminal 1, Terminal 2) appear but content is blank

Expected Behavior

Terminal content should render with a working shell session.

Actual Behavior

Terminal tabs are visible but the content area is empty. The sidecar logs show service=server error= failed (with an empty error field) repeating every ~4 seconds continuously. The TypeScript LSP also fails to initialize (45s timeout).

Environment

• OS: macOS (Apple Silicon)
• Version: v1.4.0 (desktop)
• Previous working version: v1.3.17

Relevant Logs

From ~/Library/Logs/ai.opencode.desktop/:

INFO  opencode_lib: Sidecar health check OK
INFO  opencode_lib: Loading done, completing initialisation
INFO  sidecar: opencode_lib::cli: ERROR service=server error= failed
INFO  sidecar: opencode_lib::cli: ERROR service=server error=NotFoundError failed
INFO  sidecar: opencode_lib::cli: ERROR service=server error= failed
# above line repeats every ~4 seconds indefinitely
INFO  sidecar: opencode_lib::cli: ERROR service=lsp.client serverID=typescript error=Operation timed out after 45000ms initialize error
INFO  sidecar: opencode_lib::cli: ERROR service=lsp error=LSPInitializeError Caused by: Operation timed out after 45000ms Failed to initialize LSP client typescript

The service=server error= failed loop starts immediately after sidecar initialization and never recovers.

Troubleshooting Attempted

• Cleared ~/.cache/opencode and relaunched — no fix
• Fully quit and relaunched multiple times — no fix
• Downgraded to v1.3.17 — fixes the issue

MCP Configuration

5 MCP servers configured (playwright, notion x2, atlassian, grafana) — all connect and initialize successfully. The MCP "failed to get prompts" errors are benign (servers that don't support the prompts method).

[github-actions]

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

• Desktop, terminal no longer works on 1.4.0 #21440: Desktop terminal no longer works on 1.4.0
• [BUG]: Integrated terminal is completely unresponsive (blank screen, no input) #21469: Integrated terminal completely unresponsive (blank screen, no input) on 1.4.0
• The terminal in the Opencode Desktop app just showing a blinking cursor, never interactable #21480: Terminal only showing a blinking cursor, never interactable
• Desktop terminal completely non-functional on Windows — no keyboard input, blank PTY #21498: Desktop terminal completely non-functional on Windows — no keyboard input, blank PTY
• TERMINAL dont work on 1.4.0 #21517: Terminal doesn't work on 1.4.0
• Bug: Built-in terminal fails to initialize in Desktop v1.4.0 (Windows 10) #21421: Built-in terminal fails to initialize in Desktop v1.4.0 (Windows 10)
• Desktop terminal non-functional on macOS Tahoe — no keyboard input #21502: Desktop terminal non-functional on macOS Tahoe — no keyboard input

There appear to be several reports of the same regression in v1.4.0 where the terminal is blank or non-functional. If one of the above covers your issue, please consider closing this one and adding your information (especially the sidecar logs) to the existing report instead.

[hdd69]

@adamdotdevin I can look into that if no one started on it yet.