Source Intelligence
Follow Discord

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.

← All of v2.1.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Review-page publishes are validated for capabilities and approve stamps

You'll notice
Useful3 Signal0
Artifacts

PR review pages you publish are now strictly validated, with a clear refusal message when something is off.

What

PR review artifacts now go through a strict validator covering what the page may declare and what its approve action may do, with a specific refusal string per failure.

Details
  • The capabilities declaration may only carry mcp and self, and self must be the empty-object marker.
  • The mcp manifest must name exactly one GitHub connector and must declare exactly the live read tool and the approve tool, once each.
  • The live slot must be a read-shaped tool: "a read verb prefix such as get_/list_/search_, or an entity_read suffix such as pull_request_read / issue_read".
  • The approve stamp's inputs must all be the anchored PR's own owner/repo/number, or an approve word under an event-named key.
  • live.shaPath must point at a head sha field.
Evidence

stamp.input does not carry an explicit approve value under an event-named key

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.221 →