Summary
Cursor is widening the control plane for cloud agents across collaboration and workflow surfaces instead of keeping them tied to the editor. Alongside Teams and Jira triggers, Cursor now exposes Automations directly in the Agents Window with multi-repo and no-repo runs for always-on agent workflows.
What changed
Cursor expanded its cloud-agent surface across Microsoft Teams, Jira, and the in-product Agents Window, including automation support for multi-repo and no-repo agent runs.
Why it matters
This makes Cursor look more like an operational agent platform than a coding IDE feature. Teams can trigger work from chat, ticketing systems, or recurring automations, which moves coding agents closer to the systems where engineering work is requested and handed off.
Evidence excerpt
Cursor says teams can mention @Cursor in Teams, assign work inside Jira, and use Automations inside the Agents Window with support for multi-repo and no-repo runs.