[Feature Request] Support for Multiple Workspaces (Work/Personal Isolation) #220

New issue

Closed

opened 2026-06-01 03:58:04 +02:00 by sanashii · 1 comment

sanashii commented

2026-06-01 03:58:04 +02:00

(Migrated from github.com)

[Feature Request] Support for Multiple Workspaces (Work/Personal Isolation)

🚀 Problem Statement
I've been using Odysseus for both my professional work and personal projects, and I've noticed a significant pain point: the lack of separation between these two contexts.

Currently, users manage a single set of API keys and a unified chat history. For those using AI for work, it is risky and disorganized to mix company-funded API keys with personal ones. Additionally, the mental load of switching between professional and personal contexts is higher when the UI and history are blended.

💡 Proposed Solution
I suggest implementing a Workspace feature that allows users to create and switch between distinct environments. Each workspace would ideally include:

Isolated API Configuration: The ability to assign different API keys (OpenAI, Anthropic, etc.) to different workspaces.
Separate Chat Histories: Conversations are scoped to the active workspace, keeping professional and personal logs separate.
Workspace-Specific Settings: Different default models or system prompts tailored to the specific needs of that workspace.

🎯 Value Proposition
This feature would transform Odysseus from a single-user interface into a professional-grade AI hub. It would be highly attractive to developers and power users who require a "clean" separation of concerns for security, billing, and organization.

Would this be something you're open to adding to the roadmap?

[Feature Request] Support for Multiple Workspaces (Work/Personal Isolation) 🚀 Problem Statement I've been using Odysseus for both my professional work and personal projects, and I've noticed a significant pain point: the lack of separation between these two contexts. Currently, users manage a single set of API keys and a unified chat history. For those using AI for work, it is risky and disorganized to mix company-funded API keys with personal ones. Additionally, the mental load of switching between professional and personal contexts is higher when the UI and history are blended. 💡 Proposed Solution I suggest implementing a **Workspace** feature that allows users to create and switch between distinct environments. Each workspace would ideally include: - **Isolated API Configuration:** The ability to assign different API keys (OpenAI, Anthropic, etc.) to different workspaces. - **Separate Chat Histories:** Conversations are scoped to the active workspace, keeping professional and personal logs separate. - **Workspace-Specific Settings:** Different default models or system prompts tailored to the specific needs of that workspace. 🎯 Value Proposition This feature would transform Odysseus from a single-user interface into a professional-grade AI hub. It would be highly attractive to developers and power users who require a "clean" separation of concerns for security, billing, and organization. Would this be something you're open to adding to the roadmap?

👀 6

jdelucca commented

2026-06-01 15:47:00 +02:00

(Migrated from github.com)

I haven't installed/run/looked at the code yet, but I am curious on if you just git clone it twice, will it work in this way? Obviously less good than being able to hit a "swap accounts" button inside of it, but I wonder if it's good enough. I also wonder if people might want separate venv's per account, which would be a lot easier if you shut down and swap to a different local repo.