Skip to content
Cursor Handbook

Automations

Recurring agent work that runs on Cursor's infrastructure whether or not your laptop is open.

  • Automation
  • Pro, Pro+, Ultra, Teams and Enterprise.

Checked against cursor.com on 25 September 2026

What it does

Plenty of engineering work is predictable and nobody wants to own it: dependency bumps, documentation that drifts from the code, flaky tests that need triaging, security reviews on a cadence. Automations attach a cloud agent to a schedule or a trigger so that work runs on its own and arrives as a pull request.

Because automations run as cloud agents, they do not need your machine to be awake, and on Teams plans they carry shared team context so the output matches house conventions rather than whatever the model assumes.

Results land as pull requests rather than pushes to a branch people are working on, which keeps a human in the approval path.

Checked against Automations documentation on 25 September 2026.

Frequently asked questions

What can Cursor automations do?
Run a cloud agent on a schedule or trigger. Common uses are keeping documentation in sync with code, running recurring security or dependency reviews, and triaging failing tests, with the result opened as a pull request.
Do automations need my computer to be running?
No. Automations execute as cloud agents on Cursor's infrastructure, so they run on schedule regardless of whether the editor is open.
Which plans include automations?
Automations follow cloud agents, so they are available on Pro, Pro+, Ultra, Teams and Enterprise. Teams and Enterprise add shared team context.

Keep reading