You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
Internal ChangesKind: in v2.1.305,
What probably matters to youSection of the release
Unclear It is not stated what this list is for or whether attributionProjectPolicy does anything yet.
What
A session can now name a claude.ai Project that the organization's usage reports attribute it to. Claude Code picks the Project in this order:
CLAUDE_CODE_ATTRIBUTION_PROJECT, a new environment variable (a value set in the shell before starting Claude Code), takes precedence.
attributionProject, a new setting, read from each settings layer. Project settings are skipped in some cases when user settings are present.
attributionProjectPolicy, a new default that only managed settings (settings an organization's administrator sets centrally) can supply.
Project IDs are converted to a claude_proj_01… form, and UUIDs are converted too. Invalid values are ignored and reported. A notice at startup names the chosen Project or warns that the ID is invalid.
The Project is only sent when you sign in with claude.ai or use the Anthropic API directly, outside cloud sessions, when CLAUDE_CODE_ATTRIBUTION_HEADER is not 0, and when a subscriber check passes. A new sign-in source was also added to an analytics list in the same change.
Why
Organizations can see which claude.ai Project Claude Code usage belongs to, and administrators can set a default for everyone. Watch the startup notice: if the ID you set is invalid, it is ignored rather than used.
