codex-task-inspector

To check the progress of Codex asynchronous tasks, you can use a skill that inspects session and rollout logs, local worker status, and CI polling data to determine if a task is in progress, completed, or failed.

Yes, you can monitor local Codex worker status and CI polling logs simultaneously by parsing their respective log directories, allowing you to track continuous integration job statuses and local task execution in one view.

The best way to inspect a specific Codex task is to run a command with its session or rollout id, such as `bifrost inspect-task codex-task-inspector 019df414-235e-74e3-be4b-84f883e0ea17`, to retrieve detailed task progress information.

Yes, you need Python3 installed, because monitoring Codex continuous integration workflows requires Python scripts for detecting task directories and parsing the asynchronous task log data.

Codex task monitoring may fail to find session logs if the Python3 dependency is missing or if the directory detection scripts cannot access the correct local worker paths to parse the asynchronous task data.

When inspecting Codex rollout logs, the available information includes the current state of the asynchronous task, detailed progress data, local worker running status, and continuous integration polling job statuses.