Agents
Cursor for Microsoft Teams: Start Cloud Agents with @Cursor
Cursor's Microsoft Teams integration lets you run Cloud Agents from Teams by mentioning @Cursor with a prompt. Cursor picks the repository and model from your message, the thread context, and your recent activity, and you can pin them explicitly with repo, branch, and model options. It works in personal chats, team channels, and group chats, and surfaces launch and completion cards with links to open the agent in the web or desktop app.
On this page
What does the Microsoft Teams integration do?
It connects Cursor's Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. to Microsoft Teams so you can kick off coding work without leaving the conversation. You mention @Cursor with a prompt, and an agent starts against the right repository. The integration supports personal chats, team channels, and group chats.
Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. understand and use context from existing Teams discussions. When your team talks through an issue in a thread and you then mention @Cursor, the agent reads the relevant thread or chat context and acts on that discussion.
How do you install Cursor in Microsoft Teams?
Installation starts from the Cursor integrations dashboard and finishes back in Cursor, where you connect a repository provider and confirm settings. These are Cursor's documented steps.
- 1Go to Cursor integrations and click Connect next to Microsoft Teams (or open the Microsoft Marketplace listing).
- 2Install the Cursor app in your Microsoft Teams workspace.
- 3After installing, you are redirected back to Cursor to finalize setup.
- 4Connect GitHub, GitLab, Azure DevOps, or Bitbucket if you have not connected a repository provider yet.
- 5Enable usage-based pricing and confirm your privacy settings.
- 6Start using Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. in Teams by mentioning @Cursor.
How do you start and steer an agent from Teams?
Mention @Cursor and give your prompt; Cursor picks the repository and model automatically. To pin a specific repository or model, name it in the message or use inline options. Run @Cursor help for an up-to-date command list. The table below lists the documented commands.
- Command
- @Cursor [prompt]
- What it does
- Start a Cloud Agent. In channel threads with existing agents, adds follow-up instructions.
- Command
- @Cursor help
- What it does
- Show setup and usage help.
- Command
- @Cursor unlink
- What it does
- Disconnect your Cursor account from Microsoft Teams.
- Command
- @Cursor disconnect
- What it does
- Disconnect your Cursor account from Microsoft Teams.
- Command
- @Cursor [options] [prompt]
- What it does
- Use advanced options: repo, branch, model.
| Command | What it does |
|---|---|
| @Cursor [prompt] | Start a Cloud Agent. In channel threads with existing agents, adds follow-up instructions. |
| @Cursor help | Show setup and usage help. |
| @Cursor unlink | Disconnect your Cursor account from Microsoft Teams. |
| @Cursor disconnect | Disconnect your Cursor account from Microsoft Teams. |
| @Cursor [options] [prompt] | Use advanced options: repo, branch, model. |
Commands from Cursor's Microsoft Teams integration docs.
Options can be written naturally or inline, and the bot parses them from anywhere in the message. The two syntaxes below produce the same result.
@Cursor with opus, fix the login bug in backend-api @Cursor repo=acme/backend branch=dev model=opus Fix the login bug
How does Cursor choose the repository, branch, and model?
Cursor evaluates your message in a fixed order, so explicit options always win and dashboard defaults act as the fallback. Understanding the order helps when an agent picks an unexpected repo.
- 1Explicit options: repo, branch, and model values written in your prompt.
- 2Your message content: repository, model, or branch names mentioned in the prompt.
- 3Recent agent activity: repositories you have used recently.
- 4Default repository: the fallback when no match is found.
Manage default model, repository selection, and base branch from Dashboard > Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop.. Leave the base branch blank to use the repository's default branch, often main. Inline options override values inferred from your message; dashboard settings apply when nothing is specified or inferred.
What do the status cards and privacy settings cover?
When an agent starts, Teams shows a launch card with the selected repository, model, and branch, plus options to Open in Web, Open in Desktop, and Switch repository. On completion you get a notification with the result, and if the agent opened a pull request the card links to it. You can also add follow-ups, switch repository, or delete the agent from the card.
Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. support Privacy ModeCursor's setting that routes requests under zero-data-retention terms so providers don't store or train on your code., but Privacy Mode (Legacy) is not supported because Cloud Agents require temporary code storage while running. The integration requests Teams permissions including identity, messaging team members, and read access to channel and chat messages and metadata for thread context.
Frequently asked questions
How do I start a Cursor Cloud Agent from Microsoft Teams?
Mention @Cursor with a prompt in a personal chat, team channel, or group chat. Cursor picks the repository and model from your message, the thread, and recent activity, and you can pin them with repo, branch, and model options.
Can I choose which repository and model the agent uses?
Yes. Name the repository or model in your message, or use inline options like repo=acme/backend, branch=dev, and model=opus. Explicit options take precedence, followed by message content, recent activity, and your dashboard defaults.
Does the Microsoft Teams integration support Privacy Mode?
Cloud Agents support Privacy Mode, but Privacy Mode (Legacy) is not supported because Cloud Agents need temporary code storage while running. Manage privacy settings from Dashboard > Cloud Agents.
Sources & last verified
Cursor ships frequently. Facts verified against primary sources on June 26, 2026.