Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

Spill-to-tool-results error message now distinguishes project_read from project_memory_read

Error when a large result fails to save now names whether it came from project_read or project_memory_read

TierYou'll noticehow much it should matter to you
Useful1my rating, 1 to 5
Signal0worth watching, 1 to 5
AreaProject Memorywhat it touches
KindImprovementsin v2.1.265,
You'll notice

Error when a large result fails to save now names whether it came from project_read or project_memory_read

What

When a tool result is too large and gets spilled into separate tool-results storage, and that save fails, the error message now says specifically which method triggered it: "project_read: spill to tool-results failed" or "project_memory_read: spill to tool-results failed", instead of one generic message.

Why

This makes it clearer, when something goes wrong saving a large result, exactly which operation caused it, which helps with diagnosing failures.

See this entry in the whole of v2.1.265 →

Feedback