-
[OPIK-7418] [DOCS] docs: document how cost-policy delivery works (#7688)
frostbyte_neo 发布于
2026-07-31 12:11:43 +00:00 - [OPIK-7418] [DOCS] docs: dedicated "Roll out cost policies" page
Consolidate cost-policy behavior — previously spread thinly across four pages
and hard to follow — into one page that explains it as a topic: how org and
user policies inherit, locks and who can change what, how a developer is
identified, how changes reach devices, and what happens when a developer edits
a setting locally or an admin clears one, with a behavior-at-a-glance recap,
the device write surface, and three annotated screenshots.Register it in the nav after "Reduce coding agent spend"; slim the four source
pages to a sentence and a link and retarget the moved anchors. Correct the
managed-settings page to reality: managed settings deliver the deploy-once
bootstrap, and cost policies are not embedded there — they sync to devices
dynamically, the same way whether you install with managed settings, MDM, or
the macOS app. Source labels match the UI (Customized by you/user/admin;
inherited values carry no label).Co-Authored-By: Claude Fable 5 noreply@anthropic.com
- docs: note that policies are defaults, overridable by higher CC settings layers
Set expectations honestly: policies land in the user settings Claude Code
reads, and Claude Code lets higher-precedence layers — a project's own
.claude/settings.json or a settings file passed at session start — win over
them. A developer can override a policy that way; Cost Intelligence does not
manage those layers. Values a developer cannot override at all are a
device-management concern beyond these policies.Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Co-authored-by: Claude Fable 5 noreply@anthropic.com
下载附件