osfeed.dev
Release / / with v0.2.48

Desktop Commander MCP v0.2.50

Reconnect a remote device without losing access after a local process failure.

Before you upgrade to v0.2.50

1 to fix

Large stored results are replaced with an omission marker by the new 4 KiB output cap; history is a recent-action record rather than a full result archive.

Behavior changedReview recent tool calls and their arguments and results to recover context.Affects: Users retrieving large results from recent tool historyInferred
Read the evidence

Fuzzy-search telemetry no longer sends `character_codes`.

Behavior changedSet allowed folders, blocked commands, the default shell, file limits and telemetry preferences.Affects: Users with telemetry enabled
Read the evidence

What changed in v0.2.50

v0.2.48 makes remote session persistence the default; v0.2.50 adds local logout and recovery after process failures or revoked devices.

Also: Read PowerShell UTF-16LE files and preserve configuration across multiple server processes.

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

New things you can do

Fixed and improved

Failed process launches no longer kill the server; remote execution recovers after the local MCP process dies. Revoked saved devices require fresh browser authorization.

Now worksRun local commands and edit files from ChatGPT, Claude web or another remote MCP client.
Read the evidence

Multiple Desktop Commander processes no longer overwrite each other's configuration changes.

Now worksSet allowed folders, blocked commands, the default shell, file limits and telemetry preferences.
Read the evidence

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