Static query registration - #63
Open
prinskumar-tigergraph wants to merge 8 commits into
Open
Conversation
Tag queries with a native GSQL description so the agent catalog can pick them by match, without treating every installed query as a tool. Co-authored-by: Cursor <cursoragent@cursor.com>
prinskumar-tigergraph
force-pushed
the
static_query_registration
branch
from
August 31, 2026 10:32
3b395d4 to
a9e818a
Compare
Register Queries now collects the description as the same slots built-in tools use (what it returns, use for, do not use) and merges them into one line, with a preview of what the planner will see. The planner and react strategies resolve the question against the conversation, split it into sub-needs, and match each sub-need to the whole catalog, so a registered query can cover one slice while hybrid or structural covers the rest. Each unstructured step now carries a standalone search question for its own slice, so a compound question no longer sends the leftover wording to vector search. Co-authored-by: Cursor <cursoragent@cursor.com>
…, resolve pronouns from Conversation Co-authored-by: Cursor <cursoragent@cursor.com>
…-multi-clause-routing) Pronoun resolution and standalone unstructured query rules are now in the prompt-multi-clause-routing branch. This branch keeps only the graphrag__gsql__* routing rules: match-description routing, INSTALLED kind, and the GSQL-aware modifications to the Prioritize/Use-BOTH lines.
…ion, clarifying question fallback - When a question refers to something from earlier in the conversation, resolve it from ## Conversation and use the full name in retrieval args. If history has multiple candidates and it is unclear which is meant, ask the user one short clarifying question instead of guessing. - For each unstructured retrieval step, set the question to that clause only as a standalone search query. Do not pass the full multi-part question, a clause already covered by another step, or an unresolved reference from conversation history. - When a question has multiple clauses, assign each clause to its own retrieval step; plan additional RAG steps for any clause not yet covered. - Synthesizer: answer each part of a multi-part question from its matching source; do not mix structured notes with document-passage answers.
… ban cross-clause term bleed
…rid for multi-clause questions
…tory before any retrieval
prinskumar-tigergraph
force-pushed
the
static_query_registration
branch
from
September 7, 2026 11:50
5d126cb to
eec2789
Compare
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
[GRAPHRAG_TOOL]description.graphrag__gsql__*tools; the planner uses one only when the description matches the question.Test plan