{"version":"2.1.269","anchor":"memory-extraction-pass-can-now-bypass-its-own-feature-gate-w","canonical_anchor":"memory-extraction-pass-can-now-bypass-its-own-feature-gate-w","heading":"Memory-extraction pass can now bypass its own feature gate when post-turn-memory config is present","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/memory-extraction-pass-can-now-bypass-its-own-feature-gate-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Memory-extraction pass can now bypass its own feature gate when post-turn-memory config is present\n\nMemory extraction can now turn itself on when post-turn-memory config is present, bypassing its usual feature gate\n\n**What**\n\nThe internal switch that decides whether the memory-extraction pass runs (used both for per-turn extraction and for the flush that happens on shutdown) now returns true automatically whenever a post-turn-memory configuration is present, before it even checks the `tengu_passport_quail` feature gate that normally controls this feature.\n\n**Why**\n\nIn practice this means setting up post-turn-memory configuration (as described in the related MCP memory server change) can enable memory extraction even for accounts where the underlying feature gate is off, since the config check now short-circuits the gate check entirely.\n\n- Flag `tengu_passport_quail`: Off in both readings (read for one account on one subscription tier against v2.1.269; this account: off, anonymous baseline: off, compiled default: off)\n- Flag `tengu_slate_thimble`: Off in both readings (read for one account on one subscription tier against v2.1.269; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Memory\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}