The release moves Cursor Automations into the same workspace as agents and adds multi-repo support so agents can reason across all required context. It also introduces no-repo automations for tasks like Slack digests, product analytics, FAQ drafting, finance reporting, and customer health monitoring. In other words, Cursor is pushing from code assistance into broader agent operations.
This matters because a lot of engineering work spans more than one repository or sits outside code entirely. The ability to coordinate across repos should reduce friction for refactors, release work, and cross-service verification. The no-repo mode is also a clue that Cursor wants to own more of the surrounding operational workflow, not just source editing.
Teams should treat the new templates as starting points, not finished products. The best use case is to wire one repetitive workflow into Automations, then check whether the agent can gather context, act, and report back without human babysitting. If that works, expand carefully to cross-repo work where verification matters.
Read Original Post →