AI Pulse · Under the Radar

A Reddit user dug into Anthropic’s new Opus 5 model and found something unexpected: a hardcoded instruction telling the model not to spawn subagents by default. That matters because the same week, everyone was talking about fan-out patterns, where one AI agent spins up multiple smaller agents to tackle pieces of a problem in parallel. Anthropic apparently decided to turn that off at the system level.

The discovery made it to Hacker News alongside a separate thread noting that Anthropic stripped more than 80% of Claude Code’s system prompt for the Opus 5 and Fable 5 releases. Put those two things together and you see a company aggressively rewriting how its models behave by default. Builders are reverse-engineering these changes in real time, which tells you how opaque the process still is.

Why does this matter if you run a company? Because the models you rely on are changing under the hood, often without clear release notes. If you built workflows assuming Claude would handle tasks a certain way, or if you were counting on subagent spawning for complex automation, you might find your setup suddenly behaves differently. The system prompt is the invisible rulebook that shapes every response. When 80% of it disappears or new guardrails appear, your tools shift.

This is exactly the kind of thing we track and test inside the Omni Command Centre, so you know when a model update breaks or improves your workflows before it hits production. The takeaway is not that Anthropic is doing something wrong. It is that the ground moves fast, and if you are building on these models, you need to watch the changes that do not make the marketing blog.