Cursor in Microsoft Teams
TL;DR
Cursor integration is now available in Microsoft Teams. Users can mention @Cursor in channels to delegate tasks to cloud agents, which automatically select repositories and models, read thread context, implement solutions, and create PRs.
## What changed Cursor added direct integration with Microsoft Teams. Users can now mention @Cursor inside any channel to hand off work to cloud agents.
These agents pick the right repository and model on their own. They pull context from the thread, write the code, and open a pull request.
The feature rolled out on May 18, 2026 and works with existing Cursor cloud accounts.
## Why it matters Teams that already live in chat can now skip the step of opening an editor. A product manager or support lead can describe a fix and watch an agent turn it into a real PR.
The move pressures pure chat tools and low-code platforms that still treat code changes as a separate workflow. Cursor is betting that conversation context plus agent autonomy beats manual hand-offs for many small tasks.
Solo builders gain a new input surface but lose some control over which model and repo the agent chooses.
## How to use it Enable the Teams app from the Cursor dashboard under Integrations. Add the bot to the channels where your team discusses work.
Type @Cursor followed by a clear request that includes any relevant repo name or branch. The agent replies in the thread once the PR is ready.
Access requires a Cursor Pro or Team plan and an active cloud agent quota.
## Watch for Track whether the agents consistently pick the correct repo and avoid breaking changes on first try. Failures here would show up as repeated PR rejections or off-topic commits.
The next logical step is similar hooks in Slack and Linear so the same agent pool can be reached from every tool a builder already opens.
Harsh’s take
Cursor in Teams moves the AI coding surface into the same window where most business requests already arrive. For a solo operator this cuts one context switch but adds a new dependency on Cursor's cloud agent making the right repo and model choices without supervision.
The real trade-off is speed versus oversight. You get PRs started from a quick mention, yet you still have to review every diff because the agent only reads the thread you gave it.
Do this now: connect the Teams bot to your single active project, run three small tasks through it this week, and measure how many PRs need rework before you decide to route more work this way.
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.
- IntegrationIntegrate Cursor with Microsoft Teams
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.