Feature request: Projects as a first-class entity (per-session working directory inside one project)

[aobakaolengmian]

Motivation

Right now the workspace (cwd) is the only grouping key in the sidebar: one workspace → one flat list of sessions. That works when a project maps cleanly onto a single directory, but it breaks down as soon as one project spans several directories:

• A typical repo has frontend/, backend/, docs/, infra/.
• To work on the whole project you either register four separate workspaces (so one project's sessions are scattered across four lists, and the sidebar fills up), or pick one directory as "the" workspace (so the session's cwd is wrong for most of the work).

Claude Desktop / Claude Code solve this with Projects as a first-class entity: a project is a named container, and each conversation inside it carries its own working directory. The project is the unit of organization; the cwd is per-conversation metadata.

This is the one thing I keep missing after moving to dsh.

Behavior

Desired, minimal version:

1. Project = a named container, created/renamed/deleted by the user (a project has no directory of its own; it is metadata, like a label).
2. Sessions belong to a project, and while creating or inside a session the user can choose its working directory from the directories attached to that project (default: the project's primary folder).
3. The sidebar groups by project, with the per-session cwd visible as a subtitle/badge, instead of grouping by cwd.
4. No migration of existing data: existing sessions keep working exactly as today (they already carry cwd), a project is additive metadata; sessions outside any project fall back to today's workspace grouping.
5. Optional, not required for the first cut: attach several directories to one project; per-project default model / system prompt.

Why this seems cheap to add

cwd is already per-session in the data model — dsh stores session.cwd and it is already propagated to the agent. So this is mostly an identity/grouping addition (a project id + a name + a list of attached directories), not a data-model rewrite. The sidebar grouping is a client-side concern; the project record itself could live in the existing storage domain.

Workarounds people use today

• Naming several workspaces with a common prefix (e.g. MyProject/frontend) — clunky, and the name is the only grouping mechanism.
• Community plugins that emulate it in the view layer (dsh-session-folders, dsh-projects) — they add folders/groups on top of the sidebar, but a project is still not a real entity, so a session cannot really "belong to a project while using another directory".

---

中文摘要

侧边栏目前只用工作区(cwd) 分组：一个工作区 = 一列会话。当一个"项目"横跨多个目录（前端/后端/文档）时就很难受——要么把项目拆成四个工作区（会话被拆散、侧边栏变长），要么只选一个目录当工作区（会话的 cwd 对其余工作都是错的）。

希望能像 Claude Desktop 那样：Project 是一等实体（一个命名容器），项目内的每个对话可以各自选择工作目录（默认用项目的主目录），侧边栏按项目分组。数据层其实已经具备条件——session.cwd 本来就是每个会话各自的字段，所以这更多是"增加一层身份/分组"，而不是改数据模型。