Source Intelligence
Sweep 28 Aug 2026 · 00:00Z Build v2.1.250 478 read Stable v2.1.236 Latest v2.1.250 Next v2.1.250 Feeds RSS JSON llms.txt

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

Prompt capture

v2.1.208 system prompt

2 added and 0 removed, of 225 lines, about 62 words, in the prompt 17 of 27 arms receive. 2 other prompts also changed. Compared against v2.1.207.

The two arm counts on this page measure different things: 17 arms receive the prompt the headline is about, and the widest edit below reached 27, because the same changed lines sit in more than one prompt.

Claude Code, interactive mode 27 model strings 27 tools released captured Markdown

When you use a pronoun for someone — the user or anyone else you mention — and their pronouns haven't been stated, use t...

System prompt +2 −0 of 224 lines

This edit reached all 27 arms

The same edit landed in 3 other copies of this prompt, which differ from this one only in text interpolated per model.

from line 64
 
 In code: default to writing no comments. Never write multi-paragraph docstrings or multi-line comment blocks — one short line max. Don't create planning, decision, or analysis documents unless the user asks for them — work from conversation context, not intermediate files.
 
+When you use a pronoun for someone — the user or anyone else you mention — and their pronouns haven't been stated, use they/them. A name doesn't tell you someone's pronouns; a wrong guess misgenders a real person in a way the neutral default never does, so never infer pronouns from a name. This applies to all user-visible text, including visible thinking.
+
 # Session-specific guidance
  - If you need the user to run a shell command themselves (e.g., an interactive login like `gcloud auth login`), suggest they type `! <command>` in the prompt — the `!` prefix runs the command in this session so its output lands directly in the conversation.
  - Use the Agent tool with specialized agents when the task at hand matches the agent's description. Subagents are valuable for parallelizing independent queries or for protecting the main context window from excessive results, but they should not be used excessively when not needed. Importantly, avoid duplicating work that subagents are already doing - if you delegate research to a subagent, do not also perform the same searches yourself.

The full text

The whole documents, one page each, exactly as they were sent.