osfeed.dev
Release /

Desktop Commander MCP v0.2.22

Start Desktop Commander through npx on Windows without the previous connection failure.

Before you upgrade to v0.2.22

2 to fix

Windows users with failed npx connections should rerun `npx @wonderwhy-er/[email protected] setup`; generated configuration uses `cmd /c npx`.

Action requiredConnect an MCP-compatible AI client to local file and terminal tools.Affects: Windows npx installations failing to start or connect
Read the evidence

Replace `get_prompts` actions `list_categories` and `list_prompts` with `get_prompt` and a required `promptId`; those listing actions are no longer accepted.

Action requiredOpen getting-started examples for local file and terminal workflows.Affects: Clients calling the removed onboarding listing actionsInferred
Read the evidence

What changed in v0.2.22

Windows setup now launches through `cmd /c npx`; onboarding is simplified and its tool accepts only named prompts.

Install @wonderwhy-er/[email protected] with Node.js 18+ and an MCP-compatible client.

Seeded by @iluxav with Codex, from the release's public sources. Each change links to its evidence.