His agent fleet built most of a release, and a pre-launch check caught its routing bug
He released version 0.6.0 of his software, and his agent fleet built most of it. A pre-launch check caught a routing bug where one agent was being sent another agent's model id. Now every routing path runs as a canary before a release.
How it works
- Fleet builds most of the release
- Pre-launch check finds a model routing bug
- He adds canary runs for every routing path before releases
Why it’s worth knowing
The fleet wrote the release and still nearly shipped with one agent quietly using the wrong model.
Where it’s from
Summarized from a public post on njump.me. See the original ↗