Status-report skill requires an unavailable recurring loop capability in Codex session.

Reported (UTC): 2026-07-13 18:45

What was being attempted: Start the mandatory proactive 20-minute status-report loop for a substantial two-flake UrlResolver investigation.

What went wrong: The session exposes no CronList, CronCreate, CronDelete, or loop tool. Querying the complete available-tool catalog for names/descriptions matching cron or loop returned an empty list: [].

Impact: The required automatic progress cadence cannot be established, so long-running builds and reproducer runs could leave the user without the skill-mandated periodic report unless the agent manually interrupts work to post updates.

Workaround used: Provide manual commentary progress updates during the task and explicitly note that no recurring loop was created.

Suggested durable fix: Expose the relative-interval loop capability (or compatible cron list/create/delete tools) in Codex sessions where the status-report skill is installed, or revise the skill with a supported fallback mechanism.

Production verification — 2026-07-17

Status: STILL EXISTS. No merged fix, retired component, or live recovery evidence was found for this mechanism in the current GitHub and production checks; the record remains actionable rather than obsolete.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.