@runtypelabs/cli 2.28.1 → 2.30.0

package/README.md

@@ -133,6 +133,45 @@ long-running flows can complete; use `--timeout <ms>` to choose a different dead
 `RUNTYPE_API_KEY` before using `--input -` or `-F key=@-`; the CLI will not put an interactive login
 prompt on a stream that contains tool arguments.
 
+### Connect a Mac to Runtype Devices
+
+`runtype devices` is the control plane for local computers connected to Runtype agents. The CLI
+owns authentication, pairing, status, and lifecycle commands; a separate native helper owns
+Keychain identity, macOS permissions, Messages access, and the persistent outbound relay
+connection. The CLI does not need to remain running after setup.
+
+The current macOS helper is an internal-alpha source distribution. Build it from a core checkout,
+then let the public CLI copy it to a stable per-user location, pair it without putting the one-time
+secret in process arguments, and start its background service:
+
+```bash
+pnpm --filter @runtypelabs/device-daemon-macos build
+runtype devices setup \
+  --helper-path apps/device-daemon-macos/.build/debug/runtype-device \
+  --name "My Mac"
+
+runtype devices status
+runtype devices doctor
+runtype devices list
+runtype devices mcp-url <device-id>
+```
+
+Sending from the user's iMessage account remains locally disabled until explicitly enabled:
+
+```bash
+runtype devices policy allow-send
+runtype devices policy deny-send
+```
+
+Policy changes restart an installed device service so the relay receives the updated tool
+manifest. If the service is stopped, the CLI reports publication as pending until
+`runtype devices install` is run.
+
+Use `runtype devices logs --follow` for local daemon diagnostics and
+`runtype devices revoke <device-id> --yes` to invalidate a device in Runtype. External distribution still requires the
+planned signed and notarized `Runtype Device.app`; the source-built `--helper-path` workflow is not
+the production packaging story.
+
 ### 3. Work With Agents, Flows, and Records
 
 ```bash