claude-code - 💡(How to fix) Fix Add config to disable idle/awaiting-input reminder notification separately from completion notifications

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Problem

Claude Code fires a notification (terminal bell or system notification) ~60 seconds after a response completes if no new user input has been received. This happens even when the user was actively in the window when the response finished — they read it and switched windows, and then get notified anyway.

There is currently no way to disable this idle reminder without also disabling completion notifications entirely. The only notification setting available disables all notifications.

Expected behavior

Either:

  1. A separate config option to disable the idle/awaiting-input reminder independently of completion notifications, or
  2. The idle reminder should not fire if the window was focused when the response completed (i.e., the user demonstrably saw it)

Current behavior

  • Task completes, user reads it while window is active
  • User switches to another window
  • ~60 seconds later, notification fires as a "hey, respond to me" nudge
  • No config exists to suppress just this behavior

Request

Add a granular config (e.g. idleReminderEnabled: false) so users can keep completion notifications without the nagging reminder.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Either:

  1. A separate config option to disable the idle/awaiting-input reminder independently of completion notifications, or
  2. The idle reminder should not fire if the window was focused when the response completed (i.e., the user demonstrably saw it)

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING