@mightybot/mbcli 0.6.9-rc.877 → 0.6.10-dev.1002

package/README.md

@@ -106,7 +106,9 @@ agents. Auth flags pass through (e.g. `--base-url <your-platform-url>`).
 | `mb auth configure` | Set/switch the backend (base URL, environment). |
 | `mb auth probe-write` | Pre-flight check that the token can perform writes. |
 
-> `mb` has **one** profile slot — the last `mb auth login` wins. Confirm the
+> Inside a git repository `mb` uses that checkout's own `.mightybot.json`, so
+> each worktree keeps its own backend and token. Outside one it falls back to a
+> single global profile, where the last `mb auth login` wins. Confirm the
 > active backend with `mb auth inspect` before any write.
 
 ### `mb mcp` — local design-time MCP server
@@ -137,10 +139,41 @@ mb surface step          # step-level detail
 | `mb workflow list` | List workflow definitions. |
 | `mb workflow inspect <id>` | Show a definition's full configuration. |
 | `mb workflow create` / `update` / `duplicate` / `delete` | Manage definitions. |
-| `mb workflow export <id>` | Export a definition (e.g. for diffing/backup). |
+| `mb workflow export <id>` | Write a definition's config to a local file (for diffing/backup). |
+| `mb workflow fork <id> --target-org <id-or-name>` | Copy a workflow into another organization you administer. Stages a background job. |
+| `mb workflow export-job <job_id>` | Check one copy job. |
+| `mb workflow jobs <id>` | List a workflow's recent copy/deploy/release jobs. |
 | `mb workflow diff` | Diff two definitions/versions. |
 | `mb workflow versions` / `version` / `version-history` / `version-diff` | Inspect version history and compare versions. |
 
+**Three verbs copy a workflow — pick by destination.** `export` writes config to
+your local disk. `duplicate` copies within the *same* organization. `fork` copies
+*into another organization* you administer.
+
+```bash
+# Copy into another org. Lands a DRAFT there with secrets blanked.
+mb workflow fork expense-approver --target-org "Acme Corp"
+# → {"status_code": 202, "body": {"export_job_id": "...", "status": "PENDING"}}
+# Like every mb command, the response is wrapped — read .body.export_job_id:
+mb workflow fork expense-approver --target-org "Acme Corp" | jq -r .body.export_job_id
+
+# Block until the copy — and its Git sync — settles. Exits non-zero if it failed,
+# so this works as a CI gate.
+mb workflow fork expense-approver --target-org "Acme Corp" --wait
+
+# Or poll it yourself.
+mb workflow export-job <export_job_id>
+mb workflow jobs expense-approver
+```
+
+`--target-org` takes an organization id or an exact name. Omit it entirely to
+stage a same-org export. Other flags: `--repo owner/name` (target workflow repo),
+`--branch` (source branch to copy from), `--no-config` (shell only),
+`--no-sync-to-git` (skip the Git branch sync).
+
+Forking needs platform super-admin, or admin in **both** the source and target
+organization, and the backend must run with `WORKFLOW_CROSS_ORG_EXPORT_ENABLED`.
+
 ### `mb git` — git ↔ workflow sync state
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mightybot/mbcli",
-  "version": "0.6.9-rc.877",
+  "version": "0.6.10-dev.1002",
   "description": "MightyBot mb CLI and local MCP server",
   "bin": {
     "mb": "bin/mb.js"
@@ -15,11 +15,11 @@
   "license": "UNLICENSED",
   "private": false,
   "optionalDependencies": {
-    "@mightybot/mbcli-darwin-arm64": "0.6.9-rc.877",
-    "@mightybot/mbcli-darwin-x64": "0.6.9-rc.877",
-    "@mightybot/mbcli-linux-x64": "0.6.9-rc.877",
-    "@mightybot/mbcli-linux-arm64": "0.6.9-rc.877",
-    "@mightybot/mbcli-win32-x64": "0.6.9-rc.877"
+    "@mightybot/mbcli-darwin-arm64": "0.6.10-dev.1002",
+    "@mightybot/mbcli-darwin-x64": "0.6.10-dev.1002",
+    "@mightybot/mbcli-linux-x64": "0.6.10-dev.1002",
+    "@mightybot/mbcli-linux-arm64": "0.6.10-dev.1002",
+    "@mightybot/mbcli-win32-x64": "0.6.10-dev.1002"
   },
   "homepage": "https://mightybot.ai"
 }