Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.221entry #86

Claude Code v2.1.221 ·

Review-page publishes are validated for capabilities and approve stamps

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

You'll notice New Features
JSON All of v2.1.221
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.221,
New FeaturesSection of the release
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 →

Feedback