Dev finds Argon enough for nearly all coding tasks, misses it after switching to Opus 5.5

m2saxon · x · 2026-10-03

Developer m2saxon reports that only one task in his workflow required stepping up from argon (a predecessor) to Opus 5.5 — and after switching, he immediately missed argon. His complaint: Opus's extreme opaque conciseness and its amnesia about what it actually told him versus what only existed in its chain of thought. A first-hand observation on real-world usability of frontier models in coding workflows.

Original post →

More from coding & agent

coding & agent channel →