Cursor finished.
Your phone knows.

Zero setup, works while you are at the machine

Cursor can play a completion sound and surface a system notification when the agent finishes. Open Cursor Settings and search for notifications to toggle them. This is the setting most people are looking for when they search for the agent completion sound. It does nothing once you close the laptop or walk away.

Cursor hooks fire a script when the agent completes

Cursor supports hooks defined in hooks.json at the project or user level (~/.cursor/hooks.json). The stop event fires on agent completion and spawns your script with JSON context on stdin, so a two-line script can run osascript on macOS or notify-send on Linux. The same mechanism exposes beforeShellExecution, which is how enforced approval gates are built.

{
  "version": 1,
  "hooks": {
    "stop": [
      { "command": "./hooks/notify.sh" }
    ]
  }
}

Point the stop hook at ntfy.sh and your phone buzzes

Make the stop hook script curl a free ntfy topic and the completion reaches your phone. The trade-offs: it is one-way, so when the agent is waiting on a decision you still have to get back to Cursor to answer, and public ntfy topics are readable by anyone who guesses the name unless you reserve one or self-host.

#!/bin/bash
curl -s -d "Cursor agent finished" ntfy.sh/your-topic

The only option where you can answer Cursor remotely

Add Pushary to Cursor's MCP config and the agent gains notify and ask tools: you get a push when a task completes, and when the agent needs a decision, the notification carries the question. Tap yes or no from your lock screen and it continues. The Pushary hooks plugin adds a fail-closed beforeShellExecution gate on top, so risky shell commands wait for your approval instead of running. Every decision lands in an audit trail.

{
  "mcpServers": {
    "pushary": {
      "url": "https://pushary.com/api/mcp/mcp"
    }
  }
}