-
Notifications
You must be signed in to change notification settings - Fork 3.9k
fix: parallel edit clarity #9137
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
base: main
Are you sure you want to change the base?
Conversation
Learn moreAll Green is an AI agent that automatically: ✅ Addresses code review comments ✅ Fixes failing CI checks ✅ Resolves merge conflicts |
1 similar comment
Learn moreAll Green is an AI agent that automatically: ✅ Addresses code review comments ✅ Fixes failing CI checks ✅ Resolves merge conflicts |
|
✅ Review Complete Code Review SummaryTroubleshooting
|
|
No documentation updates needed for this PR. This change clarifies an internal LLM instruction for the editFile tool but doesn't affect user-facing behavior or features documented in our docs. |
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.
No issues found across 1 file
|
The E2E test failure is unrelated to this PR - it's a CI infrastructure issue where the test setup failed to download VS Code from Microsoft's servers ("ReadError: The server aborted pending request"). The PR only changes an internal LLM instruction string and doesn't affect any test logic. This can be safely merged once the flaky CI test passes on re-run. |

Description
Opus is smart enough to interpret the previous prompt as "can only call in parallel with itself"
Summary by cubic
Clarified the editFile tool’s parallel-calling instruction to explicitly forbid running in parallel with any tools, including itself. Prevents misinterpretation and avoids concurrent edit conflicts.
Written for commit 41c4f29. Summary will update automatically on new commits.