Summary
On July 17, 2026 Cursor improved its Slack integration so its agent posts a plan before it starts work, lets users redirect early, operates across multiple repository environments by auto-selecting the right repos, and reads other channels and threads for broader context. The update also cleaned up message rendering with compact footer links and clearer PR and table displays.
What changed
Cursor in Slack now responds with a plan before executing, supports multi-repo environments with automatic repo selection, reads other channels and threads for context, and refined its in-Slack rendering.
Why it matters
Moving the coding agent into Slack with plan-first behavior and multi-repo awareness turns team chat into a control surface for delegated engineering work, meeting developers where coordination already happens and reducing context-switching into the IDE.
Evidence excerpt
Cursor now responds with a plan before it begins, so you can jump in and redirect early. The agent can operate across multiple repository environments, and can read messages from other Slack channels and threads to gather broader context.