@nocobase/plugin-ai 2.1.1 → 2.1.3

package/dist/ai/docs/nocobase/ai/claude-code/index.md

@@ -63,7 +63,7 @@ Before starting, make sure you have the following environment ready:
 
 - Claude Code installed (`npm install -g @anthropic-ai/claude-code`)
 - Node.js >= 22 (for running NocoBase CLI and Skills)
-- If you already have a NocoBase instance, **AI capabilities are evolving rapidly and only the latest beta version provides the full experience. Minimum version >= 2.1.0-beta.20, latest version strongly recommended.**
+- If you already have a NocoBase instance, **AI capabilities are evolving rapidly. The minimum required version is NocoBase 2.1.0, and we recommend updating to the latest version.**
 
 ## Quick Start
 

package/dist/ai/docs/nocobase/ai/codex/index.md

@@ -61,7 +61,7 @@ Before starting, make sure you have the following environment ready:
 
 - Codex installed (`npm install -g @openai/codex`)
 - Node.js >= 22 (for running NocoBase CLI and Skills)
-- If you already have a NocoBase instance, **AI capabilities are evolving rapidly and only the latest beta version provides the full experience. Minimum version >= 2.1.0-beta.20, latest version strongly recommended.**
+- If you already have a NocoBase instance, **AI capabilities are evolving rapidly. The minimum required version is NocoBase 2.1.0, and we recommend updating to the latest version.**
 
 ## Quick Start
 

package/dist/ai/docs/nocobase/ai/hermes-agent/index.md

@@ -69,7 +69,7 @@ Before starting, make sure you have the following environment ready:
 
 - A server running Hermes Agent (Linux / macOS, Python 3.10+)
 - Node.js >= 22 (for running NocoBase CLI and Skills)
-- If you already have a NocoBase instance, **AI capabilities are evolving rapidly and only the latest beta version provides the full experience. Minimum version >= 2.1.0-beta.20, latest version strongly recommended.**
+- If you already have a NocoBase instance, **AI capabilities are evolving rapidly. The minimum required version is NocoBase 2.1.0, and we recommend updating to the latest version.**
 
 Installing Hermes requires just one command:
 

package/dist/ai/docs/nocobase/ai/index.md

@@ -92,7 +92,7 @@ features:
     items:
       - title: NocoBase CLI
         details: The command-line tool for NocoBase — install and you're ready to go, with built-in AI Skills that let your AI assistant directly operate NocoBase.
-        link: /api/cli/
+        link: /nocobase-cli/
       - title: NocoBase Skills
         details: Domain knowledge packages installable into AI Agents, enabling AI to understand NocoBase's capabilities and conventions.
         link: /ai-builder#nocobase-skills

package/dist/ai/docs/nocobase/ai/install-nocobase-app.md

@@ -0,0 +1,104 @@
+---
+title: Install NocoBase App
+description: Install NocoBase CLI and quickly create a new NocoBase application with `nb init --ui`, so your AI Agent can start working right away.
+---
+
+# Install NocoBase App
+
+## Prerequisites
+
+- Node.js >= 22
+- Yarn 1.x
+- If you plan to install with Docker, make sure Docker is already running
+
+## Step 1: Install CLI
+
+Install NocoBase CLI globally first:
+
+```bash
+npm install -g @nocobase/cli
+nb --version
+```
+
+If you often work with multiple terminals or want to operate in parallel with AI Agents, we also recommend running `nb session setup` once. This lets each session keep its own `current env`, so they are less likely to affect one another.
+
+## Step 2: Initialize the app
+
+We recommend opening the visual wizard directly:
+
+```bash
+nb init --ui
+```
+
+![2026-06-11-20-14-32](https://static-docs.nocobase.com/2026-06-11-20-14-32.png)
+
+Different setup paths show slightly different steps. If you follow the default `Install a new app` path, you will usually see these six steps:
+
+1. `Getting started` - set the `--env` identifier and choose `Install a new app`
+2. `App environment` - set the app basics, storage location, and runtime port
+3. `App source and version` - choose how to get the app and which source and version to use
+4. `Configure the database` - choose the built-in database or a custom database
+5. `Create an admin account` - set up the first admin account
+6. `Connection & authentication` - enter the app access URL and choose an authentication method
+
+If you prefer terminal interaction, you can also run:
+
+```bash
+nb init
+```
+
+If you need to initialize in scripts or CI, use non-interactive mode:
+
+```bash
+nb init --yes --env app1
+```
+
+:::tip Install on a remote server
+
+If you run `nb init --ui` on a server, we recommend changing the default host to that server's IP first. That way, you can open the wizard from your local browser.
+
+```bash
+nb config set default-ui-host <server-ip>
+nb config set default-api-host <server-ip>
+```
+
+:::
+
+## Step 3: Confirm the app is ready
+
+After installation, it is usually worth confirming these three things first:
+
+- The env has been saved successfully
+- The app has started normally
+- You can sign in with the administrator account
+
+Common commands:
+
+```bash
+nb env list
+nb env info
+nb app logs
+```
+
+For a local default installation, you can usually open `http://localhost:13000` in your browser directly. After signing in, start a new AI Agent session or restart the current one, and the AI can begin working with this NocoBase app.
+
+CLI configuration is stored in `~/.nocobase/` by default, so AI Agents can usually access it from any working directory.
+
+If this app will be exposed to real users later, we do not recommend using `IP + port` for the long term. The next step is usually to put it behind a reverse proxy and enable HTTPS.
+
+## Next Steps
+
+- If you already have a running NocoBase app, see [AI Agent Integration Guide](./quick-start.mdx)
+- If you want to manage app startup, shutdown, logs, and upgrades, see [Manage apps](../nocobase-cli/operations/manage-app.md)
+- If you want to continue with production deployment, see [Install apps with CLI](../nocobase-cli/installation/cli.md) and [Production deployment overview](../nocobase-cli/production/index.md)
+- If you want AI to start building apps, see [AI Builder](../ai-builder/index.md)
+
+## Related Links
+
+- [Installation and Version Comparison](../get-started/quickstart.md) — Compare installation methods and version channels first, then decide how to install
+- [AI Agent Integration Guide](./quick-start.mdx) — Connect an existing NocoBase app and let your AI Agent start working
+- [`nb init` command reference](../api/cli/init.md) — Initialize a new app, take over an existing local app, or connect a remote app
+- [`nb env info` command reference](../api/cli/env/info.md) — View the connection details and runtime configuration of the current env
+- [NocoBase CLI](../api/cli/index.md) — Full reference for all `nb` commands
+- [Manage apps](../nocobase-cli/operations/manage-app.md) — Start, stop, restart, view logs, and upgrade apps
+- [Multiple environment management](../nocobase-cli/operations/multi-environment.md) — Common operations when you maintain multiple envs at the same time

package/dist/ai/docs/nocobase/ai/openclaw/index.md

@@ -63,7 +63,7 @@ Before starting, make sure you have the following environment ready:
 
 - A deployed OpenClaw Agent ([one-click Lark deployment](https://openclaw.feishu.cn) or local deployment)
 - Node.js >= 22 (for running NocoBase CLI and Skills)
-- If you already have a NocoBase instance, **AI capabilities are evolving rapidly and only the latest beta version provides the full experience. Minimum version >= 2.1.0-beta.20, latest version strongly recommended.**
+- If you already have a NocoBase instance, **AI capabilities are evolving rapidly. The minimum required version is NocoBase 2.1.0, and we recommend updating to the latest version.**
 
 :::warning Note
 

package/dist/ai/docs/nocobase/ai/opencode/index.md

@@ -63,7 +63,7 @@ Before starting, make sure you have the following environment ready:
 
 - OpenCode installed ([installation guide](https://opencode.ai/docs/))
 - Node.js >= 22 (for running NocoBase CLI and Skills)
-- If you already have a NocoBase instance, **AI capabilities are evolving rapidly and only the latest beta version provides the full experience. Minimum version >= 2.1.0-beta.20, latest version strongly recommended.**
+- If you already have a NocoBase instance, **AI capabilities are evolving rapidly. The minimum required version is NocoBase 2.1.0, and we recommend updating to the latest version.**
 
 ## Quick Start
 

package/dist/ai/docs/nocobase/ai/quick-start.mdx

@@ -2,7 +2,6 @@
 title: "AI Agent Integration Guide"
 description: "Install NocoBase CLI, connect to or install a NocoBase application, and let AI Agents start operating your business system."
 keywords: "NocoBase CLI,AI Agent,integration,connect,installation,Skills,quick start"
-sidebar: false
 ---
 
 # AI Agent Integration Guide
@@ -58,15 +57,16 @@ Configuration files and application data are stored in your home directory by de
 
 :::
 
-The browser will automatically open a visual configuration page, guiding you through 5 steps:
+The browser will automatically open a visual configuration page, guiding you through 6 steps:
 
-1. **Start Configuration** — Set the application name (also used as the CLI environment name), select "Fresh Installation"
-2. **Create Application** — Choose the installation method (Docker / npm / Git), set port and other basic configurations
-3. **Download Application Files** — Select source and version, download NocoBase source code or image
-4. **Configure Database** — Use the built-in database or configure an external database (PostgreSQL, MySQL, MariaDB)
-5. **Create Admin Account** — Set the admin email and password
+1. "Getting started" — Choose whether to install a new app, manage a local app, or connect a remote app.
+2. "App environment" — Set the app basics, storage location, and runtime port.
+3. "App source and version" — Choose how to get the app and which source and version to use.
+4. "Configure the database" — Use built-in or custom.
+5. "Create an admin account" — Set up the first admin.
+6. "Connection & authentication" — Enter the app access URL and choose an authentication method.
 
-![nocobase cli visual wizard](https://static-docs.nocobase.com/2026-04-29-15-55-19.png)
+![nocobase cli visual wizard](https://static-docs.nocobase.com/2026-06-11-20-14-32.png)
 
 After installation is complete, open your browser and visit `http://localhost:13000` (default port), then log in with the admin account you just set up.
 
@@ -92,7 +92,7 @@ After configuration is complete, restart your AI Agent session and you can start
 
 ## Connect AI Agent to an Existing NocoBase
 
-If you already have a running NocoBase instance, you can connect AI Agent to it directly. **Since AI capabilities are evolving rapidly, only the latest beta version provides the full experience. The minimum required version is 2.1.0-beta.20 — we strongly recommend updating to the latest.**
+If you already have a running NocoBase instance, you can connect AI Agent to it directly. **Since AI capabilities are evolving rapidly, the minimum required version is NocoBase 2.1.0, and we recommend updating to the latest version.**
 
 <Tabs>
 <Tab label="Manual Connection" value="manual-connect">
@@ -116,12 +116,12 @@ Configuration files are stored in your home directory by default. See [NB_CLI_RO
 
 :::
 
-The browser will automatically open a visual configuration page. In the first step "Start Configuration", select "Connect to Existing Application", then:
+The browser will automatically open a visual configuration page. In the first step "Start Configuration", select "Remote Connection", then:
 
 1. **Enter API Address** — Input the API address of your existing NocoBase instance (e.g., `http://localhost:13000/api`)
 2. **Select Authentication Method** — Choose an [authentication method](../ai-builder/security) (OAuth is recommended for quick setup)
 
-![nocobase cli visual wizard](https://static-docs.nocobase.com/2026-04-29-15-55-55.png)
+![nocobase cli visual wizard](https://static-docs.nocobase.com/2026-06-11-21-18-31.png)
 
 No need to configure installation method, database, or admin account — the wizard will skip those steps.
 
@@ -132,7 +132,7 @@ Start a new or restart the AI Agent session, and you can let the AI Agent start
 </Tab>
 <Tab label="Connect with AI Agent" value="ai-connect">
 
-Copy the prompt below to your AI assistant. It will complete CLI installation and guide you through connecting to your existing NocoBase instance. Select "Connect to Existing Application" in the first step of the visual wizard:
+Copy the prompt below to your AI assistant. It will complete CLI installation and guide you through connecting to your existing NocoBase instance. Select "Remote Connection" in the first step of the visual wizard:
 
 ```
 Help me install NocoBase CLI and complete initialization: https://docs.nocobase.com/ai/ai-quick-start.md (please read the linked content directly)
@@ -145,6 +145,13 @@ After configuration is complete, restart your AI Agent session and you can start
 
 ## What's Next
 
+### Production Installation and Deployment
+
+If you're preparing to deploy NocoBase to production, this order usually works best:
+
+1. [Install using CLI](../nocobase-cli/installation/cli.md) - the complete installation flow. This is the right place when you want to install CLI from scratch, initialize env, and confirm the app is already running on your server
+2. [Production deployment overview](../nocobase-cli/production/index.md) - the next step after the app is running. This mainly covers autostart, reverse proxy, domain setup, and HTTPS
+
 ### Manage Application Environments
 
 If you need to manage existing NocoBase instances (such as test or production environments), or switch between multiple environments, see [Environment Management](../ai-builder/env-bootstrap) — covering environment checks, adding environments, upgrades, and troubleshooting.
@@ -172,4 +179,4 @@ If you already have a NocoBase application running, or have successfully complet
 - [AI Employees](../ai-employees/index.md) — Collaborate with AI in the business interface
 - [Environment Management](../ai-builder/env-bootstrap) — Environment checks, adding environments, upgrades, and troubleshooting
 - [NocoBase CLI Command Reference](../api/cli/index.md) — Full parameter documentation for all commands
-- [Installation Methods and Version Comparison](../get-started/quickstart) — Different installation methods and version channels for NocoBase
+- [Installation Methods and Version Comparison](../ai/quickstart) — Different installation methods and version channels for NocoBase

package/dist/ai/docs/nocobase/ai/workbuddy/index.md

@@ -70,7 +70,7 @@ Before starting, make sure you have the following environment ready:
 
 - WorkBuddy account ([registration portal](https://www.codebuddy.cn))
 - Node.js >= 22 (for running NocoBase CLI and Skills)
-- If you already have a NocoBase instance, **AI capabilities are evolving rapidly and only the latest beta version provides the full experience. Minimum version >= 2.1.0-beta.20, latest version strongly recommended.**
+- If you already have a NocoBase instance, **AI capabilities are evolving rapidly. The minimum required version is NocoBase 2.1.0, and we recommend updating to the latest version.**
 
 :::warning Note
 

package/dist/ai/docs/nocobase/ai-builder/index.md

@@ -95,13 +95,27 @@ The AI first outputs a design plan, then builds everything at once after confirm
 
 To learn more about building complete systems, see [Solutions](./dsl-reconciler).
 
+### Build a milestone, and the AI saves a restorable version for you
+
+After finishing a page, a set of data tables, or a workflow, let the AI save the current state as a version — if a configuration goes wrong, you can always roll back to the last clear milestone.
+
+```
+Save the current build as a version: completed customer management page, filter area, and edit form configuration
+```
+
+![AI creates a version after building](https://static-docs.nocobase.com/20260611115804.png)
+
+The AI won't save a version every time it changes a field; it only saves after completing and verifying a clear milestone, which keeps the version list easy to read and makes it easier to decide where to roll back to.
+
+To learn more about version control, see [Version Control](./version-control).
+
 ## Security & Audit
 
 Before letting an AI Agent operate NocoBase, we recommend understanding the authentication methods, permission controls, and operation auditing — ensuring the AI only does what it should, with every step recorded. See [Security & Audit](./security).
 
 ## NocoBase Skills
 
-[NocoBase Skills](https://github.com/nocobase/skills) are domain knowledge packages that can be installed into AI Agents, enabling AI to understand NocoBase's configuration system. NocoBase provides 8 Skills covering the entire building workflow:
+[NocoBase Skills](https://github.com/nocobase/skills) are domain knowledge packages that can be installed into AI Agents, enabling AI to understand NocoBase's configuration system. NocoBase provides 9 Skills covering the entire building workflow:
 
 - [Environment Management](./env-bootstrap) — Environment checks, installation, deployment, upgrades, and troubleshooting
 - [Data Modeling](./data-modeling) — Create and manage data tables, fields, and relationships
@@ -111,6 +125,7 @@ Before letting an AI Agent operate NocoBase, we recommend understanding the auth
 - [Solutions](./dsl-reconciler) — Batch-build entire business systems from YAML
 - [Plugin Management](./plugin-manage) — View, enable, and disable plugins
 - [Release Management](./publish) — Cross-environment releases, backup & restore, and migration
+- [Version Control](./version-control) — Save restorable versions after completed milestones
 
 :::tip
 

package/dist/ai/docs/nocobase/ai-builder/version-control.md

@@ -0,0 +1,120 @@
+---
+title: "Version Control"
+description: "The Version Control Skill (nocobase-revision) creates restorable application versions after AI Builder completes milestone work."
+keywords: "AI Builder,version control,nocobase-revision,nb revision create,restore version"
+---
+
+# Version Control
+
+:::tip Prerequisites
+
+- Before reading this page, install the NocoBase CLI and complete initialization as described in [AI Builder Quick Start](./index.md)
+- Enable the Backup Management and Version Control plugins
+- Community and Standard editions do not include the Version Control plugin. If you only need a rollback point before key changes, use [Backup Management](../ops-management/backup-manager/index.mdx)
+
+:::
+
+## Introduction
+
+The Version Control Skill (`nocobase-revision`) creates a restorable application version after AI Builder completes a meaningful milestone. For example, after building a page, creating a group of collections, or configuring a workflow, AI can run `nb revision create` to save the current state.
+
+It does not create a version for every field change. By default, it saves only after a clear milestone is completed and verified, so the version list stays readable and rollback points are easier to choose.
+
+For version lists, manual version creation, restore operations, and retention settings, see the [Version Control plugin guide](../ops-management/version-control/index.md).
+
+## Capabilities
+
+Can do:
+
+- Create a version after a building milestone is completed and verified
+- Write a concise description that explains what was saved
+- Create versions using the current CLI environment
+
+Cannot do:
+
+- Replace the underlying save and restore capabilities of the Backup Management plugin
+- Create versions when the Version Control plugin is not enabled
+- Restore to a version automatically. Use the [Version Control plugin](../ops-management/version-control/index.md) to restore versions
+
+## Prompt Examples
+
+### Scenario A: Save a completed page configuration
+
+```text
+Save the current build as a version: completed customer management page, filter area, and edit form configuration
+```
+
+The Skill turns the description into a concise version note and creates a version.
+
+Command mode:
+
+```bash
+nb revision create "Completed customer management page, filter area, and edit form configuration"
+```
+
+### Scenario B: Save data model and workflow milestones
+
+```text
+The supplier collections and purchase approval workflow have been verified. Create a version for me.
+```
+
+This fits work that spans multiple capabilities. For example, create collections with [Data Modeling](./data-modeling), configure an approval process with [Workflow Management](./workflow), verify the result, then save a version.
+
+### Scenario C: Create a version in a specified environment
+
+```text
+In the dev environment, save a version: completed ticket management page and SLA field configuration
+```
+
+If the specified environment is not the current CLI environment, the Skill confirms the target environment first to avoid saving the version to the wrong application.
+
+Command mode:
+
+```bash
+nb revision create --env dev --yes "Completed ticket management page and SLA field configuration"
+```
+
+## How to Write Version Descriptions
+
+A version description should say what has been completed, not just use a vague label.
+
+Recommended:
+
+- `Completed customer ledger, detail page, and approval submission flow`
+- `Completed supplier collections, purchase request form, and approval workflow`
+- `完成客户台账、详情页与审批提交流程配置`
+
+Not recommended:
+
+- `snapshot`
+- `backup`
+- `test`
+- `version 2`
+- Date or timestamp only
+
+Also, do not include tokens, URLs, passwords, or other sensitive information. Descriptions appear in the version list and should stay clear, readable, and auditable.
+
+## FAQ
+
+**When should I create a version?**
+
+Create one after a milestone that can be reviewed on its own. For example, a page opens and edits correctly, collection relationships have been verified, or a workflow has been saved and its node chain checked.
+
+**Why not create a version after every AI adjustment?**
+
+Too many tiny versions quickly make the list hard to read. A version should usually represent a point you can restore to and continue working from, not a single field rename or button position change.
+
+**Should the result be verified before creating a version?**
+
+Yes. The Version Control Skill is for saving completed and verified work. If a page still errors or a workflow is not confirmed, ask AI to fix and verify it before creating a version.
+
+**Where do I restore a version after it is created?**
+
+Restore it in the version list of the Version Control plugin. Restoring overwrites the current application configuration and the data included in that version. Read the [Version Control plugin guide](../ops-management/version-control/index.md) before operating.
+
+## Related Links
+
+- [Version Control plugin guide](../ops-management/version-control/index.md) — manually create versions, restore versions, and configure version rules
+- [Backup Management](../ops-management/backup-manager/index.mdx) — the underlying capability required by Version Control
+- [AI Builder Overview](./index.md) — overview and installation guide for all AI Builder Skills
+- [Release Management](./publish.md) — cross-environment releases, backup restore, and migration

package/dist/ai/docs/nocobase/api/cli/plugin/import.md

@@ -71,4 +71,4 @@ You do not need to extract anything into `storage/plugins` by hand. `nb plugin i
 
 - [`nb app restart`](../app/restart.md)
 - [`nb plugin enable`](./enable.md)
-- [`Install and upgrade third-party plugins`](../../../quickstart/plugins/third-party.md)
+- [`Install and upgrade third-party plugins`](../../../nocobase-cli/plugins/third-party.md)

package/dist/ai/docs/nocobase/get-started/how-nocobase-works.mdx

@@ -3,4 +3,11 @@
 <video controls width="100%" poster="https://static-docs.nocobase.com/video-cover-home.png">
   <source src="https://static-docs.nocobase.com/nocobase-2-main-1080p-en-v2.mp4" type="video/mp4" />
   Your browser does not support video playback.
-</video>
+</video>
+
+## What's Next
+
+If you've finished the video and want to start right away, there are usually two common paths:
+
+1. If you want to compare installation methods and version channels first, continue with [Installation and Version Comparison](/ai/quickstart)
+2. If you want to install the app right away, continue with [Install NocoBase App](/ai/install-nocobase-app)

package/dist/ai/docs/nocobase/get-started/quickstart.md

@@ -55,4 +55,9 @@ You can install NocoBase in different ways.
 | **Scenarios** | No-code users; users who want to quickly deploy to a server. | Front-end/full-stack developers; team projects; low-code development. | Technical developers; users who want to try unreleased versions. |
 | **Technical Requirement** | ★☆☆☆☆ | ★★★☆☆ | ★★★★★ |
 | **Upgrade Method** | Pull the latest image and restart the container. | Update dependencies with yarn. | Synchronize updates through Git. |
-| **Tutorials** | [<code>Installation</code>](#) [<code>Upgrade</code>](#) [<code>Deployment</code>](#) | [<code>Installation</code>](#) [<code>Upgrade</code>](#) [<code>Deployment</code>](#) | [<code>Installation</code>](#) [<code>Upgrade</code>](#) [<code>Deployment</code>](#) |
+
+![2026-06-11-20-09-54](https://static-docs.nocobase.com/2026-06-11-20-09-54.png)
+
+## What's Next
+
+If you've already picked an installation method, the next step is [Install NocoBase App](/ai/install-nocobase-app). It walks you through installing NocoBase CLI and finishing the app installation and initialization.

package/dist/ai/docs/nocobase/index.md

@@ -11,21 +11,21 @@ hero:
   actions:
     - theme: brand
       text: Get Started
-      link: /quickstart/how-nocobase-works
+      link: /ai/how-nocobase-works
     - theme: alt
       text: GitHub
       link: https://github.com/nocobase/nocobase
 
 features:
   - title: Start
-    details: Get started with NocoBase the traditional way - install, configure, and explore step by step.
+    details: Get started with NocoBase quickly - install, configure, and explore step by step.
     items:
-      - title: NocoBase Getting Started
+      - title: How NocoBase Works
         details: Understand NocoBase's core concepts and basic operations.
-        link: /quickstart/how-nocobase-works
-      - title: Install App
-        details: Quickly install and manage applications.
-        link: /quickstart/installation/cli
+        link: /ai/how-nocobase-works
+      - title: Install NocoBase App
+        details: Use NocoBase CLI to install an application quickly.
+        link: /ai/install-nocobase-app
       - title: Tutorials
         details: Step-by-step tutorials to build real projects with NocoBase from scratch.
         link: /tutorials/v2/
@@ -33,9 +33,6 @@ features:
   - title: AI
     details: An AI-powered new way to get started - use natural language to build, use, and develop.
     items:
-      - title: Quick Start
-        details: Install NocoBase CLI, configure AI Skills, and connect your AI Agent, preparing for AI building, using, and developing NocoBase.
-        link: /ai/quick-start
       - title: AI Builder
         details: Build NocoBase applications from scratch with AI, covering the full process from data modeling, UI configuration, workflows to release management.
         link: /ai-builder

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/index.md

@@ -1,4 +1,4 @@
-# Quick start
+# NocoBase CLI Overview
 
 If this is your first time using this CLI, you don’t need to memorize all the commands at the beginning. Use `nb init --ui` to install an application first, and then continue looking at the rest according to the scenario.
 
@@ -20,7 +20,7 @@ Keep this in mind first, and the subsequent documents will be much smoother.
 
 If you're not sure where to start, it's usually easiest to follow this path:
 
-1. First read [Installation using CLI (recommended)](./installation/cli.md) and complete `nb init` once.
+1. First read [Install using CLI](./installation/cli.md) and complete `nb init` once.
 2. After the application is saved as env, look at [Multiple Environment Management](./operations/multi-environment.md) to confirm the current env, switch env, and check the status.
 3. For daily startup, stop, log and upgrade, continue to see [Manage Application](./operations/manage-app.md).
 4. Before making upgrades, migrations or important changes, see [Backup and Restore](./operations/backup-restore.md).
@@ -32,8 +32,8 @@ The first three steps cover most usage scenarios.
 
 | I want... | Where to look |
 | --- | --- |
-| There is no application yet, first install a new NocoBase and save it as CLI env | [Install using CLI (recommended)](./installation/cli.md) |
-| Already have a running NocoBase and want to access CLI management | [Install using CLI (recommended)](./installation/cli.md) |
+| There is no application yet and you want to install a new NocoBase and save it as a CLI env | [Install using CLI](./installation/cli.md) |
+| You already have a running NocoBase and want to bring it under CLI management | [Install using CLI](./installation/cli.md) |
 | Gradually migrate old installation methods to CLI | [Migrate from old installation methods to CLI](./installation/migration.md) |
 | See which envs are saved locally, switch the current env, and check the status | [Multiple environment management](./operations/multi-environment.md) |
 | Start, stop, restart the application, view logs, or continue the upgrade | [Manage Application](./operations/manage-app.md) |
@@ -44,11 +44,11 @@ The first three steps cover most usage scenarios.
 
 ## When to look at the command reference
 
-This set of quick start documents is more "what do I want to do now". If you already know which command you want to execute and just want to continue to see the complete parameters, just go to [NocoBase CLI Command Reference](../api/cli/index.md).
+This set of quick start documents is more about "what do I want to do now". If you already know which command you want to run and only want the full parameters, go straight to [NocoBase CLI Command Reference](../api/cli/index.md).
 
 The default suggestions are:
 
-- First use the Quick Start document to establish a sense of path
+- First use this overview and the quick start documents to establish a sense of path
 - Then check the parameter details on the specific command page
 
 This makes it easier to get started than reading the complete command tree at first glance.

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/installation/cli.md

@@ -1,4 +1,4 @@
-# Install using CLI (recommended)
+# Install using CLI
 
 After NocoBase 2.1.0, the official CLI-based installation and management method is provided. You can use it to complete installation, connection, upgrade and daily maintenance, and you can also prepare a connectable and operable environment for AI Agent.
 

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/installation/env.md

@@ -2,7 +2,7 @@
 
 This page only applies to applications created or hosted via the NocoBase CLI.
 
-If you have just finished reading [Installation using CLI (recommended)](./cli.md) and have seen the "Installation Directory" section, then the most common problems you will encounter are usually the following:
+If you have just finished reading [Install using CLI](./cli.md) and have seen the "Installation Directory" section, then the most common problems you will encounter are usually the following:
 
 - Where is the `.env` file placed?
 - Which configurations are still suitable to be written into `.env`
@@ -17,7 +17,7 @@ Let’s talk about the conclusion first:
 
 ## Find `app-path` first
 
-In [Install using CLI (recommended)](./cli.md#Installation directory), the default directory structure of CLI env is as follows:
+In [Install using CLI](./cli.md#Installation directory), the default directory structure of CLI env is as follows:
 
 ```text
 <app-path>/
@@ -148,6 +148,6 @@ This is also the mentality that this page most wants to help you build:
 
 ## Where to look next
 
-- If you have not confirmed the application directory structure, first go back to [Install using CLI (recommended)](./cli.md#Installation directory)
+- If you have not confirmed the application directory structure, first go back to [Install using CLI](./cli.md#Installation directory)
 - If you want to modify basic configurations such as ports, time zones, database connections, and public access paths, continue to see [`nb env update`](../../api/cli/env/update.md)
 - If you want to start, restart or view application logs, continue to see [Manage Application](../operations/manage-app.md)

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/installation/migration.md

@@ -99,5 +99,5 @@ By default, it is enough to migrate the test environment first. Only migrate the
 
 ## Where to look next
 
-- If you are ready to install and manage applications in a new way, continue to [Installation using CLI (recommended)](./cli.md)
+- If you are ready to install and manage applications in a new way, continue to [Install using CLI](./cli.md)
 - If you just continue to use the original installation method, just go back to the installation and upgrade document entry above.

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/production/index.md

@@ -69,7 +69,7 @@ If you happen to be stuck here "Why do you need `nb app autostart`", just contin
 - If you are going to connect to the reverse proxy, `appPort` has been saved in env
 - If you are ready to officially open it to the outside world, you have already planned the domain name, entrance port and HTTPS solution.
 
-If you have not completed the CLI installation or env initialization, go back to [Installation using CLI (recommended)](../installation/cli.md).
+If you have not completed the CLI installation or env initialization, go back to [Install using CLI](../installation/cli.md).
 
 If the command prompts that env is missing `appPort`, first execute [`nb env update`](../../api/cli/env/update.md) to fill it in.
 

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/production/reverse-proxy/caddy.md

@@ -290,6 +290,6 @@ nb proxy caddy status
 
 - [Production environment reverse proxy](./index.md)
 - [Nginx](./nginx.md)
-- [Install using CLI (recommended)](../../installation/cli.md)
+- [Install using CLI](../../installation/cli.md)
 - [Application configuration with `.env`](../../installation/env.md)
 - [`nb proxy caddy` Command Reference](../../../api/cli/proxy/caddy/index.md)

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/production/reverse-proxy/index.md

@@ -45,4 +45,4 @@ It can usually be judged like this:
 | Follow the Nginx management site entrance | [Nginx](./nginx.md) |
 | Connect HTTPS as soon as possible | [Caddy](./caddy.md) |
 | First adjust the env configuration that will affect the proxy results, such as `app-port`, `app-public-path` | [`nb env update`](../../../api/cli/env/update.md) |
-| First confirm the installation and env configuration of the application | [Install using CLI (recommended)](../../installation/cli.md) |
+| First confirm the installation and env configuration of the application | [Install using CLI](../../installation/cli.md) |

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/production/reverse-proxy/nginx.md

@@ -246,6 +246,6 @@ However, if you just want to get available HTTPS as soon as possible, and don't
 
 - [Production environment reverse proxy](./index.md)
 - [Caddy](./caddy.md)
-- [Install using CLI (recommended)](../../installation/cli.md)
+- [Install using CLI](../../installation/cli.md)
 - [Application configuration with `.env`](../../installation/env.md)
 - [`nb proxy nginx` Command Reference](../../../api/cli/proxy/nginx/index.md)