DesktopCommanderMCP · Issues· 252 open

ChatGPT Remote on Windows 0.2.50: non-confirmable safety blocks; request for supported diagnosis and correlation IDs

Remote 0.2.47 can report online/pong while all execution tools return Not connected

Feature request: compact ↓ inbound / ↑ outbound traffic indicators in Remote terminal

Feature request: conversation-scoped Remote sessions for concurrent AI chats

[Remote MCP] Device is online and ping/list_devices work, but first start_process fails; persisted session forces re-auth

Remote 0.2.50 / ChatGPT: broadcast_v1 calls complete locally in ~2s but results return 15–38s later

[Remote MCP] Successful device verification returns terminated Supabase session

Remote device cannot survive a restart: persisted refresh token is never updated after rotation (v0.2.50)

[feat][Remote MCP] Native artifact upload from ChatGPT to a remote device without Base64-in-MCP

[feat] Expose a read-only capability registry for native vs compatibility paths

ChatGPT Remote plugin: allow configuring a custom self-hosted Remote MCP backend

start_search maxResults is per-file and unbounded collector can exhaust memory

Startup takes 25-90+s (causing MCP client connection timeouts) — eager-loads exceljs/pdf-lib/puppeteer on every launch regardless of use

remote: device startup fails with -32603 "Unexpected end of JSON input" when a second DC instance writes config.json; online status is a false green

Android/Termux remote startup: config fetch returns 403 in v0.2.48