Problem
When a host authorizes exactly one project root, models still have to guess or ask for its absolute path before calling open_workspace. This produces avoidable failures in desktop and other embedded integrations.
Proposed direction
Allow the server or workspace registry to resolve an omitted path to a host-defined default authorized root. The behavior should remain generic, avoid product-specific wording, reject an explicitly invalid path instead of silently replacing it, and return a clear choice list when no unique default exists.
This likely needs an issue-level API decision before implementation because it changes workspace-selection semantics.
Problem
When a host authorizes exactly one project root, models still have to guess or ask for its absolute path before calling
open_workspace. This produces avoidable failures in desktop and other embedded integrations.Proposed direction
Allow the server or workspace registry to resolve an omitted path to a host-defined default authorized root. The behavior should remain generic, avoid product-specific wording, reject an explicitly invalid path instead of silently replacing it, and return a clear choice list when no unique default exists.
This likely needs an issue-level API decision before implementation because it changes workspace-selection semantics.