Cursor Automations no longer live exclusively on cursor.com — version 3.5 pulls them into the Agents Window inside the editor, and adds the ability to attach multiple repos (or none) to a single automation.
Three concrete changes shipped:
- Automations in the Agents Window. You can now create, configure, and monitor automations without leaving the IDE. Previously this required switching to cursor.com.
- Multi-repo automations. A single automation can span multiple attached repositories — useful for monorepo-adjacent setups or cross-service workflows like syncing API contracts.
- No-repo automations. Automations no longer require a repo at all, opening the door to tasks like triaging Slack messages or responding to PagerDuty incidents without touching code directly.
Cursor originally launched Automations as always-on agents triggered by events — merged GitHub PRs, new Linear issues, Slack messages, PagerDuty alerts. The two main patterns that emerged internally at Cursor were code review (auditing diffs for security vulnerabilities) and reactive maintenance (auto-responding to issues). Moving the control surface into the editor collapses the feedback loop: you see automation results alongside your code, not in a separate browser tab.
TIP
New automations created now get 50% off all agent runs for 7 days — worth testing if you’ve been waiting to try event-driven agents on your own codebase.
The multi-repo addition matters most for teams. Before this, each automation was scoped to a single repository. If your CI pipeline spans a frontend repo and a shared types package, you needed two separate automations doing overlapping work. Now one automation handles both.
Available now in Cursor 3.5. Check the changelog for the full release notes, and the half-price window on new automation runs is live for the next seven days.