[FEATURE] Notifications for task completion and when awaiting user response

Resolved 💬 3 comments Opened Oct 18, 2025 by mertkalak Closed Oct 22, 2025

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When delegating complex tasks to Claude Code, I often multitask (e.g., watching videos, working on other things) while Claude works. However, I
need to constantly check back to see if:

  1. Claude has completed the task
  2. Claude is waiting for my approval (e.g., after ExitPlanMode)
  3. Claude needs my input to continue

Currently, notifications only trigger for the AskUserQuestion tool. This means I miss when Claude finishes work or is blocked waiting for me,
forcing me to constantly context-switch to check status.

This breaks my workflow because I want to delegate and be notified when my attention is needed, rather than polling the interface.

Proposed Solution

Add notifications for these events:

  1. Task completion: When Claude finishes executing a plan or task
  2. Awaiting approval: When Claude uses ExitPlanMode and is waiting for user to approve/reject the plan
  3. Blocked/waiting: When Claude is idle and waiting for user response (not actively processing)

Ideally, these would be system-level notifications (same mechanism as AskUserQuestion currently uses) so users can confidently multitask while
Claude works.

Optional: Add a setting to enable/disable these notification types individually.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

  1. I'm working on a Flutter dental app and need to refactor the authentication system
  2. I ask Claude Code to "analyze the auth flow and create a refactoring plan"
  3. I switch to YouTube to watch a video while Claude analyzes the codebase
  4. Claude finishes the analysis and presents a plan via ExitPlanMode (currently: no notification, I keep watching YouTube unaware)
  5. With this feature, I would receive a notification: "Claude Code: Plan ready for review"
  6. I switch back to Claude Code, review the plan, and approve it
  7. I return to YouTube while Claude implements the plan
  8. Claude completes the implementation (currently: no notification, I waste time checking periodically)
  9. With this feature, I receive a notification: "Claude Code: Task completed - Authentication refactor done"
  10. I switch back, review the changes, test the code, and continue working

Time saved: Instead of checking Claude Code every 2-3 minutes (wasting focus and context-switching), I can fully focus on other tasks and only
switch back when actually needed. This turns Claude Code into a true async collaborator rather than requiring constant supervision.

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗