[Android Remote][WSL] Remote Voice hides workspace-creation failures

Open 💬 1 comment Opened Aug 5, 2026 by kendonB
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Drafted by GPT 5.6 Sol xhigh

Problem

Android Remote Voice fails before starting a realtime session when the WSL host cannot create ~/Documents/Codex.

In my case, ~/Documents was a broken self-referential symlink. The host's workspace-creation process exited, but Android only displayed Voice connection failed. The underlying filesystem error was not shown.

Host logs showed:

thread/realtime/listVoices
process/spawn
process/exited

thread/realtime/start was never called.

Environment

  • Windows Codex app 26.727.6591.0
  • WSL2
  • Android ChatGPT 1.2026.209

Confirmation

Replacing the broken symlink with a real ~/Documents/Codex directory made Remote Voice work immediately with the same Codex binary.

Expected behaviour

Workspace creation should be handled by app-server and return a clear error to the mobile client.

At minimum, Android should check the spawned process's exit status and display its stderr instead of reporting a generic voice connection failure.

Suggested regression test

Attempt Remote Voice startup with an invalid or unwritable ~/Documents path and verify that Android receives an actionable workspace-creation error.

View original on GitHub ↗

1 Comment

github-actions[bot] contributor · 23 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #35899

Powered by Codex Action