Skip to content

fix(router): llmPick handles meta-phrased 'which agent for X' questions (v0.292.6) - #538

Merged
vikasprogrammer merged 1 commit into
mainfrom
feat/router-metaphrase
Aug 3, 2026
Merged

fix(router): llmPick handles meta-phrased 'which agent for X' questions (v0.292.6)#538
vikasprogrammer merged 1 commit into
mainfrom
feat/router-metaphrase

Conversation

@vikasprogrammer

Copy link
Copy Markdown
Owner

Follow-up to #537. "which agent can help me build a feature?" still disambiguated wrongly — llmPick read the meta-phrasing as a question about routing (→ UNSURE) rather than a task to route.

Its prompt now states a message may be a task OR a "which/who agent for X" question, and to route to the agent best for the underlying work either way. So it → engineer, matching the bare "build a feature" — which is exactly what Cockpit's "Route to an agent instead" sends.

typecheck + build clean; governance unaffected (prompt-only change). Verified live after deploy.

src/edge/router.ts.

🤖 Generated with Claude Code

…ns (v0.292.6)

"which agent can help me build a feature?" still disambiguated wrongly because
llmPick read it as a question ABOUT routing (→ UNSURE) rather than a task to
route. Its prompt now tells the model a message may be a task OR a "which/who
agent for X" question, and to route to the agent best suited for the underlying
work either way — so it → engineer, matching the bare "build a feature". This is
what Cockpit's "Route to an agent instead" sends.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@vikasprogrammer
vikasprogrammer force-pushed the feat/router-metaphrase branch from 48d1021 to 7be8a20 Compare August 3, 2026 08:07
@vikasprogrammer
vikasprogrammer merged commit 9e4d508 into main Aug 3, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant