[FEATURE]: Windows desktop ships the CLI but there is no way to run it #55772

Activity

1. opencode-agent commented on Oct 15, 2026

   

   opencode-agentBot

   on Oct 15, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the detailed request! You're asking for the Windows desktop app to give you a way to run the CLI it already bundles: either an install action like the one on macOS that puts an opencode command on PATH, or a way to start the TUI from the existing "open PowerShell in the project directory" action.

   You're right that the install action only supports macOS for now: packages/desktop/src/main/service/desktop-cli.ts stops on every other platform. Maintainers will consider this.

   Related issues:

   • [FEATURE]: Bundle Desktop App with CLI Binary for Better Enterprise Management #43605: bundling the desktop app with the CLI binary
   • desktop: stale cli/<version> binaries are never pruned, disk grows ~175 MB per update #53617: old cli/<version> binaries are never removed
   • feature(desktop): system tray icon with clean shutdown of the background opencode-cli service (Windows) #50633: tray icon and clean shutdown of the background opencode-cli service on Windows
   • cli: v2 Windows PowerShell install cannot be upgraded in place #51755: the Windows PowerShell install can't be upgraded in place
   • [FEATURE]: Disable opencode cli on windws when using WSL #53952: an option to turn off the bundled CLI on Windows when using WSL
2. sogeisetsu commented on Oct 26, 2026

   

   sogeisetsu

   on Oct 26, 2026

   Author

   More actions

   The bundled CLI is already staged on Windows: DesktopCli.resolve copies resources/opencode-cli.exe to <userData>/cli/<version>-<arch>/opencode-cli.exe and returns it as cli.binary. So the smallest fix that gives Windows a TUI without touching PATH:

   • packages/app/src/shell/commands/desktop-menu.ts: the app.installCli item lives in the app menu, which is platforms: ["macos"], and menu.ts returns early on non-darwin — so on Windows there is no entry point at all. Add the item to file or help with platforms: ["windows"].
   • packages/desktop/src/main/service/desktop-cli.ts: the process.platform !== "darwin" guard sits in front of the whole install, but only the PATH installer is macOS-only. A Windows branch can just open the project directory and spawn the resolved cli.binary via wt.exe, falling back to powershell.exe.

   That avoids editing PATH, stale versioned shortcuts, and collisions with an existing npm/zip opencode on PATH.

   If you'd rather have the real install-to-PATH behaviour, it's a copy to %USERPROFILE%\.opencode\bin\opencode.exe plus an idempotent HKCU\Environment PATH edit that preserves REG_EXPAND_SZ (so not setx), which needs more care, and it should probably be skippable for WSL users (#53952).

   Happy to do this work if a maintainer approves the direction — I've read the code paths above but haven't built the desktop app yet.