If you’re already using Cursor’s Automations—the always-on agents that handle repetitive tasks for you—the June 18th changelog deserves a setup session. Cursor expanded them with a new /automate skill, five fresh GitHub triggers, an emoji reaction trigger for Slack, and computer use enabled by default. Fair warning before you start: Automations isn’t new. This is a dated expansion, not a launch—so if you already had agents running, it’s about doing more with the same plumbing.
Here’s what changed in detail, and then we’ll build an end-to-end PR comment autofix workflow.
What /automate does
The headline is the new /automate skill. You run it inside your local agent session, describe in natural language the task you want to automate, and Cursor sets up the triggers, instructions, and tools for you. No clicking through a setup UI field by field—you describe, it wires.
That’s the whole pitch, in Cursor’s own words: the feature exists to “save you time by automating repetitive tasks with always-on agents.”
The new triggers
Five new GitHub triggers expand what can fire up an agent:
- Issue comment — a comment on an issue that isn’t a PR
- PR review comment — an inline comment left on a pull request’s diff
- PR review submitted — when a review is submitted
- Review thread updated — when a review thread is marked as resolved or unresolved
- Workflow run completed — when a GitHub Actions run finishes on a PR or branch
An emoji reaction trigger for Slack — react to any Slack message with a designated emoji and the automation fires. The Cursor team itself uses it to launch automations straight from Slack.
Computer use, by default — cloud agents launched by an automation can now control their own desktop to produce demos or work artifacts. You don’t enable anything; just tell the agent in your instructions to include a demo.
There are also three minor quality-of-life improvements: automations can be saved mid-setup (handy when you need to step away to configure an MCP auth), they can open PRs by default without you specifying that tool, and you can delete memory files from the UI or have the automation prune old memories on its own.
Building a PR comment autofix workflow
Cursor shipped two templates in the Marketplace with this release—one for triaging failed GitHub Actions, another for autofixing PR review comments. We’ll use the autofix template as the backbone and wire it ourselves so you understand each piece.
Step 1 — Start from /automate. In your local agent session, run /automate and describe the goal: “When someone leaves an inline review comment on a PR, address the comment and push a fix to the branch.” Cursor suggests the trigger, instructions, and tools.
Step 2 — Confirm the trigger. The right trigger here is PR review comment (the inline on the diff), not PR review submitted—you want the agent to react to each specific line comment, not wait for an entire review to land. If you prefer batching, switch it to PR review submitted.
Step 3 — Tweak the instructions. Tell the agent to read the comment, make the change on the PR’s existing branch, and reply to the review comment summarizing what it did. Since automations now open PRs by default, you don’t need to spell out the PR tool—but since this is an existing branch, instruct it to push to the branch instead of opening a new PR.
Step 4 — Add a demo (optional). If the fix touches UI, add a line like “include a short demo of the result” to your instructions. Computer use is already on, so the cloud agent will produce the artifact without extra setup.
Step 5 — Save and test. Leave a throwaway inline comment on an open PR (“rename this variable to userCount”) and watch it fire. If you need to pause mid-setup to authorize an MCP server, the incomplete save now lets you pick up where you left off.
The Marketplace shortcut
If you’d rather not wire it by hand, the PR review comment autofix template gives you the same workflow preconfigured, and the failed Actions triage template pairs well with the Workflow run completed trigger. Templates are the fast track; building from /automate is how you learn what each knob does.
To get started you need the latest version of Cursor.
Are you already running Automations on your team, or is this expansion your reason to start? Let us know what repetitive task you’d automate first.