Integrate Cursor with Microsoft Teams
TL;DR
Cursor is now available in Microsoft Teams. Users can mention @Cursor in any channel to delegate tasks to cloud agents, which can read thread context, select repositories, and create pull requests directly from the chat.
## What changed On May 11 2026 Cursor added a Microsoft Teams integration. Users can now mention @Cursor in any channel to hand tasks to cloud agents.
The agent reads the full thread for context, chooses the right repository and model based on recent activity, then creates a pull request for review. The feature works with existing cloud agent capabilities.
## Why it matters This move places Cursor inside the chat tool many engineering teams already live in. It reduces context switching for task delegation and review.
Solo builders gain a direct line from discussion to code changes without leaving Teams. The bet is that conversation history contains enough signal to drive reliable agent work.
## How to use it Install the integration from the Cursor dashboard at cursor.com/dashboard/integrations#integrations. No extra plan is required beyond standard cloud agent access.
Once connected, type @Cursor followed by a task description in any Teams channel. The agent pulls thread details automatically and surfaces the resulting PR back in chat.
## Watch for Success shows up as accurate repository selection and clean PRs created from chat threads. Failures will appear as wrong repo picks or incomplete context handling.
Expect Cursor to add similar hooks for Slack or Discord next if Teams usage grows.
Harsh’s take
For a solo operator this integration mainly saves tab switching. You still need solid prompts and a well-maintained repo for the agent to produce usable output.
The real trade-off is visibility: every task you delegate now lives in a shared channel where teammates can see both the request and the PR. That can speed feedback but also exposes unfinished work.
Connect the integration today and test it on one small bug fix from a Teams thread. Measure how many follow-up messages you still send before the PR is ready.
by Harsh Desai
About Cursor
View the full Cursor page →All Cursor updatesMore from Cursor
- FeatureNew PR Review Experience and Parallel Building
Introduces a unified PR review interface with inline threads and commit history. New 'Build in Parallel' feature allows Cursor to execute independent plan tasks simultaneously using async subagents to speed up development.
- App UpdateCustomize Bugbot PR Review Effort
Admins and Individual plan users can now set Bugbot's effort level to Default, High, or Custom. High effort allows for deeper reasoning to find more bugs, while Custom effort uses natural language instructions to determine review intensity.
- FeatureConfigure Agent Development Environments
New tools allow teams to configure development environments for agents using Dockerfile-based configuration with build secrets and layer caching. Supports multi-repo environments and provides full version history and audit logs for governance.