{"version":"2.1.271","anchor":"artifacts-tool-prompt-gains-a-database-capability-read-dbw","canonical_anchor":"artifacts-tool-prompt-gains-a-database-capability-read-dbw","heading":"Artifacts tool prompt gains a database capability (read_db\/write_db)","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifacts-tool-prompt-gains-a-database-capability-read-dbw","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Artifacts tool prompt gains a database capability (read_db\/write_db)\n\nArtifacts can now keep a shared database, readable and writable via read_db\/write_db actions\n\n**What**\n\nPublished artifacts (shareable pieces of content or apps Claude can create) can now keep a small shared database attached to the artifact's page. The artifact tool gains `read_db` and `write_db` actions with operations including `get`, `list`, `query`, `set`, `update`, `delete`, and `batch`. Batch writes are capped at a limit, and in some configurations, updates can use optimistic concurrency control via an `if_version` field along with string-replace-style field edits.\n\n**Why**\n\nThis lets an artifact persist and share state across viewers or sessions instead of being purely static content, opening the door to artifacts that behave more like small interactive apps with real data behind them.\n\n- Area: Artifacts\n- Names: `read_db`, `write_db`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}