Changes in the system prompt between Claude Opus 4.6 and 4.7
claude
| Source: Mastodon | Original article
Claude’s latest Opus release rewrites the model’s “system prompt” – the hidden instruction set that shapes tone, verbosity and internal reasoning – and the shift is already rippling through developers’ pipelines.
Anthropic disclosed that Opus 4.7 replaces the warm, validation‑heavy phrasing of 4.6 with a more direct, opinionated voice and trims the default emoji usage. More consequentially, the new prompt ties response length to the model’s own assessment of task complexity, abandoning the fixed verbosity ceiling that many users relied on for predictable output. Thinking blocks now stream empty unless callers explicitly request them, a silent change that can break code expecting the previous “thinking” field to be populated.
The rewrite matters because the system prompt is effectively a model‑specific contract. As we reported on 18 April, Opus 4.7 is not a drop‑in upgrade; prompts tuned for 4.6 no longer behave identically, and the same principle applies across LLM families. Teams that built agents, code assistants or customer‑support bots on 4.6 must audit prompt wording, adjust “think carefully” cues, and test for altered verbosity. Failure to do so can lead to truncated explanations, missing reasoning traces, or a tone that feels brusque to end users.
Anthropic’s migration guide now lists the system‑prompt overhaul as a checklist item, and the API docs advise developers to explicitly opt‑in to thinking content if they need it. The next week will reveal how quickly the community adapts: watch for updated open‑source prompt libraries, early‑stage benchmark reports comparing 4.6 and 4.7 on complex tasks, and any follow‑up statements from Anthropic about further prompt refinements. The pace of adoption will be a barometer for how much hidden prompt engineering can still be abstracted away in the era of increasingly self‑tuning LLMs.
Sources
Back to AIPULSEN