Possible bug: Codex Automations (Beta) test runs stay IN_PROGRESS with no output

Codex
1

Hi everyone, sharing a reproducible issue I hit while testing Codex Automations (Beta).

Environment:

  • Windows + WSL workflow
  • Codex Desktop, codex-cli 0.108.0-alpha.8
  • Automation status: ACTIVE
  • CWD points to a WSL repo path (UNC style)

Repro:

  1. Create/update an automation (also tested with a minimal one-line prompt).
  2. Click Test (and also waited for scheduled trigger).
  3. Check Automations/Inbox for output.

Expected:

  • Run completes and produces an inbox/thread result.

Actual:

  • Test appears briefly then disappears.
  • No inbox output is created.
  • Local automation DB shows:
    • automations.last_run_at updates (trigger seems to fire),
    • automation_runs row is created,
    • status remains IN_PROGRESS indefinitely,
    • inbox_items stays empty.

Troubleshooting tried:

  • Restarted app (normal + admin).
  • Retried with different WSL UNC path variants.
  • Simplified prompt to minimal output.

Looks like trigger bookkeeping works, but execution/result materialization stalls. Happy to provide additional redacted diagnostics if useful.

2

It appears you are using the new Codex Windows app and reporting a problem.

If so then see this reply

3

Hi @EricGT , you mean i should add possible bugs on the form, under “Please share detailed feedback to explain your decision above.” ?

1 Like
4

Yes.

The other official way is to use the GitHub OpenAI Codex issues by first searching to see if this has not been reported. If it has just add a thumbs up to the current issue. If not create a new issue.