The 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.
In 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.
tengu_passport_quail Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.269: off
tengu_slate_thimble Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.269: off
Read once, for one account on one subscription tier, against v2.1.269. It isn't a statement about your account. What a flag value here can and cannot tell you