Guide
Cursor Automations Guide
Answer first
Cursor's June 2026 Automations update added /automate, Slack emoji triggers, five GitHub triggers and computer use for cloud-agent automations. It also made automations easier to save through MCP auth, open PRs by default and clean up outdated memory files.
What changed in Cursor Automations, June 2026?
Cursor's June 2026 Automations update added /automate, Slack emoji triggers, five GitHub triggers and computer use for cloud-agent automations. It also made automations easier to save through MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. auth, open PRs by default and clean up outdated memory files.
- Release fact
- /automate
- Why it matters
- Create an automation from a local agent session in plain language.
- Release fact
- Slack emoji trigger
- Why it matters
- React to a Slack message with a configured emoji to start an automation.
- Release fact
- GitHub triggers
- Why it matters
- Issue comment, PR review comment, PR review submitted, Review thread updated and Workflow run completed can now trigger work.
- Release fact
- Computer use
- Why it matters
- Cloud agents started by automations can produce demos, screenshots or artifacts.
- Release fact
- Memory and PR defaults
- Why it matters
- Incomplete saves, PR creation defaults and memory-file cleanup reduce setup friction.
| Release fact | Why it matters |
|---|---|
| /automate | Create an automation from a local agent session in plain language. |
| Slack emoji trigger | React to a Slack message with a configured emoji to start an automation. |
| GitHub triggers | Issue comment, PR review comment, PR review submitted, Review thread updated and Workflow run completed can now trigger work. |
| Computer use | Cloud agents started by automations can produce demos, screenshots or artifacts. |
| Memory and PR defaults | Incomplete saves, PR creation defaults and memory-file cleanup reduce setup friction. |
Release facts checked on 2026-06-23. Use the linked Cursor sources before quoting product mechanics in a live customer, security or pricing conversation.
How should a team use Cursor Automations?
- 1Prove the workflow manually once in a local agent session.
- 2Use
/automateor a Marketplace template to draft the trigger, tools and instructions. - 3Choose the narrowest Slack, GitHub, webhook or schedule trigger that carries enough context.
- 4Review the first runs for noise, PR quality, memory behavior and permission creep.
Interactive diagram. Use Tab to move through hotspots or use the step controls when shown.
What should stay bounded?
Define no-op behavior so low-signal comments or emoji reactions do not create noisy PRs.
Treat MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. auth, Slack access and GitHub write access as separate permission reviews.
Review automation memory files periodically and delete stale memories when they can steer future runs badly.
Frequently asked questions
Who is Cursor Automations Guide for?
Developers, DevEx teams and engineering managers turning repeated Cursor work into always-on workflows.
What makes this page credible?
The guide is grounded in Cursor's June 18, 2026 changelog and maps each new trigger to a reviewable workflow.
What should I do next?
Start with one real repo task, capture the prompt and review the result before scaling the workflow.
Editorial notes
Source review
- Last checked
- June 23, 2026
- Scope
- Cursor docs, Cursor Learn pages and product docs.
- Refresh
- Quarterly, plus changes to Cursor agent or CLI docs.
- Reviewer
- Learn Cursor editorial
Page assets
- Primary media
- Workflow diagram.
- Supporting media
- Learn Cursor practice screenshot.
- Interactive element
- Step diagram.
- Transcript
- Add a transcript when a recorded walkthrough is added.
- Refresh owner
- Learn Cursor editorial.
Content pod
- Pod
- Workflow pod
- Owner
- Editorial director
- Reviewers
- DevRel engineer, SEO lead, Senior editor
QA gate
- Human signal
- Includes a task-specific diagram, checklist or calculator.
- Claims
- Claims stay tied to sources, visible limits and page scope.
- Visual proof
- Uses product screenshots or annotated workflow diagrams, not stock art.
- Page rhythm
- Sections vary between answer, method, visual and action blocks.
Sources & last verified
- Cursor changelog: Improvements to Cursor Automations
- Cursor changelog
- Cursor changelog: Cloud Environment Setup and Cloud Subagents
Cursor ships frequently. Facts verified against primary sources on June 23, 2026.