Hand bug reports to Muse first
Workflow
Give the Muse model a bug report and ask it to explain the cause and check whether a fix is already open as a PR (a proposed code change waiting to be merged).
Theo's current stance
On a real T3 Code bug, Muse gave a readable explanation and found a smaller, cleaner existing fix. Opus and GPT-6.1 Soul did neither.
Try it
- Paste a bug report and ask what is broken, in short readable terms.
- Ask it to check open PRs for an existing fix before writing new code.
- Prefer merging a small existing fix over a new one.
First seen
23:37
Opus one. So, not only was this model's response much much much more easy to understand, it also found a much smaller, cleaner PR somebody else had already filed that fixes the problem. None of the other models found a PR that fixed it. None of the other models had a readable output on what the problem was,
Every mention
23:37
Opus one. So, not only was this model's response much much much more easy to understand, it also found a much smaller, cleaner PR somebody else had already filed that fixes the problem. None of the other models found a PR that fixed it. None of the other models had a readable output on what the problem was,
24:19
stuff, and I will be throwing it a lot of bug reports going forward just in case I want to understand what's wrong, and maybe somebody else already has a
Theo Daily is unofficial and not affiliated with Theo or t3.gg. Written by Claude Opus 5.5 from each video's transcript.