You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
multi-agent: paired model-routing eval for retrieval, review and mechanical-edit roles #6901
No published measurement covers Claude 5.5 models on this repo's subagent roles: codebase retrieval, code review and verification, and bounded mechanical edits. Routing defaults in plugins/multi-agent/reference/defaults.yaml therefore rest on judgment. Haiku 5.5 may take no role until that role passes this eval.
Proposal
After the Haiku 5.5 documentation PRs land, build a paired eval comparing these setups on the same tasks from this repo:
Haiku 5.5 at high and xhigh
Haiku 5.5 with an Opus 5.5 advisor, using Anthropic's Haiku coding prompt
Sonnet 5.5 at low, medium and high
Opus 5.5 at low and medium
Measure:
pass rate, or verified findings
tokens per completed task (input, output and thinking)
advisor call rate
wall time
State no prices. Use a judge from outside the candidate set, or Opus with its self-preference noted.
Acceptance
An eval suite covers the retrieval, review and mechanical-edit roles
Results are recorded and the routing defaults are confirmed or changed
A role moves to Haiku only when it matches the current model's accuracy at no higher token cost per completed task
Split by the owner's HITL session (2026-10-24, C12, Q93-Q95) into sub-issues. Slices with no blocker can run in parallel; the rest wait on their blocked-by edges. Intake triage sets each slice's fields, then admission takes it.
Activity
github-actions commentedon Oct 11, 2026
Proposed work class: none
Thanks for the report. Automated triage handed this issue to a maintainer.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Oct 25, 2026
The triage verdict left this issue at
status: needs-decision:Size:lineComplexity:lineUncertainty:lineFlags:linekyle-sexton commentedon Oct 25, 2026
Split by the owner's HITL session (2026-10-24, C12, Q93-Q95) into sub-issues. Slices with no blocker can run in parallel; the rest wait on their blocked-by edges. Intake triage sets each slice's fields, then admission takes it.