From c9eb168601195359f553fcb2858518b36293ded7 Mon Sep 17 00:00:00 2001 From: Schaled Date: Wed, 19 Aug 2026 15:58:07 +0800 Subject: [PATCH] docs: add LLOneBot adapter --- .gitignore | 3 +- .vitepress/sidebar/en.ts | 1 + .vitepress/sidebar/zh.ts | 1 + en/manual/adapters/LLOneBot.md | 167 +++++++++++++++++++++++++++++++++ zh/manual/adapters/LLOneBot.md | 167 +++++++++++++++++++++++++++++++++ zh/manual/adapters/index.md | 35 ++++++- 6 files changed, 372 insertions(+), 2 deletions(-) create mode 100644 en/manual/adapters/LLOneBot.md create mode 100644 zh/manual/adapters/LLOneBot.md diff --git a/.gitignore b/.gitignore index bc390f6..3063974 100644 --- a/.gitignore +++ b/.gitignore @@ -147,4 +147,5 @@ package-lock.json # OpenCode .sisyphus -.omo \ No newline at end of file +.omozh/manual/adapters/LuckyLilliaDoc/ +zh/manual/adapters/LuckyLilliaDoc/ diff --git a/.vitepress/sidebar/en.ts b/.vitepress/sidebar/en.ts index 39c1dff..cf7a578 100644 --- a/.vitepress/sidebar/en.ts +++ b/.vitepress/sidebar/en.ts @@ -155,6 +155,7 @@ export const sidebar: DefaultTheme.Sidebar = { items: [ { text: 'Adapters Overview', link: '/en/manual/adapters/' }, { text: 'NapCat QQ Connection', link: '/en/manual/adapters/napcat' }, + { text: 'LLOneBot (LLBot) Adapter', link: '/en/manual/adapters/LLOneBot' }, { text: 'GoCQ Adapter', link: '/en/manual/adapters/gocq' }, { text: 'SnowLuma Adapter', link: '/en/manual/adapters/snowluma' }, { text: 'Telegram Adapter', link: '/en/manual/adapters/telegram' }, diff --git a/.vitepress/sidebar/zh.ts b/.vitepress/sidebar/zh.ts index 728018e..3ddcc0f 100644 --- a/.vitepress/sidebar/zh.ts +++ b/.vitepress/sidebar/zh.ts @@ -116,6 +116,7 @@ export const sidebar: DefaultTheme.Sidebar = { items: [ { text: '适配器概览', link: '/manual/adapters/' }, { text: 'NapCat QQ 连接', link: '/manual/adapters/napcat' }, + { text: 'LLOneBot(LLBot) 适配器', link: '/manual/adapters/LLOneBot' }, { text: 'GoCQ 适配器', link: '/manual/adapters/gocq' }, { text: 'SnowLuma 适配器', link: '/manual/adapters/snowluma' }, { text: 'Telegram 适配器', link: '/manual/adapters/telegram' }, diff --git a/en/manual/adapters/LLOneBot.md b/en/manual/adapters/LLOneBot.md new file mode 100644 index 0000000..4083b2d --- /dev/null +++ b/en/manual/adapters/LLOneBot.md @@ -0,0 +1,167 @@ +--- +title: Connect QQ with LLOneBot (LuckyLilliaBot) +--- + +# Connect QQ with LLOneBot (LuckyLilliaBot) + +LLOneBot (LuckyLilliaBot, "LLBot") is an NTQQ-based QQ bot protocol server that supports OneBot 11, Satori, and Milky protocols. MaiBot has no dedicated LLOneBot plugin; instead it reuses the **NapCat Adapter** to connect to LLBot's **OneBot 11 Forward WebSocket (WebSocket server)**. The adapter connects to LLBot as a client and passes messages to MaiBot through the plugin message gateway, so no separate legacy standalone adapter is needed. + +This approach can sometimes help with newly registered or unstable QQ accounts. If you already have an LLBot environment, it can replace NapCat for the QQ integration. + +::: info Connection direction +`LLBot WebSocket server ← NapCat adapter client → MaiBot plugin message gateway` + +The plugin version does not use `[maim_message]`, and no Reverse WebSocket entry is needed in LLBot. You only need to enable OneBot 11 **Forward WebSocket** in LLBot. +::: + +Adapter source: [Mai-with-u/MaiBot-Napcat-Adapter](https://github.com/Mai-with-u/MaiBot-Napcat-Adapter) +LLBot source and docs: [LLOneBot/LuckyLilliaBot](https://github.com/LLOneBot/LuckyLilliaBot) · [Official documentation](https://www.llonebot.com/guide/introduction) + +::: warning Risk notice +LLBot is an unofficial QQ protocol server, and no unofficial protocol server can completely avoid account risk controls. Use a dedicated QQ side account and follow platform rules. LLBot's pure-protocol (headless) mode carries a disconnection risk; be cautious with accounts in poor health. +::: + +## 1. Install and Log In to LLBot + +LLBot is available as Desktop (Windows GUI), CLI (Linux / macOS), and Docker. Choose whichever fits your environment; detailed steps are in the [official installation guide](https://www.llonebot.com/guide/choice_install): + +- **Desktop** — Extract the archive, run `llbot.exe`, and press start. In headed mode LLBot must launch the QQ client itself; an QQ opened manually will not be managed by LLBot. +- **CLI** — Extract and run `./start.sh`, then scan the QR code shown in the terminal or log in via the WebUI (default `http://localhost:3080`). +- **Docker** — Run the one-click install script or pull the image directly, then scan the QR code in the container log or the WebUI. + +LLBot can run in two modes: **headed mode** launches the original NTQQ client and is more stable, while **headless mode** (pure protocol) does not depend on a QQ client and uses fewer resources, but carries a disconnection risk. + +The QQ account you log in with is the bot's account. After a successful login, all protocol configuration is done in the LLBot WebUI (default `http://localhost:3080`). + +## 2. Enable OneBot 11 Forward WebSocket + +Enable the OneBot 11 protocol in LLBot and add a **Forward WebSocket (`ws`)** entry, using any of the following methods: + +- **LLBot WebUI** (default `http://localhost:3080`) — create or enable the forward WS under the OneBot 11 settings, set the port and token, then save. +- **LLBot Desktop** — do the same under "Bot 配置 → OneBot11". +- **Edit the config file directly** `data/config_.json` (under `bin/llbot/data/` for Windows / CLI; mounted in a Docker Volume): + +::: code-group + +```json5 [JSON5 ~vscode-icons:file-type-json~] +{ + "ob11": { + "enable": true, // enable the OneBot 11 protocol + "connect": [ + { + "type": "ws", // Forward WS: LLBot acts as the WebSocket server + "enable": true, + "port": 3001, // listening port, commonly 3001 + "heartInterval": 60000, + "token": "", // access token; leave empty if none is set + "reportSelfMessage": false, // keep false to ignore messages sent by itself + "reportOfflineMessage": false, + "messageFormat": "array" + } + ] + } +} +``` + +::: + +Key points: + +- **`type: "ws"`** — must be Forward WebSocket. LLBot's "Reverse WebSocket" makes LLBot act as a client that connects to an address you provide, which the plugin adapter does not need. +- **`port`** — the Forward WebSocket listening port, commonly `3001`; fill it into the adapter later. +- **`token`** — the Forward WebSocket access token. If set, enter the same token in the adapter later; leave empty if none is configured. +- **`messageFormat`** — keep `array`. +- **`reportSelfMessage`** — keep `false` so the bot does not process messages it just sent. + +Do not confuse the LLBot WebUI token, MaiBot WebUI Access Token, and the OneBot WebSocket token. + +::: tip Local-only listening +By default `onlyLocalhost` is `true`, so LLBot only listens on localhost. If MaiBot and LLBot run on different machines or are deployed in separate containers, set `onlyLocalhost` to `false` (so LLBot listens on an accessible network interface), use a strong token, and restrict sources in the firewall. +::: + +## 3. Configure MaiBot's Bot Account + +Set the platform and QQ account in WebUI basic settings, or edit `config/bot_config.toml`: + +::: code-group + +```toml [TOML ~vscode-icons:file-type-toml~] +[bot] +platform = "qq" +qq_account = "123456789" +``` + +::: + +`qq_account` must match the QQ account actually logged in through LLBot. LLBot logs that account into QQ, while MaiBot core uses this setting to identify messages sent by the bot itself. The plugin adapter does not use `[maim_message]`, but it still requires `[bot].qq_account`. + +## 4. Install and Enable the Adapter + +Open **Plugin Management** in MaiBot WebUI, install **NapCat Adapter** from the plugin marketplace, and enable it manually. Its default configuration is disabled, so a successful installation alone does not start it. + +If the marketplace is unavailable, clone the repository into MaiBot's `plugins/` directory: + +::: code-group + +```bash [Bash ~vscode-icons:file-type-shell~] +git clone https://github.com/Mai-with-u/MaiBot-Napcat-Adapter.git plugins/MaiBot-Napcat-Adapter +``` + +::: + +After a manual clone, use the WebUI to enable and configure it. The actual directory name may vary by installation method, so do not use a hard-coded directory name as proof that installation succeeded. + +## 5. Configure the Connection + +In the NapCat Adapter settings, point the connection at LLBot: + +**`napcat_server.host`** — LLBot's address. Use `127.0.0.1` when both run on the same host; otherwise use the LAN address of the machine running LLBot; use the service name `llbot` with a project Docker Compose file. + +**`napcat_server.port`** — the Forward WebSocket listening port, such as `3001`; must match step 2. + +**`napcat_server.token`** — the Forward WebSocket access token, or empty if none is configured. + +The adapter connects to an address such as `ws://127.0.0.1:3001`. After saving, its `on_config_update` lifecycle stops the old connection and reconnects with the new settings; a full MaiBot restart is normally unnecessary. + +::: warning Docker networking +When MaiBot and LLBot are in different containers, do not use `127.0.0.1` (it only points to the container itself). Use the Compose service name or `host.docker.internal` depending on your deployment. +::: + +## 6. Configure Chat Lists + +Chat-list filtering is enabled by default. Group and private chats both default to whitelist mode, with initially empty lists. Messages outside the lists are discarded. + +You can temporarily disable filtering during testing. For regular use, keep filtering enabled and add the allowed group or QQ IDs. For example: + +::: code-group + +```toml [TOML ~vscode-icons:file-type-toml~] +[chat] +enable_chat_list_filter = true +show_dropped_chat_list_messages = true +group_list_type = "whitelist" +group_list = ["your-qq-group-id"] +``` + +::: + +## Verification and Troubleshooting + +**Plugin loaded** — NapCat Adapter is enabled in the WebUI and the MaiBot log contains no load error. + +**Correct direction** — LLBot runs the WebSocket server and the adapter log reports a connection to LLBot. Do not configure Reverse WebSocket in LLBot. + +**Connected but no messages** — Check the group/private whitelist first and temporarily enable dropped-message logs; then confirm LLBot is logged in, the Forward WebSocket is enabled, and the port matches the adapter. + +**Connection failure** — Verify the host, port, and WebSocket token. Use `127.0.0.1` only when both run on the same host; for Docker / cross-device deployments check `onlyLocalhost`, port mapping, and firewall. + +**No reconnect after saving** — Check the plugin configuration-update log. Use a full MaiBot restart only as a fallback after hot reload fails. + +**Frequent disconnects in headless mode** — LLBot's pure-protocol mode carries a disconnection risk. If it is severe, switch back to headed mode or use another protocol server such as [NapCat](./napcat.md). + +## Related Documentation + +- [Connect QQ with the NapCat Adapter](./napcat.md) — full usage of the adapter plugin used by this guide +- [Adapter Overview](./index.md) — choosing adapters for QQ and other platforms +- LLBot official docs: [Introduction](https://www.llonebot.com/guide/introduction) · [Quick Install](https://www.llonebot.com/guide/choice_install) · [Configuration](https://www.llonebot.com/guide/config) · [FAQ](https://www.llonebot.com/guide/faq) +- LLBot source: [LLOneBot/LuckyLilliaBot](https://github.com/LLOneBot/LuckyLilliaBot) \ No newline at end of file diff --git a/zh/manual/adapters/LLOneBot.md b/zh/manual/adapters/LLOneBot.md new file mode 100644 index 0000000..4254594 --- /dev/null +++ b/zh/manual/adapters/LLOneBot.md @@ -0,0 +1,167 @@ +--- +title: 使用 LLOneBot（LuckyLilliaBot）连接 QQ +--- + +# 使用 LLOneBot（LuckyLilliaBot）连接 QQ + +LLOneBot（LuckyLilliaBot，简称 LLBot）是一个基于 NTQQ 的 QQ 机器人协议端，支持 OneBot 11、Satori、Milky 协议。MaiBot 没有独立的 LLOneBot 插件，而是复用 **NapCat 适配器**连接 LLBot 的 **OneBot 11 正向 WebSocket（WebSocket 服务器）**：适配器作为客户端主动连接 LLBot，再通过插件消息网关把消息交给 MaiBot，不需要额外运行旧版独立适配器。 + +该方案对新注册或登录不稳定的 QQ 账号有时会有一定帮助；如果你已有 LLBot 环境，也可以直接用它替代 NapCat 完成 QQ 接入。 + +::: info 连接方向 +`LLBot WebSocket 服务器 ← NapCat 适配器客户端 → MaiBot 插件消息网关` + +插件版不使用 `[maim_message]`，也不需要把 LLBot 配置成“反向 WebSocket”。在 LLBot 中只需开启 OneBot 11 的**正向 WebSocket**。 +::: + +适配器源码：[Mai-with-u/MaiBot-Napcat-Adapter](https://github.com/Mai-with-u/MaiBot-Napcat-Adapter) +LLBot 源码与文档：[LLOneBot/LuckyLilliaBot](https://github.com/LLOneBot/LuckyLilliaBot) · [官方文档](https://www.llonebot.com/guide/introduction) + +::: warning 风控提示 +LLBot 属于非官方 QQ 协议端，任何非官方协议端都无法完全避免账号风控。建议使用专用 QQ 小号并遵守平台规则；LLBot 的纯协议（无头）模式存在掉线风险，账号体质不佳时慎用。 +::: + +## 1. 安装并登录 LLBot + +LLBot 提供 Desktop（Windows 图形界面）、CLI（Linux / macOS）和 Docker 三种安装方式，选择适合你的环境即可，具体步骤见[官方安装文档](https://www.llonebot.com/guide/choice_install)： + +- **Desktop 版** — 解压后双击 `llbot.exe` 并点击启动。有头模式必须由 LLBot 拉起 QQ，自己手动打开的 QQ 不会被 LLBot 接管。 +- **CLI 版** — 解压后运行 `./start.sh`，按终端提示扫码登录，或访问 WebUI 登录（默认 `http://localhost:3080`）。 +- **Docker 版** — 运行一键安装脚本或直接拉取镜像，然后在容器日志或 WebUI 中扫码登录。 + +LLBot 支持两种运行方式：**有头模式**由 LLBot 拉起原版 NTQQ 客户端，稳定性较好；**无头模式**（纯协议）不依赖 QQ 客户端、资源占用更低，但存在掉线风险。 + +登录时使用的 QQ 号就是机器人的账号。登录成功后，后续的协议配置都在 LLBot WebUI（默认 `http://localhost:3080`）中完成。 + +## 2. 开启 OneBot 11 正向 WebSocket + +在 LLBot 中启用 OneBot 11 协议并新建一条**正向 WebSocket（`ws`）**连接，可通过以下任一方式： + +- **LLBot WebUI**（默认 `http://localhost:3080`）— 在 OneBot11 配置中新建或启用正向 WS，填写端口和 Token 后保存 +- **LLBot Desktop** — 在“Bot 配置 → OneBot11”中操作 +- **直接修改配置文件** `data/config_<你的QQ号>.json`（Windows / CLI 版位于 `bin/llbot/data/`；Docker 版挂载在 Volume 中）： + +::: code-group + +```json5 [JSON5 ~vscode-icons:file-type-json~] +{ + "ob11": { + "enable": true, // 是否启用 OneBot 11 协议 + "connect": [ + { + "type": "ws", // 正向 WS：LLBot 作为 WebSocket 服务器 + "enable": true, + "port": 3001, // 监听端口，常用 3001 + "heartInterval": 60000, + "token": "", // 访问 Token，未设置则留空 + "reportSelfMessage": false, // 建议保持 false，不处理自己发出的消息 + "reportOfflineMessage": false, + "messageFormat": "array" + } + ] + } +} +``` + +::: + +关键项说明： + +- **`type: "ws"`** — 必须是正向 WebSocket。LLBot 的“反向 WebSocket”是让 LLBot 作为客户端去连接你提供的地址，插件版适配器不需要它。 +- **`port`** — 正向 WebSocket 监听端口，常用 `3001`，稍后填入适配器。 +- **`token`** — 正向 WebSocket 的访问 Token。如果设置了，稍后把同一个 Token 填入适配器；未设置则留空。 +- **`messageFormat`** — 保持 `array`。 +- **`reportSelfMessage`** — 建议保持 `false`，避免机器人处理自己刚发出的消息。 + +不要把 LLBot WebUI Token、MaiBot WebUI Access Token 和 OneBot WebSocket Token 混用。 + +::: tip 仅监听本地 +LLBot 默认 `onlyLocalhost: true`，只监听本地地址。如果 MaiBot 与 LLBot 不在同一台机器，或用 Docker 分开部署，需要把 `onlyLocalhost` 改为 `false`（让 LLBot 监听可访问的网卡地址）、设置强 Token，并用防火墙限制来源。 +::: + +## 3. 配置 MaiBot 的机器人账号 + +在 WebUI 基础配置中填写平台和 QQ 账号，或编辑 `config/bot_config.toml`： + +::: code-group + +```toml [TOML ~vscode-icons:file-type-toml~] +[bot] +platform = "qq" +qq_account = "123456789" +``` + +::: + +`qq_account` 必须与 LLBot 实际登录的 QQ 号一致。LLBot 用该账号登录 QQ；MaiBot 核心用这个配置识别机器人自己发送的消息。插件版虽然不使用 `[maim_message]`，但仍然需要 `[bot].qq_account`。 + +## 4. 安装并启用适配器 + +在 MaiBot WebUI 中打开“插件管理”，从插件市场安装 **NapCat Adapter**，然后手动启用。插件默认配置为禁用，安装成功不等于已经运行。 + +如果插件市场不可用，也可以把仓库克隆到 MaiBot 的 `plugins/` 目录： + +::: code-group + +```bash [Bash ~vscode-icons:file-type-shell~] +git clone https://github.com/Mai-with-u/MaiBot-Napcat-Adapter.git plugins/MaiBot-Napcat-Adapter +``` + +::: + +手动克隆后仍建议在 WebUI 中完成启用和配置。插件目录名可能因安装方式而异，不要依赖固定目录名判断是否安装成功。 + +## 5. 配置连接 + +在 NapCat Adapter 的插件设置中，把连接地址指向 LLBot： + +**`napcat_server.host`** — LLBot 的地址。同机运行填 `127.0.0.1`；不在同一台机器时填 LLBot 所在设备的局域网地址；使用项目 Docker Compose 时填服务名 `llbot`。 + +**`napcat_server.port`** — LLBot 正向 WebSocket 的监听端口，例如 `3001`，必须与第 2 步一致。 + +**`napcat_server.token`** — LLBot 正向 WebSocket 的访问 Token；未设置则留空。 + +适配器会连接类似 `ws://127.0.0.1:3001` 的地址。保存配置后，插件的 `on_config_update` 会停止旧连接并按新配置重新连接，通常不需要重启 MaiBot。 + +::: warning Docker 网络 +MaiBot 与 LLBot 在不同容器时，不要把地址写成 `127.0.0.1`（它只指向容器自身）。按部署方式填写 Compose 服务名或 `host.docker.internal`。 +::: + +## 6. 配置聊天名单 + +适配器默认启用聊天名单过滤，群聊与私聊均默认为白名单，初始名单为空。未加入名单的消息会被丢弃。 + +测试时可在插件设置中临时关闭名单过滤；正式使用建议保留过滤并把允许的群号或 QQ 号加入对应名单。例如： + +::: code-group + +```toml [TOML ~vscode-icons:file-type-toml~] +[chat] +enable_chat_list_filter = true +show_dropped_chat_list_messages = true +group_list_type = "whitelist" +group_list = ["你的QQ群号"] +``` + +::: + +## 验证与排错 + +**确认插件已加载** — WebUI 插件列表显示 NapCat Adapter 已启用，MaiBot 日志没有加载错误。 + +**确认连接方向** — LLBot 运行的是 WebSocket 服务器，适配器日志显示已连接到 LLBot；不要在 LLBot 里配置反向 WebSocket。 + +**已连接但不收消息** — 首先检查群聊或私聊白名单，并临时打开丢弃消息日志；然后确认 LLBot 已登录 QQ、正向 WebSocket 已启用，端口与适配器一致。 + +**连接失败** — 核对地址、端口和 WebSocket Token。同机填写 `127.0.0.1`；Docker / 跨设备部署检查 `onlyLocalhost`、端口映射和防火墙。 + +**改配置后没有重连** — 查看插件配置更新日志；只有热更新回调失败时，才把完整重启 MaiBot 作为兜底。 + +**无头模式频繁掉线** — LLBot 纯协议模式存在掉线风险，情况严重时改回有头模式或使用其他协议端（如 [NapCat](./napcat.md)）。 + +## 相关文档 + +- [使用 NapCat 适配器连接 QQ](./napcat.md) — 本方案使用的适配器插件的完整用法 +- [适配器概览](./index.md) — QQ 及其他平台适配器的选择 +- LLBot 官方文档：[项目介绍](https://www.llonebot.com/guide/introduction) · [快速安装](https://www.llonebot.com/guide/choice_install) · [配置说明](https://www.llonebot.com/guide/config) · [常见问题](https://www.llonebot.com/guide/faq) +- LLBot 源码：[LLOneBot/LuckyLilliaBot](https://github.com/LLOneBot/LuckyLilliaBot) \ No newline at end of file diff --git a/zh/manual/adapters/index.md b/zh/manual/adapters/index.md index 3796621..58c2ace 100644 --- a/zh/manual/adapters/index.md +++ b/zh/manual/adapters/index.md @@ -12,6 +12,7 @@ title: 适配器概览 - [NapCat](./napcat.md)（推荐使用）— 麦麦官方维护的 QQ 适配器，支持插件版和独立版，插件版是当前推荐方案 - [GoCQ](./gocq.md)（可用，偏旧）— 基于 go-cqhttp / AstralGocq 的 QQ 适配方案，适合已有 GoCQ 环境或特定需求 - [SnowLuma](./snowluma.md)（可用，测试中）— 新一代 QQ 适配方案 +- [LLOneBot](./LLOneBot.md) (对新账号和登录不稳定的账号有一定作用）- 兼容多协议的QQ适配器，与NapCat适配插件通用 **其他平台** — 社区适配 - [Telegram](./telegram.md) — Telegram 平台适配方案 @@ -82,4 +83,36 @@ title: 适配器概览 2. 适配器是否正常启动。 3. 适配器是否成功连接消息平台。 4. 独立版适配器是否成功连接 MaiBot。 -5. MaiBot 是否已经完成初始化并正常运行。 \ No newline at end of file +<<<<<<< Updated upstream +5. MaiBot 是否已经完成初始化并正常运行。 +======= +5. MaiBot 是否已经完成初始化并正常运行。 + +## 适配器账号与身份 + +从 1.2.0 起，MaiBot 会**持久化适配器实际报告的平台账号身份**，而不是只依赖你在配置里手填的账号： + +- **身份来源** — 适配器连接后上报的平台账号（账号 ID、昵称等）会被持久化保存，作为该适配器实例的稳定身份 +- **多账号识别** — 同一个 MaiBot 实例对接同一平台的多个账号时，每个账号都能被稳定识别为"自身"，不会混淆 +- **自动获取 ID** — 适配器可以自动获取并上报自己的 ID，无需手动在配置中填写 +- **备用值回退** — 原本在配置里填写的平台账号配置仍被保留，仅在适配器没有上报身份时作为备用值使用 + +适配器实际上报的身份与备用配置的区分，可以在 WebUI 的设置页中查看：已发现账号列表会展示在线状态，并支持软禁用 / 恢复操作。详见 [WebUI 适配器管理](./../webui/adapter-management.md)。 + +## 群聊 / 私聊访问策略 {#adapter-access-policy} + +从 1.2.0 起，MaiBot 提供**统一适配器聊天名单策略**，可以独立控制群聊与私聊的放行： + +- **默认动作** — 群聊与私聊各自有独立的默认动作，默认都是"放行"（`allow`），也可以改为"拒绝"（`block`） +- **名单规则** — 可以为具体适配器配置 `allow_ids` / `deny_ids` 白名单与黑名单，精细控制哪些群 / 私聊可被该适配器接入 +- **配置文件** — 策略存放在独立的 `config/adapter_policy.toml` 中，文件不存在时默认放行；可通过 WebUI 的适配器管理页或聊天管理页维护 + +::: tip 兼容性说明 +为兼容现有适配器，群聊与私聊的默认动作都保持"放行"。只有当你显式改默认动作或添加名单规则时，访问控制才会收紧。 +::: + +## 相关文档 + +- [WebUI 适配器管理](./../webui/adapter-management.md) — 已发现账号、在线状态、软禁用 / 恢复 +- [消息服务器与适配器对接](../../develop/message-server-and-adapters.md) — 身份持久化、自动获取 ID 与访问策略的实现细节 +>>>>>>> Stashed changes