{"version":"2.1.277","anchor":"new-per-turn-current-time-beta-signal-gated-by-an-env-var","canonical_anchor":"new-per-turn-current-time-beta-signal-gated-by-an-env-var","heading":"New per-turn timing signal for requests","tier":"soon","area":"API Client","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-per-turn-current-time-beta-signal-gated-by-an-env-var","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New per-turn timing signal for requests\n\nClaude Code can now send the current time with each turn under a new beta flag, controlled by CLAUDE_CODE_PER_TURN_TIMING\n\n**What**\n\nClaude Code can now include the current timestamp with each turn it sends to the model, as a new field alongside the existing per-turn effort mechanism. This only happens when a new beta flag is enabled and the `CLAUDE_CODE_PER_TURN_TIMING` environment variable is set, together with the existing eligibility checks used for per-turn effort.\n\n- A new per-request field injects the current time into each turn's request when the beta flag and environment variable enable it.\n\n- The internal list of flags used to build prompts and decide cache validity now includes `per_turn_timing` next to the existing `per_turn_effort`.\n\n**Why**\n\nThis is a gated, opt-in signal, so it has no effect unless `CLAUDE_CODE_PER_TURN_TIMING` is set. Once enabled, it lets the model be aware of timing information on a per-turn basis, similar to how per-turn effort already works.\n\n- Area: API Client\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}