[BUG] In remote mode, when the remote port is invalid, there will be no prompt #4814

Open
opened 2026-02-16 17:45:33 -05:00 by yindo · 2 comments
Owner

Originally created by @DoiiarX on GitHub (Jan 12, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

In remote mode, when the remote port is invalid, there will be no prompt

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @DoiiarX on GitHub (Jan 12, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description In remote mode, when the remote port is invalid, there will be no prompt ### Plugins _No response_ ### OpenCode version _No response_ ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the bug label 2026-02-16 17:45:33 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 12, 2026):

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

  • #7887: opencode mcp auth fails silently in remote/headless sessions (SSH, devcontainer) - Similar pattern of missing user feedback/prompts in remote scenarios

Both issues describe scenarios where OpenCode fails to provide proper error messages or feedback to the user in remote/remote-mode contexts. The root cause may be related to error handling in remote connections that doesn't properly surface messages to the user.

Feel free to ignore if your specific case involves a different scenario.

@github-actions[bot] commented on GitHub (Jan 12, 2026): This issue might be a duplicate of existing issues. Please check: - #7887: opencode mcp auth fails silently in remote/headless sessions (SSH, devcontainer) - Similar pattern of missing user feedback/prompts in remote scenarios Both issues describe scenarios where OpenCode fails to provide proper error messages or feedback to the user in remote/remote-mode contexts. The root cause may be related to error handling in remote connections that doesn't properly surface messages to the user. Feel free to ignore if your specific case involves a different scenario.
Author
Owner

@DoiiarX commented on GitHub (Jan 12, 2026):

This is unrelated to MCP or SSH. Not a duplicate.

@DoiiarX commented on GitHub (Jan 12, 2026): This is unrelated to MCP or SSH. Not a duplicate.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4814