/goal runtime includes approval-wait time

What version of Codex CLI is running?

0.130.0

What subscription do you have?

pro

Which model were you using?

gpt-5.5

What platform is your computer?

macOS

What terminal emulator and version are you using (if applicable)?

Ghostty 1.3.1

What issue are you seeing?

When /goal is waiting for user approval, the /goal time accounting keeps advancing as if work is in progress, even though execution is blocked waiting on approval. This makes goal timing and runtime attribution misleading.

What steps can reproduce the bug?

1. Start a /goal session with a workflow that requires permission approval.
2. Let the agent reach an approval gate (for example, a dangerous-operation confirmation or equivalent sandbox/tool approval prompt).
3. Delay approval for an extended period (e.g., several minutes).
4. Observe the /goal time/usage counters while approval is pending.
5. Approve and resume.
6. Confirm the waiting interval was counted similarly to active goal runtime.

What is the expected behavior?

/goal should pause or mark the session as blocked while waiting for approval and avoid attributing approval-wait latency as active run time. This is suboptimal to track the actual time the model spent working.