Repository navigation
feat(autofix): Send PR context tools option for PR iteration - #126743
Merged
Merged
Conversation
Send enable_pr_context_tools in the Autofix feature dispatch's agent run options, true for PR iteration and false for the other steps, next to enable_coding. Seer currently forces the flag on for the step; sending it from here lets Seer pass the options through like every other step, so the decision lives in one place. Refs getsentry/seer#8693
rbro112
approved these changes
Oct 7, 2026
This was referenced Oct 15, 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.
Follow-up to review feedback on getsentry/seer#8693: the Autofix feature dispatch now sends
enable_pr_context_toolsinagent_run_options, true for PR iteration and false for the other steps, next toenable_coding. Today Seer forces the flag on for the step with amodel_copy; this lets Seer drop that override and pass the options through like every other step, so the decision lives in one place. This must merge before the Seer change that removes the override. No production impact expected: Seer already forces the same value, and the path is behindorganizations:autofix-pr-iteration-in-seer, which isn't enabled yet.