{"version":"2.1.228","anchor":"server-side-path-for-reading-artifact-comments-disabled-by-d","canonical_anchor":"server-side-path-for-reading-artifact-comments-disabled-by-d","heading":"Server-side path for reading artifact comments, disabled by default","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/server-side-path-for-reading-artifact-comments-disabled-by-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Server-side path for reading artifact comments, disabled by default\n\nArtifact comments could be fetched server-side instead of through the frame host, but that switch is off.\n\n**What**\n\nFetching comments on an artifact can go through a new server-side path, falling back to the existing frame-host URL flow if the server call errors. The switch is `tengu_onyx_sluice` and its built-in default is off, so unless a remote configuration value turns it on, nothing changes for you.\n\n**Details**\n\n- A fallback after a failed server call is recorded as `server_primary_fell_back`.\n\n**Evidence**\n\n`server_primary_fell_back`\n\n- Flag `tengu_onyx_sluice`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.228; 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- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}