Cursor の Slack 連携がアップデート：マルチリポジトリ対応と事前プラン提示Cursor's Slack integration has been updated to support multiple repositories…

Cursor, the AI-assisted code editor built on a fork of Visual Studio Code, has updated its Slack integration to handle work across multiple repositories and to display a proposed plan before it carries out any changes. The update matters because it moves the tool's agent capabilities further into shared team spaces, where code changes are increasingly initiated, reviewed, and coordinated without anyone opening the editor itself.

The Slack integration lets developers trigger Cursor's background agent directly from a Slack channel or thread, typically by mentioning the bot and describing a task in natural language. The agent then works against a connected codebase, and can open pull requests or report results back into the conversation. Bringing this capability into Slack is significant because it turns an ambient chat tool into an entry point for coding work, allowing a team member to delegate a fix or investigation from wherever a discussion is already happening.

The headline change is support for multiple repositories. Previously, a given interaction was generally scoped to a single repository, which constrained tasks that touched more than one service or crossed the boundaries of a typical microservices layout. With multi-repository support, a request made from Slack can appear to span several codebases, which is useful for organizations that split functionality across many smaller repositories rather than keeping everything in one monolith. The practical effect is that teams should be able to route a task to the correct repository, or coordinate related changes, without having to reconfigure the integration or switch contexts for each project.

The second addition is a plan presented before execution. Instead of immediately acting on an instruction, the agent appears to outline what it intends to do, giving a human a chance to review the approach before code is written or a pull request is opened. This kind of preview step reflects a broader pattern in agentic coding tools, where an explicit planning phase is used both to improve the quality of the eventual output and to keep a person in the loop. For team workflows in particular, showing intent up front lowers the risk of an autonomous agent making unwanted or wide-reaching changes, since reviewers can catch a misunderstanding at the planning stage rather than after the work is done.

Together, these two features are framed as making team use safer and more flexible. The multi-repository capability addresses flexibility by matching how many engineering organizations actually structure their code, while the pre-execution plan addresses safety by adding a checkpoint before changes land. The combination is aimed at the collaborative scenario where several people share a channel and any of them might invoke the agent, and where a visible plan doubles as a lightweight record of what was requested and why.

This release fits into a wider industry push toward what is often called agentic or autonomous coding, where AI systems take on multi-step tasks rather than only offering inline completions. Cursor competes in a crowded field that includes GitHub Copilot and its more agent-oriented features, tools such as Devin from Cognition, Anthropic's Claude Code, and various open-source coding agents. Many of these products are converging on similar ideas: background agents that run asynchronously, integration with chat and issue-tracking surfaces, and mechanisms to review or approve an agent's actions before they take effect. Slack has separately been positioning itself as a hub for such integrations, exposing app and bot frameworks that let third-party tools operate inside conversations.

For teams considering the update, a few prerequisites are worth keeping in mind. Using the integration generally requires connecting Cursor to a code host such as GitHub and granting the appropriate repository permissions, along with installing and authorizing the Slack app for the relevant workspace. Organizations with strict access controls will likely want to confirm how repository permissions map onto Slack-initiated tasks, especially now that a single request can reach across multiple repositories. As with any tool that can modify source code from a chat prompt, the value of the new plan-preview step depends on teams actually reading and vetting the proposed actions. Readers should consult Cursor's official documentation for the precise configuration steps and any limits, since integration features of this kind tend to evolve quickly.