Repository navigation
Let Harnesses own function and MCP URL limits - #770
Merged
Merged
Conversation
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.
Core and the adapters no longer apply limits that neither the pinned official schema nor a Harness defines.
server_urlmay carry a query, as every native MCP client accepts. Userinfo and fragments stay rejected. A Vault Credential for a query URL now matches the Session server, since matching is byte for byte.Usage.Modelwith the requested model when the Harness reports none.Docs: execution-tools.md and wire-semantics.md with zh mirrors.
Tests: 65 functions with a 600-byte name are admitted; a query URL is admitted and reaches the Runtime binding unchanged; the Claude bridge accepts a query and rejects a fragment.
Need help on this PR? Tag
@codesmith-botwith what you need.