Repository navigation
Conversation
1 of 6 tasks
Contributor
Automated Reviewer SuggestionsBased on the
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9496 +/- ##
=========================================
Coverage 91.57% 91.57%
Complexity 5159 5159
=========================================
Files 1300 1301 +1
Lines 58092 58111 +19
Branches 7615 7615
=========================================
+ Hits 53198 53217 +19
Misses 2958 2958
Partials 1936 1936
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Every model call carried the compact schema of each allowed operator type in the system prompt: 18.8 KB by default, 189.2 KB with all 168 types. The add tool also accepted every type, whatever the allowed list said. The prompt now names each usable type in one line, and the agent reads the properties of the types it needs with get_operator_schema, several at once. The prompt's list, the lookup and the add tool share one list of operator types.
bobbai00
force-pushed
the
feat/agent-operator-lookup
branch
from
November 19, 2026 08:38
576416c to
7fd7ae0
Compare
This branch has not been deployed
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.
What changes were proposed in this PR?
Every model call carried the compact schema of each allowed operator type in the system prompt: 18.8 KB by default, 189.2 KB with all 168 types. The prompt also told the model to call a
getOperatorSchematool that did not exist, andaddOperatoraccepted every type whatever the allowed list said.mainget_operator_schema, for several types in one calladdOperatorThis is the first part of #9481;
edit_workflowandexecute_workflowfollow.Any related issues, documentation, discussions?
Part of #9481
Part of #9453
How was this PR tested?
cd agent-service && bun test(352 pass),bun run typecheckandbun run format:check. New tests cover the lookup (several types, an unknown, a disallowed or a miscased type, an empty list), the prompt's list (allowlist, no allowlist, nothing known, no schema left), one list for the prompt, the lookup andaddOperator, and a thrown tool error recorded on its step.The evaluation from test(agent-service): evaluate the agent on real prompts #9495 with Claude Haiku 5.5, three runs per case, against
main:mainA first version kept the types out of the prompt behind a
find_operatortool and looked up one type per call. It passed the same runs but made 5.3 model calls per run for 30,616 input tokens, since the model searched for each type before reading it, so this PR names the types in the prompt and reads several at once.Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 5.5