Seamless Slack Integration
Developers can now interact with Cursor’s Background Agents by simply mentioning @Cursor in any Slack thread. This functionality allows agents to:
- Read and understand Slack thread context.
- Perform tasks like bug fixes or code improvements.
- Create and link GitHub pull requests automatically.
- Notify users with updates in Slack, including links to Cursor and GitHub.
How It Works
To get started:
-
Visit cursor.com/dashboard → Integrations → Slack.
-
Ensure the (Legacy) Privacy Mode is disabled to allow code storage on Cursor servers.
-
Mention @Cursor in a Slack thread with a prompt, such as:
@Cursor fix the login bug@Cursor [repo=torvalds/linux] fix bugto specify a repository.
Available Commands
| Command | Description |
|---|---|
@Cursor [prompt] | Starts or updates an agent with the given prompt |
@Cursor settings | Adjust default settings and repository preferences |
@Cursor [options] [prompt] | Use advanced options like branch, model, and repo |
@Cursor agent [prompt] | Creates a new agent forcibly within a thread |
@Cursor list my agents | Lists all running agents associated with the user |
For more information, refer to the Cursor Slack integration documentation.
An (expected) caveat
Disabling (Legacy) Privacy Mode is mandatory for code processing and agent functionality. The (Legacy) Privacy Mode blocks this by design—as it prevents any code from being retained or processed beyond the local environment.