{"version":"2.1.281","anchor":"reminder-fold-decision-tengu-chair-sermon-is-now-fixed-per","canonical_anchor":"reminder-fold-decision-tengu-chair-sermon-is-now-fixed-per","heading":"Reminder-fold decision (tengu_chair_sermon) is now fixed per session and passed to subagents","tier":"internal","area":"System Reminders","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/reminder-fold-decision-tengu-chair-sermon-is-now-fixed-per","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Reminder-fold decision (tengu_chair_sermon) is now fixed per session and passed to subagents\n\nWhether system reminders are folded is now fixed once per session and handed down to subagents\n\n**Unclear.** The finding does not say what folding a system reminder does.\n\n**What**\n\nSystem reminders are notes Claude Code adds to the conversation for the model. Whether they get folded used to be decided by reading `tengu_chair_sermon` each time. Now:\n\n- The decision is stored on the session and recorded in `prompt_snapshot` as a new optional `reminderFold` field.\n\n- Subagents, the helper agents Claude starts for part of a task, receive it through `inheritedReminderFold`.\n\n- The decision is fixed this way only when `tengu_foamy_spring` is on.\n\n- A value that came from the built-in fallback, rather than from the server, is not fixed.\n\n**Why**\n\nReminders are handled the same way for a whole session and for every subagent in it, rather than changing partway through if the server's answer changes.\n\n- Flag `tengu_chair_sermon`: Off in both readings (read for one account on one subscription tier against v2.1.281; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: System Reminders\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}