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.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Comment threads explain two more reasons a resolve was refused

You'll notice
Useful2 Signal2
Artifacts

Refused comment-thread resolves now name the reason instead of failing generically.

What

Resolving a comment thread on a published artifact can now report "not resolved (another user's activation)" and "not resolved (unavailable from this session)" instead of a generic failure, and the resolve request tries a session-scoped route first.

Details
  • If the session-scoped route returns a 404 that is not a missing-thread error, the request falls back to the older route and records that it fell back.
  • The two new refusals come from server responses: one for a comment raised by a different user's session, and one where the server says the action requires a claude.ai session.
  • The 404 message no longer mentions the artifact being republished.
Evidence

session_route_fell_back, not resolved (unavailable from this session)

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →