Skip to content

[Feature] 允许用户为工作区(workspace / 项目)设置自定义显示名称 #822

Description

@nightwares

类型: 功能建议 · Feature Request

使用场景 · Context

用 ZCode 同时连接多个远程环境(多个 devcontainer、多台 SSH 主机)时,工作区列表和标题只能显示路径叶子名。两个常见痛点:

  1. 工作区路径是容器根目录 / 时,标题直接退化为 /(bug report 见 #821,附修复补丁);路径叶子相同(如多个仓库都叫 atelier)时也无法区分。
  2. 长路径 / 容器名 / IP:端口这类自动派生的名字,不携带"这个工作区是干什么的"信息,切换时总要靠记忆或悬停看完整路径。

Working across several remote environments, workspace titles are auto-derived from the path leaf only. Root-path workspaces degrade to /, duplicate leaf names are indistinguishable, and derived names carry no information about what the workspace is for.

建议方案 · Proposal

允许用户为工作区设置自定义显示名称(rename),用于所有标题面(Header、工作区切换菜单、任务列表归属标签、窗口标题):

  • 入口:Header 工作区标题的上下文菜单加一个「重命名」(与现有任务重命名同级)
  • 存储:以 workspaceIdentity(已有统一身份键,远程/本地都稳定)为键持久化覆盖名;workspacePath 变化但 identity 不变时名称保持
  • 回落:未命名时保持现有自动派生(路径叶子 / 主机标识)

Add a per-workspace custom display name, persisted against the existing workspaceIdentity key (stable across path changes, uniform for local/remote), falling back to the current auto-derived name when unset.

预期价值 · Value

  • 多环境工作流(devcontainer / SSH 农场)里一眼分辨工作区,减少误切换
  • 与现有 workspaceIdentity 身份隔离体系自然衔接,不引入新的身份口径
  • 顺带根治根目录 / 标题这类"自动派生名字不可用"的边缘场景的长期方案

Instantly distinguishable workspaces for multi-environment workflows, consistent with the existing identity-isolation design, and the durable fix for cases where the auto-derived name is unusable (root paths, duplicate leaf names).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions