Microsoft Teams

With Cursor's integration for Microsoft Teams, you can use Cloud Agents to work on tasks directly from Microsoft Teams by mentioning @Cursor with a prompt.

Get started

Installation

1. Go to Cursor integrations

2. Click Connect next to Microsoft Teams or go to the Microsoft Marketplace listing

3. Install the Cursor app in your Microsoft Teams workspace

4. After installing in Microsoft Teams, you'll be redirected back to Cursor to finalize setup

   1. Connect GitHub, GitLab, Azure DevOps, or Bitbucket, if you haven't connected a repository provider yet
   2. Enable usage-based pricing
   3. Confirm privacy settings

5. Start using Cloud Agents in Microsoft Teams by mentioning @Cursor

How to use

Mention @Cursor and give your prompt. Cursor automatically picks the right repository, model, base branch, or named cloud agent environment based on your message, the thread context, and your recent agent activity.

To use a specific repository, include its name in your message:

• @Cursor in cursor-app, fix the login bug
• @Cursor fix the auth issue in backend-api

To use a specific model, mention it in your message:

• @Cursor with opus, fix the login bug
• @Cursor use gpt-5.2 to refactor the auth module

To use a named environment, mention it in your message or add env=<name>:

• @Cursor use the Platform environment to update the shared API
• @Cursor env=Platform update the shared API
• @Cursor env="Platform Services" update the shared API

Commands

Run @Cursor help for an up-to-date command list.

Options

Customize Cloud Agent behavior with these options:

Syntax formats

Natural:

@Cursor with opus, fix the login bug in backend-api

Inline:

@Cursor env="Platform Services" branch=dev model=opus Fix the login bug

Option precedence

When combining options:

• Explicit values override defaults
• Inline options override model and repository values inferred from your message
• Dashboard settings apply when no value is specified or inferred
• env takes precedence over repo when both are present

The bot parses options from anywhere in the message, allowing natural command writing.

Using thread context

Cloud Agents understand and use context from existing Microsoft Teams discussions. This is useful when your team discusses an issue and you want the agent to make the code change based on that conversation.

Follow-up instructions

In channel threads, reply in the agent's thread with another @Cursor mention to add follow-up instructions.

In personal chats and group chats, continue the conversation from Cursor using Open in Web or Open in Desktop.

Status updates & handoff

When Cloud Agent starts, Microsoft Teams shows a launch card with the selected repository, model, and branch. The card includes options to Open in Web, Open in Desktop, and Switch repository.

When Cloud Agent completes, you get a Microsoft Teams notification with the result. If the agent opened a pull request, the card includes an option to view the PR.

Managing agents

Manage Cloud Agents using actions on the Microsoft Teams cards.

Available options:

• Add follow-up: Add instructions to an existing agent from a channel thread
• Switch repository: Relaunch the same request against a different repository
• Delete: Stop and archive the Cloud Agent
• Open in Web: Continue in the web interface
• Open in Desktop: Continue in Cursor
• Update settings: Manage your Cloud Agent defaults
• Give feedback: Send feedback about agent performance

Configuration

Manage default settings and privacy options from Dashboard -> Cloud Agents.

Settings

Default model

Used when no model is specified in your message. See settings for available options.

Repository selection

Cursor automatically selects the right repository based on:

1. Your message content: repository names or keywords in your prompt
2. Recent agent activity: repositories you've used recently
3. Default repository: fallback when no match is found

To use a specific repository, include its name in your message. For example: @Cursor in mobile-app, fix the login bug.

Base branch

Starting branch for Cloud Agent. Leave blank to use the repository's default branch, often main.

Routing behavior

Cursor evaluates your Microsoft Teams message in this order:

1. Explicit options: repo, env, branch, and model values in your prompt
2. Your message content: repository names, model names, or branch names in your prompt
3. Recent agent activity: repositories you've used recently
4. Default repository: fallback when no match is found

Privacy

Cloud Agents support Privacy Mode.

Read more about Privacy Mode or manage your privacy settings.

Display agent summary

Display agent summaries and diff images. They may contain file paths or code snippets. You can turn this on or off.

Permissions

Cursor requests these Microsoft Teams permissions for Cloud Agents to work in your workspace:

The Cursor app supports personal chats, team channels, and group chats in Microsoft Teams.

Disclaimer

Cursor can make mistakes. Please double-check code and responses.

Privacy Policy

For information about how Cursor collects, uses, and protects your data, see our Privacy Policy.