Unclear Exactly which remote sessions keep pinning off is not established.
What
Artifact pinning lets you pin and unpin artifacts. When the CLAUDE_CODE_ARTIFACT_PIN environment variable was not set, the check used to ask a remote switch, tengu_cobalt_plinth_holly, and treated it as off if there was no answer. That lookup is gone:
- With
CLAUDE_CODE_ARTIFACT_PINunset, pinning now defaults to on, so it is available in local sessions without any remote switch. CLAUDE_CODE_ARTIFACT_PINcan still turn it off.- The remote-session exceptions are unchanged. Pinning stays off when
CLAUDE_CODE_REMOTEis set and an internal check fails, and another internal check can still turn it off in remote sessions. - Deleting artifacts is separate and still depends on the remote switch
tengu_cobalt_plinth_alder, treated as off when there is no answer.
Why
In local sessions you get artifact pin and unpin by default. If you do not want it, set CLAUDE_CODE_ARTIFACT_PIN to turn it off.
tengu_cobalt_plinth_holly On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.285: not a boolean we can read
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.
tengu_cobalt_plinth_alder Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.285: 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.
Read once, for one account on one subscription tier, against v2.1.285. It isn't a statement about your account. What a flag value here can and cannot tell you
By default, metrics and events from a cloud session carry the [standard attributes](#standard-attributes), including `session.id`, `ccr.session.id`, and `organization.id`, so you can filter by session or organization without extra configur…see the edit
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.
Exactly which remote sessions keep pinning off is not established.
CLAUDE_CODE_REMOTE on Monitoring