[FEATURE] Mobile push notifications when Claude Code finishes a task or requires input
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
Claude Code is designed for long-running, agentic tasks — refactoring codebases, running tests, scaffolding projects. However, it currently provides no out-of-band signal when a task completes or when it pauses to request user input or approval.As a result, developers must either watch their terminal continuously or poll manually, which defeats the purpose of handing off work to an autonomous agent. This friction is especially significant for tasks that take several minutes, where the natural workflow would be to context-switch to something else while Claude works.There is no way today to know — without looking at the terminal — whether Claude Code finished successfully, hit an error, or is blocked waiting for a decision.
Proposed Solution
Send push notifications to the Claude mobile app (iOS / Android) when Claude Code reaches a state that requires user attention. The mobile app is already authenticated to the same Anthropic account, making it the natural delivery channel.
Trigger a notification on:
Task completed (success or failure)
Permission prompt — Claude Code is waiting for the user to approve an action
Clarification needed — Claude cannot proceed without additional input
Unrecoverable error
Notification should include a short summary of the context (e.g. "Claude finished refactoring auth module" or "Claude needs approval to delete 3 files") and ideally deep-link back to the relevant session.
Configuration should be opt-in, with per-trigger granularity in settings (e.g. notify only on completion, or only when blocked).
Prior art: GitHub Actions, Bitrise, and Xcode Cloud all follow this pattern — send a push when the async job needs the developer's attention.
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
Developer tools/SDK
Use Case Example
_No response_
Additional Context
_No response_