fix(codex): pin Node runtime for npm launcher hooks - #213
Open
hxy91819 wants to merge 2 commits into
Open
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
2 participants
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.
Summary
node tokenjuice codex-post-tool-usecommands.Why
Codex hooks may run from a non-login app-server environment with a minimal PATH. An npm launcher that relies on
#!/usr/bin/env nodecan therefore select an unintended or stale system Node runtime, causing PostToolUse to terminate without a usable exit status.Test plan
pnpm exec vitest run test/hosts/codex.test.ts test/hosts/shared/hook-command.test.tsenv -u TOKENJUICE_NO_OMISSION pnpm verify