bug: Workspace path binding conflict prevents multiple designs from sharing workspace

[Sun-sunshine06]

Description

When creating or opening multiple designs that reference the same workspace path, the app throws "Workspace path is already bound to another design" error. This prevents users from working on multiple designs that share a workspace directory.

Reproduction

1. Create a design and bind it to a workspace folder
2. Create a second design or try to rebind the same workspace path
3. The error fires and the operation is blocked

Log Evidence

From main.log (2026-05-04), 5 occurrences:

[2026-05-04 ...] error: bindWorkspace failed { error: 'Workspace path is already bound to another design' }

Environment

• Version: v0.2 (experimental)
• Platform: Windows 11

Impact

Users cannot have multiple designs share the same filesystem workspace, which is a common workflow when iterating on related design files.

Notes

This may be intentional behavior to prevent conflicts, but the UX does not make this clear — the error should either be surfaced as a user-facing message with guidance, or the binding logic should allow shared workspaces with proper conflict resolution.

[github-actions]

Thank you for reporting this, @Sun-sunshine06. The "Workspace path is already bound to another design" error is enforced by the current binding logic in packages/core/src/workspace.ts (or similar IPC handler, e.g., apps/desktop/src/main/workspace-ipc.ts), which stores a one-to-one mapping between designs and their workspace folder paths. This is intentional to avoid file conflicts when the agent reads/writes files, but the UX should indeed handle this more gracefully.

Relevant code:

• apps/desktop/src/main/workspace-ipc.ts — handles bindWorkspace IPC calls and checks for existing bindings
• packages/core/src/workspace.ts — likely contains the workspace binding map and the conflict check

Notes:

• Shared workspaces across multiple designs is a valid workflow, especially for related prototypes or design iterations.
• The error is currently logged only to main.log – it should be surfaced to the UI as a user-facing message with clear guidance (e.g., "This folder is already bound to design X. Do you want to rebind? Existing files will be migrated.")
• The v0.2 plan (see AGENTS.md and CLAUDE.md) introduces workspace-backed design sessions, so improving this UX aligns with that direction.

Next steps:

• Would you like to see shared workspaces with conflict detection, or is a clearer rebind dialog sufficient for now?
• Could you share the specific design workflow you're trying to achieve (e.g., viewing two versions of the same prototype)?

We'll update the issue with the relevant code path and consider this for the v0.2 UX improvements.

---

Open-CoDesign Bot

[Sun-sunshine06]

澄清：经进一步分析，工作区路径排他绑定本身是预期行为（防止多设计对同一目录产生写冲突），不是 bug。

真正需要改进的是错误提示的用户体验 — 当前只抛出一条 raw error Workspace path is already bound to another design，没有向用户说明：

1. 为什么会触发这个限制
2. 如何解除已有绑定（或切换到其他工作区）
3. 是否可以将多个设计指向同一工作区（如果设计了冲突解决机制）

建议将此 issue 转为 enhancement：在绑定冲突时给出明确的 UI 提示和操作引导，而不是静默报错。

[Sun-sunshine06]

已在 #295 中修复并合并到 main。

修复内容：

• 保留“同一 workspace 不能同时绑定多个 design”的保护逻辑。
• 冲突发生时，错误信息现在会包含已占用该 workspace 的 design 名称。
• 错误信息也会提示用户下一步：选择其他文件夹，或先打开占用该文件夹的 design 并修改它的 workspace。
• 补充/更新了 workspace 绑定冲突测试和 changeset。

验证：本地已跑 targeted Biome、design-workspace Vitest、desktop typecheck、desktop 全量测试、根 typecheck；PR 上 CI、CodeQL、Dependency Review、Codex PR Review 全绿，bot review 确认无问题。该 issue 已由 Fixes #286 自动关闭。