Repository navigation
Description
Problem
On Windows, Buzz Desktop reports Codex and Claude Code as CLI missing / Not installed, although the CLIs and ACP adapters are installed and runnable from a terminal.
Environment observed:
- Codex CLI is available through the OpenAI WindowsApps installation. The resolved command is an extensionless codex alias under %LOCALAPPDATA%\Microsoft\WindowsApps\ or the packaged Codex resources directory.
- Codex ACP adapter: @agentclientprotocol/[email protected], installed as the npm shim codex-acp.cmd.
- Claude Code CLI: claude.
- Claude ACP adapter: @agentclientprotocol/[email protected], installed as the npm shim claude-agent-acp.cmd.
- The same commands resolve from a terminal, but the packaged Buzz Desktop process does not report them as installed.
This appears to be a Windows discovery/environment compatibility issue rather than a missing installation. GUI-launched applications can have a different or stale environment from a terminal, and Windows App Execution Aliases may be extensionless.
Suggested fix
I prepared a small, focused branch with these changes:
- Include the user npm directory (%APPDATA%\npm), WindowsApps, and other relevant Windows locations in discovery.
- Fall back to paths derived from the home directory when APPDATA / LOCALAPPDATA are unavailable.
- Rebuild the common path list dynamically instead of caching it for the entire process lifetime.
- Probe extensionless Windows aliases in addition to .exe, .cmd, and .bat.
- Add Windows regression coverage for the WindowsApps path and extensionless command candidates.
I have not yet been able to run the Rust build/tests locally because the Rust toolchain is not installed in this development environment. TypeScript checks and git diff --check pass.
I would be grateful if the maintainers could review whether this diagnosis matches the intended discovery behavior and decide whether some or all of the changes are appropriate for upstream. I am happy to adjust the patch based on feedback.
Reproduction
- Install Codex CLI through the Windows desktop/App Execution Alias and install the ACP adapter with npm.
- Install Claude Code and @agentclientprotocol/claude-agent-acp with npm.
- Launch Buzz Desktop from the installed application rather than from a terminal.
- Open Settings → Agents and run discovery.
- Observe Codex/Claude Code reported as missing despite the commands being available in a terminal.
Commit prepared locally: cc5147514 (DCO signed).
Activity
todiane commentedon Oct 16, 2026
My workaround on Windows 11: install Claude ACP adapter globally and restart
I encountered a similar issue with Buzz Desktop on Windows 11. Claude Code was installed and working from PowerShell, but Buzz initially reported it as not installed.
Environment
2.1.261C:\Users\xxxxx\.local\bin\claude.exeChecks performed
claude --versionconfirmed Claude Code was installed and working.where.exe claude-agent-acpcould not find the adapter.npm list -g @agentclientprotocol/claude-agent-acpshowed that the adapter was not installed globally.Solution that worked
I ran the following command in PowerShell:
I then restarted the computer. After restarting, Buzz detected Claude Code and I was able to complete the setup successfully.
In my case, the missing global Claude ACP adapter was the key issue. Installing it globally and restarting Windows resolved the problem. Thought I would add it here in case it helps another Windows user.