Source Intelligence
Follow Discord
Sweep 28 Aug 2026 · 00:00Z Build v2.1.250 478 read Stable v2.1.236 Latest v2.1.250 Next v2.1.251 Feeds RSS JSON llms.txt
Reading a new release v2.1.251 Analysing changes · 2/5 Writing the entries · 2/4 steps 470 findings $18.91 so far

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

WebSearch tool description

27 model strings share this prompt, byte for byte.

v2.1.8 27 lines 1313 chars sha256 0da72f876cda Plain text Whole capture

This renders the markdown inside the description, so it isn't quite the description itself. The raw view and the plain text are the bytes as they were sent.

  • Allows Claude to search the web and use the results to inform responses
  • Provides up-to-date information for current events and recent data
  • Returns search result information formatted as search result blocks, including links as markdown hyperlinks
  • Use this tool for accessing information beyond Claude's knowledge cutoff
  • Searches are performed automatically within a single API call

CRITICAL REQUIREMENT - You MUST follow this:

  • After answering the user's question, you MUST include a "Sources:" section at the end of your response

  • In the Sources section, list all relevant URLs from the search results as markdown hyperlinks: Title

  • This is MANDATORY - never skip including sources in your response

  • Example format:

    [Your answer here]

    Sources:

Usage notes:

  • Domain filtering is supported to include or block specific websites
  • Web search is only available in the US

IMPORTANT - Use the correct year in search queries:

  • Today's date is 2026-08-14. You MUST use this year when searching for recent information, documentation, or current events.
  • Example: If the user asks for "latest React docs", search for "React documentation 2026", NOT "React documentation 2025"