{"version":"2.1.267","anchor":"artifact-assets-capability-gated-by-cached-org-roster-a","canonical_anchor":"artifact-assets-capability-gated-by-cached-org-roster-a","heading":"Artifact 'assets' capability now driven by a cached org roster","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/artifact-assets-capability-gated-by-cached-org-roster-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Artifact 'assets' capability now driven by a cached org roster\n\nWhether the artifact tool exposes an 'assets' action is now decided by a cached per-org capability roster fetched from the server\n\n**What**\n\n- A new roster subsystem fetches and disk-caches a per-account\/org capabilities roster, used to decide whether the artifact tool schema exposes the \"assets\" action. The `CLAUDE_CODE_ARTIFACT_ASSETS` environment variable overrides this entirely; otherwise it falls back to an internal flag (gated by `tengu_cobalt_plinth_fennel`, off by default), and finally to whatever the cached or live roster from the server reports.\n\n- After an account switch or login, Claude Code now automatically kicks off an async refresh of this artifact-capability roster.\n\n**Why**\n\nThis keeps the artifact tool's available actions in sync with what an account or organization is actually entitled to, refreshing automatically after login rather than relying on stale cached data.\n\n- Flag `tengu_cobalt_plinth_fennel`: Off in both readings (read for one account on one subscription tier against v2.1.267; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}