@flumecode/runner 0.23.1 → 0.25.0-preview.39

package/README.md

@@ -17,22 +17,34 @@ FlumeCode service never stores an API key or runs your code itself.
 
 ## Install & run
 
-The runner ships as a global CLI on npm. The Runners page in the web app shows
-these exact commands with your token pre-filled:
+The runner ships as a global CLI on npm:
 
 ```bash
 npm install -g @flumecode/runner
 
-# Save the server URL + token (or run `flumecode login` for an interactive prompt)
-flumecode login --server https://<your-app> --token flrun_…
+# Authorize this machine in the browser (GitHub sign-in). One approval provisions
+# BOTH the runner token (for `start`) and the CLI token (for the `tui`).
+flumecode login --server https://<your-app>
 
 # Start polling for jobs (keep it running)
 flumecode start
 ```
 
-Config is written to `~/.flume/config.json` (mode 0600). The token lives only
-there and is sent only as the `Authorization` header to your server. The default
-server for a bare interactive `flumecode login` can be set via `FLUME_SERVER`.
+`flumecode login` opens `<server>/cli/authorize`, you sign in with GitHub and
+approve, and the tokens are handed back to a one-shot `127.0.0.1` listener the CLI
+runs (a loopback OAuth-style flow). Use `--cli-only` / `--runner-only` to provision
+just one. The default server is `http://localhost:3000`, overridable with
+`--server` or the `FLUME_SERVER` env var.
+
+For CI or a headless box, skip the browser and paste tokens minted in the web app
+(**Runners** page → runner token, **Settings → CLI tokens** → CLI token):
+
+```bash
+flumecode login --server https://<your-app> --runner-token flrun_… --cli-token flcli_…
+```
+
+Config is written to `~/.flume/config.json` (mode 0600). Tokens live only there and
+are sent only as the `Authorization` header to your server.
 
 ## Developing on the runner