{"version":"2.1.224","anchor":"permission-prompts-for-artifact-database-access","canonical_anchor":"permission-prompts-for-artifact-database-access","heading":"Permission prompts for artifact database access","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/permission-prompts-for-artifact-database-access","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Permission prompts for artifact database access\n\nArtifact database access asks permission first, with reads and writes scoped differently.\n\n**What**\n\nThe new artifact database actions ask before first use, and the prompt spells out how far approval reaches: approving a write covers database writes to any artifact for the rest of the session, approving a read covers that one artifact for the rest of the conversation. Writes persist and are visible to everyone who can open the artifact. The actions are gated behind `CLAUDE_CODE_ARTIFACT_DB` and the `tengu_umber_lattice` gate.\n\n**Details**\n\n- In plan mode the request is always routed to the user rather than the automatic permission classifier.\n\n**Evidence**\n\n`Claude wants to write to this artifact's database \\u2014 writes persist and are visible to everyone who can open the artifact; approving covers database writes to any artifact for the rest of this session.`\n\n- Flag `tengu_umber_lattice`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.224; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Artifacts\n- Names: `CLAUDE_CODE_ARTIFACT_DB`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}