{"version":"2.1.265","anchor":"spill-to-tool-results-error-message-now-distinguishes-projec","canonical_anchor":"spill-to-tool-results-error-message-now-distinguishes-projec","heading":"Spill-to-tool-results error message now distinguishes project_read from project_memory_read","tier":"notice","area":"Project Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/spill-to-tool-results-error-message-now-distinguishes-projec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Spill-to-tool-results error message now distinguishes project_read from project_memory_read\n\nError when a large result fails to save now names whether it came from project_read or project_memory_read\n\n**What**\n\nWhen 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.\n\n**Why**\n\nThis makes it clearer, when something goes wrong saving a large result, exactly which operation caused it, which helps with diagnosing failures.\n\n- Area: Project Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}