cli doesnt connect to vscode #9194

Activity

1. pdeva

   added

   bugSomething isn't workingSomething isn't working

   on Jan 18, 2026
2. github-actions

   assigned

   rekram1-node

   on Jan 18, 2026
3. github-actions commented on Jan 18, 2026

   

   github-actionsBot

   on Jan 18, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Lost changes and session in vscode #6051: Lost changes and session in vscode - Similar VSCode extension connection and session management issues
   • [FEATURE]: cleaner and more aware extensions integration with vscode #7275: [FEATURE]: cleaner and more aware extensions integration with vscode - Related to VSCode extension integration challenges
   • Cross platform open opencode in VSCode #2220: Cross platform open opencode in VSCode - Related to opening OpenCode from VSCode on different platforms
   • OpenCode TUI loses connection with server #5094: OpenCode TUI loses connection with server - General connection loss issues between CLI and server

   Feel free to ignore if none of these address your specific case.
4. LIHUA919 commented on Jan 18, 2026

   

   LIHUA919

   on Jan 18, 2026

   More actions

   The root cause of this issue is that in Remote SSH scenarios, the VSCode extension runs on your local macOS machine, but the CLI server runs on the remote Ubuntu machine.

   When the extension tries to connect via fetch(http://localhost:${port}/app`)` (line 78 in extension.ts), it connects to local localhost instead of the remote localhost where the CLI server is listening.

   Solution

   VSCode provides the vscode.env.asExternalUri() API to handle this exact scenario. It automatically sets up port forwarding for remote environments.

   For the OpenCode maintainers

   The fix requires modifying sdks/vscode/src/extension.ts:

   Current code (line 78):

   await fetch(`http://localhost:${port}/app`)

   Should be:

   const externalUri = await vscode.env.asExternalUri(
     vscode.Uri.parse(`http://localhost:${port}/app`)
   );
   await fetch(externalUri.toString());

   The same change is needed in the appendPrompt function (line 94).

   Workaround for users

   Until this is fixed, you can manually set up SSH port forwarding:

   1. Find the port displayed in the terminal (the random port number)
   2. Add SSH port forwarding in your SSH config or use:

      ssh -L ${port}:localhost:${port} your-server

   Reference: Supporting Remote Development and GitHub Codespaces - see the "Forwarding localhost" section

   👍React with 👍4Reacted by Johannes Ulén, ZeroAurora, Artem Artemyev and emremsgl
5. github-actions commented on Mar 27, 2026

   

   github-actionsBot

   on Mar 27, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

   😄React with 😄1Reacted by emremsgl
6. github-actions

   closed this as completedon Mar 27, 2026