@nocobase/plugin-ai 2.2.0-beta.7 → 2.2.0-beta.8

package/dist/ai/docs/nocobase/api/cli/config/delete.md

@@ -33,6 +33,7 @@ nb config delete proxy.nginx-driver
 nb config delete proxy.caddy-driver
 nb config delete bin.nginx
 nb config delete bin.git
+nb config delete bin.pnpm
 ```
 
 ## Related commands

package/dist/ai/docs/nocobase/api/cli/config/index.md

@@ -10,7 +10,7 @@ Manage default CLI configuration values. The currently supported keys are mainly
 
 - CLI itself: `locale`, `update.policy`, `license.pkg-url`
 - Docker runtime: `docker.network`, `docker.container-prefix`
-- External executables: `bin.docker`, `bin.caddy`, `bin.git`, `bin.nginx`, `bin.yarn`
+- External executables: `bin.docker`, `bin.caddy`, `bin.git`, `bin.nginx`, `bin.pnpm`, `bin.yarn`
 - Proxy generation: `proxy.nb-cli-root`, `proxy.upstream-host`, `proxy.nginx-driver`, `proxy.caddy-driver`
 
 Most projects only need a few of these keys. In practice, the most common ones are:
@@ -34,6 +34,7 @@ Most projects only need a few of these keys. In practice, the most common ones a
 | `bin.caddy` | `caddy` | Override the Caddy executable path |
 | `bin.git` | `git` | Override the Git executable path |
 | `bin.nginx` | `nginx` | Override the Nginx executable path |
+| `bin.pnpm` | `pnpm` | Override the pnpm executable path |
 | `bin.yarn` | `yarn` | Override the Yarn executable path |
 | `proxy.nb-cli-root` | CLI root, usually the current user's home directory | Override the root path visible to the generated proxy config when the proxy process and CLI do not see the same filesystem root |
 | `proxy.upstream-host` | `127.0.0.1` | Override the host used when the proxy forwards traffic back to the NocoBase app |
@@ -70,12 +71,14 @@ nb config get docker.network
 nb config set docker.network nocobase
 nb config set bin.nginx /usr/sbin/nginx
 nb config set bin.git /usr/bin/git
+nb config set bin.pnpm /usr/local/bin/pnpm
 nb config delete docker.container-prefix
 ```
 
 ## Notes
 
 - `bin.nginx` and `bin.caddy` only affect the `local` driver for `nb proxy nginx` and `nb proxy caddy`
+- `bin.pnpm` is used when commands need to run pnpm directly, such as updating a pnpm-managed global CLI install with `nb self update`
 - `proxy.nginx-driver` and `proxy.caddy-driver` store the default driver used by each provider
 - `proxy.nb-cli-root` and `proxy.upstream-host` are advanced proxy overrides. Most CLI-managed `local` or `docker` envs can use the defaults directly
 - If you only want to switch the active proxy driver, using `nb proxy nginx use` or `nb proxy caddy use` is usually clearer than setting the config key manually

package/dist/ai/docs/nocobase/api/cli/config/set.md

@@ -33,6 +33,7 @@ nb config set bin.docker /usr/local/bin/docker
 nb config set bin.caddy /opt/homebrew/bin/caddy
 nb config set bin.git /usr/bin/git
 nb config set bin.nginx /usr/sbin/nginx
+nb config set bin.pnpm /usr/local/bin/pnpm
 nb config set proxy.nb-cli-root /workspace
 nb config set proxy.upstream-host host.docker.internal
 nb config set proxy.nginx-driver docker

package/dist/ai/docs/nocobase/api/cli/env/auth.md

@@ -1,17 +1,19 @@
 ---
 title: "nb env auth"
-description: "nb env auth command reference: run OAuth login for a saved NocoBase env."
-keywords: "nb env auth,NocoBase CLI,OAuth,login,authentication"
+description: "nb env auth command reference: authenticate a saved NocoBase env with basic, token, or OAuth authentication."
+keywords: "nb env auth,NocoBase CLI,basic,token,OAuth,login,authentication"
 ---
 
 # nb env auth
 
-Run OAuth login for a selected env. When the env name is omitted, the current env is used.
+Authenticate a saved NocoBase env again, or update the authentication information saved for it. When the env name is omitted, the current env is used.
+
+`nb env auth` supports three authentication methods: `basic`, `token`, and `oauth`. If `--auth-type` is omitted, the CLI first infers the method from the authentication options you pass. If it still cannot infer the method, it uses the authentication method already saved in the env.
 
 ## Usage
 
 ```bash
-nb env auth [name]
+nb env auth [name] [flags]
 ```
 
 ## Parameters
@@ -19,19 +21,65 @@ nb env auth [name]
 | Parameter | Type | Description |
 | --- | --- | --- |
 | `[name]` | string | Configured environment name to sign in to; uses the current env if omitted |
+| `--auth-type`, `-a` | string | Authentication method: `basic`, `token`, or `oauth` |
+| `--access-token`, `-t` | string | API key or access token used with `token` authentication |
+| `--username` | string | Username used with `basic` authentication; prompted in TTY when omitted |
+| `--password` | string | Password used with `basic` authentication; prompted in TTY when omitted |
+
+## Compatibility options
+
+| Option | Type | Description |
+| --- | --- | --- |
+| `--env`, `-e` | string | Environment name, equivalent to `[name]`. This hidden option is kept for compatibility with other commands; normally the positional argument is enough |
 
 ## Notes
 
-Internally, this command uses the PKCE flow: start a local callback server, open the browser for authorization, exchange the token, and save it to the config file.
+The authentication methods work as follows:
+
+- `basic`: sign in to NocoBase with a username and password, then save the returned access token and username
+- `token`: save the API key or access token passed through `--access-token`
+- `oauth`: start the browser authentication flow, then save the access token after authentication finishes
+
+In an interactive terminal, the CLI prompts for `--auth-type`, `--username`, `--password`, or `--access-token` when needed. In non-interactive mode, `basic` authentication requires both `--username` and `--password`.
+
+`oauth` authentication first tries Device Authorization Grant. When the OAuth server supports this flow, the command prints a verification URL and user code, then polls until the browser approval is complete. This works on remote or headless servers because it does not require a local callback listener.
+
+If the OAuth server does not expose a device authorization endpoint, the command falls back to the PKCE loopback flow: start a local callback server, open the browser for authorization, exchange the token, and save it to the config file.
+
+After authentication succeeds, the CLI automatically runs `nb env update <name>` to re-sync the env state.
+
+## Limits
+
+- `[name]` and `--env` cannot provide different environment names at the same time
+- `--access-token` cannot be used with `--username` or `--password`
+- `--auth-type oauth` cannot be used with `--access-token`, `--username`, or `--password`
+- `--auth-type token` cannot be used with `--username` or `--password`
+- `--auth-type basic` cannot be used with `--access-token`
+- `--access-token`, `--username`, and `--password` cannot be empty after they are provided
 
 ## Examples
 
 ```bash
+# Authenticate the current env with the saved authentication method
 nb env auth
+
+# Authenticate a specific env
 nb env auth prod
+
+# Use OAuth browser login
+nb env auth prod --auth-type oauth
+
+# Sign in with username and password
+nb env auth prod --auth-type basic --username admin --password secret
+
+# Save an API key or access token
+nb env auth prod --auth-type token --access-token <api-key>
 ```
 
+For device authorization, follow the URL printed by the command and enter the displayed code in the browser.
+
 ## Related Commands
 
 - [`nb env add`](./add.md)
+- [`nb env info`](./info.md)
 - [`nb env update`](./update.md)

package/dist/ai/docs/nocobase/api/cli/self/check.md

@@ -6,7 +6,7 @@ keywords: "nb self check,NocoBase CLI,version check"
 
 # nb self check
 
-Check the current NocoBase CLI installation, resolve the latest version for the selected channel, and report whether automatic self-update is supported.
+Check the current NocoBase CLI installation, resolve the latest version for the selected channel, and report whether self-update is supported.
 
 ## Usage
 
@@ -18,9 +18,26 @@ nb self check [flags]
 
 | Parameter | Type | Description |
 | --- | --- | --- |
-| `--channel` | string | Release channel to compare with, default `auto`; options: `auto`, `latest`, `beta`, `alpha` |
+| `--channel` | string | Release channel to compare with, default `auto`; options: `auto`, `latest`, `test`, `beta`, `alpha` |
 | `--json` | boolean | Output JSON |
 
+## Install Method
+
+`nb self check` detects the current install method at runtime. It does not use the historical `self-install-methods.json` cache.
+
+The command can report these install methods:
+
+| Install method | Meaning |
+| --- | --- |
+| `npm-global` | The CLI is installed under the current `npm prefix -g`. |
+| `pnpm-global` | The CLI is installed under a pnpm global `node_modules` tree. |
+| `yarn-global` | The CLI is launched from `yarn global bin` or installed under `yarn global dir`. |
+| `package-local` | The CLI is installed in a local project dependency tree. |
+| `source` | The CLI is running from a repository checkout. |
+| `unknown` | The CLI install could not be matched to a supported install method. |
+
+Self-update is supported for `npm-global`, `pnpm-global`, and `yarn-global`. For `package-local` or `source`, update the parent project or repository checkout instead.
+
 ## Examples
 
 ```bash

package/dist/ai/docs/nocobase/api/cli/self/index.md

@@ -19,7 +19,7 @@ nb self <command>
 | Command | Description |
 | --- | --- |
 | [`nb self check`](./check.md) | Check current CLI version and self-update support |
-| [`nb self update`](./update.md) | Update the globally npm-installed NocoBase CLI |
+| [`nb self update`](./update.md) | Update the globally npm-, pnpm-, or yarn-installed NocoBase CLI |
 
 ## Examples
 

package/dist/ai/docs/nocobase/api/cli/self/update.md

@@ -1,12 +1,12 @@
 ---
 title: "nb self update"
-description: "nb self update command reference: update the globally npm-installed NocoBase CLI."
+description: "nb self update command reference: update the globally npm-, pnpm-, or yarn-installed NocoBase CLI."
 keywords: "nb self update,NocoBase CLI,update,self update"
 ---
 
 # nb self update
 
-Update the installed NocoBase CLI when the current CLI is managed by a standard global npm installation.
+Update the installed NocoBase CLI when the current CLI is managed by a standard global npm, pnpm, or yarn installation.
 
 ## Usage
 
@@ -18,12 +18,26 @@ nb self update [flags]
 
 | Parameter | Type | Description |
 | --- | --- | --- |
-| `--channel` | string | Release channel to update to, default `auto`; options: `auto`, `latest`, `beta`, `alpha` |
+| `--channel` | string | Release channel to update to, default `auto`; options: `auto`, `latest`, `test`, `beta`, `alpha` |
 | `--yes`, `-y` | boolean | Skip update confirmation |
 | `--json` | boolean | Output JSON |
 | `--skills` | boolean | Also refresh the globally installed NocoBase AI coding skills |
 | `--verbose` | boolean | Show detailed update output |
 
+## Update Behavior
+
+`nb self update` first detects the current install method at runtime. It does not use the historical `self-install-methods.json` cache.
+
+When an update is available, the command uses the same package manager that manages the current global CLI install:
+
+| Install method | Update command |
+| --- | --- |
+| `npm-global` | `npm install -g @nocobase/cli@<channel>` |
+| `pnpm-global` | `pnpm add -g @nocobase/cli@<channel>` |
+| `yarn-global` | `yarn global add @nocobase/cli@<channel>` |
+
+Interactive confirmation defaults to yes. Use `--yes` to skip the prompt in scripts.
+
 ## Examples
 
 ```bash

package/dist/ai/docs/nocobase/nocobase-cli/installation/cli.md

@@ -35,6 +35,8 @@ nb config set update.policy auto
 nb config set update.policy off
 ```
 
+Self-update is only supported when the CLI is managed by a standard global npm, pnpm, or yarn install. If you are running from source or from a local project dependency tree, use [`nb self check`](../../api/cli/self/check.md) to see the detected install method and update that parent project instead.
+
 If you are going to deploy NocoBase to the server and want to open the `nb init --ui` wizard from a remote browser, it is recommended to first change the CLI's default host to the current server IP:
 
 ```bash