Summary
Cursor's agent infrastructure work now spans managed cloud-agent environments, desktop cloud-subagent setup, and a new /automate skill for configuring recurring automations from a local agent session. The combined signal is that Cursor is making remote execution, environment definition, and always-on workflow automation part of the everyday coding surface rather than a separate platform workflow.
What changed
Cursor added and expanded cloud-agent development-environment controls, then added the /automate skill with GitHub and Slack triggers and computer-use support for Cursor Automations.
Why it matters
Cursor is moving deeper into agent execution infrastructure. Environment setup, security policy, multi-agent cloud supervision, and recurring automation configuration are becoming editor-native features for teams trying to run long-lived coding agents against real internal stacks.
Evidence excerpt
Cursor's changelog describes cloud environment setup, cloud subagents in the Agents Window, and /automate support for configuring automations with GitHub and Slack triggers.