[FEATURE]: Integrate opencode serve as a first-class monitor mode in the desktop client

Summary

• I have searched for existing issues before filing this

Integrate opencode serve as a first-class, optional monitor/mode within the OpenCode desktop client — so users can serve their local instance to mobile or other devices without running a separate sidecar process.

Problem

Today, opencode serve must be run as a separate process alongside the desktop client. This creates:

1. Mobile access friction — users who want OpenCode on their phone/tablet must set up serve as a sidecar, manage auth, port forwarding, and reverse proxy manually
2. Fragmented UX — "Run OpenCode" and "Serve OpenCode" are two separate mental models; most users don't discover serve exists
3. Half-baked integrations — plugins like neohiro/mobile-sync exist to fill this gap but are inherently limited because serve was never an integrated feature
4. No unified session/project sharing — serve as a sidecar doesn't carry OpenCode's session context naturally between devices

Proposed Solution

Add a "Serve Mode" toggle in the desktop client:

Status Popover → [ ] Enable Serve
┌─ Serve Settings ──────────────────┐
│ Port:     [ 18792 ]              │
│ Auth:     [x] Require password  │
│ Network:  ( ) Local only         │
│           (•) Accessible LAN     │
│           ( ) Public (Tunnel)   │
│ Password: [ ••••••••••••••••• ] │
└──────────────────────────────────┘

Behavior:

• Serve starts/stops within the same OpenCode process
• Session and project context is shared naturally (same process)
• Auth is integrated with the client's auth system
• Client shows a "Serving" indicator with URL and QR code
• Future: built-in tunneling for true mobile access

Related Issues

OS

Primarily Windows and macOS (desktop use case). All platforms benefit.

🦙 Creative Monkey at FrenzyPenguin Media — open-source security hardening & privacy tools