{"version":"2.1.288","anchor":"dark-launched-tengu-mellow-beacon-marker-gate","canonical_anchor":"dark-launched-tengu-mellow-beacon-marker-gate","heading":"Hidden setting adds a marker to some background requests","tier":"soon","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/dark-launched-tengu-mellow-beacon-marker-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Hidden setting adds a marker to some background requests\n\nA server-controlled setting can make some background requests to the model point back to the reply they came from\n\n**Unclear.** It is not clear what the marker does once a request is sent.\n\n**What**\n\nClaude Code makes some background requests to the model that are not your main conversation. A new setting can add a marker to these requests that points to the assistant reply they came from. It applies only when a connection keep-alive header is being sent and a second marker slot is free. The setting is decided on Anthropic's servers, and its built-in default is off.\n\n**Why**\n\nThis is probably an experiment with caching on requests to the model. It has no visible effect on the screen.\n\n- Flag `tengu_mellow_beacon`: Not enough to say (read for one account on one subscription tier against v2.1.288; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: API Requests\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}