@jmfederico/pi-web 1.202606.7 → 1.202607.1

package/README.md

@@ -34,9 +34,9 @@ Your browser is the control surface. The work stays where it can keep running.
 
 Requirements:
 
-- Node.js 22 or newer
+- Node.js 22.19.0 or newer
 - npm
-- Pi Coding Agent configured for your user
+- Pi Coding Agent `>=0.80.8 <0.81`, configured for your user
 - git and the development tools your agents need
 
 Install and start PI WEB as per-user services:
@@ -64,6 +64,9 @@ pi-web version
 pi-web uninstall
 ```
 
+<!-- Keep README guidance concise. Put install variants, troubleshooting,
+configuration, and operational details in docs/, then link from here. -->
+
 For more install options, including one-line install, Pi package install, WSL/manual usage, and remote access, see the [installation guide](https://pi-web.dev/install).
 
 ## Core model
@@ -97,13 +100,19 @@ Read more: [Remote-first development](https://pi-web.dev/remote-first)
 
 ## Machines and fleets
 
-PI WEB can register other PI WEB runtimes as remote machines. One browser-facing PI WEB instance can proxy projects, files, git state, sessions, terminals, and activity from trusted remote machines.
+PI WEB can register other PI WEB runtimes as remote machines. One browser-facing PI WEB instance can proxy projects, files, git state, sessions, terminals, activity, Pi package management, and selected-machine settings from trusted remote machines.
+
+When a remote machine is selected, Settings tabs label their target. Pi packages, PI WEB plugin enablement, session daemon toggles, external file access, and upload defaults target the selected machine. Gateway/server settings such as host, port, allowed hosts, registered machines/tokens, and keyboard shortcuts stay local to the gateway/browser.
 
 Read more: [Fleet and machines guide](https://pi-web.dev/machines)
 
 ## Plugins
 
-PI WEB supports trusted local browser-side plugins that can add actions, workspace panels, and workspace metadata.
+PI WEB supports trusted browser-side PI WEB plugins that can add actions, workspace panels, and workspace metadata.
+
+Pi packages are managed separately through Pi's package manager or **Settings → Pi packages**. In a federated setup, the Pi packages panel targets the selected machine and labels where installs, updates, or removals will run. Use **Settings → PI WEB plugins** to enable or disable discovered browser plugins on the selected machine.
+
+After installing, updating, or removing a Pi package, type `/reload` in each idle PI WEB session on that machine to refresh Pi runtime resources such as extensions, skills, prompt templates, themes, and context/system prompt files. Reload the browser page separately for newly discovered or changed PI WEB plugins.
 
 Read more: [Plugin API](https://pi-web.dev/plugins)
 
@@ -122,7 +131,7 @@ Project-local PI WEB config lives at:
 <project>/.pi-web/config.json
 ```
 
-Common configuration includes host/port, path access, uploads, plugins, shortcuts, and session daemon options.
+Common configuration includes host/port, path access, uploads, PI WEB plugin enablement, shortcuts, and session daemon options. In Settings, machine-affecting config targets the selected machine; gateway host/port/allowed-hosts, remote machine registration, tokens, and keyboard shortcuts stay local.
 
 Read more: [Configuration reference](https://pi-web.dev/config)