Files
archived-orca/src/main/codex
Neil b29ae01912 fix(automations): show why a hook-review-blocked automation fails, keep it running, and stop stuck-tab pile-up (#33638)
* fix(automations): pause a schedule whose agent is stuck on a hook review

Codex opens a blocking 'Hooks need review' dialog when a hook in hooks.json is
new or changed. Only a person can answer it, so every later scheduled run of
an automation hit the same dialog and failed. Pause the schedule on the first
such failure and say how to recover. Also re-enable Orca's own Codex hook on
SSH installs, matching local installs.

Refs #28252 #23289

* fix(automations): keep a hook-review-blocked schedule running and say why it fails

Replace the auto-pause with a visible, self-clearing failure: the run error
explains the Codex hook review, the automation and run pages show it above
saved output, and earlier tabs stuck on the same prompt close so only the
newest stays open to answer. Runs succeed again on their own once the hooks
are trusted or removed.

* fix(automations): only close hook-review tabs the run still owns and that are provably unused

- Cleanup resolves the pane through runOwnHandle, so a cold-restored pane holding a new process is left alone.
- Close only on definite 'unused' input history, matching headless run-terminal retention.
- Catch failures from the fire-and-forget cleanup call.
- Show the run page error notice only for dispatch_failed runs, and add the missing en catalog keys.
2026-10-26 23:21:28 -07:00
..