fix: prevent futile retries after empty or deferred results - #269
Merged
Conversation
Add bounded empty-result guidance, explicit deferred-search continuation, and shared indexing error details across MCP and CLI output. Preserve backend diagnostics and structured JSON while preventing identical retry loops.
Stop polling terminal search sessions and keep empty grep pivots accurate for case sensitivity and each command surface. Standardize continuation copy and compact scan context.
Expose backend progress waiting through MCP and CLI with the shared bounded default. Keep terminal-session recovery consistent across text and JSON, and align grep truncation guidance with normalized producer values.
Use explicit undefined types with defaults for public error metadata constructor parameters so the standalone MCP declaration build succeeds without changing call-site behavior.
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.
Summary
Release follow-up (required)
This PR deliberately does not bump package versions. A separate release PR must bump both the root
githitspackage and@githits/mcp; the MCP package must move off the already-published0.6.4or the MCP release workflow will skip publishing these changes. After publication, the hosted remote MCP must consume the new@githits/mcpversion and be redeployed before remote users receive the new guidance andsearch_status.wait_timeout_msbehavior.Validation