Repository navigation
Router: requests to see profiles go to search - #14
Merged
Merged
Conversation
With room to reason (max_tokens 600), the LLM router sent "Profiles near Indonesia in January 2026" and "Profiles in the Bay of Bengal in September 2026" to custom SQL. The prompt only said statistics go to SQL; it now says a request to see or list profiles is a search even when it names a place or a date, with an example that is not one of the benchmark questions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
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.
What
The LLM router now treats a request to see or list profiles as a profile search, even when it names a place or a date.
Why
The benchmark run after Phase 4 (#13) scored 28/30. Both misses were bare requests such as "Profiles near Indonesia in January 2026", which the router sent to custom SQL. Before #13 the router sometimes ran out of tokens and fell back to keyword routing, which handles these correctly. With
max_tokens=600it now finishes, and the prompt never said such requests are searches.The prompt's example ("Profiles off Sri Lanka in June 2026") is deliberately not a benchmark question. Summary tables ("Summarize the floats…") stay on SQL.
Checks
python -m evalagainst the live API and record the score in a follow-up PR.🤖 Generated with Claude Code