Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.288 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

Artifact storage gives a clear error when its total size limit is reached

An artifact's database now refuses writes with a specific error when its total stored size hits the limit, including when a document grows

You'll notice Improvements
JSON All of v2.1.288
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.288,
ImprovementsSection of the release
What

An artifact can keep documents in its own database. That database can now refuse a write because it has reached its storage limit. This limit is on the total size of the documents, not on how many there are. Making an existing document larger can also be refused. Before, the only limits were on the number of documents in a collection and in the database.

Why

When artifact storage fills up, you get an error that says size is the problem, rather than a confusing failure.

See this entry in the whole of v2.1.288 →

Feedback