Resuming an agent (SendMessage to a finished agent) raises agent.spawn again, with resume.agentId set. The router treated every resume as a new task: new Tn, fresh routing, the brief replaced by the resume message, the failure count and round base reset. Hence T322's "routed to Sonnet, ran on Opus" for an Opus agent that was only resumed (#4), and verifiers that judged later rounds against the wrong text (#6). - A resume passes through untouched; its message is kept as a later instruction to that agent. Task, routing, failures and rounds stay. - A SendMessage to a tracked agent (by id or by the name its Agent call gave it) that was delivered is kept as a later instruction too. - The verifier prompt lists later instructions after the brief and judges scope added there as in scope. - [router-rewrite Tn]: the stored rewrite is used up only once its agent has started (a failed start kept nothing before: T332 was then routed afresh, to Haiku). With nothing stored the call is refused instead of starting an agent with no brief. The task keeps Tn. - The routing label compares with the model the engine resolved at start, not the one the router asked for. - 11 new tests; each new rule was also broken on purpose and caught. Version 0.4.8. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MdqPWvuDpbpRvDEdURoAwo
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "model-router",
|
||||
"version": "0.4.7",
|
||||
"version": "0.4.8",
|
||||
"description": "Routes each subagent to Haiku, Sonnet or Opus by how well-defined its brief is, verifies dev work below Opus in its own clone on a different model, sends failures back to the same agent then a stronger one, and estimates the savings against Opus.",
|
||||
"author": {
|
||||
"name": "Glenn Schrooyen"
|
||||
|
||||
Reference in New Issue
Block a user