0.6.3 - Codex asks, the lane says Waiting
Pre-releaseA Codex question now lights the lane. Codex asks you things through its request_user_input tool - the multiple-choice prompts in plan mode - and that tool is the dialog: it starts when the question appears and returns when you answer. The app never saw the start, only the answer, so the lane read Running the whole time you were being asked. It now registers Codex's PreToolUse for that one tool alone (the hook fires for nothing else, so there is no extra traffic) and puts the lane on Waiting the moment the question is up; your answer clears it at once. Claude's hooks are untouched.
A Codex plan waiting for your verdict lights the lane too. Codex has no dialog for "implement this plan?" - it ends the plan-mode turn with the plan in its last message and its UI offers the choice from that - so the lane used to read Done at exactly the moment it wanted you. The hook now reports one fact about that final message, whether it carries a proposed plan (the message itself never leaves the agent), and the lane reads Waiting until you answer; accepting, declining or editing all come back as your next prompt and clear it.
Also measured and stated in the window rather than hidden: Codex reports a command only once its process has exited. If you allow it to start a server or a long npm install, the lane holds Waiting until some later command finishes - Codex has no event for the approval itself. Claude clears within seconds as before.
Upgrade: unzip, run once, delete the folder - the running copy is retired and replaced automatically. Codex then needs the new hook entry trusted: /hooks in the CLI, Settings > Hooks in the desktop app; until then the question lane stays as it was. No agent restarts needed for Claude.