[Bug]: Windows v0.12.0 packaged app: od command is missing, so MCP server cannot be started from the copied guide

[luxi78]

Before you submit

• I searched existing issues and confirmed this is not a duplicate.
• I replaced the example text with the real behavior, reproduction steps, expected result, and version from the app's About menu or od --version.

What happened?

I installed Open Design v0.12.0 on Windows from the official release package.

In the app, Settings / Integrations says Open Design can be used as an MCP server. After clicking Copy guide for an agent, the copied guide tells users to start/use the MCP server through the od CLI, for example:

od doctor
od status --json
od skills list --json
od mcp --daemon-url od://app

It also gives a generic MCP config like:

{
  "mcpServers": {
    "open-design": {
      "command": "od",
      "args": ["mcp", "--daemon-url", "od://app"]
    }
  }
}

However, in the Windows packaged app, I cannot find any od, od.exe, od.cmd, od.ps1, or similar CLI entry in the installed files. It is also not available from PowerShell or cmd.

So the MCP server cannot be started by following the copied guide.

Steps to reproduce

1. Install Open Design v0.12.0 on Windows from the official release package.
2. Open the Open Design app.
3. Go to Settings / Integrations.
4. Click Copy guide for an agent.
5. Try to use the copied MCP config or run od mcp --daemon-url od://app.
6. Search the installed app files for od, od.exe, od.cmd, or od.ps1.

Expected behavior

Either:

1. The Windows packaged app should ship/expose an od command and document how to use it.

or:

2. The copied guide should provide a packaged-app compatible MCP command that does not depend on od being available on PATH.

Open Design version

v0.12.0

Platform

Windows

Logs (optional)

Screenshots (optional)

Additional context

No response

[open-design-bot]

🎉 ✨ Welcome to Open Design, @luxi78!

✨ 🔥 Lit the spark.

🌱 Your first contribution adds energy to the project. Thanks for showing up and helping Open Design grow.

💛 Thanks for helping Open Design grow. Keep building in the open. 🚀

🔗 Share on X (English) · 分享到 X（中文）

[lefarcen]

Hey @luxi78, thanks for the very complete Windows repro — the copied commands plus the screenshot made this easy to pin down.

This looks confirmed on the current code path. The “Copy guide for an agent” flow currently hard-codes bare od ... commands in apps/web/src/components/use-everywhere/agent-guide.ts, while the Settings → MCP install flow pulls /api/mcp/install-info and builds an absolute command + args pair from the running daemon in apps/daemon/src/mcp-install-info.ts and apps/web/src/components/SettingsDialog.tsx. In packaged desktop builds the app does know the bundled CLI/runtime internally, but the copied guide is not using that data, so a Windows install with no od on PATH ends up with MCP instructions that cannot run as written.

So the bug here looks real rather than a local setup issue. The most likely fix is to make the copied guide consume the same install-info payload / absolute launcher command that the MCP settings panel already uses, instead of assuming od is available on PATH. We’ve marked this as a bug and a community PR here would be welcome.

[lefarcen]

If anyone from the community wants to take this on, feel free to comment /claim and pick it up — the repro and likely fix direction are already pretty well scoped here.

[YOMXXX]

/claim\n\nI'll take this. Plan: add a regression around the copied use-everywhere/MCP guide so it no longer assumes bare od when the daemon exposes an install-info launcher command, then wire the guide to the same install-info command/args shape Settings already uses. I'll keep the scope to the copied guide behavior and open a focused PR.

[lefarcen]

Heads-up: PR #4865 is up for this now. It switches the Use Everywhere agent guide to reuse /api/mcp/install-info, so the copied MCP JSON uses the daemon-reported command / args / env instead of assuming od is on PATH. Keeping this issue open until that PR lands.

[lefarcen]

@luxi78 we merged PR #4865 into main for this.

The copied Use Everywhere guide now reuses the daemon's MCP install info instead of hard-coding a bare od launcher, so packaged installs can emit the actual command / args / env tuple the app knows about. That should cover the Windows case you reported where the copied MCP config could not start because od was not on PATH.

When you get onto a build that includes PR #4865, could you try Settings → Integrations → Copy guide for an agent again and confirm whether the generated MCP config works on your Windows install? We'll keep this open until we hear back.

[luxi78]

Works like a charm now! Thanks so much for the fix and hard work @YOMXXX @lefarcen