openai / openai/codex

Android Remote cannot start new task for trusted WSL2 UNC project

Open
#40,519 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug remote safety-check windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Summary

Starting a new Codex Remote task from the ChatGPT Android app fails for a trusted WSL2 repository on Windows with a project trust verification error. Existing Remote tasks for the same computer/repository can still be resumed.

Environment

  • Codex Desktop for Windows: 26.818.8289.0 (also observed on 26.818.5229.0)
  • ChatGPT Android: 1.2026.230, installed from Google Play
  • Windows 11 with WSL2, Ubuntu 22.04
  • Repository stored under the Linux home directory
  • Project registered in Desktop using the UNC form \wsl.localhost\Ubuntu-22.04\home<user>\work<repo>

Reproduction

  1. Pair Android Remote with Codex Desktop on Windows.
  2. Open the WSL repository in Codex Desktop and mark it trusted.
  3. In ChatGPT Android Remote, select the connected Windows computer and the WSL project.
  4. Start a new task.

Actual behavior

Android displays that the project trustworthiness cannot be verified and asks to open the repository on the Remote computer and choose a trust setting. Re-opening/trusting the original repository, re-pairing, restarting Desktop, and restarting Windows do not resolve it.

Existing tasks can be opened and continued. Desktop reports the Remote client via remoteControl/client/list, but the failed mobile attempt produces no thread/start request on the host.

Desktop logs repeatedly show:

  • git-repo-watcher: EISDIR, illegal operation on a directory, watch '/.git'
  • the same error for refs, refs/heads, info, and the project directory itself

Expected behavior

A trusted WSL2 project can start a new Remote task from Android. Codex should canonicalize/support both \wsl$... and \wsl.localhost... forms, or provide a working migration path for an existing project registration.

Notes

The official WSL documentation recommends opening repositories via \wsl$ and keeping them under /home. The failure occurs before repository instructions or task code execute, so repository AGENTS.md content is not involved.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing project trust verification for new tasks and the remoteControl/client/list flow, then inspect the git-repo-watcher handling of WSL UNC paths. Reproduce with the listed Android, Windows, and WSL2 setup; done means a trusted project can start a new Android Remote task without the trust error.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, rust
Domain
devtools, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.