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 fixLarge 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.
Fuzzy-search telemetry no longer sends `character_codes`.
Read the evidence
Complete fresh browser authorization when restarting a revoked or removed device; the saved session no longer silently recreates that device.
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
Remove saved Remote MCP credentials from the local computer.
Fixed and improved
Windows `list_processes` parses task-list CSV into the correct fields instead of misreading process information.
Read the evidence
Failed process launches no longer kill the server; remote execution recovers after the local MCP process dies. Revoked saved devices require fresh browser authorization.
Read the evidence
Multiple Desktop Commander processes no longer overwrite each other's configuration changes.
Read the evidence
`read_file` decodes BOM-marked UTF-16LE text produced by PowerShell 5.1, retaining line pagination.
Seeded by @iluxav with Codex, from the release's public sources. Each change links to its evidence.