Codex automation stalls indefinitely on app tool call until generated thread is opened manually

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

Version 26.623.141536

What subscription do you have?

Codex PRO $200 level

What platform is your computer?

macOS: Darwin 25.5.0 arm64 arm

What issue are you seeing?

A scheduled Codex automation started at the expected time and received its automation prompt, but it did not continue executing for roughly 6.5 hours. It only resumed after I manually opened the automation thread in the Codex desktop app.

Local evidence shows the automation session did start and began work, but then blocked on a Codex app tool call:

• Session ID: 019f40a3-1c01-7542-9ca9-533f1faab73d
• Automation ID: pr-review
• Codex app / CLI version in rollout: 0.142.5
• Automation thread source: automation
• Blocked tool: codex_app.list_projects
• Tool call ID: call_BUFwI7nKqgz60LqMd3yojRK9
• Tool call started: 2026-07-08T07:31:29.134Z
• Tool call returned: 2026-07-08T13:51:47.118Z

After the delayed list_projects response returned(which only occurred after I manually opened the thread ~6.5 hours later), the automation immediately continued, created the requested review thread, and proceeded normally. This makes the automation unreliable for unattended work because it appears to require manual UI activation to unstick.

What steps can reproduce the bug?

Feedback ID: 019f420c-c523-71b3-a85b-ecacb965037c

What is the expected behavior?

A scheduled automation should continue executing in the background after the automation prompt is delivered, without requiring the user to open the generated thread in the Codex app.
If an app-side tool call such as list_projects cannot complete, the automation should fail visibly, time out, retry, or report an actionable error in the automation/Triage UI. It should not sit blocked for hours and then resume only after manual thread activation.

Additional information

GitHub would not let me enter more info into the "What steps can reproduce the bug" section outside of my Feedback ID so I am entering that information below:

1. In Codex desktop, create a standalone project-scoped cron automation against a local Git project.
2. Use a prompt that asks the automation to create a background Codex thread/worktree, then poll it. Example shape:

```Assist me with code review for PR #778.

Goal: iterate until two consecutive code reviews do not surface any P0-P2 issues.

Steps:

1. Open a new thread and ask for a thorough code review of the PR branch compared to local main.
2. Poll every 60 seconds until the review is complete.
3. Fix agreed P0-P2 issues and commit changes locally.
4. Archive the review thread.

3. Let the automation run on schedule without opening its generated automation thread.
4. Observe that the automation thread is created and receives the prompt, but execution stalls.
5. Open the automation thread manually in Codex desktop.
6. Observe that the automation resumes and continues from the original prompt without any additional user instruction.