{"version":"2.1.251","anchor":"live-presence-on-artifacts-switched-off-in-this-build","canonical_anchor":"live-presence-on-artifacts-switched-off-in-this-build","heading":"Live presence on artifacts, switched off in this build","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/live-presence-on-artifacts-switched-off-in-this-build","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Live presence on artifacts, switched off in this build\n\nArtifacts can show who else is viewing live, but only if you set an environment variable.\n\n**What**\n\nA new subsystem opens a websocket to `\/api\/frame\/sync` to track who is currently viewing an artifact, with owner and account verification, token refresh over the connection, reconnect and backoff, and its own telemetry. It is off by default: it turns on only if the remote config flag `tengu_brass_plover` is enabled or the environment variable `CLAUDE_CODE_ARTIFACT_PRESENCE` is set.\n\n**Details**\n\n- The environment variable takes precedence over the remote flag; with neither, the check returns false and nothing connects.\n- Telemetry events under the \"artifact_presence\" name cover connection failures and stalls, including `closed_4403`, `ws_open_error` and `stall_run_started`.\n\n**Usage**\n\n`CLAUDE_CODE_ARTIFACT_PRESENCE=1 claude` **Evidence** `tengu_brass_plover`\n\n- Flag `tengu_brass_plover`: Off in both readings (read for one account on one subscription tier against v2.1.251; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Artifacts\n- Names: `CLAUDE_CODE_ARTIFACT_PRESENCE`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}