@nocobase/plugin-ai 2.1.0-beta.44 → 2.1.0-beta.45

package/dist/ai/docs/nocobase/api/cli/app/autostart/index.md

@@ -0,0 +1,63 @@
+---
+title: "nb app autostart"
+description: "nb app autostart command group reference: enable or disable autostart for local or Docker envs, and start all enabled envs in one run."
+keywords: "nb app autostart,NocoBase CLI,autostart,local,docker"
+---
+
+# nb app autostart
+
+Manage application autostart settings.
+
+This command group covers two kinds of work:
+
+- enable or disable the autostart flag for one env
+- start every env that already has autostart enabled
+
+`nb app autostart` only applies to envs with a CLI-managed runtime on the current machine, namely `local` and `docker`. If an env is only a remote API connection, or is not a CLI-managed app runtime that can be started on this machine, it cannot be part of this autostart flow.
+
+## Usage
+
+```bash
+nb app autostart <command>
+```
+
+## Subcommands
+
+| Command | Description |
+| --- | --- |
+| [`nb app autostart enable`](./enable.md) | Enable the autostart flag for one env |
+| [`nb app autostart disable`](./disable.md) | Disable the autostart flag for one env |
+| [`nb app autostart list`](./list.md) | Show autostart status for all envs |
+| [`nb app autostart run`](./run.md) | Start every env that has autostart enabled |
+
+## Notes
+
+`nb app autostart enable` only marks an env as allowed to start automatically. It does not wire the env into your operating system startup flow by itself. In a real production setup, you usually still need to call `nb app autostart run` from your own host startup mechanism, such as `systemd`, a container platform startup script, or another boot process you already use.
+
+Also, `nb app autostart run` checks each enabled env one by one. Startable envs continue through `nb app start --env <name> --yes`. Envs that should not be started automatically on the current machine show up as `skipped` or `failed` in the result table.
+
+## Examples
+
+```bash
+# Enable autostart for the current env
+nb app autostart enable
+
+# Enable autostart for a specific env
+nb app autostart enable --env app1 --yes
+
+# Show autostart status
+nb app autostart list
+
+# Start every enabled env
+nb app autostart run
+
+# Show underlying startup output
+nb app autostart run --verbose
+```
+
+## Related commands
+
+- [`nb app start`](../start.md)
+- [`nb app stop`](../stop.md)
+- [`nb env list`](../../env/list.md)
+- [`nb env use`](../../env/use.md)

package/dist/ai/docs/nocobase/api/cli/app/autostart/list.md

@@ -0,0 +1,41 @@
+---
+title: "nb app autostart list"
+description: "nb app autostart list command reference: list autostart status for every configured env."
+keywords: "nb app autostart list,NocoBase CLI,autostart,env list"
+---
+
+# nb app autostart list
+
+List autostart status for every configured env.
+
+The output table includes:
+
+- `Current`: marks the current env with `*`
+- `Env`: env name
+- `Kind`: env kind
+- `Source`: install or source type
+- `Autostart`: whether autostart is enabled
+
+## Usage
+
+```bash
+nb app autostart list
+```
+
+## Example
+
+```bash
+nb app autostart list
+```
+
+## Notes
+
+If there are no saved envs yet, the command prints `No environments are configured.`.
+
+This command only shows the saved CLI state. It does not check whether an app is already running, and it does not check whether your operating system startup flow already calls `nb app autostart run`. Its main purpose is to show which envs are marked for autostart in the CLI config.
+
+## Related commands
+
+- [`nb app autostart enable`](./enable.md)
+- [`nb app autostart disable`](./disable.md)
+- [`nb env list`](../../env/list.md)

package/dist/ai/docs/nocobase/api/cli/app/autostart/run.md

@@ -0,0 +1,50 @@
+---
+title: "nb app autostart run"
+description: "nb app autostart run command reference: start every env that has application autostart enabled."
+keywords: "nb app autostart run,NocoBase CLI,autostart,batch start"
+---
+
+# nb app autostart run
+
+Start every env that has application autostart enabled.
+
+This command is typically called after the host system boots, through your own startup mechanism. The CLI reads all saved envs, filters the ones that have autostart enabled, and then tries to start them one by one.
+
+## Usage
+
+```bash
+nb app autostart run [flags]
+```
+
+## Flags
+
+| Flag | Type | Description |
+| --- | --- | --- |
+| `--verbose` | boolean | Show raw startup output from the underlying local or Docker command |
+
+## Examples
+
+```bash
+nb app autostart run
+nb app autostart run --verbose
+```
+
+## Notes
+
+If no env has autostart enabled, the command prints `No environments have app autostart enabled.`.
+
+During execution, the CLI processes each enabled env one by one:
+
+- startable envs show up as `started`
+- envs that should not be started automatically on the current machine show up as `skipped`
+- envs that fail during startup show up as `failed`
+
+Internally, this command calls `nb app start --env <name> --yes`. If you pass `--verbose`, that flag is forwarded to the underlying startup flow as well.
+
+If any result is `failed`, the command exits with an error and prints `Some app autostart envs failed to start.`. This makes failures visible in `systemd`, CI, or other host startup mechanisms.
+
+## Related commands
+
+- [`nb app autostart enable`](./enable.md)
+- [`nb app start`](../start.md)
+- [`nb app logs`](../logs.md)

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

@@ -1,12 +1,12 @@
 ---
-title: "nb app"
-description: "nb app command reference: manage NocoBase app runtime, including start, stop, restart, logs, cleanup, and upgrades."
-keywords: "nb app,NocoBase CLI,app runtime,start,stop,logs,upgrade"
+title: 'nb app'
+description: 'nb app command reference: manage the NocoBase application runtime, including start, stop, restart, logs, and upgrade.'
+keywords: 'nb app,NocoBase CLI,start,stop,restart,logs,upgrade'
 ---
 
 # nb app
 
-Manage the runtime of a selected NocoBase env. npm/Git envs run local app commands; Docker envs manage app containers from the saved env config.
+Manage the NocoBase application runtime. In npm/Git env, application commands run in the local source directory; in Docker env, application containers are managed based on the saved configuration.
 
 ## Usage
 
@@ -16,27 +16,30 @@ nb app <command>
 
 ## Subcommands
 
-| Command | Description |
-| --- | --- |
-| [`nb app start`](./start.md) | Start the app or recreate the Docker container |
-| [`nb app stop`](./stop.md) | Stop the app or remove the Docker container |
-| [`nb app restart`](./restart.md) | Stop and then start the app |
-| [`nb app logs`](./logs.md) | View app logs |
-| [`nb app down`](./down.md) | Stop and clean up local runtime resources |
-| [`nb app upgrade`](./upgrade.md) | Stop the app, replace the source or image, then start it again |
+| Command                          | Description                                                                 |
+| -------------------------------- | --------------------------------------------------------------------------- |
+| [`nb app start`](./start.md)     | Start the application or recreate the Docker container                      |
+| [`nb app stop`](./stop.md)       | Stop the application or clean up the Docker container                       |
+| [`nb app restart`](./restart.md) | Stop the application first, then start it                                   |
+| [`nb app autostart`](./autostart/index.md) | Manage app autostart flags and start all enabled envs |
+| [`nb app logs`](./logs.md)       | View application logs                                                       |
+| [`nb app upgrade`](./upgrade.md) | Stop the application, replace the source code or image, then start it again |
 
 ## Examples
 
 ```bash
 nb app start --env app1
 nb app restart --env app1
+nb app autostart enable --env app1 --yes
+nb app autostart run
 nb app logs --env app1
-nb app stop --env app1
-nb app down --env app1 --all --force
+nb app upgrade --env app1 --skip-download
+nb app stop --env app1 --with-db
 ```
 
-## Related Commands
+## Related commands
 
 - [`nb env info`](../env/info.md)
+- [`nb env remove`](../env/remove.md)
 - [`nb db ps`](../db/ps.md)
 - [`nb source download`](../source/download.md)

package/dist/ai/docs/nocobase/api/cli/app/restart.md

@@ -1,12 +1,12 @@
 ---
 title: "nb app restart"
-description: "nb app restart command reference: restart the NocoBase app for a selected env and recreate the Docker app container from saved env config when needed."
+description: "nb app restart command reference: restart the NocoBase app for a selected env; when applicable, the CLI first synchronizes the commercial plugins allowed by the current license, then local envs automatically complete install or upgrade preparation during restart, and Docker envs recreate the app container from saved env config when needed."
 keywords: "nb app restart,NocoBase CLI,restart app,Docker"
 ---
 
 # nb app restart
 
-Stop and then start the NocoBase app for a selected env. Local envs reuse the `nb app stop` and `nb app start` flow; Docker envs remove the current container first, then recreate the app container from saved env config.
+Stop and then start the NocoBase app for a selected env. When applicable, the CLI first synchronizes the commercial plugins allowed by the current license. Then local envs reuse the `nb app stop` and `nb app start` flow and, by default, automatically complete install or upgrade preparation before starting again; Docker envs remove the current container first, then recreate the app container from saved env config.
 
 ## Usage
 
@@ -20,11 +20,7 @@ nb app restart [flags]
 | --- | --- | --- |
 | `--env`, `-e` | string | CLI env name to restart; uses the current env if omitted |
 | `--yes`, `-y` | boolean | When an explicitly passed `--env` targets a different env than the current env, skip the interactive confirmation prompt |
-| `--quickstart` | boolean | Start the app in quickstart mode after stopping |
-| `--port`, `-p` | string | Override the `appPort` saved in env config |
 | `--daemon`, `-d` / `--no-daemon` | boolean | Whether to run in daemon mode after stopping; enabled by default |
-| `--instances`, `-i` | integer | Number of instances to run after stopping |
-| `--launch-mode` | string | Launch mode: `pm2` or `node` |
 | `--verbose` | boolean | Show underlying stop and start command output |
 
 ## Examples
@@ -32,18 +28,14 @@ nb app restart [flags]
 ```bash
 nb app restart
 nb app restart --env local
-nb app restart --env local --quickstart
-nb app restart --env local --port 12000
 nb app restart --env local --no-daemon
-nb app restart --env local --instances 2
-nb app restart --env local --launch-mode pm2
 nb app restart --env local --verbose
 nb app restart --env local-docker
 ```
 
 If you explicitly pass `--env` and it differs from the current env, the CLI asks for confirmation first. In non-interactive terminals or AI agent sessions, add `--yes` yourself or run `nb env use <name>` first and try again.
 
-Whenever the CLI needs to wait for readiness, it checks `__health_check`: it prints one waiting line first, then one progress line every 10 seconds until the app becomes available or times out. If you pass `--no-daemon` for a local env, the app runs in the foreground, so the CLI does not keep waiting for the readiness check after startup.
+By default, when applicable, the CLI first runs `nb license plugins sync --skip-if-no-license` to synchronize the commercial plugins allowed by the current license. Then local envs automatically complete any required install or upgrade preparation before starting again, and Docker envs complete that step before recreating the container. Whenever the CLI needs to wait for readiness, it checks `__health_check`: it prints one waiting line first, then one progress line every 10 seconds until the app becomes available or times out. If you pass `--no-daemon` for a local env, the app runs in the foreground, so the CLI does not keep waiting for the readiness check after startup.
 
 ## Related Commands
 

package/dist/ai/docs/nocobase/api/cli/app/start.md

@@ -1,12 +1,12 @@
 ---
 title: "nb app start"
-description: "nb app start command reference: start the NocoBase app for a selected env and recreate the Docker app container from saved env config when needed."
+description: "nb app start command reference: start the NocoBase app for a selected env; when applicable, the CLI first synchronizes the commercial plugins allowed by the current license, then local envs automatically complete install or upgrade preparation before startup, and Docker envs recreate the app container from saved env config."
 keywords: "nb app start,NocoBase CLI,start app,Docker,pm2"
 ---
 
 # nb app start
 
-Start the NocoBase app for a selected env. npm/Git installations run local app commands; Docker installations recreate the saved app container from the saved env config.
+Start the NocoBase app for a selected env. When applicable, the CLI first synchronizes the commercial plugins allowed by the current license. Then npm/Git installations automatically complete install or upgrade preparation before running local app commands; Docker installations recreate the saved app container from saved env config.
 
 ## Usage
 
@@ -20,11 +20,7 @@ nb app start [flags]
 | --- | --- | --- |
 | `--env`, `-e` | string | CLI env name to start; uses the current env if omitted |
 | `--yes`, `-y` | boolean | When an explicitly passed `--env` targets a different env than the current env, skip the interactive confirmation prompt |
-| `--quickstart` | boolean | Start the app in quickstart mode |
-| `--port`, `-p` | string | Override the `appPort` saved in env config |
 | `--daemon`, `-d` / `--no-daemon` | boolean | Whether to run in daemon mode; enabled by default |
-| `--instances`, `-i` | integer | Number of instances to run |
-| `--launch-mode` | string | Launch mode: `pm2` or `node` |
 | `--verbose` | boolean | Show underlying local or Docker command output |
 
 ## Examples
@@ -32,19 +28,15 @@ nb app start [flags]
 ```bash
 nb app start
 nb app start --env local
-nb app start --env local --quickstart
-nb app start --env local --port 12000
 nb app start --env local --daemon
 nb app start --env local --no-daemon
-nb app start --env local --instances 2
-nb app start --env local --launch-mode pm2
 nb app start --env local --verbose
 nb app start --env local-docker
 ```
 
 If you explicitly pass `--env` and it differs from the current env, the CLI asks for confirmation first. In non-interactive terminals or AI agent sessions, add `--yes` yourself or run `nb env use <name>` first and try again.
 
-By default, local envs start in daemon mode and Docker envs recreate the app container from saved env config. Whenever the CLI needs to wait for readiness, it checks `__health_check`: it prints one waiting line first, then one progress line every 10 seconds until the app becomes available or times out.
+By default, when applicable, the CLI first runs `nb license plugins sync --skip-if-no-license` to synchronize the commercial plugins allowed by the current license. Then local envs automatically complete any required install or upgrade preparation before starting in daemon mode, and Docker envs recreate the app container from saved env config. Whenever the CLI needs to wait for readiness, it checks `__health_check`: it prints one waiting line first, then one progress line every 10 seconds until the app becomes available or times out.
 
 If you pass `--no-daemon` for a local env, the app runs in the foreground. In that case, the CLI does not keep waiting for the readiness check after startup.
 

package/dist/ai/docs/nocobase/api/cli/app/stop.md

@@ -1,12 +1,14 @@
 ---
-title: "nb app stop"
-description: "nb app stop command reference: stop the NocoBase app and remove the Docker app container for a selected env."
-keywords: "nb app stop,NocoBase CLI,stop app,Docker"
+title: 'nb app stop'
+description: 'nb app stop command reference: stop the NocoBase application for the specified env, and optionally clean up the CLI-managed built-in database container as well.'
+keywords: 'nb app stop,NocoBase CLI,stop application,Docker,with-db,built-in database'
 ---
 
 # nb app stop
 
-Stop the NocoBase app for a selected env. npm/Git installations stop local app processes; Docker installations remove the saved app container.
+Stop the NocoBase application for the specified env. For npm/Git installations, this stops the local application process. For Docker installations, it removes the saved application container.
+
+If you pass `--with-db` and this env uses a CLI-managed built-in database, the command will also clean up the database container. If this env uses an external database, the database resources will not be touched.
 
 ## Usage
 
@@ -16,25 +18,33 @@ nb app stop [flags]
 
 ## Parameters
 
-| Parameter | Type | Description |
-| --- | --- | --- |
-| `--env`, `-e` | string | CLI env name to stop; uses the current env if omitted |
-| `--yes`, `-y` | boolean | When an explicitly passed `--env` targets a different env than the current env, skip the interactive confirmation prompt |
-| `--verbose` | boolean | Show underlying local or Docker command output |
+| Parameter     | Type    | Description                                                                                                  |
+| ------------- | ------- | ------------------------------------------------------------------------------------------------------------ |
+| `--env`, `-e` | string  | Name of the CLI env to stop; uses the current env if omitted                                                 |
+| `--yes`, `-y` | boolean | Skip the interactive confirmation when the env explicitly pointed to by `--env` differs from the current env |
+| `--with-db`   | boolean | Also clean up the database container when a CLI-managed built-in database exists                             |
+| `--verbose`   | boolean | Show underlying local or Docker command output                                                               |
 
 ## Examples
 
 ```bash
 nb app stop
 nb app stop --env local
+nb app stop --env local --with-db
 nb app stop --env local --verbose
 nb app stop --env local-docker
 ```
 
-If you explicitly pass `--env` and it differs from the current env, the CLI asks for confirmation first. In non-interactive terminals or AI agent sessions, add `--yes` yourself or run `nb env use <name>` first and try again.
+## Notes
+
+The CLI checks whether the specified env matches the current env only when you explicitly pass `--env`. If you explicitly specify a different env, an interactive terminal will ask for confirmation first; in a non-interactive terminal or AI agent scenario, you need to explicitly add `--yes` yourself, or run `nb env use <name>` first and then try again.
+
+`--with-db` affects only CLI-managed built-in database containers. In general, if you only want to stop the application itself, you do not need this flag; add it only when you also want to stop the built-in database runtime on the current machine.
+
+This command can operate only on local or Docker runtimes on the current machine. If an env is only an HTTP API connection, or is a reserved SSH env, `nb app stop` cannot stop it remotely for you.
 
-## Related Commands
+## Related commands
 
 - [`nb app start`](./start.md)
 - [`nb app restart`](./restart.md)
-- [`nb app down`](./down.md)
+- [`nb env remove`](../env/remove.md)

package/dist/ai/docs/nocobase/api/cli/app/upgrade.md

@@ -1,12 +1,12 @@
 ---
 title: "nb app upgrade"
-description: "nb app upgrade command reference: stop the app, replace the saved source or image, then start the selected NocoBase app again."
+description: "nb app upgrade command reference: stop the app, replace the saved source or image, then upgrade and start the selected NocoBase app."
 keywords: "nb app upgrade,NocoBase CLI,upgrade,update,Docker image"
 ---
 
 # nb app upgrade
 
-Upgrade a selected NocoBase app. The CLI stops the current app, replaces the saved source or image by default, synchronizes commercial plugins, quickstarts the app again, and refreshes the env runtime at the end. Docker envs recreate the app container from the saved env config during startup.
+Upgrade a selected NocoBase app. The CLI stops the current app, replaces the saved source or image by default, synchronizes commercial plugins, upgrades and starts the app, and refreshes the env runtime at the end. Docker envs recreate the app container from the saved env config during startup.
 
 ## Usage
 
@@ -21,7 +21,7 @@ nb app upgrade [flags]
 | `--env`, `-e` | string | CLI env name to upgrade; uses the current env if omitted |
 | `--yes`, `-y` | boolean | When an explicitly passed `--env` targets a different env than the current env, skip the interactive confirmation prompt |
 | `--force`, `-f` | boolean | Skip the upgrade confirmation prompt. Required in non-interactive terminals and AI agent sessions |
-| `--skip-download`, `-s` | boolean | Restart from the currently saved local source or Docker image without downloading updates first; also skips `nb license plugins sync` |
+| `--skip-download`, `-s` | boolean | Skip source or image download and run the upgrade-and-start flow against the currently saved local source or Docker image; also skips `nb license plugins sync` |
 | `--version` | string | Override the target version for this upgrade; when the upgrade succeeds, the new version is written back to `downloadVersion` in the env config |
 | `--verbose` | boolean | Show underlying update and restart command output |
 
@@ -48,13 +48,13 @@ By default, `nb app upgrade` runs these steps:
 1. `nb app stop`
 2. `nb source download --replace`
 3. `nb license plugins sync --skip-if-no-license`
-4. `nb app start --quickstart`
+4. `nb app start`
 5. Save the new `downloadVersion` when needed
 6. `nb env update`
 
-When `--skip-download` is passed, the CLI skips steps 2 and 3 and restarts the currently saved source or image directly. If `--version` is also passed, the CLI does not download that version during this run; instead it only saves it as the new `downloadVersion` after a successful restart so later upgrades can use it.
+When `--skip-download` is passed, the CLI skips steps 2 and 3 and runs the upgrade-and-start flow directly against the currently saved source or image. If `--version` is also passed, the CLI does not download that version during this run; instead it only saves it as the new `downloadVersion` after a successful start so later upgrades can use it.
 
-Step 4 waits for the app to pass `__health_check`. During this wait, the CLI prints one waiting line first, then one progress line every 10 seconds until the app is ready or the health check times out.
+Step 4 automatically completes any required upgrade preparation for the current code state, then waits for the app to pass `__health_check`. During this wait, the CLI prints one waiting line first, then one progress line every 10 seconds until the app is ready or the health check times out.
 
 If the final `nb env update` step fails, the upgrade still counts as successful. The CLI prints a warning and tells you to run `nb env update <envName>` manually afterward.
 

package/dist/ai/docs/nocobase/api/cli/backup/create.md

@@ -0,0 +1,49 @@
+---
+title: 'nb backup create'
+description: 'nb backup create command reference: create a backup through the selected env and download the backup file locally.'
+keywords: 'nb backup create,NocoBase CLI,create backup,download backup,nbdata'
+---
+
+# nb backup create
+
+Create a backup through the selected env and download the backup file locally. When `--output` is omitted, the CLI saves the file to the current working directory and reuses the backup filename returned by the remote side—usually `backup_*.nbdata`.
+
+## Usage
+
+```bash
+nb backup create [flags]
+```
+
+## Parameters
+
+| Parameter             | Type    | Description                                                                                                                                                    |
+| --------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--env`, `-e`         | string  | Name of the CLI env for which to create the backup; uses the current env when omitted                                                                          |
+| `--yes`, `-y`         | boolean | Skip interactive confirmation when the env explicitly pointed to by `--env` differs from the current env                                                       |
+| `--output`, `-o`      | string  | Download target path. Saves to the current directory when omitted; if it points to an existing directory, the remote backup filename is appended automatically |
+| `--json-output`, `-j` | boolean | Output the final result as JSON, including the fields `env`, `name`, and `output`                                                                              |
+
+## Examples
+
+```bash
+nb backup create
+nb backup create --output ./backups
+nb backup create --output ./backups/base.nbdata
+nb backup create --env e2e --output ./backups --yes
+nb backup create --env e2e --json-output
+```
+
+## Notes
+
+The CLI checks whether `--env` matches the current env only when you explicitly pass `--env`. If a different env is explicitly specified, an interactive terminal asks for confirmation first; in a non-interactive terminal or AI agent scenario, you need to explicitly add `--yes` yourself, or run `nb env use <name>` first and then retry.
+
+The creation flow is divided into two steps: first, it calls the backup API of the target env to create a remote backup, then it polls the status every 2 seconds; after the backup is complete, it downloads the file locally. If the remote side still returns `inProgress: true` after 600 seconds, the command exits with a timeout.
+
+`--output` can be either a file path or an existing directory path. The CLI recognizes only an existing path as a directory; if the path does not exist, it is treated as a target file path.
+
+After passing `--json-output`, the CLI no longer outputs progress text and instead prints the final JSON result directly. This mode is better suited for further consumption by scripts and agent workflows.
+
+## Related commands
+
+- [`nb backup restore`](./restore.md)
+- [`nb env update`](../env/update.md)

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

@@ -0,0 +1,46 @@
+---
+title: 'nb backup'
+description: 'nb backup command reference: create a NocoBase backup and download it locally, or restore a local backup file to the target env.'
+keywords: 'nb backup,NocoBase CLI,backup,restore,nbdata'
+---
+
+# nb backup
+
+Create or restore a NocoBase backup. `nb backup create` creates a remote backup in the target env and then downloads the backup file locally; `nb backup restore` uploads a local backup file to the target env and waits for the application to become ready again.
+
+## Usage
+
+```bash
+nb backup <command>
+```
+
+## Subcommands
+
+| Command                             | Description                                   |
+| ----------------------------------- | --------------------------------------------- |
+| [`nb backup create`](./create.md)   | Create a backup and download it locally       |
+| [`nb backup restore`](./restore.md) | Restore a local backup file to the target env |
+
+## Examples
+
+```bash
+nb backup create
+nb backup create --env app1 --output ./backups
+nb backup create --env app1 --output ./backups/result.nbdata
+nb backup restore --env app1 --file ./backups/backup_20260520_190408_8397.nbdata --yes --force
+```
+
+## Notes
+
+Before execution, the CLI first checks whether the target env exposes runtime commands related to backup. If commands are missing, it automatically refreshes the runtime cache once; if the `nb api backup ...` capability is still missing after the refresh, it means the target env has not yet enabled or synchronized backup/restore capabilities, and you need to handle the target application itself first.
+
+Specifically:
+
+- `nb backup create` depends on `nb api backup create`, `nb api backup status`, and `nb api backup download`
+- `nb backup restore` depends on `nb api backup restore-upload`
+
+## Related commands
+
+- [`nb env update`](../env/update.md)
+- [`nb app restart`](../app/restart.md)
+- [`nb api`](../api/index.md)

package/dist/ai/docs/nocobase/api/cli/backup/restore.md

@@ -0,0 +1,46 @@
+---
+title: 'nb backup restore'
+description: 'Reference for the nb backup restore command: restore a local backup file to the target env.'
+keywords: 'nb backup restore,NocoBase CLI,restore backup,restore,nbdata'
+---
+
+# nb backup restore
+
+Restore a local backup file to the target env. Typically, a `*.nbdata` file is used here. Restoring will overwrite the target application data, so the CLI asks for confirmation by default.
+
+## Usage
+
+```bash
+nb backup restore --file <path> [flags]
+```
+
+## Options
+
+| Option         | Type    | Description                                                                                                        |
+| -------------- | ------- | ------------------------------------------------------------------------------------------------------------------ |
+| `--env`, `-e`  | string  | Name of the CLI env to restore to; uses the current env if omitted                                                 |
+| `--yes`, `-y`  | boolean | Skip interactive confirmation when the env explicitly specified by `--env` is different from the current env       |
+| `--file`, `-f` | string  | Path to the local backup file; required                                                                            |
+| `--force`      | boolean | Confirm overwriting application data; must be passed explicitly in non-interactive terminals and AI agent sessions |
+
+## Examples
+
+```bash
+nb backup restore --file ./backups/base.nbdata --force
+nb backup restore --env e2e --file ./backups/base.nbdata --yes --force
+```
+
+## Notes
+
+The CLI checks whether `--env` matches the current env only when you pass `--env` explicitly. If a different env is explicitly specified, an interactive terminal will ask for confirmation first; in non-interactive terminals or AI agent scenarios, you must explicitly add `--yes` yourself, or run `nb env use <name>` first and then try again.
+
+Before execution, the CLI checks whether the path specified by `--file` exists and confirms that it is a regular file. If the path does not exist or points to a directory, the command fails immediately.
+
+If `--force` is not provided, an interactive terminal will prompt for confirmation again, clearly indicating that this restore will overwrite application data. In non-interactive terminals and AI agent sessions, if `--force` is missing, the CLI refuses to execute directly and provides a rerun hint that can be copied directly. If it is also a cross-env operation, you usually need to provide both `--yes` and `--force`.
+
+After the upload succeeds, the CLI continues waiting for the target application to pass `__health_check` again. In other words, when the command returns successfully, the application has usually been restored to an accessible state.
+
+## Related commands
+
+- [`nb backup create`](./create.md)
+- [`nb app restart`](../app/restart.md)

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

@@ -1,12 +1,12 @@
 ---
-title: "nb config delete"
-description: "nb config delete command reference: delete an explicitly configured CLI setting."
-keywords: "nb config delete,NocoBase CLI,configuration"
+title: 'nb config delete'
+description: 'nb config delete command reference: delete an explicitly set CLI configuration item.'
+keywords: 'nb config delete,NocoBase CLI,delete configuration'
 ---
 
 # nb config delete
 
-Delete an explicitly configured CLI setting. After deletion, the CLI falls back to the default value for that key.
+Delete an explicitly set CLI configuration item. After deletion, the configuration item falls back to its default value.
 
 ## Usage
 
@@ -16,22 +16,24 @@ nb config delete <key>
 
 ## Parameters
 
-| Parameter | Type | Description |
-| --- | --- | --- |
-| `<key>` | string | Configuration key: `locale`, `update.policy`, `license.pkg-url`, `docker.network`, `docker.container-prefix`, `bin.docker`, `bin.git`, or `bin.yarn` |
+| Parameter | Type   | Description                                                                                                                             |
+| --------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------- |
+| `<key>` | string | Configuration item name. See [`nb config`](./index.md) for supported values |
 
 ## Examples
 
 ```bash
 nb config delete locale
 nb config delete update.policy
-nb config delete license.pkg-url
 nb config delete docker.network
 nb config delete docker.container-prefix
+nb config delete proxy.nb-cli-root
+nb config delete proxy.upstream-host
+nb config delete bin.nginx
 nb config delete bin.git
 ```
 
-## Related Commands
+## Related commands
 
 - [`nb config set`](./set.md)
 - [`nb config get`](./get.md)