Background Agents in Slack

Source: Cursor Date: 2025-06-12 URL: https://cursor.com/changelog/1-1

Summary

Cursor 1.1 ships Background Agents in Slack: mention @Cursor in a thread, and an agent launches, reads full thread context, executes in a secure remote environment, and can create GitHub PRs — all without leaving Slack. MCP gains progress notifications, dynamic tool registration, and roots support. Seven patches address SSH latency regression and workspace indexing.

Implications

Agent-IDE feature race. Slack as an agent entry point inverts the IDE paradigm: the agent loop now originates in a communication tool and the IDE is just execution infrastructure. This is a direct competitive move against GitHub Copilot Workspace (GitHub Issues → agent) and positions Cursor as an ambient agent platform, not just an editor enhancement. Claude Code lacks a native Slack integration; Aider is CLI-only.

MCP/protocol adoption. Dynamic tool registration and roots support in MCP are infrastructure investments: they let tool authors build richer integrations without Cursor shipping new code. Progress notifications close the feedback loop for long-running agent tasks. This is Cursor deepening MCP as a platform rather than treating it as a feature checkbox.

Watch: Whether the Slack integration expands to other surfaces (GitHub Issues, Linear, Jira) and whether the secure remote execution environment becomes a billable compute tier.