Cursor · 2026-06-18 · major
Cursor 3.8 — /automate skill plus new GitHub and Slack automation triggers
Cursor 3.8 adds the /automate skill so agents create automations from a plain-English description, five new GitHub triggers, and a Slack emoji trigger; cloud agents can now use the computer tool by default.
Cursor 3.8 lets you build automations in plain English and fire them from GitHub events or a Slack emoji react.
Key specs
| Version | 3.8 |
|---|---|
| New git hub triggers | 5 |
What is it?
Cursor 3.8 is the latest release of the Cursor coding agent. The headline change is Cursor Automations: durable agent workflows that run when an outside event fires. The /automate skill turns a description into a saved automation, and Cursor 3.8 adds five new GitHub triggers (issue comments on non-PR issues, PR review inline comments, PR review submissions, review thread updates, and Workflow run completion) plus a Slack emoji-react trigger.
How does it work?
Cursor 3.8's /automate skill runs inside a normal local agent session — describe the automation in plain English and Cursor saves it as a reusable workflow with the right trigger wired up. Triggers listen for events from connected GitHub repos and Slack channels; when one fires, Cursor 3.8 spawns a cloud agent to handle the work. In Cursor 3.8 those cloud agents can now use the computer tool by default, so they can produce demos and screenshot artifacts as part of the automation output.
Why does it matter?
Cursor 3.8 closes the loop on agent-triggered work. Until now coding agents waited for a human to ask; Cursor Automations let an agent pick up a GitHub review comment or a Slack thumbs-up emoji and start work on its own. The /automate skill also lowers the bar for setting these up — no YAML, no glue scripts.
Who is it for?
teams running cloud-based coding agents on top of GitHub and Slack
Try it
Update Cursor and run /automate in any agent chat