fix: harden remote Codex hook callbacks against planted links, replays and slow hook starts (#200835) * fix(codex): harden the remote native hook relay - Remove whatever occupies the stable credential name before the app-server writes the relay credential: fs/writeFile follows links and has no exclusive create, so a link planted between turns redirected the credential. - Accept each remote pre_tool_use and post_tool_use callback once per tool use id and event, require the id, and log every remote callback outcome. - Count the hook CLI deadline from process start: Codex starts its hook timeout before spawning the hook, so slow startup could let Codex kill the hook and run the tool call instead of receiving the relay's refusal. * test(codex): follow the credential delivery change in the relay tests - The child-retention test treated any fs/remove as early disposal. Delivery now removes the stable credential name before it writes, so count only the removals after the last write: none while the yielded parent waits, one after the retained child finishes. - Drop the process-start override from the relay CLI entry points. The deadline always counts from the performance.now() origin, and the test helper moves that origin to the call (or a simulated process age) instead.
fix: harden remote Codex hook callbacks against planted links, replay…
Find Your Interest
- Common misconceptions about implementing accessibility
- Foundations: accessibility roles and responsibilities
- Accessibility foundations
- Screen reader HTML support tables
- Designing for people with disabilities
- Foundations: colour and meaning
- The multiplier effect: How authoring tools can transform web accessibility
- Common misconceptions about disability
- The case for web accessibility in 2023
- The case for web accessibility in 2023





