Repository navigation
Restore Codex model list in Windows background services - #368
Closed
KajoVanBuyten wants to merge 1 commit into
Closed
KajoVanBuyten wants to merge 1 commit into
KajoVanBuyten wants to merge 1 commit into
Conversation
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.
On Windows, Office background services can have npm's Codex shim on PATH but no codex.exe. Node cannot spawn the .cmd shim without a shell, so the hire dialog shows no Codex models. Resolve the npm installation to its Node entry point for catalogue queries while preserving shell-free execution and native executables. Verified with the service-like PATH (7 models), typecheck, build, and 29 focused tests. The full suite reports unrelated existing client-registry and clone-test failures; the client-registry failure reproduces on the unchanged main checkout.