Artifacts can now keep a shared database, readable and writable via read_db/write_db actions
Published 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.
This 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.