| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
There is no point in using Provide more than once,
and anywhere besides the first action of a flow.
So it's not really an action, but more of a flow property.
Add Flow.Consts field to handle this case better.
Also provide slightly less verbose syntax by using a map
instead of a struct, and add tests.
|
| |
|
|
|
|
|
|
|
| |
It's very inconvinient to hardcode exact LLM replies in this test,
because it's hard to understand when exactly it will be asked to summarize.
It's easy to make a bug in the test, and provide summary reply when it wasn't asked to.
Instead support proving full generateContent callback,
and just model what an LLM would do -- provide summary only when it's asked to.
|
| |
|
|
| |
Don't memorize repeated request configs.
|
| |
|
|
|
|
|
| |
Handle LLM tool input token overflow by removing the last tool reply,
and replacing it with an order to answer right now.
I've seen an LLM tool went into too deap research and in the end
just overflowed input tokens. It could provide at least some answer instead.
|
| |
|
|
|
|
|
|
| |
A bunch of NFC refactorings:
- split action verification into 2 phases (inputs/outputs)
- change how LLMTool is verified
- remove some unused fields/parameters
- improve error messages a bit
|
|
|
Add helper function that executes test workflows,
compares results (trajectory, LLM requests) against golden files,
and if requested updates these golden files.
|
