**Feedback: recent restriction on multiple sessions using the same Local work...

[stepank]

Feedback: recent restriction on multiple sessions using the same Local workspace

Copilot Desktop currently prevents creating a new Local/branch session when another session is associated with the project root:

Session creation failed: invalid argument: This project already has an active Local workspace.

This appears to be a recent behavioral change. Around a month ago, I could use Copilot Desktop similarly to Copilot CLI: multiple parallel sessions could share the same repository folder and branch. Now I must archive the current session or create a worktree before starting another one.

This restriction disrupts legitimate workflows that do not require workspace isolation:

1. Many sessions are read-only and used only to ask questions, compare perspectives, or use different models. They do not modify files, so sharing the same folder is safe.
2. I use a “router” repository containing context about several related repositories. Sessions start from that folder but primarily inspect or modify other repositories, without changing the router repository.
3. Sometimes I want to preserve an old session for later reference while starting a fresh session in the same checkout. Reusing the old conversation is not equivalent, and archiving/restoring sessions adds unnecessary lifecycle management.
4. Copilot CLI already supports multiple sessions using the same working directory, leaving coordination of concurrent edits to the user.

Please consider restoring support for multiple sessions sharing one Local workspace, perhaps with a warning when concurrent editing is possible. Alternatives could include a read-only/context-only session mode or an explicit “share existing workspace” option. Worktrees should remain available for isolation, but they should not be mandatory for every parallel session.

---

Field	Value
App version	1.1.15
OS	Windows 10.0.26200
Theme	GitHub
Path	/chat
Tenure	Week 5

[lyczkop]

duplicate: #3530