Repository navigation
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.
Prevent Codex exec tool rejection with Copilot inference #65654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Prevent Codex exec tool rejection with Copilot inference #65654
Changes from all commits
10b887d040d22aa94dbe9File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/diagnosing-bugs] Root cause only partially addressed:
validateCodexManagedConfigonly blocksengine.configTOML overrides. ButbuildCodexCommandappendsworkflowData.EngineConfig.Args(customArgsParam) as the last segment of the generatedcodex exec ...command, aftershellToolParam(-c features.shell_tool=false). Since later-cflags win in Codex CLI arg parsing, a workflow withengine: {id: codex, args: ["-c", "features.shell_tool=true"]}silently re-enables the exec tool for GitHub inference, bypassing the new guard entirely.💡 Suggested fix
Add a check (alongside/near
validateCodexManagedConfig, or inbuildCodexCommand) that scansworkflowData.EngineConfig.Argsfor afeatures.shell_tooloverride whenResolveLLMProvider(workflowData) == LLMProviderGitHub, and rejects it the same way the TOML override is rejected. Add a regression test mirroringTestCodexGitHubInferenceRejectsExecToolOverridebut usingArgsinstead ofConfig.@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/diagnosing-bugs] Confirmed by running
go test ./pkg/workflow/ -run TestConcurrencyQueueSchemaValidation: this change makes the existing test fail, becausequeuewith a GitHub Actions expression (e.g.${{ github.event_name == 'pull_request' && 'single' || 'max' }}) is a documented, tested case that the compiler generates (seeconcurrency_command_test.go's mixed-PR scenario). Dropping theexpressionSyntaxbranch regresses that feature, not just a theoretical risk.💡 Test failure output
Restore the
oneOfwithexpressionSyntaxforqueue, or update/removeTestConcurrencyQueueSchemaValidation's expression case if dropping expression support forqueueis intentional — but as-is this is an unrelated regression bundled into a Codex-provider fix PR.@copilot please address this.
Uh oh!
There was an error while loading. Please reload this page.