[Parked pending benchmark evidence] Intent-aware browse query planner
Open
Nobody has claimed this yet.
area/routing
blocked
needs-info
priority: low
product
- Dominant language
- Python
- Stars
- 9
- Forks
- 17
- Avg merge
- 21h 36m
- Merged PRs (30d)
- 22
Description
Context / Problem
- Weak browse queries reduce first-pass routing quality.
- Users repeat queries with trial-and-error wording.
- Clarification loops add latency and cost.
Proposal
- Add deterministic query planner for browse prompts.
- Suggest query variants before route execution.
- Surface reason tags for each suggested variant.
- Keep manual query entry always available.
Acceptance Criteria
- Planner produces stable suggestions for same input.
- Suggestions stay within defined token budget.
- Users can accept or skip suggestions.
- Benchmarks show improved first-pass selection rate.
Implementation Notes
- Keep planner rules explicit and editable.
- Do not auto-execute without user choice.
- Preserve existing browse path by default.
Tasks / Checklist
- Define planner policy and output schema.
- Implement suggestion generation and ranking.
- Add regression tests and benchmark cases.
- Document usage patterns and limits.
References
- Anthropic routing workflow guidance: https://www.anthropic.com/engineering/building-effective-agents
- MCP tools protocol model: https://modelcontextprotocol.io/specification/2025-06-18/server/tools
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Anthropic routing guidance and MCP tools protocol, then define the planner policy and output schema described in the issue. Benchmark cases should establish stable suggestions, token-budget compliance, and improved first-pass selection before implementation; regression tests and usage documentation are also required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100