Automations

Source: Cursor Date: 2026-03-05 URL: https://cursor.com/changelog/03-05-26

Summary

Cursor ships Automations: always-on agents that run on schedules or event triggers from Slack, Linear, GitHub, PagerDuty, and webhooks, executing in cloud sandboxes with configured MCPs and models. A memory tool enables agents to learn from past runs. Automations are configurable at cursor.com/automations with marketplace templates available.

Implications

Agent-IDE feature race. Automations are Cursor’s entry into the autonomous agent platform space — not just agents you invoke, but agents that run continuously on event triggers. This puts Cursor in direct competition with n8n, Zapier, and GitHub Actions for workflow automation, and with Devin and SWE-agent for autonomous background engineering tasks. The combination of PagerDuty triggers + coding agents is a particularly compelling on-call automation pattern.

MCP/protocol adoption. Automations running with configured MCP servers means MCP tooling is now a first-class automation substrate, not just an interactive session enhancement. An automation triggered by a PagerDuty alert that uses a Datadog MCP and a GitHub MCP to diagnose and patch a production issue is a complete autonomous incident response pipeline.

Pricing model evolution. Always-on cloud agents with memory that improve over time is a recurring compute commitment. Watch for Automations to drive a new pricing tier (per-automation or per-run cost) distinct from the per-seat or per-request model used for interactive agents.