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.238 Home All releases ←olderv2.1.237 v2.1.239newer→
Claude Code v2.1.238

Artifact publishing names your plan's daily limit and why a fetch was blocked

You'll notice
Useful3 Signal3
Artifacts

Hitting your plan's daily artifact limit now says so by name instead of a generic rate-limit error.

What

Hitting your plan's daily cap on new artifacts or pushes is now reported as such, with copy naming the plan, instead of a generic rate-limit error. Other rate limits are retried after the delay the server asks for, capped at 30 seconds. Failures fetching content now say whether a proxy refused the connection (including a 407 auth challenge) or an allowlist blocked it.

Details
  • The cap message reads "daily new-artifact limit for your plan reached".
  • Allowlist remediation text differs for cloud environments, remote sessions and the desktop app's network settings.
  • Reachable by anyone publishing artifacts.
Evidence

daily new-artifact limit for your plan reached

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.238 →