{"version":"2.1.277","anchor":"attribution-billing-header-gains-a-cc-turn-origin-field","canonical_anchor":"attribution-billing-header-gains-a-cc-turn-origin-field","heading":"New cc_turn_origin field added to billing headers and log scrubbing","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/attribution-billing-header-gains-a-cc-turn-origin-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New cc_turn_origin field added to billing headers and log scrubbing\n\nFirst-party API requests now send a cc_turn_origin field, and it's also scrubbed from logs like other request identifiers\n\n**What**\n\nThe 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.\n\nThe 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`.\n\n**Why**\n\nThis 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.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}