"Run now" does not work with automation

Open 💬 1 comment Opened May 22, 2026 by ppenteado13

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

26.519.31651

What subscription do you have?

Plus Plan

What platform is your computer?

Windows 11

What issue are you seeing?

Codex Desktop automation runner failure.

Automation: ooh-phase-3-pm-morning-check-9-30
Workspace: C:\Tract In\OneDrive - Private\Tractin Leadership Team - oOh! Media\Phase 3
Schedule: weekdays 9:30am
Execution: Local
Model originally: GPT-5.2
Retested after changing to: GPT-5.5
Result: same failure.

Observed behaviour:

  • Run now creates a new run/dialog.
  • The run dialog is completely blank.
  • The automation page remains active and shows the full prompt.
  • The previous runs show spinning status indicators and never complete.

Local evidence:

  • Three manual runs created session files, but each session file contains only session_meta.
  • There is no turn_context, no user_message, no task_started, no agent output, and no error message.

Session files:
C:\Users\ppent\.codex\sessions\2026\05\22\rollout-2026-05-22T12-20-07-019e4d7b-9e02-7103-9e74-cb1082ad50e5.jsonl
C:\Users\ppent\.codex\sessions\2026\05\22\rollout-2026-05-22T14-02-31-019e4dd9-5f97-72e2-a5a7-c9764ce7f2c6.jsonl
C:\Users\ppent\.codex\sessions\2026\05\22\rollout-2026-05-22T16-17-55-019e4e55-5318-79a3-b057-eae01727e150.jsonl

Likely failure point:
The automation run container is being created, but the automation prompt is not being injected into the run. This appears to fail before the agent starts.

What steps can reproduce the bug?

Feedback ID: 019e4d65-adae-7212-a7c8-3c360d6330f2

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗