{"version":"2.1.280","anchor":"database-write-hint-text-clarifies-why-a-file-read-is-refuse","canonical_anchor":"database-write-hint-text-clarifies-why-a-file-read-is-refuse","heading":"Database-write hint text clarifies why a file read is refused","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/database-write-hint-text-clarifies-why-a-file-read-is-refuse","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Database-write hint text clarifies why a file read is refused\n\nError message for blocked artifact database file reads now suggests passing the document inline in data instead\n\n**What**\n\nWhen a database write for an artifact tries to read a document's contents directly from a file, Claude Code still refuses this, but the explanation shown now tells you what to do instead: pass the document inline in `data`.\n\n**Why**\n\nThis makes the refusal actionable instead of just a dead end. Rather than having to guess a workaround, you're told directly how to supply the document content so the write can go through.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}