Cursor Improvements to Cursor in Slack

+ 신기능 4개

• Slack에서 Cursor가 실행 전 계획을 공유하고, 멀티 레포지토리 환경에서 작동하며, 채널과 스레드 간에 작동할 수 있게 된다 # 에이전트
  원문

  Improvements to Cursor in Slack: Cursor in Slack now shares a plan before it starts, runs in multi-repo environments, and can work across channels and threads.

• Slack에서 Cursor가 단일 기본 레포지토리 대신 이름이 지정된 멀티 레포지토리 환경에서 시작할 수 있게 된다 # 에이전트
  원문

  Multi-repo environment support: From Slack, Cursor can now start in a named multi-repo environment instead of a single default repository. If your frontend, backend, and shared code live in separate repos, Cursor reads your request and targets the environment that gives it access to all of them. Mid-task, when Cursor needs a repo outside the current environment, it prompts you with a **Switch repository** button. Click it, choose the repo or environment, and Cursor picks up right where it left off.

• Cursor가 시작 전 계획을 공유하고 상태를 업데이트하며, Slack 내 메시지 버튼을 제거하고 콤팩트한 푸터 링크로 대체하며, 테이블, PR, 아티팩트의 렌더링을 개선한다 # UI
  원문

  Interaction improvements: Cursor now responds with a plan before it begins, so you can jump in and redirect early. As it works, it updates its status so you can follow each step. We also refined how Cursor's responses look in Slack. In-message buttons are gone, replaced by compact footer links. Tables, PRs, and artifacts now render more cleanly.

• Cursor가 다른 Slack 채널과 스레드에서 메시지를 읽고 보낼 수 있게 된다 # 에이전트
  원문

  Cross-channel workflows: Cursor can now read from and send messages to other Slack channels and threads. During a task, it can pull context from elsewhere in the workspace and post updates back in the original thread or the relevant channel. Learn more in our Slack docs.