Question: Support multiple concurrent sessions under the same root directory

[grokking88]

Hi DevSpace maintainers,

I would like to ask whether DevSpace currently supports running multiple independent coding sessions concurrently under the same configured root directory.

My use case:

• I have a large repository configured as an allowed root.
• I open multiple ChatGPT coding sessions at the same time.
• Each session is working on a different task (usually different branches/worktrees).
• I expect each session to keep its own workspace state, context, and tool execution state isolated.

However, from my experience, when multiple sessions share the same root, the sessions sometimes appear to become mixed up:

• A session may seem to operate on a workspace created by another session.
• Workspace/session context appears inconsistent.
• Tool calls may reference unexpected workspace state.
• It becomes difficult to guarantee that one conversation is isolated from another.

I would like to understand:

1. Is running multiple concurrent sessions under the same root directory officially supported?

2. If yes:

   • What is the recommended workflow?
   • Should each session always use a separate DevSpace workspace/worktree?
   • Are workspace IDs expected to provide complete isolation?

3. If no:

   • Is this a known limitation?
   • Are there plans to support multiple concurrent sessions sharing the same root?

My expectation would be that:

• Each ChatGPT conversation should have an independent session context.
• Each opened workspace should have isolated state.
• Multiple conversations should not interfere with each other even if they originate from the same allowed root.

Thanks for the great work on DevSpace. This workflow is very promising, but reliable multi-session isolation is important for using it as a daily coding agent.