Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.277 ·

New cc_turn_origin field added to billing headers and log scrubbing

First-party API requests now send a cc_turn_origin field, and it's also scrubbed from logs like other request identifiers

Group of 2 Under the hood Internal Changes
JSON All of v2.1.277
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.277,
Internal ChangesSection of the release

What

The internal billing/attribution header sent with first-party API requests now includes a cc_turn_origin value (a lowercase string matching /^[a-z][a-z_]{0,31}$/), alongside the existing cc_version, cc_entrypoint, cc_workload, cc_is_subagent, cc_prev_req, and cc_prompt_id fields. It's only included when the account is a first-party account and a valid origin string is present.

The regex Claude Code uses to strip sensitive query/cookie fields from logs, which already covered cc_prev_req, cc_prompt_id, and cc_workload, now also scrubs cc_turn_origin.

Why

This lets Claude Code track where a turn originated for billing/attribution purposes while making sure that new field is treated the same as other sensitive request identifiers and kept out of logs.

See this entry in the whole of v2.1.277 →

Feedback