@rynx-ai/cli 0.1.10 → 0.1.11-beta.10

package/dist/usage.js

@@ -1,10 +1,14 @@
 export const USAGE = `Usage: rynx <command>
 
 General:
-  version | --version  print the installed Rynx version
+  version [--json] | --version
+                     print the installed Rynx version
 
 Setup:
-  setup              interactive configuration wizard
+  setup [--non-interactive] [--default-runtime <codex|traex|claude>]
+        [--host <host>] [--port <port>] [--log-level <level>]
+        [--install-browser|--skip-browser] [--json]
+                     initialize configuration and local dependencies
   doctor             read-only health check
 
 Lifecycle:
@@ -12,11 +16,15 @@ Lifecycle:
   update [version] [--check] [--json]
 
 Plugins:
-  plugin manage list
-  plugin manage install <source> [--force] [--grant-all] [--expect-digest <sha256-...>] [...]
-  plugin manage update <id> [--grant-all] [--expect-digest <sha256-...>] [...]
-  plugin manage enable|disable|uninstall <id>
-  plugin <id> <command>       invoke a plugin command through daemon RPC
+  market list
+  market add <git-or-local-source> [--alias <id>]
+  market refresh [market-id]
+  market remove <market-id>
+  plugin list
+  plugin install <source|plugin@market> [--force] [--expect-digest <sha256-...>]
+  plugin update <plugin@market> [--expect-digest <sha256-...>]
+  plugin enable|disable|uninstall <plugin@market>
+  plugin <plugin@market> <command>  invoke a plugin-owned command
 
 Agents:
   agent list
@@ -26,7 +34,7 @@ Agents:
 
 Builtin Skills:
   skills list [--json]
-  skills get <name> [--json]
+  skills get <browser|emulator> [--full] [--json]
 
 Maintenance:
   cleanup sessions [--dry-run]
@@ -43,14 +51,17 @@ Remote Runtime:
   runtime clients list [--json]
   runtime clients revoke <grant-id>
 
+Sessions:
+  session fork <session-id> [--title <title>] [--json]
+
 Browser:
   browser install|update|version|clean [...]
-  browser open [url] --session <id> [--runtime <local|daemon-id>] [--json]
-  browser status|pages|close --session <id> [--runtime <local|daemon-id>] [--json]
-  browser endpoint [--ensure] --session <local-id> [--json]
-  browser snapshot --session <local-id> [--json]
-  browser navigate <url> --session <local-id> [--json]
-  browser click (--ref <ref>|--selector <css>|--x <n> --y <n>) --session <local-id> [--json]
-  browser type (--ref <ref>|--selector <css>) --text <text> --session <local-id> [--json]
-  browser screenshot --output <absolute-path> --session <local-id> [--json]
+  browser open [url] [--session <id>] [--runtime <local|daemon-id>] [--json]
+  browser status|pages|close [--session <id>] [--runtime <local|daemon-id>] [--json]
+  browser endpoint [--ensure] [--session <local-id>] [--json]
+  browser snapshot [--session <local-id>] [--json]
+  browser navigate <url> [--session <local-id>] [--json]
+  browser click (--ref <ref>|--selector <css>|--x <n> --y <n>) [--session <local-id>] [--json]
+  browser type (--ref <ref>|--selector <css>) --text <text> [--session <local-id>] [--json]
+  browser screenshot --output <absolute-path> [--session <local-id>] [--json]
 `;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rynx-ai/cli",
-  "version": "0.1.10",
+  "version": "0.1.11-beta.10",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/rynx-ai/rynx.git",
@@ -9,13 +9,17 @@
   "description": "Rynx command-line client and local control-plane management surface.",
   "license": "MIT",
   "type": "module",
+  "engines": {
+    "node": ">=22"
+  },
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
     "access": "public"
   },
   "files": [
     "dist",
-    "skills"
+    "skills",
+    "skill-guides"
   ],
   "bin": {
     "rynx": "./dist/cli.js"
@@ -34,14 +38,24 @@
     "./commands": {
       "types": "./dist/commands/index.d.ts",
       "default": "./dist/commands/index.js"
+    },
+    "./standalone": {
+      "types": "./dist/standalone.d.ts",
+      "default": "./dist/standalone.js"
+    },
+    "./app-runtime": {
+      "types": "./dist/app-runtime.d.ts",
+      "default": "./dist/app-runtime.js"
     }
   },
   "dependencies": {
+    "@clack/prompts": "^1.6.0",
     "ws": "^8.21.0",
-    "@rynx-ai/core": "0.1.10",
-    "@rynx-ai/emulator": "0.1.10",
-    "@rynx-ai/protocol": "0.1.10",
-    "@rynx-ai/browser-cdp": "0.1.10"
+    "@rynx-ai/browser-cdp": "0.1.11-beta.10",
+    "@rynx-ai/core": "0.1.11-beta.10",
+    "@rynx-ai/daemon": "0.1.11-beta.10",
+    "@rynx-ai/emulator": "0.1.11-beta.10",
+    "@rynx-ai/protocol": "0.1.11-beta.10"
   },
   "devDependencies": {
     "@types/ws": "^8.18.1"

package/skill-guides/browser.md

@@ -0,0 +1,72 @@
+---
+name: browser
+description: Use the bundled Rynx CLI to inspect and automate the Browser owned by the active Rynx Session with snapshots, accessibility refs, navigation, clicks, typing, screenshots, page inspection, and safe failure handling.
+---
+
+# Rynx Browser
+
+Use the bundled `rynx` executable supplied by the active Rynx Session. Choose
+that executable once and reuse it. Do not locate another installation with
+`which`, `npx`, npm, filesystem searches, App-name guesses, or alternate paths.
+
+The active Session already owns the resident daemon, Browser host, and Session
+binding. Omit `--session`; the managed Session credential scopes every command
+to the current Session. Prefer `--json`.
+
+## Sandbox boundary
+
+If a `rynx browser ...` command cannot connect to its local endpoint, do not
+interpret that as a stopped daemon. Stop and ask the user to approve rerunning
+the exact same command outside the Agent sandbox.
+
+Do not change the command or try another executable, endpoint, port, transport,
+installation, App, browser, or service. Do not scan `/Applications`, use `find`
+or `mdfind`, run `open`, `open -a`, or `osascript`, inspect Preview/dev builds,
+or launch/relaunch a Rynx App or daemon.
+
+## Core loop
+
+Open or navigate the Session Browser when needed:
+
+```sh
+rynx browser open https://example.com --json
+rynx browser navigate https://example.com/next --json
+```
+
+Inspect before acting:
+
+```sh
+rynx browser snapshot --json
+```
+
+Use a returned accessibility `ref` for the next action:
+
+```sh
+rynx browser click --ref <ref> --json
+rynx browser type --ref <ref> --text "hello" --json
+```
+
+Take a fresh snapshot after navigation or substantial DOM replacement because
+old refs become stale. Use `--selector` only when no useful accessibility ref
+exists. Use coordinate clicks only as a final fallback after a screenshot.
+
+Inspect pages and save visual evidence with:
+
+```sh
+rynx browser status --json
+rynx browser pages --json
+rynx browser screenshot --output /absolute/path/page.png --json
+```
+
+Do not request or connect to the raw CDP endpoint unless diagnosing Rynx itself.
+Do not close a Browser generation the user still needs.
+
+## Failure handling
+
+- On endpoint access failure, follow **Sandbox boundary** and make no fallback
+  attempt.
+- On `stale reference`, take a new snapshot and retry once.
+- On `busy`, preserve the current Turn or Terminal for the user to resolve.
+- On an unavailable capability, report the missing App integration or macOS
+  permission; do not install an unpinned replacement.
+- Preserve structured error codes and relevant stderr when reporting failure.

package/skill-guides/emulator.md

@@ -0,0 +1,79 @@
+---
+name: emulator
+description: Use the bundled Rynx CLI to inspect and control the iOS Simulator, Android emulator, or adb-visible Android device bound to the active Rynx Session, including device discovery, attach, taps, typing, buttons, screenshots, rotation, launch, and gestures.
+---
+
+# Rynx Emulator
+
+Use the bundled `rynx` executable supplied by the active Rynx Session and run
+Emulator operations through `rynx emulator ...`. Choose that executable once
+and reuse it. Do not locate another CLI or call `serve-sim`, `simctl`, or `adb`
+directly.
+
+The active Session already owns the resident daemon and Session binding. Use the
+Session's bound device by default. Add `--runtime <local|daemon-id>` only when
+the user explicitly selected another paired Runtime. Prefer `--json`.
+
+## Sandbox boundary
+
+If a `rynx emulator ...` command cannot connect to its local endpoint, do not
+interpret that as a stopped daemon. Stop and ask the user to approve rerunning
+the exact same command outside the Agent sandbox.
+
+Do not change the command or try another executable, endpoint, port, transport,
+installation, App, or service. Do not scan `/Applications`, use `find` or
+`mdfind`, run `open`, `open -a`, or `osascript`, inspect Preview/dev builds, or
+launch/relaunch a Rynx App or daemon.
+
+## Inspect and select
+
+Inspect current state before acting:
+
+```sh
+rynx emulator devices --json
+rynx emulator active --json
+```
+
+Attach only when no suitable device is already bound or the user asks to switch:
+
+```sh
+rynx emulator attach <device-id-or-exact-name> --json
+```
+
+Never reuse a device id, serial, or name remembered from another Session. After
+switching or reconnecting, read `active --json` again.
+
+## Control loop
+
+```sh
+rynx emulator tap <x> <y> --json
+rynx emulator type "hello" --json
+rynx emulator type --mode keys "hello" --json
+rynx emulator button home --json
+rynx emulator button backspace --json
+rynx emulator button appswitch --json
+rynx emulator screenshot --json
+rynx emulator rotate portrait --json
+rynx emulator launch <bundle-id-or-package> --json
+rynx emulator gesture '<json-points>' --json
+```
+
+Coordinates are normalized `0..1` with top-left origin. Re-inspect with a
+screenshot after every meaningful UI-changing action.
+
+For `launch`, use an exact iOS `CFBundleIdentifier` or Android package name.
+Never pass a display name or guess an identifier. If only a visible app name is
+known, navigate visually and confirm with screenshots.
+
+Do not run `exec`, `kill`, or `shutdown` as routine cleanup. Raw host commands
+and device/process lifecycle changes require an explicit user request.
+
+## Failure handling
+
+- On endpoint access failure, follow **Sandbox boundary** and make no fallback
+  attempt.
+- On a missing/stale device, refresh `devices --json` and `active --json`.
+- On `busy`, preserve the current Turn or Terminal for the user to resolve.
+- On an unavailable capability, report the missing integration or macOS
+  permission; do not install an unpinned replacement.
+- Preserve structured error codes and relevant stderr when reporting failure.

package/skills/rynx-cli/SKILL.md

@@ -1,99 +1,31 @@
 ---
 name: rynx-cli
-description: Operate Rynx-managed local and remote runtimes through the bundled `rynx` CLI, including Browser inspection and automation, Emulator control, runtime pairing, and plugin commands. Use when a task needs to inspect or act on a Rynx Session Browser or Emulator, manage a Rynx runtime target, or invoke a Rynx plugin. Prefer this bundled CLI over direct CDP calls, guessed ports, globally installed browser drivers, or ad-hoc device tools.
+description: Use the bundled `rynx` CLI when a task needs to inspect or automate the Browser or Emulator owned by the active Rynx Session. Load the version-matched Browser or Emulator guide from the CLI before operating it. Prefer this over direct CDP, browser drivers, `serve-sim`, `simctl`, adb, guessed ports, or guessed App installations.
 ---
 
 # Rynx CLI
 
-Use the bundled `rynx` command. Rynx supplies the correct executable and current
-Session context; do not locate another installation with `which`, `npx`, or npm.
+This file is a discovery stub, not the usage guide. Rynx injects it into an
+active Session only so the Agent can discover the capability without carrying a
+stale copy of the CLI command surface.
 
-## Choose the target
+Use the bundled `rynx` executable supplied by the Session. Do not locate or try
+another installation with `which`, `npx`, npm, filesystem searches, App-name
+guesses, or alternate executable paths.
 
-- Inside a Rynx Session, omit `--session`; the injected Session credential
-  restricts commands to that Session.
-- Outside a managed Session, pass `--session <id>`.
-- Add `--runtime <local|daemon-id>` only when the user explicitly selected a
-  different paired Runtime.
-- Prefer `--json` for inspection and automation output.
+Before running an operational command, load only the matching version-matched
+guide from that exact CLI:
 
-If the CLI reports that the daemon is unavailable, ask the user to open Rynx or
-enable its resident daemon. Never start an unrelated service or guess a port.
-
-## Browser workflow
-
-Open the Session Browser when needed:
-
-```sh
-rynx browser open https://example.com --json
-```
-
-Inspect before acting:
-
-```sh
-rynx browser snapshot --json
-```
-
-Use a returned `ref` for the next action. Take a fresh snapshot after navigation
-or substantial DOM replacement because old references become stale.
-
-```sh
-rynx browser click --ref <ref> --json
-rynx browser type --ref <ref> --text "hello" --json
-rynx browser navigate https://example.com/next --json
-rynx browser screenshot --output /absolute/path/page.png --json
+```text
+rynx skills get browser
+rynx skills get emulator
 ```
 
-Use `--selector` only when no useful accessibility reference exists. Use
-coordinate clicks only as a final fallback after a screenshot.
-
-Useful inspection commands:
-
-```sh
-rynx browser status --json
-rynx browser pages --json
-```
-
-Do not request or connect to the raw CDP endpoint unless diagnosing Rynx itself.
-Do not close a Browser generation that the user still needs.
-
-## Emulator workflow
-
-Inspect available commands and devices before acting:
-
-```sh
-rynx emulator --help
-rynx emulator devices
-rynx emulator active
-```
-
-Use the Session's bound device by default. Select another device or Runtime only
-when the user asks. Re-inspect the screen after every navigation or state-changing
-input, and never call `kill` or `shutdown` as cleanup unless requested.
-
-## Runtime and plugin operations
-
-List and test Runtime targets before selecting a remote target:
-
-```sh
-rynx runtime list --json
-rynx runtime test <local|daemon-id> --json
-```
-
-Invoke plugin-declared commands through:
-
-```sh
-rynx plugin <plugin-id> <command> --json
-```
-
-Treat pairing, client revocation, plugin installation, Browser engine updates,
-and daemon lifecycle changes as administrative operations. Perform them only
-when the user explicitly requests them.
-
-## Failure handling
+Use `browser` for Browser inspection/automation and `emulator` for mobile device
+inspection/control. Do not load an unrelated guide. These commands read guides
+shipped in the exact CLI npm package and do not contact the daemon or network.
 
-- On `stale reference`, take a new Browser snapshot and retry once.
-- On `busy`, preserve the current Turn or Terminal and let the user resolve it.
-- On an unavailable capability, report the missing App integration or macOS
-  permission; do not install an unpinned replacement.
-- Preserve structured error codes and relevant stderr when reporting failure.
+If `rynx skills get <topic>` itself cannot execute, report its exact error and
+stop. Do not scan `/Applications`, use `find` or `mdfind`, run `open`, `open -a`,
+or `osascript`, inspect Preview/dev builds, start a daemon, guess a port, or try
+a different Rynx App or CLI.

package/dist/legacy-adapter.d.ts

@@ -1,7 +0,0 @@
-/**
- * Temporary bridge for commands whose daemon-owned mutation has no management
- * RPC yet. It crosses the package boundary as a subprocess, never by importing
- * daemon implementation modules into the CLI process.
- */
-export declare function runLegacyDaemonCli(args: readonly string[]): Promise<number>;
-export declare function resolveLegacyDaemonCli(env?: NodeJS.ProcessEnv, moduleUrl?: string): string | null;

package/dist/legacy-adapter.js

@@ -1,63 +0,0 @@
-import { spawn } from "node:child_process";
-import { existsSync, realpathSync, statSync } from "node:fs";
-import { fileURLToPath } from "node:url";
-import path from "node:path";
-const LEGACY_CLI_ENV = "RYNX_LEGACY_CLI_PATH";
-/**
- * Temporary bridge for commands whose daemon-owned mutation has no management
- * RPC yet. It crosses the package boundary as a subprocess, never by importing
- * daemon implementation modules into the CLI process.
- */
-export async function runLegacyDaemonCli(args) {
-    const cliPath = resolveLegacyDaemonCli();
-    if (!cliPath) {
-        throw new Error("This command still requires the legacy daemon CLI, but it is not installed. " +
-            `Set ${LEGACY_CLI_ENV} to its absolute cli.js path or use the bundled Rynx App.`);
-    }
-    return new Promise((resolve, reject) => {
-        const child = spawn(process.execPath, [cliPath, ...args], {
-            stdio: "inherit",
-            env: process.env,
-        });
-        child.once("error", (error) => {
-            reject(new Error(`failed to launch legacy daemon CLI: ${error.message}`));
-        });
-        child.once("exit", (code, signal) => {
-            if (signal) {
-                reject(new Error(`legacy daemon CLI exited with signal ${signal}`));
-                return;
-            }
-            resolve(code ?? 1);
-        });
-    });
-}
-export function resolveLegacyDaemonCli(env = process.env, moduleUrl = import.meta.url) {
-    const configured = env[LEGACY_CLI_ENV];
-    if (configured !== undefined) {
-        if (!path.isAbsolute(configured)) {
-            throw new Error(`${LEGACY_CLI_ENV} must be an absolute path`);
-        }
-        return validateCliFile(configured);
-    }
-    // Works both in the workspace and when @rynx-ai/cli and @rynx-ai/daemon are
-    // siblings under node_modules/@rynx-ai.
-    const sibling = fileURLToPath(new URL("../../daemon/dist/cli.js", moduleUrl));
-    return validateCliFile(sibling);
-}
-function validateCliFile(candidate) {
-    try {
-        if (!existsSync(candidate) || !statSync(candidate).isFile())
-            return null;
-        const resolved = realpathSync(candidate);
-        const current = process.argv[1];
-        if (current &&
-            existsSync(current) &&
-            realpathSync(current) === resolved) {
-            return null;
-        }
-        return resolved;
-    }
-    catch {
-        return null;
-    }
-}