Codex task progress is not updated incrementally, making it impossible to intervene during execution

Summary

When Codex executes multiple tasks within a single thread, the task progress indicator does not update incrementally. Instead, it often jumps directly from 0/4 to 4/4, or briefly shows 1/4 before immediately completing all tasks.

This behavior makes it difficult to monitor execution progress and prevents timely intervention when a task does not meet expectations.

Steps to Reproduce
Start a Codex thread that triggers multiple tasks (e.g., 4 tasks)
Observe the task progress indicator during execution

Expected Behavior
Task progress should update step-by-step (e.g., 1/4 → 2/4 → 3/4 → 4/4)
Each task should be marked as completed individually
Users should be able to identify which task is currently running
Users should have the opportunity to stop or interrupt execution mid-way

Actual Behavior
Progress jumps directly from 0/4 to 4/4, or:
0/4 → 1/4 → 4/4
No clear indication of intermediate task execution
Tasks appear to complete in a batch rather than incrementally
Users cannot determine which task is currently running
No clear opportunity to stop execution at a specific task

Impact
Difficult to debug or validate intermediate results
Prevents fine-grained control over task execution
Leads to inefficiency when re-running tasks due to partial dissatisfaction
Reduces transparency of Codex execution workflow

Suggested Improvements
Ensure task progress updates in real-time for each completed sub-task
Expose currently executing task in the UI
Allow users to interrupt or cancel execution at any step
Optionally provide logs or checkpoints per task