{"version":"2.1.248","anchor":"usage-limits-surface-now-behind-the-tengu-ember-latch-flag","canonical_anchor":"usage-limits-surface-now-behind-the-tengu-ember-latch-flag","heading":"Usage-limits surface now behind the tengu_ember_latch flag","tier":"soon","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/usage-limits-surface-now-behind-the-tengu-ember-latch-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Usage-limits surface now behind the tengu_ember_latch flag\n\nA usage-limits surface for Pro and Max accounts is now hidden behind an off flag.\n\n**What**\n\nA limits-related interface that previously showed for Pro and Max accounts is now wrapped in an additional check tied to the `tengu_ember_latch` feature flag. Nothing in this build sets that flag, and it falls back to off, so the surface stays hidden unless server config enables it.\n\n**Details**\n\n- The Pro\/Max account condition still applies underneath the new outer check.\n\n**Evidence**\n\n`tengu_ember_latch`\n\n- Flag `tengu_ember_latch`: Off in both readings (read for one account on one subscription tier against v2.1.248; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Usage & Limits\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}