Cursor in Slack now spans repos and channels
Cursor's Slack integration now shares its plan before starting, runs across multiple repos, and works across channels and threads instead of one at a time.
Cursor updated its Slack integration on July 17 so agent runs can share a plan before they start, work across multiple repositories in one run, and follow a task across different channels and threads instead of being scoped to wherever it was first asked. Cursor’s changelog describes the update as improving how agent activity displays in Slack alongside the multi-repo and cross-channel support.
Before this update, Cursor in Slack worked best for single-repo requests started and finished in one thread; a task spanning more than one repository, or one that needed input from a different channel, required switching back to the editor or CLI. The update targets exactly that gap.
What it means for operators
Multi-repo support is the detail that matters most here: most real engineering tasks (a feature that touches a service and its shared library, a fix that spans a frontend and backend repo) don’t fit in one repository, and that mismatch is a common reason teams try an agent-in-Slack workflow once and then quietly go back to the terminal. Pairing this with the “plan before it starts” step also gives a reviewer a checkpoint before an agent starts editing code across repos it wasn’t explicitly asked about. It is a smaller update than Claude Code’s auto mode default on enterprise clouds or its manual-mode default change, but it closes a gap in the same competitive lane: making agentic coding usable from chat, not just an IDE.