Windows taskbar notification / progress indicator when long-running tasks complete
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 Claude Code is working on a long task (10, 20, 30+ minutes), there is no way to know when it has finished without constantly switching back to the window to check. This is a significant workflow interruption — you either miss the completion for a long time, or you keep interrupting your other work to check.
Proposed Solution
One or more of the following notification mechanisms when a task completes (or requires user input):
- Taskbar icon flashing — standard Windows behavior used by many apps (e.g. terminals, IDEs) to signal that attention is needed
- Taskbar progress bar — show a progress indicator in the taskbar button while Claude is working (green fill on completion), just like file copy dialogs or browser downloads do via the Windows Taskbar API
- Windows Toast Notification — a system notification in the bottom-right corner: "Claude Code: Task completed" or "Claude Code: Input required"
- Sound alert — optional audio cue on completion (configurable on/off)
Why This Matters
Developers routinely switch to other tasks while Claude Code runs. Without a completion signal, they either:
- Waste time polling the window repeatedly
- Miss the completion and leave Claude idle for long periods
This is standard behavior in IDEs (VS Code, Visual Studio), build tools, and CI runners. It would make Claude Code significantly more ergonomic for long agentic sessions.
Platform
Windows (primary request), but macOS already has a similar convention via Dock bouncing — so a cross-platform implementation would benefit all users.
Thank you for considering this!
Alternative Solutions
_No response_
Priority
Low - Nice to have
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗