{"version":"2.1.248","anchor":"tab-aware-read-separator-still-off-and-its-value-no-longer-s","canonical_anchor":"tab-aware-read-separator-still-off-and-its-value-no-longer-s","heading":"Tab-aware read separator still off, and its value no longer sticky","tier":"soon","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/tab-aware-read-separator-still-off-and-its-value-no-longer-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Tab-aware read separator still off, and its value no longer sticky\n\nThe tab-aware read separator flag is read fresh each time but still off.\n\n**What**\n\nThe `tengu_tab_read_sep` flag is now read fresh on each call through a small accessor rather than cached once per session. The compiled fallback is off, so the feature is still disabled unless remote config turns it on.\n\n**Evidence**\n\n`tengu_tab_read_sep`\n\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: Elsewhere\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}