Codex App reconnect loop when stale deleted workspace path is still referenced (ENOENT in git-origins)

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

26.305.950

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Darwin 24.6.0 arm64 i386 (macOS 15.6.1)

What issue are you seeing?

I frequently get Reconnecting... in Codex App, while Codex in terminal is stable on the same machine/network.

Observed logs repeatedly show stale workspace path resolution failures for a deleted folder:

• [git-origins] failed to list worktrees for dir=/Users/lijunjie/Downloads/awesome-story-generation
• ENOENT: path does not exist: /Users/lijunjie/Downloads/awesome-story-generation
• [git-origin-and-roots] Failed to resolve origin for workspace ...

This path was deleted already, but the app still tries to resolve git metadata for it.

I prepared a fix in my fork (I cannot open PR due repo policy: only collaborators can open PRs):

• Fork branch: Picrew/codex:fix/skills-list-missing-cwd-error
• Commit: 6dd9644
• Compare: https://github.com/openai/codex/compare/main...Picrew:fix/skills-list-missing-cwd-error
• Changed file: codex-rs/app-server/src/codex_message_processor.rs
• Added test: codex-rs/app-server/tests/suite/v2/skills_list.rs

Patch behavior:

• In skills/list, if a requested cwd does not exist, return a structured per-entry error and continue.
• This avoids bubbling ENOENT into deeper skill/git metadata paths and keeps response shape deterministic.

Expected:

• Missing/deleted workspace paths should not cause repeated error cascades or reconnect loops.
• App should handle stale paths gracefully and report a clear entry-level error.

What steps can reproduce the bug?

1. Open Codex App (version 26.305.950) on macOS 15.6.1.
2. Open a workspace directory in Codex/paired IDE.
3. Delete that workspace directory from disk (example: /Users/lijunjie/Downloads/awesome-story-generation).
4. Keep using Codex App and send prompts in the same conversation/session.
5. Observe intermittent/frequent Reconnecting... in the UI.

Observed logs include repeated missing-path failures:

• [git-origins] failed to list worktrees for dir=/Users/lijunjie/Downloads/awesome-story-generation
• ENOENT: path does not exist: /Users/lijunjie/Downloads/awesome-story-generation
• [git-origin-and-roots] Failed to resolve origin for workspace ...

Note:

• On the same machine/network, terminal Codex usage is stable.
• App appears to keep resolving git metadata for a stale deleted workspace path.

What is the expected behavior?

Codex App should handle deleted/stale workspace paths gracefully.

Expected behavior:

• If a requested workspace cwd no longer exists, return a clear structured entry-level error for that path.
• Continue processing other valid paths without cascading failures.
• Do not trigger repeated reconnect behavior in the app UI due to stale path metadata resolution.

Additional information

_No response_