Fordel StudiosCursor is rolling out a new kind of agentic coding tool
What Happened
Called Automations, the new system gives users a way to automatically launch agents within their coding environment, triggered by a new addition to the codebase, a Slack message, or a simple timer.
Our Take
Honestly? Automations in your IDE sound great until Slack messages start triggering agent runs while you're mid-debugging. Cursor's solving a real scatter problem (agents live everywhere), but the UX here feels like we learned nothing from chaos.
The real issue: unintended triggers. You mention a refactor casually in Slack, agent ships code, you're back in the fire. You're not buying automation, you're buying technical debt with a better GUI.
Skip this until there's a "kill all agents" button that actually works.
What To Do
Wait for a stable kill-switch before enabling Slack triggers in your workflow.
Cited By
React