Cursor for Microsoft Teams: Start Cloud Agents with @Cursor

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. Press Enter for the full definition. to Microsoft Teams, so you can start coding work without leaving the conversation. You mention @Cursor with a prompt, and an agent starts on the repository Cursor picks. The integration supports personal chats, team channels and group chats.

None of the work happens inside Teams. The agent runs as a Cloud Agent on Cursor's side, against a repository connected through your Git provider. That also sets the plan you need: 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. Press Enter for the full definition. come with Premium or higher, a Cursor Teams or Enterprise plan, or a legacy paid plan, and a Free or Plus plan doesn't include them.

The value shows up in a narrow case, when the task has already been described in the channel. Someone reported a bug, two people worked out what was wrong, and the fix that is left is one sentence. Mentioning @Cursor there saves restating all of it somewhere else.

You start in the Cursor integrations dashboard, install the app in Teams, and finish back in Cursor, where you connect a repository provider and confirm settings.

1. 1Go to Cursor integrations and click Connect next to Microsoft Teams (or open the Microsoft Marketplace listing).
2. 2Install the Cursor app in your Microsoft Teams workspace.
3. 3After installing, you are redirected back to Cursor to finalize setup.
4. 4Connect GitHub, GitLab, Azure DevOps, or Bitbucket if you have not connected a repository provider yet.
5. 5Enable usage-based pricing and confirm your privacy settings.
6. 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. Press Enter for the full definition. in Teams by mentioning @Cursor.

That order makes the Teams install look like the first move in adopting 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. Press Enter for the full definition., but it belongs near the end. The app can be installed in Teams while the Cursor side is unfinished, and an agent with no connected repository provider has nothing to work on. Cursor's Cloud Agent guidance is to set up the environment first, so get a few runs working from Cloud Agent setup and add Teams after that.

Settle the privacy question before you ask anyone to install anything. 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. Press Enter for the full definition. don't support Privacy Mode (Legacy)A Cursor data setting that blocks Grok Bot because the product requires cloud data storage. Press Enter for the full definition., so an organization on that setting has nothing here to pilot.

Team size decides where the list stalls. With two engineers, one of them does all of it in a sitting. Bigger organizations tend to stall in the middle, because enabling usage-based pricing is a billing decision, and whoever wants the integration is not always the person who can approve it.

Mention @Cursor and give your prompt. Cursor picks the repository, model, base branch or named environment from your message, the thread and your recent activity. To pin one, name it in the message or use an inline option. The table below lists the documented commands.

Options can be written in natural language or inline, and the bot parses them from anywhere in the message. The first line below is Cursor's natural example, and the second uses the documented inline keys. They are not the same request, so read them as two syntaxes, not as a before and after.

@Cursor with opus, fix the login bug in backend-api
@Cursor repo=acme/backend branch=dev model=opus Fix the login bug

Both forms work, so the choice is about who else reads the message. Natural phrasing stays readable to the people in the channel. Inline repo= and model= are precise and a little ugly, which is worth it when you point an agent at a repository you don't normally touch. If your team uses named cloud agent environments, env= picks one, and it takes precedence over repo when a message has both. In your usual repo, with dashboard defaults set, none of them is worth typing.

The table above is a snapshot of the docs. @Cursor help returns the live list.

Two rows there carry the same description: unlink and disconnect both disconnect your Cursor account from Microsoft Teams. They look like aliases, though the docs don't say so. Either one takes a single person's link out and leaves the app in place for everyone else.

Cursor evaluates your message in a fixed order, so explicit options always win and dashboard defaults are the fallback. Knowing the order helps when an agent picks an unexpected repo.

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

Explicit values sit at the top of that list, and they are the ones worth typing, because inference fails quietly. A missing repository name doesn't raise an error. At worst it produces an agent working in the wrong codebase, and you find out when a pull request appears somewhere you weren't watching.

Read step three twice. Recent agent activity means repositories you have used recently, so it resolves per person, not per channel. Two people in the same conversation can send the same sentence and start agents on different repositories, and nothing in the message shows that it happened. On a team with one repository this never comes up. Once several repos and several teams share a channel, make naming the repo a habit.

Base branch runs on a shorter ladder, and the note below has the mechanics. Left blank, it falls through to the repository's default branch, often main. A team that integrates on a dev line and never sets that default gets Teams-started agents branching from main whenever nobody names one. The launch card shows the branch, if anyone checks it.

In a channel thread, yes. Reply in the agent's thread with another @Cursor mention, and it lands as a follow-up instruction. In personal chats and group chats you can't, so you continue from Cursor through Open in Web or Open in Desktop on the card.

That difference catches people out, because the natural way to try a new bot is privately. You message it, the first result looks good, and the second instruction has nowhere to go except out of Teams and into the web app. That works fine, but it isn't what you set out to test.

So run the trial in a channel thread, even if a private chat feels safer, and start it where the follow-ups will have to happen.

When an agent starts, Teams shows a launch card with the selected repository, model and branch, plus 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.

Settle agent summaries and diff images before this goes into a busy channel, because they can carry file paths and code snippets. Cursor's Microsoft Teams docs name one setting for them, Display agent summary. The 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. Press Enter for the full definition. settings page lists two admin-only toggles: that one, and one that extends it to Slack or any external channel you've connected. Check both before a pilot in a channel the whole department reads.

Read the launch card first, then work outward. It names the repository, model and branch, so most surprises show up there before the agent gets far.

The app is installed once for the workspace, but the account link is per person. That is what the messageTeamMembers permission covers: Cursor sends direct messages for setup, account linking and notifications. When one person's mention behaves differently from everyone else's, check their direct message from the bot before any dashboard setting.

If the repository is what went wrong, use Switch repository on the card. It relaunches the same request against a different repository.