Screenshot from cursor.com/changelog Cursor Comes to Microsoft Teams and Adds Multi-Repo Cloud Environments
Cursor's newest releases let anyone in a Teams channel delegate coding tasks to a cloud agent by mentioning @Cursor, while a separate update brings Dockerfile-based multi-repo development environments with 70% faster cache builds and version history.
Cursor shipped two updates in quick succession this week. The first puts Cursor inside Microsoft Teams. The second turns cloud agent environments into proper infrastructure with Dockerfile support, multi-repo access, and 70% faster caching.
Cursor in Microsoft Teams
The Teams integration is live as of May 11. Anyone in a Teams channel can type @Cursor followed by a task description, and Cursor spins up a cloud agent to handle it. The agent reads the thread for context, picks the relevant repository and model automatically, implements the change, and opens a pull request.
No IDE required. No one needs to have the Cursor IDE installed to trigger an agent. The idea is that wherever developers are already talking about a task, that’s where they can now also delegate it.
Copilot has had Teams integration for some time. Cursor catching up here matters because it means Cursor’s cloud agents are now accessible without switching tools. A product manager describing a bug in a Teams thread can hand that description directly to Cursor without pulling in an engineer to translate it into an editor prompt.
Multi-Repo Cloud Environments
The May 13 update covers development environments for cloud agents, and the multi-repo support is the most significant part.
Previously, a cloud agent environment was built around a single repository. The new system lets you configure an environment with multiple repos in a single Dockerfile-based setup. Build secrets support private registries. Layer caching cuts build times by 70% on subsequent runs, which matters when agents are spawning frequently.
Environment version history lets you roll back to a previous configuration if something breaks. That’s basic infrastructure reliability, but it’s been absent from cloud agent setups in general — most tools treat environments as disposable rather than stateful.
The audit logs tie into governance. Teams running agents at scale need a record of what ran, in what environment, and from which configuration. The combination of version history and audit logs is what turns “a cloud environment” into something an ops team can reason about.
What This Adds Up To
Both releases point in the same direction. Cursor has been expanding outward from the IDE: cloud agents in 3.0, worktrees and parallel subagents in 3.2, PR review in 3.3, and now Teams integration and multi-repo environments. The IDE is still the core, but Cursor is building for the scenario where the agent operates independently of the editor.
The Teams integration specifically bets that the next interface for AI coding isn’t the IDE. It’s wherever the conversation about the work already lives. If that framing proves right, the IDE becomes one entry point among several rather than the only place coding assistance happens.
Full details at cursor.com/changelog.
Sources: Cursor changelog — Microsoft Teams (May 11, 2026), Cursor changelog — Cloud environments (May 13, 2026)