feat: enable analyst agent in Rill Developer chat #8796
+6
−9
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
ericpgreen2
changed the title
The developer chat sidebar was hardcoding `developer_agent`, so all questions — including analytical ones — were routed to the developer agent which only has raw SQL tools and no metrics view tools. Now the developer chat omits the agent, letting the router agent classify each message and pick the best agent. When only one agent is accessible (developer_agent feature flag off), the router auto-selects with zero extra cost. When both are available, the router uses an LLM call to classify the question. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
ericpgreen2
force-pushed
the
egreen/developer-chat-router-agent
branch
from
8b07060 to
4b72af2
Compare
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.
The developer chat sidebar was hardcoding
developer_agent, so all questions — including analytical ones — were routed to the developer agent (raw SQL tools only, no metrics view tools). A customer reported that the AI chat was "running raw duckdb sql instead of using the metricsview mcp."Now the developer chat omits the agent, letting the router agent classify each message and pick the best agent per question.