Claude Opus 5 works better after an agent workflow is stripped back
thedealdirector · x · 2026-07-26
A reaction to the Claude Opus 5 launch says the model is hard to love at first: it argued with instructions, stopped before finishing work, and did not fit existing skills and plugins well in an internal agent workflow.
The author says things changed after deleting the workflow stack and starting over from scratch:
- Opus 5 got much better without the old layers of skills and plugins.
- It showed flashes of brilliance in coding, writing, and knowledge-work tasks.
- Their first impression was negative, but the model seemed to prefer a cleaner setup.
The takeaway is less about raw benchmark strength and more about how much agent performance depends on the surrounding workflow.
More from coding & agent
- Hugging Face incident may be context pollution, not model plotting escape, critics say — sebkrier · 2026-07-26
- A prompt for building a Call of Duty-scale FPS with sub-agents raises token budget concerns — petergyang · 2026-07-26
- ChatGPT has been running a prompt overnight to automate ML, PINNs and LLM fine-tuning — burhop · 2026-07-26
- CCAR-P is an architect exam, not an API quiz, with integration and design dominating — Mauve_Tess · 2026-07-26
- Grok 4.5 adds Workflows, Excel, Outlook, and 1,024-agent orchestration — XFreeze · 2026-07-26
- Transitioning to Applied AI: 3 Actionable Tips for Non-Technical Builders — brandon_galang · 2026-07-26