Opencode Web: Terminal not working #7578

Activity

1. conradkoh

   added

   bugSomething isn't workingSomething isn't working

   on Jan 10, 2026
2. github-actions

   assigned

   adamdotdevin

   on Jan 10, 2026
3. github-actions

   added

   webRelates to opencode on web / desktopRelates to opencode on web / desktop

   on Jan 10, 2026
4. github-actions commented on Jan 10, 2026

   

   github-actionsBot

   on Jan 10, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Cannot type in terminal in web app with mobile browser #7530: Cannot type in terminal in web app with mobile browser (exact same issue on mobile platforms)
   • Bug: Web terminal fails when accessing via network IP instead of localhost #5844: Web terminal fails when accessing via network IP instead of localhost
   • Cannot open terminal from opencode web #5685: Cannot open terminal from opencode web
   • Bug: Desktop embedded terminal freezes when shell exits via Ctrl+D or exit command #6004: Desktop embedded terminal freezes when shell exits
   • Input goes into weird buffer instead of chat box #3974: Input goes into weird buffer instead of chat box (similar symptom)

   Feel free to ignore if none of these address your specific case.
5. zbynekwinkler commented on Jan 12, 2026

   

   zbynekwinkler

   on Jan 12, 2026

   More actions

   I can confirm the same behavior on windows with version 1.1.14 (1.1.7 used to work, it found and opened git bash).
6. zbynekwinkler commented on Jan 12, 2026

   

   zbynekwinkler

   on Jan 12, 2026

   More actions

   In the browser console I see bunch of errors while the last one says

   Error: Failed to load ghostty-vt.wasm.
   

   There are some 404 and some cors errors as well. This is on Edge on Windows.

   👍React with 👍1Reacted by Krishna Penukonda
7. xomaxie

   marked Web terminal fails under CSP when Ghostty WASM loads via data URL #9185 as a duplicate of this issue on Jan 18, 2026
8. adamdotdevin

   closed this as completedin #9700on Jan 21, 2026
9. ddandyy74 commented on May 6, 2026

   

   ddandyy74

   on May 6, 2026

   More actions

   I can confirm this issue still exists in v1.14.39 (latest release as of May 6, 2026).

   Environment:

   • OpenCode version: v1.14.39
   • Running as: headless server with HTTP Basic Auth
   • Browser: Chrome on Linux
   • Access: via IP address (not localhost)

   Error in console:

   Connecting to 'data:application/wasm;base64,...' violates the following Content Security Policy directive: "connect-src *". Note that '*' matches only URLs with network schemes ('http', 'https', 'ws', 'wss'), or URLs whose scheme matches self's scheme. The scheme 'data:' must be added explicitly.
   

   Current CSP from server:

   Content-Security-Policy: default-src 'self'; script-src 'self' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; media-src 'self' data:; connect-src *
   

   The issue is that ghostty-web loads the Ghostty WASM module via a data: URL, but connect-src * does not include data: scheme.

   I noticed PR #9186 proposed a fix (load ghostty wasm via asset URL) but it was closed without being merged.

   Is there any plan to address this? The web terminal is completely broken for non-localhost access.