Feature Request: Allow Desktop app to read OPENCODE_SERVER_PASSWORD and OPENCODE_DISABLE_EMBEDDED_WEB_UI environment variables, and support binding embedded server to 0.0.0.0 #34358

Is your feature request related to a problem? Please describe.

Currently, the OpenCode Desktop app does not appear to respect the OPENCODE_SERVER_PASSWORD and OPENCODE_DISABLE_EMBEDDED_WEB_UI environment variables on startup. Additionally, the embedded server seems to bind only to localhost (127.0.0.1), which prevents remote clients from connecting over the network.

This limits the flexibility of using the Desktop app in scenarios where remote access and local development are needed simultaneously.

Describe the solution you'd like

I'd like the Desktop app to support the following at launch:

• OPENCODE_SERVER_PASSWORD: Set a password for the embedded server to enable secure remote access.
• OPENCODE_DISABLE_EMBEDDED_WEB_UI=false: Explicitly control whether the embedded Web UI is enabled.
• Allow the embedded server to bind to 0.0.0.0: This could be via an environment variable (e.g., OPENCODE_SERVER_HOST=0.0.0.0) or a config option, so that remote clients can connect to the server over the network.

This would allow users to configure the Desktop app's embedded server behavior without needing to run a separate CLI server instance.

Describe your use case

My workflow requires:

1. Using OpenCode Desktop locally for day-to-day development.
2. Allowing remote clients (e.g., other machines, IDE plugins, or automation tools) to connect to the same local OpenCode server over the network.

To achieve this securely, I need to:

• Set OPENCODE_SERVER_PASSWORD so the server is not exposed without authentication.
• Ensure the embedded Web UI remains available (OPENCODE_DISABLE_EMBEDDED_WEB_UI=false) for local use.
• Bind the embedded server to 0.0.0.0 so it accepts connections from other machines on the network (not just localhost).

Why this matters

Without this feature, the only workaround is to run a separate opencode serve CLI instance alongside the Desktop app, which means:

• Duplication: Maintaining two server instances (one embedded in Desktop, one standalone CLI).
• Extra overhead: Managing ports, environment variables, and process lifecycle for the CLI server.
• Poor UX: Defeats the purpose of having an all-in-one Desktop application.

Additional context

• OpenCode Desktop Version: v1.17.11
• The CLI already supports these environment variables for opencode serve and opencode web. Extending the same behavior to the Desktop app would provide a consistent experience across all OpenCode interfaces and eliminate the need for users to run and maintain an additional CLI server just to enable remote access.

Thank you for considering this feature! 🙏