[Feature]: Setting to have the web ui running even without /pty-... command

Problem Statement

"I'm always frustrated when..."

I try to reload the browser tab with the running sessions ... and page is not reachable.

even with my own shell script setting the port env, when opencode start ... and launches a pty session ... I manually must use /pty-... to be able to refresh the browser tab to see the sessions.

Proposed Solution

a config param (v1 -> env, v2 -> env+config) to have the pty web ui start on opencode use

Alternatives Considered

... doing it manual. But when the a task runs, until the /pty-... command is processed, it might take a while and I am not able to look at the output / not being able to input if something was needed on the console.

Use Case

Describe the use case(s) this feature would enable:

being able to interact with the pty session while a task is running, and the /pty-... is not yet being processed and thus the webui is not reachable.

Start by tracing opencode startup and the existing /pty-... command handling that launches the PTY web UI; the issue does not name specific files or tests. Done means a setting, initially an environment variable, causes the web UI to be reachable when opencode starts, before /pty-... is processed, while existing manual behavior remains usable.