Cursor Brings Cloud Agents to Microsoft Teams
Cursor's new Microsoft Teams integration lets developers @mention a cloud agent directly from any Teams channel — the agent automatically selects the right repo and model, reads the full thread for context, and opens a PR for review.
Image source: Open Graph image
Cursor Brings Cloud Agents to Microsoft Teams[#cursor-brings-cloud-agents-to-microsoft-teams]
Cursor has shipped a Microsoft Teams integration that lets developers trigger cloud coding agents directly from a chat channel — no tab switching, no context loss, no manual project setup required.
Announced on May 11, the integration puts Cursor's cloud agent system inside Teams. Developers @mention @Cursor in any channel with a task description, and the agent takes it from there: picking the right repository and model, reading the full conversation thread for context, implementing a solution, and opening a pull request for the team to review.
How the Integration Works[#how-the-integration-works]
The agent isn't just a passthrough to the IDE. According to Cursor's changelog, it automatically selects the correct repository and model based on the prompt text and recent agent activity — meaning teams don't need to specify project context for each request. Cursor infers it.
Once the agent has enough context, it implements the solution end-to-end and creates a PR. The result lands in whatever code review workflow the team already uses, keeping the feedback loop inside the SCM toolchain without introducing a parallel surface to maintain.
What This Means for Engineering Teams[#what-this-means-for-engineering-teams]
The pattern here is familiar from tools like Slack + Linear or GitHub Copilot for CLI — bring the coding surface into where developers already communicate rather than forcing a context switch into a dedicated IDE. But the Cursor implementation goes further: it routes directly to a persistent cloud agent with full repository awareness that can write code, not just answer questions or surface information.
For teams that already live in Teams rather than dedicated dev consoles, the integration removes the friction of manually spawning a Cursor agent session and configuring context. A developer — or even a product manager — can drop a task description in a channel and have a cloud agent open a reviewable PR without touching the IDE at all.
It also signals Cursor's continued push to make cloud agents a first-class workflow, not an add-on. The Teams integration joins existing cloud agent surfaces that include the Cursor web dashboard and CLI.
Getting Started[#getting-started]
The integration is available now. Install it from the Cursor dashboard integrations panel, then configure which Teams channels and repositories the agent has access to. Full documentation is available at cursor.com/docs/integrations/microsoft-teams.
