{"version":"2.1.277","anchor":"task-management-reminders-suppressed-when-the-brief-tool-has","canonical_anchor":"task-management-reminders-suppressed-when-the-brief-tool-has","heading":"Task-management reminders suppressed when the Brief tool has been used","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/task-management-reminders-suppressed-when-the-brief-tool-has","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Task-management reminders suppressed when the Brief tool has been used\n\nTask-management reminders are now skipped in conversations that used the Brief tool\n\n**Unclear.** The `tengu_humble_zephyr` gate controlling an alternate code path (deferring to `fUo.isBriefEnabled()`) hasn't been read, so it's unclear whether that alternate behavior is active for any account.\n\n**What**\n\nWhen the internal task-reminder check runs, it now looks for whether the conversation has used the Brief tool. If it has, task reminders are skipped for that turn, at least by default.\n\n**Why**\n\nThis avoids nagging you with task-management reminders when you're already working through a Brief-tool workflow, which presumably handles task tracking on its own.\n\n- Flag `tengu_humble_zephyr`: Not enough to say (read for one account on one subscription tier against v2.1.277; this account: no value returned, anonymous baseline: no value returned, 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: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}