Last ned Cursor 1.1.6

You can now launch Background Agents directly from Slack by mentioning @Cursor. Agents can read the thread, understand what's going on, and create PRs in GitHub, all without leaving the conversation.
Use Cursor where your team works
Mention @Cursor in any thread with a prompt like:

Agents run remotely in a secure environment and you'll get updates directly in Slack, including links to Cursor and GitHub, when the work is done.
Agents understand context
Cursor reads the entire Slack thread before starting, so Background Agents understand the full context when you reference previous discussions or issues.

You can also ask Cursor to investigate issues and get answers:

Getting started
To use Background Agents in Slack, an admin needs to set up the integration first. Check out our setup documentation or ask your workspace admin to connect Cursor from the Dashboard → Integrations page.
Once connected, try it in any channel with @Cursor and write a prompt. Use the command help to see all commands, or settings to configure your default model, repo, and branch.
Improvements (1)
- Search in settings with Cmd/Ctrl+F
MCP (3)
- Progress notifications from servers
- Dynamic tool registration
- Roots supports
Patches (3)
1.1.1
- Fixed workspaces indexing issue
1.1.2
- Improved client side performance
1.1.3
- Fixed MCP performance regression
- Added PR search and indexing
- Improved deeplink experience
- Added option to change upstream marketplace provider
1.1.4
- Improved Background Agent reliability
- Fixed search in Chat UI bug
1.1.5
- Small performance improvements
1.1.6
- Fixed an agent latency regression that occurs for users using Remote SSH