Workspace URLs and opening EOS

Every EOS dashboard page includes its workspace ID in the URL:

https://enterprise-os.stacksync.ai/workspace/123
https://enterprise-os.stacksync.ai/workspace/123/databases?database=456
https://enterprise-os.stacksync.ai/workspace/123/inference
https://enterprise-os.stacksync.ai/workspace/123/storage

Copy the full URL to return to the same workspace and resource. The recipient must sign in and have access to that workspace and resource. Links do not grant access. Query parameters and tabs stay in the URL.

Opening a link without a workspace, with an invalid ID, or for an inaccessible workspace falls back to your current default workspace. If you need to sign in first, EOS preserves the destination through login. Each open tab keeps the workspace from its URL, even when you switch workspaces in another tab.

Open from the CLICopy Anchor Link

eos update
eos workspace current
eos open

eos open opens the selected CLI workspace in your browser and prints its URL. On a remote or headless machine, open the printed link on your own computer. If the selected workspace is still a guest workspace, the CLI asks you to sign in, claims it for that account, and then opens it.

When login claims a guest workspace, the authorization page waits for the claim and opens that workspace's Applications page. This works for new and existing accounts.

Workspace API requestsCopy Anchor Link

Use the workspace ID in the management API URL:

curl --fail-with-body \
  "https://enterprise-os.stacksync.ai/workspace/$WORKSPACE_ID/api/projects" \
  -H "Authorization: Bearer $EOS_TOKEN"

The CLI sends workspace-scoped resource requests in this format. Existing /api/... endpoints remain supported with X-Workspace-Id. If both the URL and header specify a workspace, they must match. Invalid or inaccessible API scope returns an error; API writes never silently fall back to another workspace.

Authentication and runtime authentication endpoints remain global. AI inference /api/inference/v1 and File Storage /api/storage/v1 data endpoints remain global because their API keys already determine resource access. Workspace management URLs do not change deployed application URLs or database connection strings. The OpenAPI specification lists the scoped management endpoints and compatibility routes.

Guest workspace namesCopy Anchor Link

Before claiming, the workspace is called Guest workspace. Claiming assigns a welcoming name using the account's email or display name. A company address such as person@company.com becomes Company's workspace. Personal email addresses use a first-name clue when available; for example, rubenburdin@gmail.com becomes Ruben's workspace. If no useful clue is available, EOS uses Claimed Guest workspace.

Names are best-effort suggestions and can be changed in Workspace settings. Naming does not change workspace IDs, permissions, or URLs. Unclaimed guest resources still expire 14 days after creation.