{"version":"2.1.229","anchor":"artifact-database-gains-a-private-per-viewer-area","canonical_anchor":"artifact-database-gains-a-private-per-viewer-area","heading":"Artifact database gains a private per-viewer area","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/artifact-database-gains-a-private-per-viewer-area","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Artifact database gains a private per-viewer area\n\nArtifact databases can give each viewer a private area, documented only when an internal flag is on.\n\n**What**\n\nArtifact database guidance documents an exception to shared rows: each viewer's subtree under the `data\/users\/` prefix is private to that viewer, and the literal path segment `me` stands for the current viewer's id, the same one the page gets from `claude.user.id()`. It requires the published version to declare the `user` capability alongside `db`. The paragraph is only included in the tool description when its internal flag is set.\n\n**Evidence**\n\n`data\/users\/me`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}