Windows: Codex hook failures leave worker status stale

What happened

A Codex worker (Pixel) continues executing commands, but its terminal repeatedly reports:

Hook failed
hook exited with code 1

The office worker activity remains "Open the terminal: complete login and review Office hooks in /hooks" even though its terminal shows subsequent commands, a worktree being created, and investigation of the hook failures. The queue still reports the task as running with no PR.

Steps observed

1. Start a Codex worker in Agent Office on Windows.
2. Let the worker execute tools and continue its task.
3. Compare terminal activity with the office worker status.

This sequence was observed on October 21, 2026; the underlying cause and reproducibility on a clean installation have not been established.

Expected

Hooks succeed and the office reflects current worker activity. If hook delivery fails, surface the failure clearly so an active worker is not mistaken for one waiting for login.

Evidence

• Task: 4bb1adc1df85, titled "What project were we working on last?"
• Worker: Pixel (Codex), b874de4bd6aa.
• Local evidence: .agent-office/scrollback/b874de4bd6aa.ansi and .agent-office/workers.json.
• Terminal shows repeated hook exit-code-1 errors interleaved with successful commands.
• A separate fix/codex-windows-hooks worktree was created during the investigation; no fix has been verified by this report.

Please investigate Windows hook execution and status reporting. The relationship between the hook failures and stale activity is suspected, not confirmed.

Related pull request

Potential fix: #376 (open at filing time). That PR reports a Windows shell quoting problem and successful live hook validation. This report records the observed failure; verification with updated worker hooks is still needed.