.local/control-plane. Keep an explicit HEXAGON_DATA_DIR consistent. Select a workspace with Python Hexagon.local(data_directory=...) or TypeScript Hexagon.local({dataDirectory: ...}) when needed.
Do not copy owner Tokens to frontend code. Console and SDKs have separate local discovery mechanisms. A new browser credential after restart does not imply lost database history.
Keep workspace selection consistent
A different data directory alone is not a complete isolated deployment. For two concurrent workspaces, use separate PostgreSQL targets, private data directories, API ports, preview ports and credential-listener ports; give each its own ingress routing. The launcher probes127.0.0.1 using PORT and the selected directory’s owner file. Running status/stop with a different port or directory can inspect the wrong service or fail authentication. Carry the same environment into every lifecycle command.
Do not run two launchers against one data directory, copy another workspace’s owner file to bypass authentication, or delete a directory to resolve an unknown cloud operation. Multiple workspaces are explicit deployments, not a built-in multi-workspace switcher or a high-availability topology.