Slack
Work with Background Agents from Slack
With Cursor’s Slack integration, you can use Background Agents to work on your tasks directly from Slack by mentioning @Cursor with a prompt.
Get started
Installation
-
Go to Cursor integrations
-
Click Connect next to Slack
-
You’ll be prompted to install the Cursor Slack app in your workspace.
-
After installing in Slack, you’ll be redirected back to Cursor to finalize setup
- Connect GitHub (if not already connected)
- Set default settings like repository, model and branch (read more further down)
- Enable usage based pricing
- Update privacy mode
-
Once this is configured you start using Background Agents in Slack by mentioning @Cursor
How to use
Just @Cursor and give the prompt you want. This is usually enough for most use cases, but you can also use the commands below to customize your agent.
For example, you can mention @Cursor fix the login bug directly in your conversation, or use more specific commands like @Cursor [repo=torvalds/linux] fix bug to target a particular repository.
Commands
Run @Cursor help to see a list of up to date commands.
| Command | Description |
|---|---|
| @Cursor [prompt] | Start a Background Agent. In threads with existing agents, adds followup instructions |
| @Cursor settings | Configure your defaults, and the channel’s default repository |
| @Cursor [options] [prompt] | Use advanced options: branch, model, repo |
| @Cursor agent [prompt] | Force create a new agent in a thread |
| @Cursor list my agents | Show your running agents |
Using thread context
Background Agents can understand and use the context from an existing thread discussion. This is particularly useful when your team has been discussing an issue and you want the agent to implement the solution based on that conversation.
Background Agents read the entire thread for context when invoked, allowing them to understand and implement solutions based on the team’s discussion.
When to use force commands
When do I need @Cursor agent?
In threads with existing agents, @Cursor [prompt] adds followup instructions (only works if you own the agent). Use @Cursor agent [prompt] to launch a separate agent.
When do I need Add follow-up (from context menu)?
Use the context menu (⋯) on an agent’s response to add followup instructions via a modal. This is useful when multiple agents exist in a thread and you need to specify which one to follow up on.
Status updates & handoff
When a Background Agent is running, you’ll first get an option to Open in Cursor.
When Background Agent is done, you’ll get a notification in Slack and an option to view the created PR in GitHub.
Managing agents
To see all your running agents, run @Cursor list my agents.
You can manage your Background Agents using the context menu by clicking the three dots (⋯) on any agent message.
Available options include:
- Add follow-up: Add additional instructions to an existing agent
- Delete: Stops and archives the Background Agent
- View request ID: View the unique request ID for troubleshooting (include when reaching out to support)
- Give feedback: Provide feedback about the agent’s performance
Configuration
Default settings and privacy options can be managed from Dashboard → Background Agents.
Settings
Default Model
Used when no model is explicitly specified with @Cursor [model=...]. See settings for currently available options.
Default Repository
Used when no repository is specified. Use one of the following formats:
https://github.com/org/repositoryorg/repository
If you reference a non-existent repository, it will appear as if you don’t have access to it. This will be indicated in the error message when the Background Agent fails to start.
Base Branch
Starting branch for Background Agent. We recommend leaving it blank to use the repository’s default branch (often main)
Channel Settings
You can configure default settings at the channel level using @Cursor settings. These settings are configured per team and override your personal defaults for that specific channel.
This is particularly useful when:
- Different channels work on different repositories
- Teams want consistent settings across all members in a channel
- You want to avoid specifying the repository in every command
To configure channel settings:
- Run @Cursor settings in the desired channel
- Set the default repository for that channel
- All team members using Background Agents in that channel will use these defaults
Channel settings take precedence over personal defaults but can still be overridden by explicit options like @Cursor [repo=...] [prompt]
Privacy
Display Agent Summary
Display agent summaries and diff images. May contain file paths or code snippets. Can be turned On/Off.
Display Agent Summary in External Channels
If you’re using Cursor in Slack Connect to communicate with other Slack Workspaces, or if you have channels in your workspace with external members like Guests, you can choose to display agent summaries in external channels.
Permissions
Cursor requests these Slack permissions to enable Background Agents to work within your workspace
| Permission | Description |
|---|---|
app_mentions:read | Detects when users @mention Cursor to start Background Agents and respond to requests. |
channels:history | Reads previous messages in threads to understand context when users add follow-up instructions to existing Background Agents. |
channels:join | Automatically joins public channels when users invite it or request help, eliminating the need for manual channel management. |
channels:read | Accesses basic channel metadata (IDs and names) to post replies and status updates in the correct location. |
chat:write | Sends status updates, completion notifications, and PR links back to users when Background Agents finish tasks. |
files:read | Downloads files shared by users (logs, screenshots, code samples) to provide additional context to Background Agents. |
files:write | Uploads visual summaries of agent changes so users can quickly review what was modified without opening the full PR. |
groups:history | Reads previous messages in private channels to maintain context for follow-up instructions and multi-turn conversations. |
groups:read | Accesses private channel metadata (IDs and names) to post responses in the correct thread and maintain conversation flow. |
im:history | Accesses direct message history to understand context when users continue conversations or add follow-up requests. |
im:read | Reads DM metadata to identify participants and maintain proper conversation threading in private messages. |
im:write | Initiates direct messages to send private notifications, sensitive updates, or when users prefer individual communication. |
mpim:history | Accesses group DM history to understand multi-participant conversations and provide contextual responses to all members. |
mpim:read | Reads group DM metadata to address participants properly and ensure responses reach all intended recipients. |
reactions:read | Observes emoji reactions on messages to understand user feedback and update agent status based on user confirmation signals. |
reactions:write | Adds emoji reactions to mark agent status - ⏳ for running, ✅ for completed, ❌ for failed - providing instant visual feedback. |
team:read | Identifies workspace details (name, domain, icon) to separate multiple workspace installations and apply correct settings. |
users:read | Matches Slack users with Cursor accounts using profile information to verify permissions and ensure secure agent access. |