docs: clarify API server tool execution locality - #19117
Closed
pingchesu wants to merge 1 commit into
Closed
Conversation
alt-glitch
added
type/docs
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.
Summary
First small PR for #18715.
/v1/capabilities.runtimemetadata so clients can discover currentserver_agent/ server-side tool execution semanticsWhy
When a local client points
model.base_urlat a remote Hermes API server, users may expect normal LLM-provider semantics where tool calls are returned to the client and executed locally. Today the API server creates its ownAIAgent, so tools execute on the API-server host. This PR documents and advertises that behavior before split-runtime work.Test Plan
python -m pytest tests/gateway/test_api_server.py::TestCapabilitiesEndpoint -qpython -m pytest tests/gateway/test_api_server.py -qRelated
Part 1 of the staged work for #18715. Follow-up PRs can add the tool locality/executor abstraction and then the explicit split-runtime bridge.