@animaapp/cli 0.8.0 → 0.10.0

package/README.md

@@ -187,8 +187,10 @@ options; `--json` makes any of them agent-readable.
 | | [`auth`](#auth--inspect-or-manage-credentials) | Inspect credentials, store a Figma token |
 | | [`skill`](#skill--install-the-agentgrid-guide-for-your-agent) | Install the AgentGrid guide as a SKILL.md your agent can read |
 | | [`mcp-config`](#mcp-config--print-your-mcp-server-config) | Print an MCP server config for your MCP client |
-| **Find** | [`list`](#list--your-teams-artifacts) | Your team's artifacts, most-recently-updated first |
+| **Find** | [`workspaces`](#workspaces--where-you-can-work) | The workspaces you can reach, and what you may do in each |
+| | [`list`](#list--the-artifacts-you-can-read) | The artifacts you can read, most-recently-updated first |
 | **Make** | [`create`](#create--an-artifact-for-your-code-or-ai-generated) | Import your code, an empty repo, or AI generation |
+| | [`create-knowledge`](#create--an-artifact-for-your-code-or-ai-generated) | Create a knowledge artifact |
 | | [`status`](#status--did-generation-finish) | Did generation finish? `--wait` blocks until it has |
 | | [`duplicate`](#duplicate--copy-an-existing-artifact) | Copy an artifact into a new, independent one |
 | **Change** | [`explore`](#explore--read-an-artifacts-files-no-git) | Read files: list, search, read, history |
@@ -199,6 +201,7 @@ options; `--json` makes any of them agent-readable.
 | **Ship** | [`publish`](#publish--deploy-a-session-to-a-public-url-13-min) | Deploy to a public live URL — only when asked |
 | | [`unpublish`](#unpublish--take-a-published-artifact-offline) | Take a published artifact offline |
 | | [`update`](#update--rename-or-change-visibility-metadata-only) | Rename, or change visibility |
+| | [`move`](#move--file-an-artifact-under-a-different-workspace) | File an artifact under a different workspace |
 | | [`delete`](#delete--hide-an-artifact-with-reversible-soft-deletion) | Reversible soft deletion |
 | **Figma** | [`codegen`](#codegen--figma-to-local-files-no-artifact) | Figma → local code files, no artifact |
 | **Settings** | [`config`](#config--store-cli-preferences) | Store CLI preferences (e.g. a default API URL) |
@@ -257,25 +260,46 @@ authorize when it prompts. No CLI in the loop after that. Your client needs to
 support OAuth for remote MCP servers (`.well-known` discovery); if it cannot,
 use the CLI commands instead.
 
-### `list` — your team's artifacts
+### `workspaces` — where you can work
+
+```bash
+npx @animaapp/cli@latest workspaces
+```
+
+Artifacts live in workspaces. You may have access to one or more of them, and
+what you may do can differ between them: each row shows the capabilities you
+hold there, and creating or changing an artifact needs `write`.
+
+Workspace ids are opaque: get one here (each `list` row carries its own) for `--workspace`.
+An empty list means your access reaches none of this team's workspaces — not
+that the team has none.
+
+### `list` — the artifacts you can read
 
 ```bash
 npx @animaapp/cli@latest list
+npx @animaapp/cli@latest list --workspace <id>       # just one workspace
 ```
 
 Most-recently-updated first, so you can resume existing work instead of
-creating a second artifact for the same job. Each row carries its session id
-and `artifactUrl`; `--json` adds them to every row.
+creating a second artifact for the same job. It spans every workspace you can
+read unless `--workspace` names one, and each row says which workspace it is
+in. Each row carries its session id and `artifactUrl`; `--json` adds them to
+every row.
 
 ### `create` — an artifact for your code, or AI-generated
 
 ```bash
 npx @animaapp/cli@latest create -t import --from ./my-project              # import YOUR code (instant)
 npx @animaapp/cli@latest create -t import --from ./notes --artifact-type markdown  # a readable document
+npx @animaapp/cli@latest create-knowledge --name "Team knowledge"              # server-provided template
+npx @animaapp/cli@latest create-knowledge --name "Team knowledge" --workspace <id>  # ...in a specific workspace
 npx @animaapp/cli@latest create -t empty --framework react --name "My project"  # empty repo you push to (instant)
+npx @animaapp/cli@latest create -t import --from ./my-project --workspace <id>    # in a specific workspace
 npx @animaapp/cli@latest create -t p2c -p "Analytics dashboard with a sidebar"
 npx @animaapp/cli@latest create -t l2c -u https://stripe.com
 npx @animaapp/cli@latest create -t f2c --file-key <key> --nodes 42:15
+npx @animaapp/cli@latest create -t p2c -p "Pricing page" --workspace <id>        # any type takes --workspace
 npx @animaapp/cli@latest create -t import --from ./my-project --anonymous     # no account — hand off later
 ```
 
@@ -303,6 +327,14 @@ readable document and needs `.md` files. Omit it and the server infers one:
 markdown when your files are `.md`/`.mdx` with no HTML, otherwise app. Getting it wrong is the common mistake — `.md` files
 uploaded as an app produce an artifact with nothing to render.
 
+Knowledge artifacts use the dedicated `create-knowledge` command instead of
+generic `create`. It accepts an optional `--name` (maximum 120 characters) and
+an optional `--workspace <id>`; the server-provided knowledge template supplies
+the initial files and framework.
+This command requires deployment of the server contract containing merged
+AnimaApp/anima-design-to-code PR 5114. There is no compatibility fallback to
+generic creation on older servers.
+
 | Option | Values | Default |
 |--------|--------|---------|
 | `-t, --type` | `import` (your code, with `--from`), `empty` (repo to push to), `p2c` (prompt), `l2c` (URL), `f2c` (Figma) | _required_ |
@@ -454,9 +486,11 @@ a commit cannot carry (a question answered, a change you decided against), and
 ```bash
 npx @animaapp/cli@latest duplicate <artifactUrl-or-sessionId>
 npx @animaapp/cli@latest duplicate <artifactUrl-or-sessionId> --name "My copy"
+npx @animaapp/cli@latest duplicate <artifactUrl-or-sessionId> --workspace <id>
 ```
 
-Creates a new, independent artifact in the current team's Default workspace.
+Creates a new, independent artifact in the workspace `--workspace` names, which
+is optional when you can create in only one.
 It copies code, assets, and supported database content, but does **not** copy
 chat or custom domains. The source must be readable and the destination
 workspace must be writable. Without `--name`, the API names it
@@ -532,6 +566,26 @@ npx @animaapp/cli@latest update <sessionId> --privacy private   # team only
 Never touches code or content — that's `edit` (or the git flow via
 `get-git-token`).
 
+### `move` — file an artifact under a different workspace
+
+```bash
+npx @animaapp/cli@latest workspaces                       # the ids live here
+npx @animaapp/cli@latest move <sessionId> --workspace <id>
+```
+
+**The artifact stays as it is.** Same git repository, session id, URL, history
+and live deployment — there is no new link to send and no copy to reconcile.
+
+**What changes is who can reach it.** A private artifact is reached *through*
+the workspace it is filed in, so a move hands it to the people who reach the
+destination and takes it from the rest, including whoever you already sent the
+link to. You need `write` on the artifact and `write` in the destination, which
+is what moving it back would take too.
+
+`--workspace` is required and names a workspace of the same team, where `create`
+and `duplicate` fall back to the one workspace you can write in. Moving an
+artifact where it already is leaves everything as it was.
+
 ### `get-git-token` — read/edit an artifact's code over git
 
 ```bash
@@ -617,7 +671,7 @@ is `awaiting_claim` or `expired`, alongside the `artifactUrl` to re-send.
 | `--json` | Emit a single JSON object to stdout (for agents) | every command |
 | `--api-url <url>` | API base URL — point at local or staging³ | every command except `config` |
 | `--log-file <path>` | Append a JSON debug log of each step to a file | every command that reaches the network |
-| `--verbose` | Stream progress to stderr in JSON mode¹ | `create`, `status`, `duplicate`, `upload-asset`, `publish`, `unpublish`, `update`, `delete`, `codegen`, `get-git-token` |
+| `--verbose` | Stream progress to stderr in JSON mode¹ | `create`, `create-knowledge`, `status`, `duplicate`, `upload-asset`, `publish`, `unpublish`, `update`, `delete`, `codegen`, `get-git-token` |
 | `--timeout <ms>` | How long to wait² | `create`, `status`, `codegen` |
 
 ¹ Only the commands that do slow work carry a spinner, so `--verbose` is on