Automations Errors

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor Automations failing.

Started failing on github PR triggers.

Now failing on manual triggers too.

Failing when trying to chat to automations historical runs.

And new PR’s are not even triggering the automation anymore.

Steps to Reproduce

Create new PR which should trigger a cursor automation.

or

Run manually in the automations view.

or

Try chatting with a historical automations run.

Expected Behavior

Does not error

Screenshots / Screen Recordings

Screenshot 2026-07-15 at 17.21.12.png
Screenshot 2026-07-15 at 17.21.12.png408×300 12.5 KB
Screenshot 2026-07-15 at 17.26.47.png
Screenshot 2026-07-15 at 17.26.47.png444×305 18.4 KB
Screenshot 2026-07-15 at 17.27.41.png
Screenshot 2026-07-15 at 17.27.41.png928×435 34.1 KB

Operating System

MacOS

Version Information

Version: 3.11.19
VS Code Extension API: 1.125.0
Commit: bf249e6efb5b097f23d7e21d7283429f0760b740
Date: 2026-07-12T21:39:24.175Z (2 days ago)
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Have tried several while attempting to resolve. All failing

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Still 100% broken as of 18:49 BST / 17:49 UTC.

Screenshots above show:

  • Manual run → “internal error”
  • Background agent fails to even start
  • Historical runs also throw “We encountered an unexpected error repeatedly”

Automations (PR triggers + manual + history) are completely unusable right now.

Please take a look — this is production-blocking.

7

Hey there!
Sorry this is still going, and thanks for the detailed report. This isn’t anything on your end. We’re aware of a broad issue affecting Automations that’s still ongoing, and the team is actively working on it. You can check current status any time at https://status.cursor.com

There’s no reliable workaround while it’s ongoing, so runs may fail to start or error out. Once it’s resolved, if new PRs still don’t trigger your automation, open it at cursor.com/automations and re-save to re-activate it.

I’ll follow up here as soon as it’s back to normal.