We're introducing Cursor Automations to build always-on agents. https://t.co/uxgTbncJlM
The Hook
“I'm Jack. And I'm Jon. And today we're launching Automations in Cursor.”
Problem Agitation
“As agents have gotten really capable at handling work autonomously, we found ourselves kicking them off over and over again for the same type of task. So we thought, why not automate that?”
Product Reveal
“It's been crazy to see the creative use cases that people have come up with. For example, we have an incident triage that gets triggered every time a PagerDuty monitor goes off. This one Jon loves especially because he hates getting woken up at 3:00 a.m. Famously. We give it the Datadog MCP, and then by the time he rolls out of bed all groggy, the agent has come back with a likely root cause. So I just need to merge the PR and then I can go back to sleep.”
Feature Teaser
“I have a personal automation just for myself. It runs on a nightly cron schedule. It looks at all my PRs from the last day and just cleans up dead code or bad patterns.”
Feature Teaser
“We're very fortunate to have this great community of users who are always suggesting new features to build, and we pipe those through from Twitter onto Slack. And now we can just have an agent automatically kick off with every single one and just put up a PR right away. Some of these features, if they're simple, are actually just getting implemented asynchronously. The way we do software development has changed so much in the last nine months. Yeah. And with more software, with more output, you then have more stuff you need to review, more issues you need to triage, more things to manage around software. But a lot of these things are automatable.”
Call to Action
“Thankfully, because we kind of let the agent run free, if you want comments to be inline-threaded comments on GitHub, just prompt your agent to do so. If you want it to resolve its past comments, just prompt your agent to do so. All of these things that people are used to kind of configuring with check boxes, you don't need to do that anymore. Just prompt your agent.”
Call to Action
“(No spoken dialogue — ambient room tone ending)”
Synthesizable in Remotion · key components of the developer-launch-walkthrough template.
Fades and slides two-line text up at bottom corners during live-action introduction.
Use Remotion interpolate on opacity and translateY over the first 15 frames.
Floats up from bottom-left corner with checkmark icon and dismiss button.
Trigger spring-based translateY from 20px to 0px paired with opacity fade-in.
Tumbled 3D cube rotates along X and Y axes, settling flat into the brand emblem.
Three.js Canvas inside Remotion or CSS transform rotateX/rotateY driven by spring curve.
Purpose. Introduce presenters and establish product launch in four seconds.
Execution. Medium shot of two engineers behind laptop with lower third credentials.
Purpose. Explain the friction of running repetitive manual agent tasks.
Execution. Presenter speaking interspersed with UI templates overview.
Purpose. Demonstrate real-world utility via incident triage, scheduled cleanup, and feedback routing.
Execution. Fast screencast UI walk-throughs and Slack integrations.
Purpose. Emphasize prompt-driven configuration over manual checkboxes, closing on brand mark.
Execution. Creation flow culminating in success toast and animated logo outro.