Add MCP response guidance hints - #2743
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
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
next_step_suggestionto non-empty MCPsearch,references, andexcerptstructured responses.recovery_hintto empty MCP read-tool responses across search, symbol graph reads, excerpt, impact analysis, unused symbols, and hotspots.Validation
dotnet builddotnet run --project tools/CodeIndex.Changelog -- checkdotnet test tests/CodeIndex.Tests/CodeIndex.Tests.csproj --filter "FullyQualifiedName~McpServerTests"withcommit.gpgsign=falseDocumentation and Changelog
changelog.d/unreleased/1641.added.mdchangelog.d/unreleased/1812.added.mdsrc/CodeIndex/Mcp/McpToolDefinitions.csReview
origin/main..HEAD; no blocking/actionable issues found.codex execreview attempt was blocked by usage limits.Follow-up Candidates
Fixes #1641
Fixes #1812