@aloud/runner 0.2.5 → 0.3.1

package/README.md

@@ -9,7 +9,7 @@ outbound only: nothing listens on a port, and the server holds no address for th
 ```sh
 npm install -g @aloud/runner
 
-aloud login          # paste the token from usealoud.com/app/settings/runners
+aloud login          # approve this machine in your browser
 aloud start          # waits for studies and runs them here
 ```
 
@@ -19,12 +19,25 @@ The first `aloud start` downloads Chromium, about 350 MB, once.
 
 | Command | What it does |
 | --- | --- |
+| `aloud setup` | Inspect this machine and complete whatever setup remains |
 | `aloud login [--token <token>]` | Connect this machine to your workspace |
-| `aloud start [--once] [--quiet]` | Wait for studies and run them here |
+| `aloud start [--once] [--quiet] [--no-update]` | Update, then wait for studies and run them here |
 | `aloud status` | What is set up, what is not, and whether it is running |
 | `aloud allow <host>` | Let studies open this host from this machine |
 | `aloud mcp` | Connect an MCP host to the web workspace selected by its MCP access token |
 | `aloud logout` | Forget the token on this machine |
+| `aloud --version` | Print the installed runner version |
+
+## Updates
+
+Starting with 0.3.1, `aloud start` asks the connected Aloud server which official runner release
+it recommends. If a newer one is available, it installs that exact `@aloud/runner` version and
+relaunches it before claiming work. It never replaces code during an active study.
+
+If an optional update cannot be installed, the terminal says why and a still-compatible runner may
+continue. If the server requires the update, nothing starts and the command exits non-zero with the
+manual repair command. `--no-update` is available for managed environments, but it cannot make an
+incompatible runner claim work.
 
 ## MCP access