{"version":"2.1.288","anchor":"new-tengu-remote-create-tool-serving-gate-telemetry-on-cloud","canonical_anchor":"new-tengu-remote-create-tool-serving-gate-telemetry-on-cloud","heading":"Cloud session creation now records how a feature switch was read","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/new-tengu-remote-create-tool-serving-gate-telemetry-on-cloud","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Cloud session creation now records how a feature switch was read\n\nWhen creating a cloud session, Claude Code now checks a feature switch itself and records its answer, the cached value and the wait time\n\n**Unclear.** Which way of creating a cloud session records this is not clear.\n\n**What**\n\nWhen Claude Code creates a cloud session, it now fetches its own answer for a feature switch that is set remotely, and records three things: that answer, the value it had saved earlier, and how long it waited. Before, it only checked the switch and recorded nothing.\n\n**Why**\n\nThis shows when the switch had not finished loading in time, a timing problem that could make a session start differently from what was intended. It does not change what you see.\n\n- Flag `tengu_remote_backend`: 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: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}