@getmagical/cli 0.9.2 → 0.10.1

package/README.md

@@ -543,6 +543,59 @@ These GraphQL operations come from the same shared registry used by the Apollo
 MCP server. MCP callers must provide `idempotencyKey` and
 `expectedTrialCount` directly when starting a run.
 
+## Agent export and import
+
+Use user login for agent transfers. Export selected agents from a library asset
+or a saved automation version, then import the file into a draft in the same
+workspace:
+
+```bash
+mgcl agents export --library-entity-id <library-id> --ids <agent-id> --org <org-id> --json > agents.json
+mgcl agents import --automation-id <destination-id> --base-version-id <current-draft-version-id> --file agents.json --org <org-id> --json
+```
+
+For an automation source, replace `--library-entity-id` with
+`--automation-version-id`. Export uses the existing selected-agent JSON format,
+including its selection filtering. Import returns `importedAgentIds` and the new
+`draftVersionId`.
+
+Import converts the JSON into the existing automation update operation. It
+allocates new IDs, remaps internal references, and preserves API request config.
+Instructions are converted to the update API's command format; command/comment
+identities are recreated and canvas positions are not imported. Existing update
+validation, trigger rules, normalization, audit logging, and stale-version checks
+apply. Destination settings are not imported. Cross-workspace transfers,
+shared-input migration, and branch imports are not supported.
+
+JSON imports reject literal credentials and platform resource references using
+the same scanner as portal JSON imports, even when the source workspace matches.
+Remove those values from the exported file and configure them in the destination.
+Fully templated credentials remain importable.
+
+Deploy the backend transfer fields before releasing CLI 0.9.3.
+
+## Library assets
+
+Library assets are reusable agent subtrees shared by automations in one
+workspace. Like agent transfers, these commands require user login.
+
+```bash
+mgcl library search --query login --org <org-id> --json
+mgcl library get --library-entity-id <library-id> --org <org-id> --json
+mgcl library create --name "Shared Login" --org <org-id> --json
+mgcl library convert --draft-automation-id <automation-id> --root-agent-id <agent-id> --base-version-id <current-draft-version-id> --name "Shared Login" --org <org-id> --json
+mgcl library import --draft-automation-id <automation-id> --library-entity-id <library-id> --base-version-id <current-draft-version-id> --parent-agent-id <agent-id> --org <org-id> --json
+```
+
+An asset is named after its root agent. `--name` on `create` names the new
+root agent (default `New Asset`); on `convert` it renames the converted root
+agent, which otherwise keeps its name. `convert` and `import` save the draft
+and return the new `draftVersionId`. Omit `--parent-agent-id` to import the
+asset at the top level.
+
+Deploy the backend `convertAutomationSubtreeToLibraryAsset(assetName:)`
+argument before releasing CLI 0.10.0.
+
 ## Automation branches
 
 `--branch-id` is a global, per-command authoring target. The CLI never stores a