@nocobase/plugin-ai 2.1.0-alpha.30 → 2.1.0-alpha.32

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

@@ -91,7 +91,7 @@ nb env auth local
 
 `nb env auth` launches the browser login flow. After success, the CLI saves the authentication information to the current environment configuration, and you can then continue having the AI Agent call `nb api`.
 
-The validity periods of OAuth access tokens and refresh tokens follow the system [Token policy](/security/token-policy/) configuration.
+The validity periods of OAuth access tokens and refresh tokens follow the system [Token policy](../security/token-policy/index.md) configuration.
 
 - OAuth access tokens have the same validity period as system Tokens, with a default of **1 day**
 - OAuth refresh tokens have the same validity period as system sessions, with a default of **7 days**

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

@@ -1,13 +1,20 @@
 ---
 title: "nb env add"
-description: "nb env add command reference: save a NocoBase API URL and authentication method, then switch to it as the current env."
-keywords: "nb env add,NocoBase CLI,add environment,API URL,authentication"
+description: "nb env add command reference: save a NocoBase API URL and authentication method, then switch to that env."
+keywords: "nb env add,NocoBase CLI,add environment,API Base URL,authentication"
 ---
 
 # nb env add
 
 Save a named NocoBase API endpoint and switch the CLI to use that env. When `oauth` authentication is selected, [`nb env auth`](./auth.md) is started automatically.
 
+This command does two things:
+
+- Save the env configuration
+- Switch the current env to the newly added env
+
+When session mode is enabled for the current shell or runtime, it updates the session `current env`. It also updates the global `last env` as the fallback for shells or runtimes without session mode.
+
 ## Usage
 
 ```bash
@@ -37,5 +44,6 @@ nb env add local --api-base-url http://localhost:13000/api --auth-type token --a
 ## Related Commands
 
 - [`nb env auth`](./auth.md)
+- [`nb env current`](./current.md)
 - [`nb env update`](./update.md)
 - [`nb env list`](./list.md)

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

@@ -0,0 +1,29 @@
+---
+title: "nb env current"
+description: "nb env current command reference: show the currently effective NocoBase CLI env."
+keywords: "nb env current,NocoBase CLI,current env,session env"
+---
+
+# nb env current
+
+Show the name of the currently effective env.
+
+By default, this command first reads the session env for the current `NB_SESSION_ID`. If session mode is not enabled for the current shell or runtime, it falls back to the global `last env`.
+
+## Usage
+
+```bash
+nb env current
+```
+
+## Examples
+
+```bash
+nb env current
+```
+
+## Related Commands
+
+- [`nb env use`](./use.md)
+- [`nb env status`](./status.md)
+- [`nb session setup`](../session/setup.md)

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

@@ -1,13 +1,18 @@
 ---
 title: "nb env"
-description: "nb env command reference: manage NocoBase CLI envs, including add, refresh, inspect, switch, authenticate, and remove."
-keywords: "nb env,NocoBase CLI,environment management,env,authentication,OpenAPI"
+description: "nb env command reference: manage NocoBase CLI envs, including add, inspect current env, check status, switch, authenticate, and remove."
+keywords: "nb env,NocoBase CLI,environment management,env,current env,authentication,OpenAPI"
 ---
 
 # nb env
 
 Manage saved NocoBase CLI envs. An env stores API URL, authentication info, local app paths, database config, and runtime command cache.
 
+In the current model, the CLI separates two concepts:
+
+- `current env`: the env currently used by the active shell or agent runtime, isolated by `NB_SESSION_ID` when available
+- `last env`: the globally last-used env, used as a fallback when session mode is not enabled
+
 ## Usage
 
 ```bash
@@ -18,9 +23,11 @@ nb env <command>
 
 | Command | Description |
 | --- | --- |
-| [`nb env add`](./add.md) | Save a NocoBase API endpoint and switch to it as the current env |
+| [`nb env add`](./add.md) | Save a NocoBase API endpoint and switch to that env |
+| [`nb env current`](./current.md) | Show the currently effective env |
 | [`nb env update`](./update.md) | Refresh OpenAPI Schema and runtime command cache from the app |
-| [`nb env list`](./list.md) | List configured envs and API authentication status |
+| [`nb env list`](./list.md) | List configured envs |
+| [`nb env status`](./status.md) | Show status for the current env, one env, or all envs |
 | [`nb env info`](./info.md) | Show details for a single env |
 | [`nb env remove`](./remove.md) | Remove env configuration |
 | [`nb env auth`](./auth.md) | Run OAuth login for a saved env |
@@ -30,15 +37,26 @@ nb env <command>
 
 ```bash
 nb env add app1 --api-base-url http://localhost:13000/api
+nb env current
 nb env list
+nb env status
 nb env info app1
 nb env update app1
 nb env use app1
 nb env auth app1
 ```
 
+## Session mode
+
+Session mode is the default recommendation. It keeps `current env` isolated across different terminals, shells, and agent runtimes, so parallel work does not affect each other.
+
+When session mode is not enabled, `nb env use` updates the global `last env`, and other sessions without isolation may also be affected.
+
+See [`nb session setup`](../session/setup.md) to enable it.
+
 ## Related Commands
 
 - [`nb init`](../init.md)
 - [`nb api`](../api/index.md)
 - [`nb app`](../app/index.md)
+- [`nb session`](../session/index.md)

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

@@ -1,12 +1,14 @@
 ---
 title: "nb env list"
-description: "nb env list command reference: list configured NocoBase CLI envs and API authentication status."
-keywords: "nb env list,NocoBase CLI,environment list,authentication status"
+description: "nb env list command reference: list configured NocoBase CLI envs."
+keywords: "nb env list,NocoBase CLI,environment list,API Base URL"
 ---
 
 # nb env list
 
-List all configured envs and check app API authentication status with saved Token/OAuth credentials.
+List all configured envs.
+
+This command only shows saved configuration. Use [`nb env status`](./status.md) when you want to check current runtime or API status.
 
 ## Usage
 
@@ -16,9 +18,11 @@ nb env list
 
 ## Output
 
-The output table includes the current env marker, name, type, App Status, URL, authentication type, and runtime version.
+The output table includes the current env marker, name, type, `API Base URL`, authentication type, and runtime version.
 
-`App Status` is the result of accessing the app API with the saved auth info, such as `ok`, `auth failed`, `unreachable`, or `unconfigured`. Use [`nb db ps`](../db/ps.md) to inspect database runtime status.
+- `Current` marks the currently effective env with `*`
+- `API Base URL` shows the saved raw API address
+- `Runtime` shows cached runtime version information
 
 ## Examples
 
@@ -28,6 +32,7 @@ nb env list
 
 ## Related Commands
 
+- [`nb env current`](./current.md)
+- [`nb env status`](./status.md)
 - [`nb env info`](./info.md)
 - [`nb env use`](./use.md)
-- [`nb db ps`](../db/ps.md)

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

@@ -8,6 +8,8 @@ keywords: "nb env remove,NocoBase CLI,delete environment,remove config"
 
 Remove a configured env. This command only deletes CLI env configuration; use [`nb app down`](../app/down.md) to clean up local apps, containers, and storage.
 
+If the removed env is also the current env, the CLI automatically selects a new current env from the remaining envs. If no envs remain, the current env is cleared.
+
 ## Usage
 
 ```bash
@@ -32,4 +34,5 @@ nb env remove staging -f
 ## Related Commands
 
 - [`nb app down`](../app/down.md)
+- [`nb env current`](./current.md)
 - [`nb env list`](./list.md)

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

@@ -0,0 +1,52 @@
+---
+title: "nb env status"
+description: "nb env status command reference: show status for the current env, one env, or all envs."
+keywords: "nb env status,NocoBase CLI,environment status,API Base URL"
+---
+
+# nb env status
+
+Show env status. By default it inspects the current env. You can also inspect one named env, or use `--all` to inspect all envs.
+
+This command prints a simplified status table with `Env`, `Status`, and `API Base URL`.
+
+## Usage
+
+```bash
+nb env status [name] [flags]
+```
+
+## Parameters
+
+| Parameter | Type | Description |
+| --- | --- | --- |
+| `[name]` | string | Env name to inspect; uses the current env if omitted |
+| `--all` | boolean | Show status for all configured envs |
+| `--json-output` | boolean | Output the result as JSON |
+
+`[name]` and `--all` cannot be used together.
+
+## Status values
+
+`Status` is the result returned after the CLI checks the target env. Typical values include:
+
+- `ok`: the env is reachable and authenticated
+- `auth failed`: the API is reachable but authentication failed
+- `unreachable`: the target address could not be reached
+- `unconfigured`: the env configuration is incomplete
+- `missing`: the managed app for this env no longer exists
+
+## Examples
+
+```bash
+nb env status
+nb env status app1
+nb env status --all
+nb env status --all --json-output
+```
+
+## Related Commands
+
+- [`nb env current`](./current.md)
+- [`nb env list`](./list.md)
+- [`nb env info`](./info.md)

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

@@ -8,6 +8,10 @@ keywords: "nb env use,NocoBase CLI,switch environment,current env"
 
 Switch the current CLI env. Commands that omit `--env` will use this env by default afterward.
 
+When session mode is enabled for the current shell or runtime, this change only affects the current session.
+
+When session mode is not enabled, this falls back to updating the global `last env`. In that case, other terminals or agent runtimes without session isolation may also be affected.
+
 ## Usage
 
 ```bash
@@ -26,7 +30,13 @@ nb env use <name>
 nb env use local
 ```
 
+## Recommendation
+
+The default recommendation is to run [`nb session setup`](../session/setup.md) once first. That makes `nb env use` behave more like `use dbname` in a database client: switch the current session context first, then run follow-up commands that depend on that env.
+
 ## Related Commands
 
+- [`nb env current`](./current.md)
+- [`nb env status`](./status.md)
 - [`nb env list`](./list.md)
 - [`nb env info`](./info.md)

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

@@ -35,11 +35,12 @@ The root command mainly displays help and dispatches execution to command groups
 | [`nb app`](./app/index.md) | Manage NocoBase app runtimes: start, stop, restart, logs, and upgrades. |
 | [`nb config`](./config/index.md) | Manage CLI configuration defaults. |
 | [`nb db`](./db/index.md) | Manage the built-in database for the selected env. |
-| [`nb env`](./env/index.md) | Manage NocoBase project environments, status, details, and command runtimes. |
+| [`nb env`](./env/index.md) | Manage NocoBase project environments, current env, status, details, and command runtimes. |
 | [`nb license`](./license/index.md) | Manage commercial licensing and licensed plugins. |
 | [`nb plugin`](./plugin/index.md) | Manage plugins in the selected NocoBase env. |
 | [`nb scaffold`](./scaffold/index.md) | Generate NocoBase plugin development scaffolds. |
 | [`nb self`](./self/index.md) | Inspect or update the NocoBase CLI itself. |
+| [`nb session`](./session/index.md) | Configure `NB_SESSION_ID` so current env is isolated per shell or agent runtime. |
 | [`nb skills`](./skills/index.md) | Inspect or synchronize NocoBase AI coding skills for the current workspace. |
 | [`nb source`](./source/index.md) | Work with the local NocoBase source project: download, develop, build, and test. |
 
@@ -93,6 +94,8 @@ Connect an existing app:
 
 ```bash
 nb env add app1 --api-base-url http://localhost:13000/api
+nb env current
+nb env status
 ```
 
 Start the app and refresh runtime commands:
@@ -130,6 +133,7 @@ The following environment variables affect CLI behavior:
 | --- | --- |
 | `NB_CLI_ROOT` | Root directory where the CLI stores `.nocobase` config and local app files. Defaults to the current user's home directory. |
 | `NB_LOCALE` | Language for CLI prompts and the local setup UI. Supported values are `en-US` and `zh-CN`. |
+| `NB_SESSION_ID` | Session ID for the current shell or agent runtime. When set, `nb env use` and `nb env current` are isolated per session. |
 
 Example:
 
@@ -154,6 +158,14 @@ After setting `NB_CLI_ROOT=/your/workspace`, the config file path becomes:
 
 The CLI also keeps compatibility with legacy project config under the current working directory.
 
+Current env session cache is stored in:
+
+```text
+.nocobase/sessions/<NB_SESSION_ID>.json
+```
+
+The globally last-used env is stored in the `lastEnv` field in `config.json`. When `NB_SESSION_ID` is not set, the CLI falls back to that global value.
+
 Runtime command cache is stored in:
 
 ```text

package/dist/ai/docs/nocobase/api/cli/session/id.md

@@ -0,0 +1,28 @@
+---
+title: "nb session id"
+description: "nb session id command reference: show the current effective NB_SESSION_ID."
+keywords: "nb session id,NocoBase CLI,NB_SESSION_ID,session id"
+---
+
+# nb session id
+
+Show the current effective session id.
+
+If no usable `NB_SESSION_ID` is available in the current shell or runtime, the command tells you to run [`nb session setup`](./setup.md) first, then open a new shell session or runtime.
+
+## Usage
+
+```bash
+nb session id
+```
+
+## Examples
+
+```bash
+nb session id
+```
+
+## Related Commands
+
+- [`nb session setup`](./setup.md)
+- [`nb env current`](../env/current.md)

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

@@ -0,0 +1,41 @@
+---
+title: "nb session"
+description: "nb session command reference: configure and inspect NB_SESSION_ID so current env is isolated per shell or agent runtime."
+keywords: "nb session,NocoBase CLI,NB_SESSION_ID,session mode"
+---
+
+# nb session
+
+Manage session mode for `NB_SESSION_ID`.
+
+After session mode is enabled, `nb env use` and `nb env current` use the current shell or agent runtime context first, instead of directly sharing a single global current env.
+
+## Usage
+
+```bash
+nb session <command>
+```
+
+## Subcommands
+
+| Command | Description |
+| --- | --- |
+| [`nb session setup`](./setup.md) | Install shell or runtime integration for `NB_SESSION_ID` |
+| [`nb session id`](./id.md) | Show the current effective session id |
+| [`nb session remove`](./remove.md) | Remove shell or runtime integration for `NB_SESSION_ID` |
+
+## When you need it
+
+The default recommendation is to run `nb session setup` once when you first start using the CLI. With it enabled:
+
+- terminal 1 can use `env1`
+- terminal 2 can use `env2` at the same time
+- an agent runtime can keep its own current env too
+
+Without session mode, different sessions fall back to sharing the global `last env`, which makes parallel work more likely to affect each other.
+
+## Related Commands
+
+- [`nb env current`](../env/current.md)
+- [`nb env use`](../env/use.md)
+- [`nb env status`](../env/status.md)

package/dist/ai/docs/nocobase/api/cli/session/remove.md

@@ -0,0 +1,35 @@
+---
+title: "nb session remove"
+description: "nb session remove command reference: remove shell or runtime integration for NB_SESSION_ID."
+keywords: "nb session remove,NocoBase CLI,NB_SESSION_ID,remove session integration"
+---
+
+# nb session remove
+
+Remove session integration for `NB_SESSION_ID`.
+
+This command cleans up shell configuration previously written by [`nb session setup`](./setup.md). If opencode plugin integration is detected, it removes that integration too.
+
+## Usage
+
+```bash
+nb session remove [flags]
+```
+
+## Parameters
+
+| Parameter | Type | Description |
+| --- | --- | --- |
+| `--shell` | string | Target shell. Supported values: `bash`, `zsh`, `fish`, `powershell`, `cmd` |
+
+## Examples
+
+```bash
+nb session remove
+nb session remove --shell zsh
+```
+
+## Related Commands
+
+- [`nb session setup`](./setup.md)
+- [`nb session id`](./id.md)

package/dist/ai/docs/nocobase/api/cli/session/setup.md

@@ -0,0 +1,47 @@
+---
+title: "nb session setup"
+description: "nb session setup command reference: install shell or runtime integration for NB_SESSION_ID."
+keywords: "nb session setup,NocoBase CLI,NB_SESSION_ID,shell integration"
+---
+
+# nb session setup
+
+Install session integration for `NB_SESSION_ID`.
+
+This command detects the current shell, or uses the shell you pass with `--shell`, and writes the matching initialization file so new shell sessions automatically get `NB_SESSION_ID`.
+
+If opencode configuration is detected on the machine, it also writes the related plugin integration so the agent runtime can inject its own `NB_SESSION_ID`.
+
+## Usage
+
+```bash
+nb session setup [flags]
+```
+
+## Parameters
+
+| Parameter | Type | Description |
+| --- | --- | --- |
+| `--shell` | string | Target shell. Supported values: `bash`, `zsh`, `fish`, `powershell`, `cmd` |
+
+## Notes
+
+In most cases, you only need to run this once.
+
+After it finishes, open a new shell session or reload your profile so `NB_SESSION_ID` is initialized automatically.
+
+In agent runtimes such as Codex, if the runtime already injects a context variable such as `CODEX_THREAD_ID`, the CLI reuses that value first.
+
+## Examples
+
+```bash
+nb session setup
+nb session setup --shell zsh
+nb session setup --shell powershell
+```
+
+## Related Commands
+
+- [`nb session id`](./id.md)
+- [`nb session remove`](./remove.md)
+- [`nb env use`](../env/use.md)

package/dist/ai/docs/nocobase/interface-builder/blocks/data-blocks/details.md

@@ -79,7 +79,7 @@ For more details, see [Linkage Rules](/interface-builder/linkage-rule)
 
 ### Field template
 
-Field templates let you reuse the field section configuration (selected fields, layout, and field settings) in Details blocks. See [Field template](/interface-builder/fields/field-template).
+Field templates let you reuse the field section configuration (selected fields, layout, and field settings) in Details blocks. See [Field template](../../ui-templates.md).
 
 ![field-template-menu-20251228](https://static-docs.nocobase.com/field-template-menu-20251228.png)
 

package/dist/ai/docs/nocobase/interface-builder/blocks/data-blocks/form.md

@@ -73,7 +73,7 @@ The Form block supports two layout modes, which can be set via the `layout` attr
 
 ### Field Template
 
-Field templates are used to reuse field area configurations in Form blocks. For details, see [Field Template](/interface-builder/fields/field-template).
+Field templates are used to reuse field area configurations in Form blocks. For details, see [Field Template](../../ui-templates.md).
 
 ![field-template-menu-20251228](https://static-docs.nocobase.com/field-template-menu-20251228.png)
 

package/dist/ai/docs/nocobase/plugin-development/client/examples/custom-block.md

@@ -107,7 +107,7 @@ Key points:
 
 - **`renderComponent()`** -- Renders the block UI, reading HTML content via `this.props.html`
 - **`define()`** -- Sets the display name in the "Add Block" menu. `tExpr()` is used for deferred translation because `define()` executes at module load time, when i18n hasn't been initialized yet
-- **`registerFlow()`** -- Adds a configuration panel. `uiSchema` defines the form using JSON Schema (syntax reference: [UI Schema](../../../../flow-engine/ui-schema)), `handler` writes user-filled values to `ctx.model.props`, and `renderComponent()` can read them
+- **`registerFlow()`** -- Adds a configuration panel. `uiSchema` defines the form using JSON Schema (syntax reference: [UI Schema](../../../flow-engine/ui-schema.md)), `handler` writes user-filled values to `ctx.model.props`, and `renderComponent()` can read them
 
 ## Step 3: Add Multilingual Files
 
@@ -194,7 +194,7 @@ Capabilities used in this example:
 - [Writing Your First Plugin](../../write-your-first-plugin) -- Create a plugin skeleton from scratch
 - [FlowEngine Overview](../flow-engine/index.md) -- FlowModel basic usage and registerFlow
 - [FlowEngine -> Block Extension](../flow-engine/block) -- BlockModel, DataBlockModel, CollectionBlockModel
-- [UI Schema](../../../../flow-engine/ui-schema) -- uiSchema syntax reference
+- [UI Schema](../../../flow-engine/ui-schema.md) -- uiSchema syntax reference
 - [Component vs FlowModel](../component-vs-flow-model) -- When to use FlowModel
 - [Plugin](../plugin) -- Plugin entry point and load() lifecycle
 - [i18n Internationalization](../component/i18n) -- Translation file conventions and tExpr usage

package/dist/ai/docs/nocobase/solution/crm/guide/guide-customers-emails.md

@@ -175,4 +175,4 @@ Activity records also appear in the calendar view on the Overview dashboard.
 - [CRM User Guide](./index.md)
 - [Lead Management](./guide-leads) — Leads automatically create customers and contacts upon conversion
 - [Opportunity Management](./guide-opportunities) — Opportunities linked to customers
-- [AI Employees](./guide-ai)
+- [AI Employees](../../../ai-employees/index.md)

package/dist/ai/docs/nocobase/solution/crm/guide/guide-overview.md

@@ -201,10 +201,10 @@ Drill-through comes in two forms:
 
 ---
 
-After understanding the system layout and dashboards, go back to the [User Guide](./guide) for subsequent chapters.
+After understanding the system layout and dashboards, go back to the [User Guide](./index.md) for subsequent chapters.
 
 ## Related Pages
 
-- [CRM User Guide](./guide)
+- [CRM User Guide](./index.md)
 - [Solution Overview](../index)
 - [Installation](../installation)

package/dist/ai/docs/nocobase/tutorials/v2/01-getting-started.md

@@ -19,7 +19,7 @@ Compared to other no-code tools, NocoBase has a few core principles:
 
 - **Data model driven**: Define your data structure first, then use [blocks](/interface-builder/blocks) to display data, then [actions](/interface-builder/actions) to process it — UI and data are fully decoupled
 - **WYSIWYG**: Pages are your canvas. Click anywhere to edit, as intuitive as building a Notion page
-- **Everything is a plugin**: All features are [plugins](/development/plugin), similar to WordPress — install what you need
+- **Everything is a plugin**: All features are [plugins](../../plugins/index.mdx), similar to WordPress — install what you need
 - **AI built into your workflow**: Built-in [AI employees](/ai-employees/quick-start) that can perform analysis, translation, data entry, and more
 - **Open source + self-hosted**: Core code is fully open source, all data stays on your own server
 

package/dist/ai/docs/nocobase/tutorials/v2/03-building-pages.md

@@ -181,7 +181,7 @@ This way, newly submitted tickets always appear at the top, making them easier t
 Viewing a list isn't enough — we also need to click into tickets to see details and make edits.
 
 1. In the actions column, click the second "+" icon.
-2. Click to add actions: **View**, **[Edit](/interface-builder/actions/edit)**, **[Delete](/interface-builder/actions/delete)**.
+2. Click to add actions: **View**, **[Edit](../../interface-builder/actions/types/edit.md)**, **[Delete](../../interface-builder/actions/types/delete.md)**.
 3. Each row will now have "View", "Edit", and "Delete" buttons in the actions column.
 
 ![03-building-pages-2026-03-13-09-42-42](https://static-docs.nocobase.com/03-building-pages-2026-03-13-09-42-42.png)
@@ -211,7 +211,7 @@ Remember the "Categories" collection we created in Chapter 2? It's a **tree tabl
 
 Once enabled, the table will display categories in an indented hierarchy showing parent-child relationships, instead of listing all records flat.
 
-3. Check the fields you want to display (e.g., Name, Description), and configure row actions ([Add new](/interface-builder/actions/add-new), Edit, Delete).
+3. Check the fields you want to display (e.g., Name, Description), and configure row actions ([Add new](../../interface-builder/actions/types/add-new.md), Edit, Delete).
 4. **Layout tip**: Put "Name" in the first column and "Actions" in the second. The categories table doesn't have many fields, so a two-column layout is more compact and user-friendly.
 
 [Screenshot: Categories tree table configured]

package/dist/ai/docs/nocobase/tutorials/v2/04-forms-and-details.md

@@ -1,6 +1,6 @@
 # Chapter 4: Forms & Details — Input, Display, All in One
 
-In the last chapter, we built the ticket list and used a quick form to enter test data. In this chapter, we'll **refine the form experience** — optimize [Form block](/interface-builder/blocks/data-blocks/form) field layouts, add [Details blocks](/interface-builder/blocks/data-blocks/details), configure [linkage rules](/interface-builder/linkage-rules), and use [change history](https://docs.nocobase.com/record-history/) to track every modification.
+In the last chapter, we built the ticket list and used a quick form to enter test data. In this chapter, we'll **refine the form experience** — optimize [Form block](/interface-builder/blocks/data-blocks/form) field layouts, add [Details blocks](/interface-builder/blocks/data-blocks/details), configure [linkage rules](../../interface-builder/linkage-rule.md), and use [change history](https://docs.nocobase.com/record-history/) to track every modification.
 
 :::tip
 Section 4.4 "Change History" requires the [Professional edition](https://www.nocobase.com/en/commercial). Skipping it won't affect later chapters.
@@ -15,7 +15,7 @@ In the last chapter, we quickly created a working "Add new" form. Now let's refi
 1. Make sure you're in [UI Editor](/get-started/how-nocobase-works) mode (top-right toggle is on).
 2. Go to the "All Tickets" page, and click **"[Actions](/interface-builder/actions)"** above the Table block.
 3. Check the **"Add new"** action button.
-4. An "Add new" button will appear above the table. Clicking it opens a [popup](/interface-builder/actions/pop-up).
+4. An "Add new" button will appear above the table. Clicking it opens a [popup](../../interface-builder/actions/types/pop-up.md).
 
 ![04-forms-and-details-2026-03-13-09-43-54](https://static-docs.nocobase.com/04-forms-and-details-2026-03-13-09-43-54.png)
 
@@ -268,7 +268,7 @@ In this chapter, we completed the full data lifecycle:
 - **Form** — Users can submit new tickets with default values and validation
 - **Linkage rules** — Urgent tickets automatically require a description
 - **Details block** — Clearly displays a ticket's complete information
-- **[Change history](/collection-templates/audit-log)** — Automatically tracks every modification for worry-free auditing (commercial plugin, optional)
+- **[Change history](../../record-history/index.md)** — Automatically tracks every modification for worry-free auditing (commercial plugin, optional)
 
 From "visible" to "enterable" to "traceable" — our ticket system now has basic usability.
 
@@ -276,4 +276,4 @@ From "visible" to "enterable" to "traceable" — our ticket system now has basic
 
 - [Form Block](/interface-builder/blocks/data-blocks/form) — Form block configuration guide
 - [Details Block](/interface-builder/blocks/data-blocks/details) — Details block setup
-- [Linkage Rules](/interface-builder/linkage-rules) — Field linkage configuration
+- [Linkage Rules](../../interface-builder/linkage-rule.md) — Field linkage configuration

package/dist/ai/docs/nocobase/tutorials/v2/06-workflows.md

@@ -34,7 +34,7 @@ NocoBase offers several trigger types, which you select when creating a workflow
 |---------|-------------|-----------------|
 | **[Collection event](/workflow/triggers/collection)** | Fires when a record is created, updated, or deleted | New ticket notification, status change logging |
 | **[Schedule](/workflow/triggers/schedule)** | Fires on a Cron expression or fixed time | Daily reports, periodic data cleanup |
-| **[Post-action event](/workflow/triggers/action)** | Fires after a user performs a UI action | Send notification after form submission |
+| **[Post-action event](../../workflow/triggers/post-action.md)** | Fires after a user performs a UI action | Send notification after form submission |
 | **Approval** | Initiates an approval flow with multi-level support | Leave requests, purchase approvals |
 | **Custom action** | Bound to a custom button, fires on click | One-click archiving, batch operations |
 | **Pre-action event** | Intercepts a user action synchronously before it completes | Pre-submit validation, auto-fill fields |

package/dist/ai/docs/nocobase/workflow/nodes/javascript.md

@@ -8,7 +8,7 @@ pkg: '@nocobase/plugin-workflow-javascript'
 
 The JavaScript Script node allows users to execute a custom server-side JavaScript script within a workflow. The script can use variables from upstream in the workflow as parameters, and its return value can be provided to downstream nodes.
 
-The script runs in a worker thread on the NocoBase application's server. By default, it uses a secure sandbox (isolated-vm) that does not support `require` or Node.js built-in APIs. For details, see [Execution Engine](#execution-engine) and [Feature List](#feature-list).
+The script runs in a worker thread on the NocoBase application's server. By default, it uses a secure sandbox (QuickJS, powered by WebAssembly) that does not support `require` or Node.js built-in APIs. For details, see [Execution Engine](#execution-engine) and [Feature List](#feature-list).
 
 ## Create Node
 
@@ -50,7 +50,7 @@ The JavaScript script node supports two execution engines, automatically selecte
 
 ### Safe Mode (Default)
 
-When `WORKFLOW_SCRIPT_MODULES` is **not configured**, scripts run using the [isolated-vm](https://github.com/laverdet/isolated-vm) engine. This engine executes code in an isolated V8 environment with the following characteristics:
+When `WORKFLOW_SCRIPT_MODULES` is **not configured**, scripts run using the [QuickJS](https://bellard.org/quickjs/) engine compiled to WebAssembly. This engine executes code in an isolated JavaScript runtime with the following characteristics:
 
 - **Does not support** `require` — no modules can be imported
 - **Does not support** Node.js built-in APIs (such as `process`, `Buffer`, `global`, etc.)