moondesk 0.2.0 → 0.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -279,7 +279,9 @@ A workspace is one registered project root served by MoonDesk. One running MoonD
|
|
|
279
279
|
|
|
280
280
|
On first install/legacy migration, the initial workspace comes from `WORKSPACE_ROOT` when explicitly set, otherwise from the launch directory. After the workspace registry has been created, changing the launch directory or `WORKSPACE_ROOT` does not silently repoint existing workspace URLs. Use `[w] Workspaces` to add or manage projects.
|
|
281
281
|
|
|
282
|
-
|
|
282
|
+
A workspace connector URL is intentionally stable across MoonDesk restarts. MoonDesk persists both the ngrok static domain and each workspace's random secret path in `~/.moondesk/config.toml`, then reuses them on every later session. You should normally create the ChatGPT connector for a workspace once and keep using it. The URL changes only when you explicitly rotate that workspace's secret, change the configured ngrok domain, remove and re-add the workspace, or lose/delete the MoonDesk config file. Renaming a workspace, restarting MoonDesk/ngrok, launching MoonDesk from another directory, or upgrading MoonDesk does not rotate the URL. Legacy single-workspace installs keep their existing secret during migration.
|
|
283
|
+
|
|
284
|
+
Dedicated file tools use the selected endpoint's workspace as their base path and reject traversal, absolute paths outside that root, and symlink/junction escapes. `run_command` and `start_command` are intentionally different: they start the user's normal developer shell with the workspace as its working directory. The shell inherits the normal PATH, home directory, environment, developer configuration, credentials, and OS permissions so tools such as Git, package managers, SDKs, compilers, Docker, and development servers behave normally. CWD is **not an OS sandbox**: an absolute-path shell command can read or modify other paths allowed to the MoonDesk user. Use `read-only` mode when shell/write access should not be exposed, and use a VM/container when you need OS-level isolation.
|
|
283
285
|
|
|
284
286
|
### Where to put my AGENTS.md?
|
|
285
287
|
|