Proxy the agent service's tool list - #1370
Merged
Merged
Conversation
The persona editor needs the tool names this deployment actually implements, along with what each one does, so that naming a tool is a choice from a list rather than a guess that fails silently.
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
1 participant
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.
Adds
GET /api/v2/agents/tools, proxying the agent service's new/toolsendpoint.The persona editor currently offers a free-text field for tool names. A name the agent build does not implement is dropped silently when the agent is constructed, so a typo costs the persona a capability with nothing to show for it. This gives the UI the names this deployment actually implements, plus a description of each.
Pairs with yeti-platform/yeti-agents#12, which serves
/tools, and yeti-platform/yeti-feeds-frontend#315, which consumes it. The frontend degrades to the current free-text behaviour if this endpoint is unavailable, so the three are independent at runtime.Test:
test_list_tools_forwards_names_and_descriptions, covering the same field-dropping trap that bitADKSession.