A full presence websocket subsystem is built and off unless a remote flag or env var enables it.
A 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.
- The environment variable takes precedence over the remote flag; with neither, the check returns false and nothing connects.
- Telemetry events under the "artifact_presence" name cover connection failures and stalls, including
closed_4403,ws_open_errorandstall_run_started.
CLAUDE_CODE_ARTIFACT_PRESENCE=1 claudetengu_brass_plover
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_brass_plover Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.251: off
Read once, for one account on one subscription tier, against v2.1.251. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
New in this build: CLAUDE_CODE_ARTIFACT_PRESENCE