@wix/himalaya-cli 0.1114.0 → 0.1115.0

package/guides/himi-mcp.md

@@ -80,6 +80,14 @@ runs a session with it.
 
 Each tool acts on the agent's workspace folder unless it is given a `dir`.
 
+**File tools, for hosts that cannot edit files.** `himi mcp --with-files` adds `himi_list_apps`,
+`himi_list_files`, `himi_read_file`, `himi_write_files` and `himi_delete_files`. The Claude Desktop
+Extension uses them, because Claude Desktop chat has no file editing of its own. They follow the
+hosted connector's shapes, act only inside the workspace folder (checked on the real path, so a
+symlink cannot lead out of it), and never touch `.git`, `node_modules` or `dist`. When the host names
+no workspace, `HIMI_WORKSPACE` sets the folder. Coding agents edit files themselves, so the flag is
+off by default.
+
 **What the tools will not do:** make a release live, build store binaries, touch secrets, write to a
 site's CMS, or create a Wix site. Those spend money, handle credentials, or change what real users
 see, so they stay commands a person runs. Publishing needs a sign-in first: `himi_login` opens the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1114.0",
+  "version": "0.1115.0",
   "type": "module",
   "description": "himi — the Himalaya authoring CLI. Build a Tier-5 content package on your own machine, push it to the production serve as a draft, preview it on web + Himi Player, and read worker logs back — the remote dev loop. Wraps @himalaya/serve-cli for transport.",
   "keywords": [
@@ -67,5 +67,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "0577b42d47b1e8019d8e91a63ef760878990ad8500fc4c7deec84f83"
+  "falconPackageHash": "19c38309340f59147c2cb6f97746d920feacc058a4c256331d9f4422"
 }