Codex Desktop managed worktree creation reports AGENTS.override.md failure even though git worktree add succeeds and no ls-files command is spawned
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.616.71553 • Released Jun 22, 2026
What subscription do you have?
Corporate
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
Codex Desktop managed worktree creation fails for a large private monorepo.
The UI reports:
git ls-files failed while locating AGENTS.override.md
However, Git tracing shows that git worktree add succeeds, and the expected
post-create git ls-files --others --ignored --exclude-standard -z -- command is never spawned.
':(glob)**/AGENTS.override.md'
No Codex thread is ever started. The worktree does get created successfully, but cannot be used via Codex.
What steps can reproduce the bug?
- Open the repo in Codex Desktop.
- Start a new thread using a managed worktree.
- Worktree creation fails after
git worktree add. - UI reports the AGENTS.override.md error.
What is the expected behavior?
After successful git worktree add, Codex should complete post-create setup
and start the thread, or report the real underlying command/lifecycle error.
Additional information
- Git: Apple Git 2.50.1
- Repo shape: large private monorepo, about 68k tracked files, about 900 MB checkout
Manual checks:
git worktree add --detach ... mainsucceeds.- The exact AGENTS scan succeeds when run manually.
- A fresh clone of the repo has the same failure.
- Parallel checkout reduced worktree creation from about 14s to about 7s, but the failure remains.
Git trace evidence:
git worktree add --detach <codex-worktree-path> mainexits 0.- No traced invocation of:
git ls-files --others --ignored --exclude-standard -z -- ':(glob)**/AGENTS.override.md'
- Desktop logs around the same attempt show a new conversation/worktree lifecycle issue,
including "Received turn/started for unknown conversation" while worktree creation is in progress.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗