Summary
Cursor is widening the control plane for its cloud agents across collaboration and workflow surfaces instead of keeping them tied to the editor. After bringing agent initiation into Microsoft Teams and Jira, Cursor now also exposes Automations inside the Agents Window and supports multi-repo or no-repo runs for always-on agent workflows.
What changed
Cursor expanded its cloud-agent surface across Microsoft Teams, Jira, and the in-product Automations experience, including multi-repo and no-repo automation support in the Agents Window.
Why it matters
This makes Cursor’s agent model look more like an operational platform than an IDE feature. Teams can trigger agents from chat, ticketing systems, or recurring automations, which moves coding agents closer to the systems where engineering work is requested, monitored, and handed off rather than limiting them to hands-on editor sessions.
Evidence excerpt
Cursor says teams can mention @Cursor in Teams or assign work inside Jira to start a cloud agent, and its May 20 update adds Automations to the Agents Window with support for multi-repo and no-repo agent runs.