Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.238 ·

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

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

You'll notice Improvements
JSON All of v2.1.238
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.238,
ImprovementsSection of the release
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.

See this entry in the whole of v2.1.238 →

Feedback