---
title: "Improvements to Cursor in Slack"
description: "Cursor in Slack now gives users more control over tasks by presenting a plan before work begins and reporting status as it progresses. Its Slack presentation has also changed: compact footer links replace in-message buttons, while tables, pull requests, and artifacts render more cleanly. In named multi-repo environments, Cursor can select an environment with access to related frontend, backend, and shared-code repositories; if it needs another repository, it prompts for a switch and resumes the task afterward. Cross-channel workflows let Cursor read context from other channels and threads and send updates to the original thread or a relevant channel. Together, these changes support earlier redirection, broader repository access, and task coordination across Slack workspace conversations."
---

# Improvements to Cursor in Slack

[Cursor](https://yomu.fyi/company/cursor) · Jul 17, 2026

**Type:** Announcement

## Summary

Cursor in Slack now gives users more control over tasks by presenting a plan before work begins and reporting status as it progresses. Its Slack presentation has also changed: compact footer links replace in-message buttons, while tables, pull requests, and artifacts render more cleanly. In named multi-repo environments, Cursor can select an environment with access to related frontend, backend, and shared-code repositories; if it needs another repository, it prompts for a switch and resumes the task afterward. Cross-channel workflows let Cursor read context from other channels and threads and send updates to the original thread or a relevant channel. Together, these changes support earlier redirection, broader repository access, and task coordination across Slack workspace conversations.

## Context

The update concerns Cursor’s Slack workflows, including task planning and status visibility, message rendering, multi-repo environments, and communication across channels and threads.

## Approach / What changed

Cursor first shares a task plan and then posts status updates while working. It can start in a named multi-repo environment, prompt the user to switch repositories when necessary, and continue from where it paused. It can also read context from other Slack channels and threads and post updates to the original thread or a relevant channel.

## Takeaways

- Cursor presents a plan before starting and provides status updates during a task, allowing users to redirect work earlier.
- Named multi-repo environments let Cursor work with separate frontend, backend, and shared-code repositories; users can switch repositories mid-task and have it resume afterward.
- Cursor can read from other Slack channels and threads and send updates back to the original thread or a relevant channel.

## FAQ

### What happens if Cursor needs a repository outside the current environment?

Cursor displays a Switch repository button. After the user chooses a repository or environment, Cursor picks up the task where it left off.

### Can Cursor use information from other Slack conversations?

Yes. During a task, Cursor can pull context from other channels and threads, then post updates to the original thread or the relevant channel.

### How has Cursor’s Slack output changed?

In-message buttons have been replaced by compact footer links. Tables, pull requests, and artifacts also render more cleanly.

**Tags:** [Slack](https://yomu.fyi/topic/slack)

- Source: [Cursor](https://cursor.com/changelog/slack-improvements)
- Source URL: https://cursor.com/changelog/slack-improvements
- Ingested by Yomu: 2026-09-19T10:36:22.772Z

[Read original post](https://cursor.com/changelog/slack-improvements)