Repository navigation
Fix and verify Codex hooks on native Windows - #1
Merged
Merged
Conversation
Codex runs hook commands through PowerShell on Windows, where the POSIX '...' quoting made every Office hook fail, so Codex workers never reported status, needs-input or usage. Windows now gets `& '...' '...' 'Event'` with single quotes doubled; POSIX is unchanged. The boot hint and docs say to trust the Office hooks when Codex asks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codex workers on Windows could run normally while every Office hook failed because quoted Node commands used POSIX syntax. Preserve the existing PowerShell quoting fix, verify generated commands through the real Windows shell and authenticated lifecycle bridge, and keep callback failures visible as informational Codex warnings. Large tool events now have a bounded 1 MiB input budget, while only lifecycle metadata reaches the Office.
Add a focused Windows CI job, a Windows junction regression for usage-path containment, and setup/restart troubleshooting in README.md and docs/agents.md. Native SessionStart and UserPromptSubmit callbacks were also verified using installed Codex CLI 0.163.0 and an isolated temporary Codex home, without credentials or model requests.
Validation: npm run typecheck and npm run build passed. All 14 focused Codex tests passed, as did the model catalogue and source-size checks. npm test was attempted on Windows but encountered existing POSIX fixture/platform failures (including Unix executable fixtures and symlink privileges) and stalled; that run was stopped. The existing Ubuntu workflow remains the full-suite check.