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 Publishing · 4/5 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

AskUserQuestion tool description

27 model strings share this prompt, byte for byte.

v2.1.132 22 lines 1763 chars sha256 087c9167ab5c 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.

Use this tool when you need to ask the user questions during execution. This allows you to:

  1. Gather user preferences or requirements
  2. Clarify ambiguous instructions
  3. Get decisions on implementation choices as you work
  4. Offer choices to the user about what direction to take.

Usage notes:

  • Users will always be able to select "Other" to provide custom text input
  • Use multiSelect: true to allow multiple answers to be selected for a question
  • If you recommend a specific option, make that the first option in the list and add "(Recommended)" at the end of the label

Plan mode note: In plan mode, use this tool to clarify requirements or choose between approaches BEFORE finalizing your plan. Do NOT use this tool to ask "Is my plan ready?" or "Should I proceed?" - use ExitPlanMode for plan approval. IMPORTANT: Do not reference "the plan" in your questions (e.g., "Do you have feedback about the plan?", "Does the plan look good?") because the user cannot see the plan in the UI until you call ExitPlanMode. If you need plan approval, use ExitPlanMode instead.

Preview feature: Use the optional preview field on options when presenting concrete artifacts that users need to visually compare:

  • ASCII mockups of UI layouts or components
  • Code snippets showing different implementations
  • Diagram variations
  • Configuration examples

Preview content is rendered as markdown in a monospace box. Multi-line text with newlines is supported. When any option has a preview, the UI switches to a side-by-side layout with a vertical option list on the left and preview on the right. Do not use previews for simple preference questions where labels and descriptions suffice. Note: previews are only supported for single-select questions (not multiSelect).