{"version":"2.1.321","anchor":"silent-turn-reminder-gets-a-gate-driven-default","canonical_anchor":"silent-turn-reminder-gets-a-gate-driven-default","heading":"The silent-turn reminder can now use a time limit even when you set nothing","tier":"notice","area":"Reminders","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/silent-turn-reminder-gets-a-gate-driven-default","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### The silent-turn reminder can now use a time limit even when you set nothing\n\nWhen neither the environment variable nor the model's own setting gives a seconds value, the silent-turn reminder now takes a default from a remote check\n\n**Unclear.** The default number of seconds the remote check supplies is not known, so it is unclear whether the reminder now fires for people who set nothing.\n\n**What**\n\nThe silent-turn reminder nudges Claude when it has gone quiet for a while. Claude Code now looks for its time limit, measured in seconds, in this order:\n\n- `CLAUDE_CODE_SILENT_TURN_REMINDER_SECONDS`, if you set it\n\n- a value configured for the model in use\n\n- a default number of seconds supplied by a remote check\n\nThe third step is the difference. Before, if neither of the first two gave a usable value, there was no time-based reminder at all.\n\n**Why**\n\nPeople who never set a seconds value may start seeing Claude nudged after a period of silence. Setting `CLAUDE_CODE_SILENT_TURN_REMINDER_SECONDS` yourself still takes priority over everything else.\n\n- Area: Reminders\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}