Add `server.enabled` config option to explicitly enable HTTP server

[rmk40]

Problem

Since v1.1.10 (commit 982b71e), the TUI no longer starts an HTTP server by default. While this is a reasonable security improvement, it breaks workflows that depend on the HTTP server:

• Desktop app connecting to the TUI backend
• SDK integrations that communicate via HTTP
• Remote access scenarios (e.g., driving OpenCode from a mobile app)

Current Workarounds Don't Work Well

1. port: 0 - Fails because the schema uses .positive() which rejects 0
2. hostname: "127.0.0.1" - Doesn't trigger server because it matches the default
3. mdns: true - Works but enables mDNS discovery which may not be desired

Users need a clear, explicit way to opt into the HTTP server without side effects.

Proposed Solution

Add a server.enabled config option:

{
  "server": {
    "enabled": true
  }
}

This provides a clear opt-in mechanism that:

• Is self-documenting (the intent is obvious)
• Has no side effects (unlike mdns: true)
• Restores pre-982b71e behavior for users who need it

Implementation

Minimal 3-file change:

1. Add enabled: z.boolean().optional() to Server schema
2. Return enabled from resolveNetworkOptions()
3. Add networkOpts.enabled || to shouldStartServer condition

I have a PR ready with this implementation.

References

• Commit that disabled server by default: 982b71e
• Related PR: disable server unless explicitly opted in #7529

[github-actions]

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

• [FEATURE]: SSH-based remote server connections to OpenCode Desktop #7790: [FEATURE]: SSH-based remote server connections to OpenCode Desktop - Addresses the broader need for remote server connectivity which is one of the workflows mentioned here
• [FEATURE]: Adding Authentication to opencode server api #5256: [FEATURE]: Adding Authentication to opencode server api - Related to securing HTTP server access for remote integrations mentioned in this issue
• [FEATURE]: Make server for webui safe by default #8545: [FEATURE]: Make server for webui safe by default - Related to the security implications of enabling HTTP server by default

Additionally, this issue relates to the deliberate security change in v1.1.10 (commit 982b71e) that disabled the HTTP server by default. You may want to cross-reference the discussions and decisions from that change.

Feel free to ignore if none of these address your specific case.

[thdxr]

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