[feature] Add Windows background-service support for the V2 local CLI #2182

Automatically submitted on behalf of the user by an AI agent.

@RhysSullivan, could Executor V2 offer a supported way to keep the local CLI server running across Windows restarts?

What happened

On Windows 11 with Executor 2.0.0-beta.8, the local MCP endpoint was configured as http://127.0.0.1:4312/mcp. After restarting OpenCode, its connection failed with ConnectionRefused. At diagnosis time, no Executor process was running and nothing was listening on port 4312. The local API key was still present; the endpoint itself was down.

The CLI docs explain how to run executor or executor serve and say to keep Executor running while the client is connected, but the V2 CLI has no documented Windows background-service or login-autostart setup. The server had been started as a regular CLI process, so it wasn't restored when that process went away.

Request

Please add an optional, supported Windows background-service or scheduled-task install flow for the V2 CLI, with clear start/stop/status and uninstall behavior. If persistent startup is intentionally out of scope, document the recommended Windows way to keep the local MCP endpoint available after restart.

This is related to #2173, but that issue is about V1 command aliases and migration hints; this request is specifically about V2 server lifecycle and persistence.

Environment

• Windows 11 x64
• Executor 2.0.0-beta.8
• Node.js 26.10.0
• OpenCode 2.0.22