| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
When we combine tool sets for agents, there is always a protential
problem with aliasing existing slices and introducing subtle bugs.
Add Tools function that can append tool/tool sets w/o aliasing problem.
|
| |
|
|
| |
It is not used.
|
| |
|
|
| |
Now it's compiled into the syz-agent binary itself.
|
| |
|
|
|
|
| |
Add a tool that executes git grep with the given expression.
It can handle long tail of cases that codesearcher can't handle,
while still providing less output than reading whole files.
|
| |
|
|
|
|
|
|
|
|
| |
Introduce abstract "task type" for LLM agents instead of specifying
temperature explicitly for each agent. This has 2 advantages:
- we don't hardcode it everywhere, and can change centrally
as our understanding of the right temperature evolves
- we can control other LLM parameters (topn/topk) using task type as well
Update #6576
|
| |
|
|
|
|
|
| |
Give LLM the recent commit subjects when it generates description,
so that it can use the same style.
Add infrastrcuture to write end-to-end action tests to test it.
|
| |
|
|
|
| |
More instructions slightly more concrete,
and add details about some bug types.
|
| |
|
|
|
|
| |
Move it so that it can be accessed by the dashboard as well.
Add kernel branch to output (it's needed for gerrit),
provide actual kernel commit hash instead of tag name.
|
| |
|
|
|
|
|
|
|
| |
This adds a flow feature (and creates a new flow using it) called
"sliding window summary".
It works by asking the AI to always summarize the latest knowledge,
and then we toss the old messages if they fall outside the context
sliding window.
|
| |
|
|
| |
Provide base kernel repo/commit and recipients (to/cc) for patches.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Make codeeditor error on nop changes that don't actually change the code.
Make patch testing error on empty patch.
Perhaps we need a notion of "mandatory" tools that must be called
successfully at least once... not sure yet.
|
| |
|
|
|
|
| |
Add DoWhile.MaxIterations and make it mandatory.
I think it's useful to make workflow implementer to think
explicitly about a reasonable cap on the number of iterations.
|
| |
|
|
|
| |
Add code editing tool, and patch testing action to the workflow.
Add a loop that asks to fix/regenerate patch on test errors.
|
| |
|
|
| |
The action checks out a temp dir for code edits and patch testing.
|
| |
|
|
|
|
|
| |
I've added NewPipeline constructor for a bit nicer syntax,
but failed to use it in actual workflows.
Unexport Pipeline and rename NewPipeline to Pipeline.
This slightly improves workflows definition syntax.
|
| |
|
|
|
| |
It can answer complex questions about kernel,
and provide a concise answer to other LLMs.
|
| |
|
|
|
| |
For situations where the user wants to reproduce bugs against a
different repository than mainline.
|
| |
|
|
|
|
| |
Having LLM model per-agent is even more flexible than per-flow.
We can have some more complex tasks during patch generation with the most elaborate model,
but also some simpler ones with less elaborate models.
|
| |
|
|
|
| |
We may want to use a weaker model for some workflows.
Allow to use different models for different workflows.
|
| |
|
