Codex worktree automations run but archive output without surfacing results; chat heartbeat works

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

26.519.41501 (CFBundleVersion 3044)

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

1. Open Codex Automations and create a worktree automation in a local project.
2. Use a very small prompt, for example:

Automation smoke test.
Read only README.md and one local project file.
Do not edit files.
Reply with: Automation smoke test passed.

1. Schedule it to run a few minutes later, or use a simple daily schedule near the current time.
2. Wait for the UI to show Last ran.
3. Inspect the local scheduler database:

sqlite3 ~/.codex/sqlite/codex-dev.db "select id,name,status,rrule,next_run_at,last_run_at,cwds from automations order by name; select automation_id,status,thread_title,source_cwd,inbox_title,inbox_summary,created_at,updated_at from automation_runs order by created_at desc limit 10;"

1. The worktree automation shows last_run_at populated and an automation_runs row with status ARCHIVED, but no useful output appears in the UI.
2. Create a chat-targeted heartbeat automation to a known chat. In my test, that heartbeat did visibly post into the target chat, which suggests dispatch/result routing differs by automation type.

What steps can reproduce the bug?

1. Open Codex Automations and create a worktree automation in a local project.
2. 2. Use a very small prompt, for example:

Automation smoke test.
Read only README.md and one local project file.
Do not edit files.
Reply with: Automation smoke test passed.

1. Schedule it to run a few minutes later, or use a simple daily schedule near the current time.
2. 4. Wait for the UI to show Last ran.
3. 5. Inspect the local scheduler database:

sqlite3 ~/.codex/sqlite/codex-dev.db "select id,name,status,rrule,next_run_at,last_run_at,cwds from automations order by name; select automation_id,status,thread_title,source_cwd,inbox_title,inbox_summary,created_at,updated_at from automation_runs order by created_at desc limit 10;"

1. The worktree automation shows last_run_at populated and an automation_runs row with status ARCHIVED, but no useful output appears in the UI.
2. 7. Create a chat-targeted heartbeat automation to a known chat. In my test, that heartbeat did visibly post into the target chat, which suggests dispatch/result routing differs by automation type.

What is the expected behavior?

After a worktree automation runs, the result should be visible and reviewable somewhere in the app: the automation detail page, previous run history, an inbox item, the project/thread, or a clearly linked run artifact.

If a run is archived, the UI should still make clear whether it succeeded, failed, or produced no output, and should expose the assistant response or failure reason.

At minimum, a simple worktree automation that says Reply with: Automation smoke test passed should surface that exact response or a clear error.

Additional information

_No response_