A week with Claude Opus 5.5: six tips to save your credits

every · x · 2026-09-23

After testing Claude Opus 5.5 for a week, the Every team shared six practical tips:

Set a budget and stopping point: it won't stop on its own and will eat your weekly limit; define what "done" looks like
Ask for the deliverable first: given 10 minutes for a run of show, it built a data generator and handouts, then ran out of time
Let it critique itself, then check: it caught issues the designer missed, but rejected 90% of its own work for untraceable reasons
Give it notes: 5.5 now builds on feedback instead of arguing
Move the lede up yourself: most readable prose they've measured, but still buries the point
Point it at visual work: game UI, 3D, animations and prototypes were its best one-shot results

More from coding & agent