Anthropic develops Slack-like features for Claude Desktop

Anthropic has updated its upcoming collaborative projects for Claude Code. During project creation, users can now add repositories directly as persistent context. The interface recommends adding only the repositories required for each session, and suggests attaching additional repos on a session-by-session basis when needed.

At its core, the feature is designed around shared memory and context that persist across sessions, with multiple people able to work inside the same session. The latest description also introduces multiple threads within a session.

A useful parallel is Slack: the project session effectively becomes a channel where several people and Claude are present, while threads allow separate sub-conversations around individual tasks. This fits Anthropic’s existing direction with Claude Tag on Slack, where Claude can use channel and thread context alongside connected codebases.

Anthropic has suggested this collaborative model could represent the future of software development. Instead of traditional pair programming, or a developer working alone with AI, multiple developers and Claude can work together on the same project. Anthropic has reportedly used this approach internally for some time, and managed projects could bring that workflow directly into Claude without requiring Slack.

Another important piece we discovered earlier is that Claude is expected to maintain these projects itself. It can periodically revisit context files and memories to reorganize and refine them, turning the project into a persistent workspace rather than static shared chat history.

Availability also appears to be expanding beyond friends-and-family or alpha testing, with early-access organizations potentially already having access. There is no confirmed public rollout date yet.

This may look like a relatively small addition at first, but it could become one of Anthropic’s larger workflow releases. The company is increasingly positioning Claude as infrastructure for shared organizational work, rather than only a one-to-one coding assistant, and collaborative projects appear to be a direct extension of that strategy.