# Shared chat pool across workspaces

**URL:** <https://forum.cursor.com/t/shared-chat-pool-across-workspaces/155618>\
**Category:** Feature Requests\
**Tags:** worktrees, chat\
**Created:** [March 23, 2026, 10:13am UTC](https://forum.cursor.com/t/shared-chat-pool-across-workspaces/155618 "2026-03-23T10:13:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tomer\_Roditi](https://avatars.discourse-cdn.com/v4/letter/t/5f8ce5/32.png) [@Tomer\_Roditi](https://forum.cursor.com/u/Tomer_Roditi)\
**Post date:** [March 23, 2026, 10:13am UTC](https://forum.cursor.com/t/shared-chat-pool-across-workspaces/155618/1 "2026-03-23T10:13:18Z")

</div>

### Feature request for product/service

Chat

### Describe the request

Problem: Chat history is isolated per workspace. When working with multiple worktrees of the same repositories — each opened as its own multi-root workspace — there’s no way to continue a conversation started in one workspace from another.

Use case: I use git worktrees to work on multiple branches in parallel. Each worktree is opened as a separate multi-root workspace in Cursor containing the same set of repos. Since the worktrees are different directories on disk, Cursor treats them as entirely separate workspaces with isolated chat histories — even though they’re the same codebase. A conversation I start while working on one branch can’t be continued or referenced when I switch to a different worktree/workspace.

Proposed solution: Allow users to configure a shared chat pool across specific workspaces, so chats started in one workspace appear in and can be continued from another. This could be:

A setting to link workspaces to a named chat pool  
Automatic detection that workspaces share the same git origin and offering to unify their chat history  
A way to “import” or “reference” chats from other workspaces  
A global chat history option (opt-in)  
Current workaround: None — switching worktrees means losing all conversation context.