Desktop terminal non-functional on macOS Tahoe — no keyboard input

[velisnolis]

Description

The integrated terminal in the opencode Desktop app (v1.4.0) does not accept keyboard input on macOS Tahoe. Clicking on the terminal and typing produces no visible characters or response.

Environment

• opencode Desktop: v1.4.0
• OS: macOS Tahoe (Apple Silicon)
• Terminal used for CLI: Ghostty (CLI works fine from external terminal)

Steps to Reproduce

1. Open opencode Desktop app
2. Click on the integrated terminal panel
3. Try to type any character
4. No input is registered — terminal appears completely unresponsive to keyboard

Expected Behavior

Keystrokes should be sent to the PTY and displayed in the terminal.

Actual Behavior

Terminal is non-functional — no keyboard input is accepted.

Workaround

Running opencode from an external terminal (Ghostty, iTerm2, etc.) works correctly.

Additional Context

Similar to #21498 (Windows) and #17931 (macOS cursor issues). The desktop terminal PTY appears to not be properly receiving keyboard events on this macOS version.

[github-actions]

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

• Desktop terminal completely non-functional on Windows — no keyboard input, blank PTY #21498: Same symptom — Desktop terminal non-functional with no keyboard input, same version (v1.4.0), reproduced on Windows. This may be the same underlying PTY/keyboard input bug affecting multiple platforms.

If this is a distinct macOS-specific issue, please let a maintainer know.

[nmzpy]

This doesn't work on windows either, yeah. Regression

[SimFG]

like this?

[velisnolis]

Yes

[SimFG]

sad, it's a common issue.

[SimFG]

The latest version, it works well.

[velisnolis]

Also for me

…

El 9 abr 2026, a las 13:25, SimFG ***@***.***> escribió: SimFG left a comment (anomalyco/opencode#21502) <#21502 (comment)> The latest version, it works well. — Reply to this email directly, view it on GitHub <#21502 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAIST65GBJJCXTVCLO3WJD4U6CC3AVCNFSM6AAAAACXQYHSTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMJTG43TCMRWGE>. You are receiving this because you authored the thread.