Codex app on Windows + WSL: automation shows no Local option, fails with "no rollout found for thread", and leaves orphaned worktrees

What version of the Codex App are you using (From “About Codex” dialog)?

26.313.415514

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11 with WSL Ubuntu

What issue are you seeing?

In a WSL-opened Git repository, creating/running an automation does not show a Local execution option, only Worktree.

Running the automation causes the UI/thread to flash with:
"no rollout found for thread"

Additionally, failed automation/worktree attempts left behind multiple linked Git worktrees under:
C:\Users\mike\.codex\worktrees\...

These then appeared in VSCode/source control and had to be removed manually.

What steps can reproduce the bug?

1. Open a Git repo from WSL in the Codex Windows app.
2. Create an automation for that repo.
3. Observe that only Worktree appears and no Local option is shown.
4. Run the automation.
5. Observe the UI flashing with "no rollout found for thread".
6. Check git worktree list --porcelain from the main repo.
7. Observe extra linked worktrees under C:\Users\mike\.codex\worktrees\....

What is the expected behavior?

• Automation creation should allow Local or Worktree for a Git repo.
• The automation should run successfully.
• Failed runs should not leave orphaned linked worktrees behind.

Additional information

Environment:
• Repo opened from WSL Ubuntu
• Project path: /home/mike/projects/hosting-verified

What I tested:
• Restarted the app
• Deleted and recreated the automation
• Normal local thread works and returns the correct cwd
• Manual “Worktree” thread still ran in the primary checkout rather than a linked worktree

Observed cleanup required:
The failed worktree flow left behind linked worktrees under C:\Users\mike\.codex\worktrees\...
They could not be removed normally because Git reported modified/untracked files, so they had to be removed manually with:
• git worktree remove --force <path>
• git worktree prune

Session ID:
13cb61d3-2d73-46b4-9120-19248ea0665d

Related issues:
• stale/orphaned thread entries with “no rollout found for thread”
• desktop-created worktree association issues on Windows + WSL