{"version":"2.1.248","anchor":"flag-values-can-be-pinned-for-the-life-of-the-process-and-a-","canonical_anchor":"flag-values-can-be-pinned-for-the-life-of-the-process-and-a-","heading":"Flag values can be pinned for the life of the process, and a new pinned flag appears","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/flag-values-can-be-pinned-for-the-life-of-the-process-and-a-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Flag values can be pinned for the life of the process, and a new pinned flag appears\n\nSome feature flags now stay fixed for the whole session, including a new one that is on.\n\n**What**\n\nInstead of one hand-written cache per flag, there is now a shared map that remembers the first value each flag returned and keeps it for the whole process, so a remote-config change mid-session cannot flip it. Three flags use it, including `tengu_slate_anchor`, new in this build and compiled on.\n\n**Details**\n\n- Pinned flags: `tengu_tab_read_sep` (compiled off), `tengu_tranquil_fern` (compiled on) and `tengu_slate_anchor` (compiled on).\n- `tengu_slate_anchor` is read once inside the dynamic `\/loop` tool's prompt, to ignore cache overage when working out the delay bounds shown to the model.\n- Compiled values are only the fallback; the live value comes from the server.\n\n**Evidence**\n\n`tengu_slate_anchor`\n\n- Flag `tengu_slate_anchor`: Gate removed from the code (read for one account on one subscription tier against v2.1.248; this account: on, anonymous baseline: on, compiled default: not a boolean we can read)\n- Flag `tengu_tab_read_sep`: Off in both readings (read for one account on one subscription tier against v2.1.248; this account: off, anonymous baseline: off, compiled default: not a boolean we can read)\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}