How to know when Cursor's agent is done
Set up a Cursor hook that alerts you when the agent stops, or let Flincko show what Cursor is doing at the edge of your screen.
Updated October 15, 2026
Cursor's agent can work for minutes on a big change. If you look away, you either keep checking back, or you come back much later to find it finished ages ago. Here's how to get told when it stops.
1. Add a Cursor hook for the stop event
Cursor supports hooks: commands it runs at points in the agent's loop. The stop hook runs when the agent finishes. Put this in ~/.cursor/hooks.json (merge it with any hooks you already have):
{
"version": 1,
"hooks": {
"stop": [
{
"command": "osascript -e 'display notification \"Cursor agent is done\" with title \"Cursor\" sound name \"Glass\"'"
}
]
}
}That example is for macOS. On Windows, swap the command for something like powershell.exe -NoProfile -Command "[System.Media.SystemSounds]::Asterisk.Play()" to play a sound. Restart Cursor after editing the file so it picks up the hook.
Good for: a free alert when the agent stops. Not great for: seeing what the agent is doing while it works, or telling several chats apart.
2. Watch it live with a desktop buddy
Flincko installs Cursor hooks for you (and Claude Code hooks too, if you use both). A small buddy at the edge of your screen shows the agent's state as it happens: thinking, using tools, and done. When the agent finishes, it celebrates and shows a bubble, so you can glance over instead of switching windows.
- One buddy follows Cursor, Claude Code, and claude.ai, ChatGPT and Gemini in the browser.
- Hover it to see the session, how long the turn took and what was touched.
- Runs locally on Mac and Windows. Your code and chats don't leave your computer.
Tip: keep the agent busy, not you
The point of an alert is to let you actually look away. Give the agent a clear, larger task, switch to something else, and come back when you're told it's done, instead of babysitting the chat.