Codex Desktop cron automation hangs on load_workspace_dependencies, while the same call succeeds in foreground tasks

Environment

• Windows, Codex Desktop
• Local standalone cron automation
• Workspace runtime bundle: 26.813.12317
• Time zone: America/Los_Angeles

Issue

A daily local automation needs the spreadsheet runtime before updating an XLSX file. In standalone automation threads, codex_app__load_workspace_dependencies starts but never returns. The same call returns immediately in a normal foreground Codex task using the same project.

Occurrences

• Aug 11, 2026: two attempts, both hung for more than 2 minutes
• Aug 12, 2026: timed out after 20 seconds
• Aug 13, 2026: hung for approximately 38 seconds
• Aug 14, 2026: hung for approximately 88 seconds

Expected

The loader should return the runtime paths, or return a retryable “not ready” error.

Actual

The tool remains indefinitely pending as:

Script running with cell ID …

Impact

Web research completes, but the spreadsheet cannot be updated because the spreadsheet runtime is mandatory and alternative Excel libraries are prohibited. Results are accumulating in a pending backfill queue.

Likely cause

A startup/readiness race in standalone automation threads: the automation begins before the Codex workspace-dependency provider is registered or warmed up.

Start with the codex_app__load_workspace_dependencies entry point and compare its behavior in standalone cron automation threads with foreground Codex tasks. Reproduce the pending "Script running with cell ID …" state using the listed workspace runtime bundle, then verify that the loader returns runtime paths or a retryable “not ready” error instead of remaining pending.