Codex over SSH fails on headless Windows: sandbox runner can't start in Session 0
Chance-Struggle-6285 · reddit · 2026-09-06
A Reddit user documented how Codex fails over SSH against a headless Windows 11 workstation:
- Both the VS Code Remote-SSH extension and Codex CLI 0.153.4 time out after 15000ms connecting the runner pipe; codex --version works but any file operation hangs.
- Testing sandbox configs shows only danger-full-access works, pointing to the Windows sandbox runner failing to start in a non-interactive OpenSSH session (Session 0 / window station), matching issue #30839.
- The desktop app's Remote just says "SSH connection failed" with no detail, and "Control other devices" is missing from Settings.
Local and RDP sessions work fine, but RDP defeats the thin-client setup. The user asks whether anyone has solved this, whether WSL2 dodges it, and if the feature has rolled out on Windows.
More from coding & agent
- Spec-to-APK entirely on an Android phone via Termux CLI and AI — Digital_Otorongo · 2026-09-06
- Astra review: executes hour-long agentic tasks while iterating on the plan without losing the thread — ivan_bezdomny · 2026-09-06
- Stop picking coding models on vibes: run your own A/B/C refactor tests — robleclerc · 2026-09-06
- Orca, the 62k-star ADE for running parallel coding agents, recommended for Mac Mini dev setups — kieranklaassen · 2026-09-06
- Dev Abandons LLM Agent Harness After 883 Commits and 8 Months, Open-Sources the Wreckage — dancingwithlies · 2026-09-06
- Dev one-shots a UEVR fork with GPT 6 Astra for true stereoscopic VR windows — pvncher · 2026-09-06