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.
Who this matters for
- Vibe Builders: Use @Cursor in Teams to turn product discussions into draft PRs without opening a code editor.
- Developers: Connect Cursor to Teams to automate routine bug fixes and PR creation directly from chat threads.
Harsh’s take
Cursor moving into Teams is a power play for the entire software lifecycle. By letting agents live where the conversation happens, they are removing the friction of context switching between Slack or Teams and the IDE. This is not about simple chat: it is about autonomous agents having the permission to select repos and ship code based on natural language requests from non-technical stakeholders.
The risk for teams is the loss of granular control over model selection and repo targeting. Operators must monitor these agents closely to ensure they do not create a backlog of low quality pull requests. However, for fast moving teams, the ability to trigger a PR from a support thread or a feature discussion is a massive speed boost that makes traditional ticket-to-code workflows look ancient.
by Harsh Desai
About Cursor
View the full Cursor page →All Cursor updatesGo deeper
More from Cursor
- FeatureCursor adds cloud agent management to the Agents window
Cursor sets up cloud development environments in under 10 minutes, spins up isolated cloud subagents using /in-cloud, and hands off sessions between local and cloud.
- FeatureCursor introduces /automate skill for automating repetitive tasks
Cursor's new /automate skill creates automations from plain language. Workflows trigger via Slack emojis or GitHub events while cloud agents access virtual computers.
- FeatureCursor Adds New Customize Page for Managing Workflows Plugins and Rules
Cursor introduces a Customize page to manage plugins, skills, MCPs, and rules in one place. It includes a marketplace leaderboard, prebuilt plugin canvases, and repository import support.