{"version":"2.1.271","anchor":"idle-notification-threshold-now-read-from-settings-messagei","canonical_anchor":"idle-notification-threshold-now-read-from-settings-messagei","heading":"Idle-notification threshold now read from settings (messageIdleNotifThresholdMs)","tier":"use","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/idle-notification-threshold-now-read-from-settings-messagei","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Idle-notification threshold now read from settings (messageIdleNotifThresholdMs)\n\nIdle notifications now use the messageIdleNotifThresholdMs setting directly, still 60 seconds by default\n\n**What**\n\nThe logic that decides when to send an idle notification (letting you know Claude Code is waiting on you) now reads its threshold directly from the settings field `messageIdleNotifThresholdMs`, rather than computing it through separate workflow-size-guideline logic. The default value remains 60000ms (60 seconds).\n\n**Why**\n\nThis simplifies how the idle threshold is determined, without changing the default timing you'll see in practice.\n\n- Area: Terminal UI\n- Names: `messageIdleNotifThresholdMs`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}