Invest1 distinct publisher3 min readUpdated
The deleted guidance existed to protect older models, the company says. Prompt scaffolding written for a previous generation has a short useful life, and nobody rings a bell when it lapses.
The Investor · Invest desk
Compiled by The InvestorSomething wrong?How this is made
Scaffolding depreciates because of what it was built for. Anthropic says the hard rules in Claude Code's prompt were there to keep earlier models away from worst cases such as deleting files, and that the cost was knowingly accepted: without those guardrails, older models wrote comments that were incorrect in many cases [11]. That is a hedge against one generation's failure modes. Hedges expire when the thing they were hedging stops existing.
The running cost is the part most teams have never priced. Anthropic's own transcripts showed a system prompt, skills and a user request colliding inside a single call, one instruction asking for documentation as appropriate while another said not to add comments [4]. The model can usually work out intent, but it has to reason harder about the overlap before it acts [5]. Guidance is not free storage. It is charged on every request, and past some point each additional rule buys contradiction rather than control.
Read the headline result strictly. Removing more than four fifths of the prompt with no measurable loss on the coding evaluations [1] leaves the remaining prompt at under a fifth of its former size [13] and puts the measured value of everything deleted inside the noise floor of those evaluations at the moment it was cut [14]. That is not a claim that the text never helped. It is a claim that by the Opus 5 and Fable 5 generation, it had stopped paying, and the only way anyone found out was by running the comparison.
Which is where the asymmetry sits. The evidence is Anthropic's, the model is Anthropic's, and the evaluations are coding evaluations, so nothing here speaks to a claims-handling agent or a retrieval bot [15]. A vendor can delete four fifths of a prompt because it has a suite that tells it when quality moved. Most buyers maintaining CLAUDE.md files, skill libraries and prompt fragments cannot run that experiment, so they will either keep paying tokens and latency for guidance written against a retired model, or delete on faith.
The reversal on examples is the one that should sting. Examples were the number one rule for tool use, and Anthropic now says they pen the model into a narrower exploration space, recommending expressive interface design instead, with a todo status enumerated as pending, in_progress and completed doing the work that a worked example used to do [8][16]. Few-shot blocks are the artefact teams are proudest of and the most laborious to maintain. On this guidance they are a liability with a version number attached.
The other lesson is about where context should live. Claude Code once leaned on CLAUDE.md as its memory, and now has memory, artifacts and skills to load and share context across sessions [10], alongside progressive disclosure replacing the habit of putting everything up front [12]. Anthropic has packaged the pruning advice as a command, /doctor, to rightsize skills and CLAUDE.md files [9]. A vendor shipping a tool whose purpose is to shrink what its customers wrote is a fair signal about which side of the ledger that writing now sits on.
The durable asset was never the prompt text. It is the ability to measure what the text is worth this month.
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
Anthropic says it removed over 80% of Claude Code's system prompt for models like Claude Opus 5 and Claude Fable 5 with no measurable loss on its coding evaluations.
Anthropic describes context as assembled from the system prompt, Skills, CLAUDE.md files, memory and other sources, and calls managing this context engineering.
Anthropic says it found it was overconstraining Claude Code, through the system prompt and through CLAUDE.md files and skills.
Reading transcripts of internal Claude Code usage, Anthropic saw conflicting messages in a single request, such as 'leave documentation as appropriate' against 'DO NOT add comments', as system prompt, skills and user requests clashed.
Anthropic says Claude can generally interpret user intent but must think more carefully about overlapping and conflicting messages before deciding what to do.
The old Claude Code system prompt said to default to writing no comments, never write multi-paragraph docstrings or multi-line comment blocks (one short line max), and not to create planning, decision or analysis documents unless asked.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Single first-party account, no data shown
All claims trace to one vendor blog post. The post is authoritative about Anthropic's own prompt and product changes, and it quotes retired and replacement prompt text verbatim, which is unusually concrete. But the headline result rests on unnamed internal coding evaluations with no scores, variance, or methodology, and there is no second publisher or independent replication anywhere in the cluster.
Shipped first-party, no outside uptake shown
The changes are described as live in Anthropic's own product: a reduced system prompt for the newer models, /doctor for auditing user context files, skills-based verification and deferred-loading tools. That is real deployment inside a widely used coding agent, but the cluster contains no third-party team adopting the guidance, no usage figures, and no external reports of results after following it.
Mildly overstated
The post is unusually specific for vendor writing and does not oversell the mechanism, but the memorable number carries more weight than its backing: an 80% cut validated by unnamed coding evaluations is generalised into 'new rules' for anyone building agents in any domain. Deleting guardrails that once prevented worst-case behaviour such as file deletion is presented as safe on the strength of newer models' judgement, without any regression or safety evidence, and no independent check exists.
Vendor promoting its own models and tooling
The single source is Anthropic's own blog. The narrative that less scaffolding is needed is simultaneously a capability claim for Claude Opus 5 and Claude Fable 5, a reason to move context handling onto Anthropic platform features such as memory, artifacts, skills and ToolSearch, and a prompt to run the vendor's /doctor command. No countervailing or independent voice appears in the cluster.
Reliable on intent, unverifiable on magnitude
Confidence is high that Anthropic did cut the prompt substantially and changed its recommended practices, since the vendor is the definitive source on its own prompt and quotes the text on both sides. Confidence is much lower on the magnitude and generality of the no-loss finding, which is single-sourced, unquantified beyond a percentage, and scoped to coding evaluations only.
build
Opus 5 absorbed your verify prompts. The reading is still on your desk.1 distinct publisher
build
Claude Code's new default is a confession: the approval prompt was never a control1 distinct publisher
build
Developer habit, priced at $965B: what Anthropic's run actually proves1 distinct publisher
invest
Nearly nine tenths of Anthropic spend is not on its best model, weeks before a $2T listing2 distinct publishers
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 23, 2026