Dev servers

How it works

• OpenCode starts a local server in your workspace, for example Vite, Astro, Next.js, or another preview command.
• The OpenRemote plugin reports workspace-owned listeners to the gateway.
• The app shows those servers on the connected session screen.
• When you open one, the gateway creates a short-lived forwarding link and proxies the server through the existing authenticated OpenRemote connection.

Setup

Use OpenRemote Gateway. Dev server forwarding is a gateway feature and is not available through direct plugin-only connections.

1. Start the gateway with oo gateway start.
2. Start OpenCode in your workspace.
3. Connect the app to the gateway.
4. Start a dev server from that OpenCode workspace.
5. Open the server from the app when it appears under the connected session.

What gets shown

OpenRemote only shows listeners associated with OpenCode or the active workspace. It should not list every open port on your machine.

• OpenCode child processes can be shown.
• Detached workspace processes can be shown when their working directory belongs to the workspace.
• Internal OpenRemote gateway and OpenCode service ports are hidden.

Opening a preview

OpenRemote opens dev servers in the in-app browser sheet when supported by the platform. The gateway keeps the preview behind OpenRemote auth and forwards root assets, redirects, and websocket traffic needed by common dev servers.

If a server does not appear, restart the dev command from the OpenCode workspace and check the gateway TUI. If it still does not appear, confirm the process working directory is inside the workspace.

Security

Dev server forwarding is for local preview access through your authenticated OpenRemote connection. It is not a public deployment path.

• The forwarding token is short-lived.
• The gateway forwards only to discovered local listeners.
• Remote access still depends on the same OpenRemote gateway authentication.