Integrations · Cursor
Cursor agent runs, via Cursor hooks.
When a Cursor agent is running commands and editing files, NotchPulse shows it at the top of your screen and lets you know when it’s done. It’s built on Cursor’s agent hooks — so we’re precise about what that covers.
Coming in v1 Included with NotchPulse Pro
2 livenow
Cursor · web-appRunning·Editing files
Cursor agent finishedDone·web-app
What you’ll see
- Working — “Cursor · your-workspace” once an agent run begins.
- Running a command and Editing files as the agent works.
- Finished — with a subtle celebration.
- Runs quietly complete after ten minutes without a hook event.
How it connects
- Cursor agent hooks (
hooks.json, per user or per project), which run a command at points in an agent’s lifecycle. - Works for the Cursor CLI agent in a terminal, too.
- Hooks have changed between Cursor versions, so NotchPulse checks versions and ignores fields it doesn’t know.
What NotchPulse never uploads
- Commands the agent runs.
- File paths or file contents.
- Chat content or code.
What it can’t see
- This is not a full Cursor integration. Tab completion and inline edits happen inside the editor with no external signal.
- Chat panel content or “thinking” state beyond hook points — we won’t scrape the screen for it.
- Background agents running in Cursor’s cloud.
- Whether Cursor is waiting on a confirmation, unless a hook fires at that moment.
Cursor is a trademark of its owner. NotchPulse works with Cursor through its public interfaces and is not affiliated with, sponsored by or endorsed by its maker.
Launching soon for macOS 14 and later.
Free forever, with 7 days of Pro in every download. Pro Lifetime is a single payment — no subscription.