pkg/aflow: initial version of patch-iteration agent#7081
Merged
a-nogikh merged 6 commits intogoogle:masterfrom Apr 28, 2026
Merged
pkg/aflow: initial version of patch-iteration agent#7081a-nogikh merged 6 commits intogoogle:masterfrom
a-nogikh merged 6 commits intogoogle:masterfrom
Conversation
a-nogikh
force-pushed
the
features/patching-iteration-workflow
branch
2 times, most recently
from
7d68450 to
adfb0cd
Compare
a-nogikh
added
the
AI patching
a-nogikh
force-pushed
the
features/patching-iteration-workflow
branch
4 times, most recently
from
6f64d62 to
8378939
Compare
a-nogikh
force-pushed
the
features/patching-iteration-workflow
branch
2 times, most recently
from
a9dcf84 to
cd173a8
Compare
dvyukov
reviewed
Apr 17, 2026
a-nogikh
force-pushed
the
features/patching-iteration-workflow
branch
2 times, most recently
from
db1fe1a to
f37a2be
Compare
Collaborator
Author
|
PTAL |
tarasmadan
force-pushed
the
features/patching-iteration-workflow
branch
from
f37a2be to
2d5da18
Compare
dvyukov
reviewed
Apr 27, 2026
a-nogikh
force-pushed
the
features/patching-iteration-workflow
branch
from
2d5da18 to
b885f50
Compare
Log trajectory. Fill in variables in the false path. Improve verification.
The operator will let workflows iterate over an array and do processing for each item separately.
This will be necessary to let workflows take / produce more complex inputs.
The patching workflow was previously only capable of generating the initial V1 patch. Add a new `patch-iteration` workflow that automatically addresses reviewer feedback on generated patches. The workflow executes the following high-level pipeline: 1. Verdict: Analyzes the new comments to decide if they require a new code revision, or just a textual reply. 2. Patch Generation: If a code change is needed, reapplies the previous patch to a clean kernel tree, instructs the LLM to modify it to address the feedback, and generates a new changelog. 3. Triage: Evaluates each individual comment to decide whether it requires a direct reply. 4. Aggregation: Aggregates the generated replies and outputs them along with the (possible) V+1 patch.
a-nogikh
force-pushed
the
features/patching-iteration-workflow
branch
from
b885f50 to
6d0af67
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files
🚀 New features to boost your workflow:
|
It should not distort comments as much as html escaping does.
Collaborator
Author
|
Pushed JSON escaping as a separate commit so that it's easier to see the diff. |
dvyukov
approved these changes
Apr 28, 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
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.
This PR follows up on #7047, but the code changes are independent from it.
Add a workflow to iterate on the patch candidate.
The workflow executes the following high-level pipeline:
Note The input/output data of this workflow are more complex than in other cases, so the PR also includes the changes to the
pkg/aflowframework, specifically to permit nested structures and arrays in the input.One limitation of the current implementation: it does not track the usage of nested fields. It probably should?