@mightybot/mbcli 0.5.420 → 0.6.1-rc.625

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 (2) hide show
  1. package/README.md +12 -46
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -8,49 +8,28 @@ a per-platform optional dependency (`@mightybot/mbcli-<platform>`), and npm
8
8
  installs only the one matching your machine.
9
9
 
10
10
 
11
- ## Runtwo ways
11
+ ## Start here one command
12
12
 
13
- The actual command is always **`mb`**; the package name (`@mightybot/mbcli`)
14
- is just what npm fetches. Pick whichever fits:
15
-
16
- ### Option A — `npx` (no install, always newest)
13
+ With Node.js 16+, this one command is the entire setup it signs you in and
14
+ registers the MCP server with your AI agents:
17
15
 
18
16
  ```bash
19
- npx @mightybot/mbcli@latest version # prod (stable)
20
- npx @mightybot/mbcli@latest auth login
21
- npx @mightybot/mbcli@preprod version # preprod (newest build, ahead of latest)
17
+ npx @mightybot/mbcli@latest setup
22
18
  ```
23
19
 
24
- npm fetches + caches only your platform's binary on first run; `@latest` /
25
- `@preprod` makes npx re-check the registry each run, so you always get the
26
- newest build for that channel. Nothing to upgrade.
20
+ `setup` = `mb auth login` (browser sign-in) + `mb mcp install --agent all`.
21
+ `npx` fetches the right platform binary on demand nothing to install first.
27
22
 
28
- ### Option B global install (`mb` on PATH, shorter commands)
23
+ Run any other command the same way:
29
24
 
30
25
  ```bash
31
- npm i -g @mightybot/mbcli@latest # or @preprod
32
- mb version
33
- mb auth login
34
- mb setup
26
+ npx @mightybot/mbcli@latest workflow list
27
+ npx @mightybot/mbcli@latest version
35
28
  ```
36
29
 
37
- Puts a real `mb` command on your PATH — no `npx`, no scope prefix. Faster
38
- (no per-run resolution), but it does **not** auto-update: you are pinned to the
39
- version installed until you re-run the install to upgrade:
40
-
41
- ```bash
42
- npm i -g @mightybot/mbcli@latest # upgrade to newest latest
43
- npm i -g @mightybot/mbcli@preprod # or newest preprod
44
- ```
45
-
46
- | | `npx …@latest` | `npm i -g …@latest` |
47
- |---|---|---|
48
- | Command | `npx @mightybot/mbcli@latest <cmd>` | `mb <cmd>` |
49
- | Always newest | ✅ auto | ❌ frozen at install — re-install to upgrade |
50
- | Per-run overhead | small | none |
51
-
52
- Either way, `mb setup` works the same — it installs the MCP server to the stable
53
- `~/.mightybot/mcp/mb`, independent of how you run the CLI.
30
+ > Prefer a permanent `mb` on your PATH? `npm i -g @mightybot/mbcli@latest`,
31
+ > then run `mb <cmd>` (re-run the install to upgrade). The MCP server installs to
32
+ > the stable `~/.mightybot/mcp/mb` either way.
54
33
 
55
34
  ### Release channels
56
35
 
@@ -87,18 +66,6 @@ Once the build is older than the cooldown window, plain `npx …` works with no
87
66
  flag. (This guard is intentional — it protects against installing a
88
67
  freshly-compromised package; the override is only for trusted same-day builds.)
89
68
 
90
- ## One-step setup (auth + MCP)
91
-
92
- After installing, run **one** command to get fully provisioned — it logs you in
93
- and registers the MCP server with Codex / Claude Code / OpenCode:
94
-
95
- ```bash
96
- npx @mightybot/mbcli@latest setup
97
- ```
98
-
99
- `mb setup` = `mb auth login` (browser device auth) + `mb mcp install --agent all`.
100
- Auth flags pass through, e.g. `setup --base-url <your-platform-url>`.
101
-
102
69
  ## Commands
103
70
 
104
71
  Every example below uses the bare `mb` (after a global install or inside
@@ -172,7 +139,6 @@ mb surface step # step-level detail
172
139
  | `mb workflow create` / `update` / `duplicate` / `delete` | Manage definitions. |
173
140
  | `mb workflow export <id>` | Export a definition (e.g. for diffing/backup). |
174
141
  | `mb workflow diff` | Diff two definitions/versions. |
175
- | `mb workflow validate <id>` | Validate a definition. |
176
142
  | `mb workflow versions` / `version` / `version-history` / `version-diff` | Inspect version history and compare versions. |
177
143
 
178
144
  ### `mb git` — git ↔ workflow sync state
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@mightybot/mbcli",
3
- "version": "0.5.420",
4
- "description": "MightyBot mb CLI and local design-time MCP server",
3
+ "version": "0.6.1-rc.625",
4
+ "description": "MightyBot mb CLI and local MCP server",
5
5
  "bin": {
6
6
  "mb": "bin/mb.js"
7
7
  },
@@ -15,11 +15,11 @@
15
15
  "license": "UNLICENSED",
16
16
  "private": false,
17
17
  "optionalDependencies": {
18
- "@mightybot/mbcli-darwin-arm64": "0.5.420",
19
- "@mightybot/mbcli-darwin-x64": "0.5.420",
20
- "@mightybot/mbcli-linux-x64": "0.5.420",
21
- "@mightybot/mbcli-linux-arm64": "0.5.420",
22
- "@mightybot/mbcli-win32-x64": "0.5.420"
18
+ "@mightybot/mbcli-darwin-arm64": "0.6.1-rc.625",
19
+ "@mightybot/mbcli-darwin-x64": "0.6.1-rc.625",
20
+ "@mightybot/mbcli-linux-x64": "0.6.1-rc.625",
21
+ "@mightybot/mbcli-linux-arm64": "0.6.1-rc.625",
22
+ "@mightybot/mbcli-win32-x64": "0.6.1-rc.625"
23
23
  },
24
24
  "homepage": "https://mightybot.ai"
25
25
  }