@useorgx/wizard 0.1.8 → 0.1.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +7 -6
  2. package/dist/cli.js +252 -227
  3. package/dist/cli.js.map +1 -1
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -14,15 +14,16 @@ For local development, use `pnpm dev -- --help`.
14
14
 
15
15
  ## Commands
16
16
 
17
- - `setup` configures detected automated surfaces and, when OrgX auth is available in an interactive shell, guides workspace selection or creation, optional onboarding extras, and optional companion plugin installs for detected Claude Code, Codex, and OpenClaw hosts. The founder preset preplans plugin installs before it writes standalone skills so plugin-backed hosts do not get duplicate standalone Claude assets in the same run.
17
+ - `setup` configures detected automated surfaces and, when OrgX auth is available in an interactive shell, guides workspace selection or creation, optional onboarding extras, and optional Cursor rules or companion plugin installs for detected Cursor, Claude Code, Codex, and OpenClaw hosts. The founder preset preplans plugin installs before it writes standalone skills so plugin-backed hosts do not get duplicate standalone Claude assets in the same run.
18
18
  - `surface list` shows supported surfaces and current status.
19
19
  - `surface add <name>` patches a specific surface.
20
20
  - `surface remove <name>` removes OrgX-managed config from a specific surface.
21
21
  - `mcp add [surface]` and `mcp remove [surface]` manage Claude, Cursor, Codex, VS Code, Windsurf, and Zed MCP entries.
22
- - `plugins list` shows companion plugin availability and install status for Claude Code, Codex, and OpenClaw.
23
- - `plugins add [target...]` installs the managed OrgX companion plugins into Claude Code, Codex, and/or OpenClaw. Claude Code and Codex plugins carry their own OrgX skills, so they become the source of truth for those hosts.
24
- - `plugins remove [target...]` uninstalls the managed OrgX companion plugins from Claude Code, Codex, and/or OpenClaw.
25
- - `doctor` verifies local config, hosted MCP reachability, an authenticated hosted MCP `get_setup_status` tool call when OrgX user auth is configured, npm registry readiness, current-workspace connectivity, local OpenClaw health, and optionally the remote setup status API. It exits non-zero when blocking connectivity issues remain.
22
+ - `plugins list` shows Cursor rules and companion plugin availability and install status for Cursor, Claude Code, Codex, and OpenClaw.
23
+ - `plugins add [target...]` installs managed Cursor OrgX rules or managed OrgX companion plugins into Claude Code, Codex, and/or OpenClaw. Claude Code and Codex plugins carry their own OrgX skills, so they become the source of truth for those hosts.
24
+ - `plugins remove [target...]` uninstalls managed Cursor OrgX rules or managed OrgX companion plugins from Claude Code, Codex, and/or OpenClaw.
25
+ - `uninstall` removes OrgX-managed surface config, Cursor rules and companion plugins, wizard-local auth, and wizard-local setup state. Use `--keep-auth`, `--keep-state`, `--skip-plugins`, or `--skip-surfaces` to preserve specific pieces.
26
+ - `doctor` verifies local config, hosted MCP reachability, npm registry readiness, current-workspace connectivity, local OpenClaw health, and optionally the remote setup status API. Hosted MCP tools are OAuth-scoped inside the client connector, so the wizard does not preflight them with `oxk_` API keys. It exits non-zero when blocking connectivity issues remain.
26
27
  - `auth status` shows the resolved OrgX API key source and verifies it against `POST /api/client/sync`.
27
28
  - `auth login [--base-url <url>]` starts browser pairing against OrgX, waits for approval, saves the returned per-user key to the wizard auth store, and bootstraps OpenClaw auth if OpenClaw is detected. Use `--api-key <oxk_...>` for CI or blocked-browser fallback.
28
29
  - `auth set-key <oxk_...> [--base-url <url>]` verifies a per-user OrgX key, saves it to the wizard auth store, and bootstraps OpenClaw auth if OpenClaw is detected.
@@ -40,7 +41,7 @@ For local development, use `pnpm dev -- --help`.
40
41
 
41
42
  - The wizard uses per-user `oxk_...` keys for auth verification and local bootstrap. `auth login` now prefers secure browser pairing and falls back to direct key entry with `--api-key`.
42
43
  - When `keytar` is available, the wizard stores the raw API key in the system keychain and keeps only metadata in `auth.json`. If `keytar` is unavailable or disabled, it falls back to file-backed storage in `auth.json`.
43
- - `doctor` always checks `https://mcp.useorgx.com/health` and, when user auth is configured, initializes an authenticated MCP session against `https://mcp.useorgx.com/mcp` and calls `get_setup_status` before resolving the current workspace through the OrgX API.
44
+ - `doctor` always checks `https://mcp.useorgx.com/health` and resolves the current workspace through the OrgX API. Hosted MCP tool calls are verified by the configured client connector after its OAuth flow completes, not by the wizard's per-user `oxk_` key.
44
45
  - `doctor` also checks npm registry reachability for `@useorgx/wizard` and reports whether the package is already published.
45
46
  - Remote setup status is separate: `doctor` checks `/api/setup/status` only when `ORGX_SERVICE_KEY` is present because that endpoint is still service-key-only.
46
47
  - Auth resolution order is `ORGX_API_KEY`, then the wizard auth store, then OpenClaw config.