fix: improve agent tool guidance - #243
Merged
Merged
Conversation
Expose code_grep context limits in the MCP schema and clarify docs navigation, public repository scope, and pinned source examples.
Separate the docs_read cap note from the surrounding code_grep anatomy documentation.
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.
Summary
code_grepcontext range in MCP JSON Schemadocs_readtext cap and improve CLI grep/version-pinning guidanceget_examplerouting while relevancy work continuesVerification
bun test(2512 passed)bun run typecheckbun run buildbun run format:checkBackend follow-ups
Large-repository indexing reliability, slow ready-target search continuation, and early
INDEXINGreturns remain backend-owned. Authenticated live smoke also reproduced an existing 60-second backend timeout; deterministic registration and unauthenticated smoke passed.