What
The attribution setting can now be a simple true or false value instead of only a group of fields:
falsehides all attribution. It is the same as{ "commit": "", "pr": "", "sessionUrl": false }.trueis the same as leaving the setting out.
An invalid value now produces its own error message. When attribution is false, merging settings from different places forces attribution.sessionUrl to false. The check for whether your settings configure attribution now counts attribution: false too, not only the object form or the deprecated includeCoAuthoredBy.
Why
You can turn off every kind of attribution with one value instead of spelling out each field. A session link cannot slip back in from another settings file.
Names in the bundleattribution
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up attribution, on Claude Code changelog.
* Fixed the commit attribution reminder being re-sent inside tool output when a model fallback lasts only one turnchangelog see the edit
Added since
A small documentation edit on Claude apps gateway configuration touched a line naming attribution after this was published.
In sessions signed in through `/login`, the CLI stamps each export with the authenticated user's identity, read from the gateway-issued JWT: the `user.id`, `user.email`, and `user.groups` attributes. Per-developer cost and usage attributio…claude-apps-gateway-config see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Claude apps gateway configuration touched a line naming attribution after this was published.