[Windows Desktop] 26.903.8094.0 app-server queue blocks plugins and Remote Control; recent history omitted after restart

Codex Desktop on Windows repeatedly becomes partially unusable. Messages sometimes fail to send, @ stays on "Loading plugins...", plugin setup says "Failed to load plugin connection", slash commands fail, and Remote Control cannot load devices or save availability. The user reports that symptoms recur after restarts.

Current installed package: OpenAI.Codex 26.903.8094.0. Incident observed September 10, 2026, approximately 02:58–03:30 UTC.

Local AppServerConnection logs show 5–6 in-flight requests and 64 interactive requests queued. plugin/list expires while queued after 30 seconds. remoteControl/client/list and remoteControl/disable are rejected with code -32001, "App server request queue is full". config/read, model/list and history requests also expire. Some turn/steer requests still receive immediate replies.

Please investigate requests retaining scheduler slots, MCP extension-host lifecycle and possible Windows stdio blocking-pool exhaustion. Related reports: https://github.com/openai/codex/issues/43122 and https://github.com/openai/codex/issues/42740. Our current renderer has staleTime:Infinity without an explicit gcTime on mcp-extension-host-thread, but we have not proved the live eviction trigger or identified which dispatched requests are retaining scheduler slots.

Remote behavior differs between accounts. The same underlying cause on other devices is unverified. Please provide a durable fix and a safe recovery that preserves active work, plugins and credentials.

Additional incident after restart around 03:46 UTC: the conversation UI restored older scheduled-task turns instead of the recent diagnostic messages. Native process creation times confirm the app was replaced. The local JSONL contains actual assistant message records from 03:40:11 and 03:43:55 before restart and continues to append after restart. A task-history read also returned older in-progress turns. Recent records were persisted; why they are omitted from the displayed history is unresolved. This may be a separate history-loading defect. No session database, conversation file, credential or plugin cache was changed during this investigation.

Start with the local AppServerConnection logs and the mcp-extension-host-thread configuration, tracing requests that retain scheduler slots and the Windows stdio blocking pool. Compare the persisted JSONL records and task-history results with the conversation UI after restart. Done means a durable queue fix and safe recovery that preserves active work, plugins, credentials, and recent history.