Improvements to Cursor in Slack
By Steven Van ·
Cursor in Slack now shares a plan before it starts, runs in multi-repo environments, and can work across channels and threads.
Cursor in Slack now shares a plan before it starts a task, works across multiple repos, and can pull in context from other channels and threads.
- Before starting, Cursor posts a plan so you can redirect it early, then updates its status as it works. In-message buttons have been replaced with compact footer links, and tables, PRs, and artifacts render more cleanly.
- From Slack, Cursor can start in a named multi-repo environment instead of a single default repo, so a request touching separate frontend, backend, and shared-code repos targets the environment that gives it access to all of them. If it needs a repo outside that environment mid-task, it prompts with a Switch repository button, and picks up where it left off once you choose one.
- Cursor can now read from and send messages to other Slack channels and threads, pulling context from elsewhere in the workspace and posting updates back to the original thread or the relevant channel.
More detail is in the original announcement and Cursor's Slack docs.
Cursor
AI code editor built on VS Code — agents that edit across your codebase, run in the cloud, review pull requests, and now host your repos.
View Cursor →