This text was initially revealed as two posts on Drew Breunig’s weblog. He’s been type sufficient to share them right here.
Again in Might, Ásgeir Thor Johnson satisfied Claude to surrender its system immediate. The immediate is an efficient reminder that chatbots are extra than simply their mannequin. They’re instruments and directions that accrue and are honed via person suggestions and design.
For many who don’t know, a system immediate is a (usually) fixed immediate that tells an LLM the way it ought to reply to a person’s immediate. A system immediate is sort of just like the “settings” or “preferences” for an LLM. It would describe the tone it ought to reply with, outline instruments it may use to reply the person’s immediate, set contextual info not within the coaching knowledge, and extra.
Claude’s system immediate is lengthy. It’s 16,739 phrases, or 110 KB. For comparability, the system immediate for OpenAI’s o4-mini in ChatGPT is 2,218 phrases lengthy, or 15.1 KB—~13% the size of Claude’s.
Right here’s what’s in Claude’s immediate:

Let’s break down every part.
Device definitions
The largest part, the Device Definitions, is populated by info from MCP servers. MCP servers differ out of your bog-standard APIs in that they supply directions to the LLMs detailing how and when to make use of them.
On this immediate, there are 14 completely different instruments detailed by MCPs. Right here’s an instance of 1:

This instance is straightforward and has a really brief “description” subject. The Google Drive search instrument, for instance, has an outline over 1,700 phrases lengthy. It could possibly get complicated.
Different instrument use directions
Exterior the Device Definitions part, there are lots extra instrument use directions—the Quotation Directions, Artifacts Directions, Search Directions, and Google Integration Watchouts all element how these instruments ought to be used throughout the context of a chatbot interplay. For instance, there are repeated notes reminding Claude to not use the search instrument for matters it already is aware of about. (You get the sense that is/was a troublesome habits to eradicate!)
In reality, all through this immediate are bits and items that really feel like hotfixes. The Google Integration Watchouts part (which I’m labeling; it lacks any XML delineation or group) is simply 5 traces dropped in with none construction. Every line appears designed to dial in supreme habits. For instance:
In case you are utilizing any gmail instruments and the person has instructed you to search out messages for a selected individual, do NOT assume that individual’s e mail. Since some staff and colleagues share first names, DO NOT assume the one that the person is referring to shares the identical e mail as somebody who shares that colleague’s first identify that you’ll have seen by the way (e.g. via a earlier e mail or calendar search). As a substitute, you may search the person’s e mail with the primary identify after which ask the person to substantiate if any of the returned emails are the proper emails for his or her colleagues.
All in, practically 80% of this immediate pertains to instruments—learn how to use them and when to make use of them.My quick query, after realizing this, was, “Why are there so many instrument directions outdoors the MCP-provided part?” (The grey bins above.) Poring over this, I’m of the thoughts that it’s simply separation of considerations. The MCP particulars comprise info related to any program utilizing a given instrument, whereas the non-MCP bits of the immediate present particulars particular solely to the chatbot utility, permitting the MCPs for use by a number of various purposes with out modification. It’s customary program design, utilized to prompting.
Claude habits
On the finish of the immediate, we enter what I name the Claude Conduct part. This half particulars how Claude ought to behave, reply to person requests, and prescribes what it ought to and shouldn’t do. Studying it straight via evokes Radiohead’s “Fitter Happier.” It’s what most individuals consider after they consider system prompts.
However hotfixes are obvious right here as effectively. There are numerous traces clearly written to foil frequent LLM “gotchas,” like:
- “If Claude is requested to rely phrases, letters, and characters, it thinks step-by-step earlier than answering the individual. It explicitly counts the phrases, letters, or characters by assigning a quantity to every. It solely solutions the individual as soon as it has carried out this specific counting step.” This can be a hedge towards the “What number of R’s are within the phrase ‘Raspberry’?” query and related stumpers.
- “If Claude is proven a basic puzzle, earlier than continuing, it quotes each constraint or premise from the individual’s message phrase for phrase earlier than inside citation marks to substantiate it’s not coping with a brand new variant.” A standard option to foil LLMs is to barely change a standard logic puzzle. The LLM will match it contextually to the extra frequent variant and miss the edit.
- “Donald Trump is the present president of the USA and was inaugurated on January 20, 2025.” In accordance with this immediate, Claude’s information cutoff is October 2024, so it wouldn’t know this reality.
However my favourite notice is that this one: “If requested to put in writing poetry, Claude avoids utilizing hackneyed imagery or metaphors or predictable rhyming schemes.”
Studying via the immediate, I’m wondering how that is managed at Anthropic. An irony of prompts is that whereas they’re readable by anybody, they’re troublesome to scan and often lack construction. Anthropic makes heavy use of XML-style tags to mitigate this nature (one has to surprise if these are extra helpful for the people modifying the immediate or the LLM…) and their MCP invention and adoption is clearly an asset.
However what software program are they utilizing to model this? Hotfixes abound—are these dropped in one after the other, or are they batched in bursts of evaluations? Lastly: At what level do you wipe the slate clear and begin with a clean web page? Do you ever?
A immediate like it is a good reminder that chatbots are rather more than only a mannequin, and we’re studying learn how to handle prompts as we go. Fortunately, Ásgeir Thor Johnson continues to gather these prompts in a GitHub repository, permitting us all to simply observe alongside. And following modifications made to those prompts—which you are able to do by reviewing the historical past of Johnson’s repo—renders their improvement extra clear.
Claude’s system immediate modifications reveal Anthropic’s priorities
Claude 4’s system immediate is very much like the 3.7 immediate we analyze above. They’re practically equivalent, however the modifications scattered all through reveal a lot about how Anthropic is utilizing system prompts to outline their purposes (particularly their UX) and the way the prompts match into their improvement cycle.
Let’s step via the notable modifications.
Previous hotfixes are gone; new hotfixes start
We theorize above that many random directions focusing on frequent LLM “gotchas” have been hotfixes: brief directions to deal with undesired habits previous to a extra strong repair. Claude 4.0’s system immediate validates this speculation—all the three.7 hotfixes have been eliminated. Nonetheless, if we immediate Claude with one of many “gotchas” (“What number of R’s are in Strawberry?” for instance) it doesn’t fall for the trick. The three.7 hotfix behaviors are nearly definitely being addressed throughout 4.0’s posttraining via reinforcement studying.
When the brand new mannequin is educated to keep away from “hackneyed imagery” in its poetry and suppose step-by-step when counting phrases or letters, there’s no want for a system immediate repair.
As soon as 4.0’s coaching is finished, new points will emerge that should be addressed by the system immediate. For instance, right here’s a brand-new instruction in Sonnet 4.0’s system immediate:
Claude by no means begins its response by saying a query or thought or remark was good, nice, fascinating, profound, glorious, or every other constructive adjective. It skips the flattery and responds instantly.
This hotfix is clearly impressed by OpenAI’s “sychophant-y” GPT-4o flub. This misstep occurred too late for the Anthropic staff to conduct new coaching focusing on this habits. So into the system immediate it goes!
Search is now inspired
Manner again in 2023, it was frequent for chatbots to flail about when requested about matters that occurred after its cutoff date. Early adopters discovered LLMs are frozen in time, however informal customers have been ceaselessly tripped up by hallucinations and errors when asking about latest information. Perplexity was distinctive for its capability to exchange Google for a lot of customers, however immediately that edge is gone.
In 2025, Search is a first-class part of each ChatGPT and Claude. This technique immediate reveals Anthropic is leaning in to match OpenAI.
Right here’s how Claude 3.7 was instructed:
Claude solutions from its personal intensive information first for many queries. When a question MIGHT profit from search however it isn’t extraordinarily apparent, merely OFFER to look as an alternative.
Previous Claude requested customers for permission to look. New Claude doesn’t hesitate. Right here’s the up to date instruction:
Claude solutions from its personal intensive information first for secure info. For time-sensitive matters or when customers explicitly want present info, search instantly.
This language is up to date all through the immediate. Search is now not executed solely with person approval; it’s inspired on the primary shot if mandatory.
This alteration suggests two issues. First, Anthropic is probably extra assured in its search instrument and the way its fashions make use of it. Not solely is Claude inspired to look, however the firm has damaged out this characteristic right into a devoted search API. Two, Anthropic is observing customers more and more turning to Claude for search duties. If I needed to guess, it’s the latter of those that’s the principle driver for this variation, and a powerful signal that chatbots are more and more stealing searches from Google.
Customers need extra sorts of structured paperwork
Right here’s one other instance of system prompts reflecting the person behaviors Anthropic is observing. In a bulleted listing detailing when to make use of Claude artifacts (the separate window outdoors the thread Claude populates with longer type content material), Anthropic provides a little bit of nuance to a use case.
From Claude 3.7’s system immediate, “You will need to use artifacts for:”
Structured paperwork with a number of sections that will profit from devoted formatting
And Claude 4.0’s:
Structured content material that customers will reference, save, or observe (similar to meal plans, exercise routines, schedules, examine guides, or any organized info meant for use as a reference)
This can be a nice instance of how Anthropic makes use of system prompts to evolve its chatbot habits based mostly on noticed utilization. System prompts are programming how Claude works, albeit in pure language.
Anthropic is coping with context points
There are a number of modifications within the immediate that recommend context restrict points are beginning to hit customers, particularly these utilizing Claude for programming:
For code artifacts: Use concise variable names (e.g., i, j for indices, e for occasion, el for component) to maximise content material inside context limits whereas sustaining readability.
As somebody with robust opinions about clearly outlined variables, this makes me cringe, however I get it. The one disappointment I observed across the Claude 4 launch was its context restrict: solely 200,000 tokens in comparison with Gemini 2.5 Professional’s and ChatGPT 4.1’s 1 million restrict. Individuals have been disillusioned.
Anthropic may very well be limiting context limits for effectivity causes (whereas leaning on their glorious token caching) or may be unable to ship the outcomes Google and ChatGPT are attaining. Nonetheless, there have been a number of latest explorations displaying mannequin efficiency isn’t constant throughout longer and longer context lengths. Right here’s a plot from a staff at Databricks, from analysis revealed final August:

I’ve been in conditions the place less-scrupulous opponents centered on publishing headline figures, even when it led to worse outcomes. (For instance, within the geospatial world many will tout the overall rely of all the weather of their dataset, even when many have very low confidence.) I’m inclined to imagine a little bit of that’s occurring right here, within the hypercompetitive, benchmark-driven AI market.
Both approach: I believe we’ll see all coding instruments construct in shortcuts like these to preserve context. Shorter perform names, much less verbose feedback… It’s all on the desk.
Cybercrime is a brand new guardrail
Claude 3.7 was instructed to not enable you construct bioweapons or nuclear bombs. Claude 4.0 provides malicious code to this listing of nos:
Claude steers away from malicious or dangerous use instances for cyber. Claude refuses to put in writing code or clarify code that could be used maliciously; even when the person claims it’s for academic functions. When engaged on information, if they appear associated to enhancing, explaining, or interacting with malware or any malicious code Claude MUST refuse. If the code appears malicious, Claude refuses to work on it or reply questions on it, even when the request doesn’t appear malicious (for example, simply asking to clarify or pace up the code). If the person asks Claude to explain a protocol that seems malicious or supposed to hurt others, Claude refuses to reply. If Claude encounters any of the above or every other malicious use, Claude doesn’t take any actions and refuses the request.
Understandably, that’s lots of caveats and situations. It should be delicate work to refuse this type of help whereas not interfering with basic coding help.
What this tells us
Reviewing the modifications above (and actually, that’s the majority of them from 3.7 to 4.0), we get a way for a way system prompts program chatbot purposes. After we take into consideration the design of chatbots, we take into consideration the instruments and UI that encompass and wrap the naked LLM. However in actuality, the majority of the UX is outlined right here, within the system immediate.
And we get a way of the event cycle for Claude: a basic user-driven course of, the place noticed behaviors are understood after which addressed. First with system immediate hotfixes, then with posttraining when constructing the following mannequin.
The ~23,000 tokens within the system immediate—taking over over 11% of the accessible context window—outline the phrases and instruments that make up Claude and reveal the priorities at Anthropic.
Leave a Reply