Claude Code Projects adds shared sessions and threads

Anthropic is building collaborative Projects for Claude Code into Claude Desktop, where several people and Claude can work inside one session and split off separate threads for individual tasks. The feature and its latest interface changes were described by Testingcatalog.

At a glance

• Project creation now takes repositories directly as persistent context, with the interface advising that only the repositories a session actually needs be added and further repos attached session by session.
• Shared memory and context survive across sessions, and Claude is expected to maintain them itself, periodically revisiting context files and memories to reorganize and refine what the project stores.
• Access appears to be widening past friends-and-family and alpha testing, with early-access organizations potentially already using the feature, though no public rollout date has been confirmed.

The shape of the release reads as a bet that AI-assisted development stops being one developer talking to one assistant. If the project session becomes the unit of work, the shared artifact is no longer a chat log but a maintained workspace with repositories, memory and threads attached to it. That also reduces Anthropic's dependence on Slack as the surface where Claude picks up team context.

Project creation attaches repositories as context reused across every session

The project creation interface has gained an option to add repositories directly, and those repositories act as persistent context across every session in the project instead of being attached again each time a new session opens. The interface recommends keeping the list narrow and adding only the repositories a given session requires.

For work that reaches outside that set, the interface suggests attaching additional repositories on a session-by-session basis. The feature was previously spotted under the name Managed Projects, and the description has since been updated to mention that users will be able to spawn different threads within a single project session, according to Testingcatalog.

The project session behaves as a channel, with threads for individual tasks

At its core the feature is built around shared memory and context that persist between sessions, with several people able to work inside the same session at once. The latest description adds multiple threads within a session, so separate sub-conversations can form around individual tasks.

Testingcatalog draws the parallel to Slack, where the project session behaves as a channel populated by several people and Claude. That matches Anthropic's existing work on Claude Tag in Slack, where Claude reads channel and thread context alongside connected codebases.

Claude is also expected to maintain the project itself, revisiting context files and memories on a periodic basis to reorganize and refine what they hold. Testingcatalog describes the result as a persistent workspace rather than a static record of shared chat history.

Noah Zweben says unprompted messages from Claude Tag are down about 45%

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

Recent work on Claude Tag has centred on proactivity. Noah Zweben wrote that unprompted messages are down roughly 45%, that Claude Tag is more context-aware across a user's work and more attuned to when it should stay quiet, and that monitoring is not billed separately.

Testingcatalog frames the addition as potentially one of Anthropic's larger workflow releases despite its modest appearance, with the company increasingly positioning Claude as infrastructure for shared organizational work rather than only a one-to-one coding assistant, and collaborative projects reading as a direct extension of that strategy.

Who can reach it now

Availability appears to be moving beyond friends-and-family and alpha testing, and early-access organizations may already have access. No public rollout date has been confirmed, and no pricing or plan requirement has been named for collaborative projects. The description of threads and repository context has already changed at least once, so the shipped version may differ from what the interface currently shows.