feat(platform): add slack eba adapter

- TelegramAdapter inherits AbstractPlatformAdapter with all capabilities
- TelegramEventConverter handles all Update types: message, edited_message,
  chat_member, my_chat_member, callback_query, message_reaction
- TelegramAPIMixin implements: edit_message, delete_message, forward_message,
  get_group_info, get_group_member_list/info, get_user_info, get_file_url,
  mute/unmute/kick_member, leave_group
- PLATFORM_API_MAP for call_platform_api: pin/unpin message, set chat title/desc,
  get admins, send chat action, create invite link, answer callback query
- Full backward compat: legacy FriendMessage/GroupMessage listeners still work
- Preserves all existing functionality: stream output, markdown card, forum topics
- Old sources/telegram.py untouched for gradual migration

.dockerignore

@@ -0,0 +1,8 @@
+.github
+.venv
+.vscode
+.data
+.temp
+web/.next
+web/node_modules
+web/.env

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -1,51 +1,30 @@
 name: 漏洞反馈
-description: 报错或漏洞请使用这个模板创建，不使用此模板创建的异常、漏洞相关issue将被直接关闭
+description: 【供中文用户】报错或漏洞请使用这个模板创建，不使用此模板创建的异常、漏洞相关issue将被直接关闭。由于自己操作不当/不甚了解所用技术栈引起的网络连接问题恕无法解决，请勿提 issue。容器间网络连接问题，参考文档 https://link.langbot.app/zh/docs/network  
 title: "[Bug]: "
 labels: ["bug?"]
 body:
-  - type: dropdown
-    attributes:
-      label: 部署方式
-      description: "主程序使用的部署方式"
-      options:
-        - 手动部署
-        - 安装器部署
-        - 一键安装包部署
-        - Docker部署
-    validations:
-      required: true
-  - type: dropdown
-    attributes:
-      label: 登录框架
-      description: "连接QQ使用的框架"
-      options:
-        - Mirai
-        - go-cqhttp
-    validations:
-      required: false
   - type: input
     attributes:
-      label: 系统环境
-      description: 操作系统、系统架构。
-      placeholder: 例如： CentOS x64、Windows11
-    validations:
-      required: true
-  - type: input
-    attributes:
-      label: Python环境
-      description: 运行程序的Python版本
-      placeholder: 例如： Python 3.10
+      label: 运行环境
+      description: LangBot 版本、操作系统、系统架构、**Python版本**、**主机地理位置**
+      placeholder: 例如：v3.3.0、CentOS x64 Python 3.10.3、Docker
     validations:
       required: true
   - type: textarea
     attributes:
       label: 异常情况
-      description: 完整描述异常情况，什么时候发生的、发生了什么
+      description: 完整描述异常情况，什么时候发生的、发生了什么。**请附带日志信息。** 
     validations:
       required: true
   - type: textarea
     attributes:
-      label: 报错信息
-      description: 请提供完整的**控制台**报错信息（若有）
+      label: 复现步骤
+      description: 提供越多信息，我们会越快解决问题，建议多提供配置截图；**如果涉及 Dify、n8n、Langflow 等外部平台，请提供应用的导出文件（如 Dify 应用的 DSL），我们将更快回复您。**
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: 启用的插件
+      description: 有些情况可能和插件功能有关，建议提供插件启用情况。
     validations:
       required: false

.github/ISSUE_TEMPLATE/bug-report_en.yml

@@ -0,0 +1,30 @@
+name: Bug report
+description: Report bugs or vulnerabilities using this template. For container network connection issues, refer to the documentation https://link.langbot.app/en/docs/network
+title: "[Bug]: "
+labels: ["bug?"]
+body:
+  - type: input
+    attributes:
+      label: Runtime environment
+      description: LangBot version, operating system, system architecture, **Python version**, **host location**
+      placeholder: "For example: v3.3.0, CentOS x64 Python 3.10.3, Docker"
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Exception
+      description: Describe the exception in detail, what happened and when it happened. **Please include log information.** 
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Reproduction steps
+      description: How to reproduce this problem, the more detailed the better; the more information you provide, the faster we will solve the problem.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Enabled plugins
+      description: Some cases may be related to plugin functionality, so please provide the plugin enablement status.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -1,7 +1,7 @@
 name: 需求建议
 title: "[Feature]: "
-labels: ["enhancement"]
-description: "新功能或现有功能优化请使用这个模板；不符合类别的issue将被直接关闭"
+labels: []
+description: "【供中文用户】新功能或现有功能优化请使用这个模板；不符合类别的issue将被直接关闭"
 body:
   - type: dropdown
     attributes:

.github/ISSUE_TEMPLATE/feature-request_en.yml

@@ -0,0 +1,21 @@
+name: Feature request
+title: "[Feature]: "
+labels: []
+description: "New features or existing feature improvements should use this template; issues that do not match will be closed directly"
+body:
+  - type: dropdown
+    attributes:
+      label: This is a?
+      description: New feature request or existing feature improvement
+      options:
+        - New feature
+        - Existing feature improvement
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Detailed description
+      description: Detailed description, the more detailed the better
+    validations:
+      required: true
+      

.github/ISSUE_TEMPLATE/submit-plugin.yml

@@ -0,0 +1,24 @@
+name: 提交新插件
+title: "[Plugin]: 请求登记新插件"
+labels: ["独立插件"]
+description: "【供中文用户】本模板供且仅供提交新插件使用"
+body:
+  - type: input
+    attributes:
+      label: 插件名称
+      description: 填写插件的名称
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: 插件代码库地址
+      description: 仅支持 Github
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: 插件简介
+      description: 插件的简介
+    validations:
+      required: true
+      

.github/ISSUE_TEMPLATE/submit-plugin_en.yml

@@ -0,0 +1,24 @@
+name: Submit a new plugin
+title: "[Plugin]: Request to register a new plugin"
+labels: ["Independent Plugin"]
+description: "This template is only for submitting new plugins"
+body:
+  - type: input
+    attributes:
+      label: Plugin name
+      description: Fill in the name of the plugin
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Plugin code repository address
+      description: Only support Github
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Plugin description
+      description: The description of the plugin
+    validations:
+      required: true
+      

.github/dependabot.yml

@@ -10,6 +10,4 @@ updates:
     schedule:
       interval: "weekly"
     allow:
-      - dependency-name: "yiri-mirai"
-      - dependency-name: "dulwich"
       - dependency-name: "openai"

.github/pull_request_template.md

@@ -1,25 +1,32 @@
-## 概述
+## 概述 / Overview
 
-实现/解决/优化的内容: 
+> 请在此部分填写你实现/解决/优化的内容:  
+> Summary of what you implemented/solved/optimized:
+> 
 
-### 事务
+### 更改前后对比截图 / Screenshots
 
-- [ ] 已阅读仓库[贡献指引](https://github.com/RockChinQ/QChatGPT/blob/master/CONTRIBUTING.md)
-- [ ] 已与维护者在issues或其他平台沟通此PR大致内容
+> 请在此部分粘贴更改前后对比截图（可以是界面截图、控制台输出、对话截图等）:  
+> Please paste the screenshots of changes before and after here (can be interface screenshots, console output, conversation screenshots, etc.):
+> 
+> 修改前 / Before:
+> 
+> 修改后 / After:
+> 
 
-## 以下内容可在起草PR后、合并PR前逐步完成
+## 检查清单 / Checklist
 
-### 功能
+### PR 作者完成 / For PR author
 
-- [ ] 已编写完善的配置文件字段说明（若有新增）
-- [ ] 已编写面向用户的新功能说明（若有必要）
-- [ ] 已测试新功能或更改
+*请在方括号间写`x`以打勾 / Please tick the box with `x`*
 
-### 兼容性
+- [ ] 阅读仓库[贡献指引](https://github.com/langbot-app/LangBot/blob/master/CONTRIBUTING.md)了吗？ / Have you read the [contribution guide](https://github.com/langbot-app/LangBot/blob/master/CONTRIBUTING.md)?
+- [ ] 与项目所有者沟通过了吗？ / Have you communicated with the project maintainer?
+- [ ] 我确定已自行测试所作的更改，确保功能符合预期。 / I have tested the changes and ensured they work as expected.
 
-- [ ] 已处理版本兼容性
-- [ ] 已处理插件兼容问题
+### 项目维护者完成 / For project maintainer
 
-### 风险
-
-可能导致或已知的问题: 
+- [ ] 相关 issues 链接了吗？ / Have you linked the related issues?
+- [ ] 配置项写好了吗？迁移写好了吗？生效了吗？ / Have you written the configuration items? Have you written the migration? Has it taken effect?
+- [ ] 依赖加到 pyproject.toml 和 core/bootutils/deps.py 了吗 / Have you added the dependencies to pyproject.toml and core/bootutils/deps.py?
+- [ ] 文档编写了吗？ / Have you written the documentation?

.github/workflows/build-dev-image.yaml

@@ -0,0 +1,29 @@
+name: Build Dev Image
+
+on:
+  push:
+  workflow_dispatch:
+
+jobs:
+  build-dev-image:
+    runs-on: ubuntu-latest
+    # 如果是tag则跳过
+    if: ${{ !startsWith(github.ref, 'refs/tags/') }}
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+        with:
+          persist-credentials: false
+
+      - name: Generate Tag
+        id: generate_tag
+        run: |
+          # 获取分支名称，把/替换为-
+          echo ${{ github.ref }} | sed 's/refs\/heads\///g' | sed 's/\//-/g'
+          echo ::set-output name=tag::$(echo ${{ github.ref }} | sed 's/refs\/heads\///g' | sed 's/\//-/g')
+      - name: Login to Registry
+        run: docker login --username=${{ secrets.DOCKER_USERNAME }} --password ${{ secrets.DOCKER_PASSWORD }}
+      - name: Build Docker Image
+        run: |
+          docker buildx create --name mybuilder --use
+          docker build -t rockchin/langbot:${{ steps.generate_tag.outputs.tag }} . --push

.github/workflows/build-docker-image.yml

@@ -0,0 +1,47 @@
+name: Build Docker Image
+on:
+  ## 发布release的时候会自动构建
+  release:
+    types: [published]
+jobs:
+  publish-docker-image:
+    runs-on: ubuntu-latest
+    name: Build image
+    
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+        with:
+          persist-credentials: false
+
+      - name: judge has env GITHUB_REF  # 如果没有GITHUB_REF环境变量，则把github.ref变量赋值给GITHUB_REF
+        run: |
+          if [ -z "$GITHUB_REF" ]; then
+            export GITHUB_REF=${{ github.ref }}
+            echo $GITHUB_REF
+          fi
+      - name: Check version
+        id: check_version
+        run: |
+          echo $GITHUB_REF
+          # 如果是tag，则去掉refs/tags/前缀
+          if [[ $GITHUB_REF == refs/tags/* ]]; then
+            echo "It's a tag"
+            echo $GITHUB_REF
+            echo $GITHUB_REF | awk -F '/' '{print $3}'
+            echo ::set-output name=version::$(echo $GITHUB_REF | awk -F '/' '{print $3}')
+          else
+            echo "It's not a tag"
+            echo $GITHUB_REF
+            echo ::set-output name=version::${GITHUB_REF}
+          fi
+      - name: Login to Registry
+        run: docker login --username=${{ secrets.DOCKER_USERNAME }} --password ${{ secrets.DOCKER_PASSWORD }}
+      - name: Create Buildx
+        run: docker buildx create --name mybuilder --use
+      - name: Build for Release # only relase, exlude pre-release
+        if: ${{ github.event.release.prerelease == false }}
+        run: docker buildx build --platform linux/arm64,linux/amd64 -t rockchin/langbot:${{ steps.check_version.outputs.version }} -t rockchin/langbot:latest . --push
+      - name: Build for Pre-release # no update for latest tag
+        if: ${{ github.event.release.prerelease == true }}
+        run: docker buildx build --platform linux/arm64,linux/amd64 -t rockchin/langbot:${{ steps.check_version.outputs.version }} . --push

.github/workflows/build-release-artifacts.yaml

@@ -0,0 +1,62 @@
+name: Build Release Artifacts
+
+on:
+  workflow_dispatch:
+  ## 发布release的时候会自动构建
+  release:
+    types: [published]
+
+jobs:
+  build-artifacts:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+        with:
+          persist-credentials: false
+
+      - name: Check version
+        id: check_version
+        run: |
+          echo $GITHUB_REF
+          # 如果是tag，则去掉refs/tags/前缀
+          if [[ $GITHUB_REF == refs/tags/* ]]; then
+            echo "It's a tag"
+            echo $GITHUB_REF
+            echo $GITHUB_REF | awk -F '/' '{print $3}'
+            echo ::set-output name=version::$(echo $GITHUB_REF | awk -F '/' '{print $3}')
+          else
+            echo "It's not a tag"
+            echo $GITHUB_REF
+            echo ::set-output name=version::${GITHUB_REF}
+          fi
+
+      - name: Make Temp Directory
+        run: |
+          mkdir -p /tmp/langbot_build_web
+          cp -r . /tmp/langbot_build_web
+      - name: Setup Node
+        uses: actions/setup-node@v2
+        with:
+          node-version: '22'
+      - name: Build Web
+        run: |
+          cd /tmp/langbot_build_web/web
+          npm install
+          npx vite build
+      - name: Package Output
+        run: |
+          cp -r /tmp/langbot_build_web/web/dist ./web
+      - name: Upload Artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: langbot-${{ steps.check_version.outputs.version }}-all
+          path: .
+
+      - name: Upload To Release
+        env:
+          GH_TOKEN: ${{ secrets.RELEASE_UPLOAD_GITHUB_TOKEN }}
+        run: |
+          # 本目录下所有文件打包成zip
+          zip -r langbot-${{ steps.check_version.outputs.version }}-all.zip .
+          gh release upload ${{ github.event.release.tag_name }} langbot-${{ steps.check_version.outputs.version }}-all.zip

.github/workflows/build_docker_image.yml

@@ -1,38 +0,0 @@
-name: Build Docker Image
-on:
-  #防止fork乱用action设置只能手动触发构建
-  workflow_dispatch:
-  ## 发布release的时候会自动构建
-  release:
-    types: [published]
-jobs:
-  publish-docker-image:
-      runs-on: ubuntu-latest
-      name: Build image
-      
-      steps:
-          - name: Checkout
-            uses: actions/checkout@v2
-          - name: judge has env GITHUB_REF  # 如果没有GITHUB_REF环境变量，则把github.ref变量赋值给GITHUB_REF
-            run: |
-              if [ -z "$GITHUB_REF" ]; then
-                export GITHUB_REF=${{ github.ref }}
-              fi
-          - name: Check GITHUB_REF env
-            run: echo $GITHUB_REF
-          - name: Get version
-            id: get_version
-            if: (startsWith(env.GITHUB_REF, 'refs/tags/')||startsWith(github.ref, 'refs/tags/')) && startsWith(github.repository, 'RockChinQ/QChatGPT')
-            run: echo ::set-output name=VERSION::${GITHUB_REF/refs\/tags\//}
-          - name: Build  # image name: rockchin/qchatgpt:<VERSION>
-            run: docker build --network=host -t rockchin/qchatgpt:${{ steps.get_version.outputs.VERSION }} -t rockchin/qchatgpt:latest .
-          - name: Login to Registry
-            run: docker login --username=${{ secrets.DOCKER_USERNAME }} --password ${{ secrets.DOCKER_PASSWORD }}
-          
-          - name: Push image
-            if: (startsWith(env.GITHUB_REF, 'refs/tags/')||startsWith(github.ref, 'refs/tags/')) && startsWith(github.repository, 'RockChinQ/QChatGPT')
-            run: docker push rockchin/qchatgpt:${{ steps.get_version.outputs.VERSION }}
-
-          - name: Push image
-            if: (startsWith(env.GITHUB_REF, 'refs/tags/')||startsWith(github.ref, 'refs/tags/')) && startsWith(github.repository, 'RockChinQ/QChatGPT')
-            run: docker push rockchin/qchatgpt:latest

.github/workflows/check-i18n.yml

@@ -0,0 +1,25 @@
+name: Check i18n Keys
+
+on:
+  push:
+    branches:
+      - main
+      - master
+
+jobs:
+  check-i18n:
+    name: Check i18n Key Consistency
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
+      - name: Check i18n keys against en-US reference
+        run: node web/scripts/check-i18n.mjs

.github/workflows/lint.yml

@@ -0,0 +1,60 @@
+name: Lint
+
+on:
+  push:
+    branches:
+      - main
+      - master
+      - dev
+  pull_request:
+    types: [opened, synchronize, reopened, ready_for_review]
+
+jobs:
+  ruff:
+    name: Ruff Lint & Format
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+
+      - name: Install dependencies
+        run: uv sync --dev
+
+      - name: Run ruff check
+        run: uv run ruff check src
+
+      - name: Run ruff format
+        run: uv run ruff format src --check
+
+  frontend:
+    name: Frontend Lint
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '25'
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 9
+
+      - name: Install dependencies
+        working-directory: web
+        run: pnpm install
+
+      - name: Run lint
+        working-directory: web
+        run: pnpm lint

.github/workflows/publish-to-pypi.yml

@@ -0,0 +1,46 @@
+name: Build and Publish to PyPI
+
+on:
+  workflow_dispatch:
+  release:
+    types: [published]
+
+jobs:
+  build-and-publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      id-token: write  # Required for trusted publishing to PyPI
+    
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+
+      - name: Build frontend
+        run: |
+          cd web
+          npm install -g pnpm
+          pnpm install
+          pnpm build
+          mkdir -p ../src/langbot/web/dist
+          cp -r dist ../src/langbot/web/
+
+      - name: Install the latest version of uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          version: "latest"
+
+      - name: Build package
+        run: |
+          uv build
+
+      - name: Publish to PyPI
+        run: |
+          uv publish --token ${{ secrets.PYPI_TOKEN }}

.github/workflows/run-tests.yml

@@ -0,0 +1,71 @@
+name: Unit Tests
+
+on:
+  pull_request:
+    types: [opened, ready_for_review, synchronize]
+    paths:
+      - 'pkg/**'
+      - 'tests/**'
+      - '.github/workflows/run-tests.yml'
+      - 'pyproject.toml'
+      - 'run_tests.sh'
+  push:
+    branches:
+      - master
+      - develop
+    paths:
+      - 'pkg/**'
+      - 'tests/**'
+      - '.github/workflows/run-tests.yml'
+      - 'pyproject.toml'
+      - 'run_tests.sh'
+
+jobs:
+  test:
+    name: Run Unit Tests
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ['3.11', '3.12', '3.13']
+      fail-fast: false
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install uv
+        run: |
+          curl -LsSf https://astral.sh/uv/install.sh | sh
+          echo "$HOME/.cargo/bin" >> $GITHUB_PATH
+
+      - name: Install dependencies
+        run: |
+          uv sync --dev
+
+      - name: Run unit tests
+        run: |
+          bash run_tests.sh
+
+      - name: Upload coverage to Codecov
+        if: matrix.python-version == '3.12'
+        uses: codecov/codecov-action@v5
+        with:
+          files: ./coverage.xml
+          flags: unit-tests
+          name: unit-tests-coverage
+          fail_ci_if_error: false
+        env:
+          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
+
+      - name: Test Summary
+        if: always()
+        run: |
+          echo "## Unit Tests Results" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "Python Version: ${{ matrix.python-version }}" >> $GITHUB_STEP_SUMMARY
+          echo "Test Status: ${{ job.status }}" >> $GITHUB_STEP_SUMMARY

.github/workflows/sync-wiki.yml

@@ -1,48 +0,0 @@
-name: Update Wiki
-
-on:
-  pull_request:
-    branches:
-      - master
-    paths:
-      - 'res/wiki/**'
-  push:
-    branches:
-      - master
-    paths:
-      - 'res/wiki/**'
-
-jobs:
-  update-wiki:
-    runs-on: ubuntu-latest
-    steps:
-    - name: Checkout
-      uses: actions/checkout@v2
-    - name: Setup Git
-      run: |
-        git config --global user.name "GitHub Actions"
-        git config --global user.email "github-actions[bot]@users.noreply.github.com"
-    - name: Clone Wiki Repository
-      uses: actions/checkout@v2
-      with:
-        repository: RockChinQ/QChatGPT.wiki
-        path: wiki
-    - name: Delete old wiki content
-      run: |
-        rm -rf wiki/*
-    - name: Copy res/wiki content to wiki
-      run: |
-        cp -r res/wiki/* wiki/
-    - name: Check for changes
-      run: |
-        cd wiki
-        if git diff --quiet; then
-          echo "No changes to commit."
-          exit 0
-        fi
-    - name: Commit and Push Changes
-      run: |
-        cd wiki
-        git add .
-        git commit -m "Update wiki"
-        git push

.github/workflows/test-dev-image.yaml

@@ -0,0 +1,108 @@
+name: Test Dev Image
+
+on:
+  workflow_run:
+    workflows: ["Build Dev Image"]
+    types:
+      - completed
+    branches:
+      - master
+
+jobs:
+  test-dev-image:
+    runs-on: ubuntu-latest
+    # Only run if the build workflow succeeded
+    if: ${{ github.event.workflow_run.conclusion == 'success' }}
+    
+    permissions:
+      contents: read
+    
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Update Docker Compose to use master tag
+        working-directory: ./docker
+        run: |
+          # Replace 'latest' with 'master' tag for testing the dev image
+          sed -i 's/rockchin\/langbot:latest/rockchin\/langbot:master/g' docker-compose.yaml
+          echo "Updated docker-compose.yaml to use master tag:"
+          cat docker-compose.yaml
+
+      - name: Start Docker Compose
+        working-directory: ./docker
+        run: docker compose up -d
+
+      - name: Wait and Test API
+        run: |
+          # Function to test API endpoint
+          test_api() {
+            echo "Testing API endpoint..."
+            response=$(curl -s --connect-timeout 10 --max-time 30 -w "\n%{http_code}" http://localhost:5300/api/v1/system/info 2>&1)
+            curl_exit_code=$?
+            
+            if [ $curl_exit_code -ne 0 ]; then
+              echo "Curl failed with exit code: $curl_exit_code"
+              echo "Error: $response"
+              return 1
+            fi
+            
+            http_code=$(echo "$response" | tail -n 1)
+            response_body=$(echo "$response" | head -n -1)
+            
+            if [ "$http_code" = "200" ]; then
+              echo "API is healthy! Response code: $http_code"
+              echo "Response: $response_body"
+              return 0
+            else
+              echo "API returned non-200 response: $http_code"
+              echo "Response body: $response_body"
+              return 1
+            fi
+          }
+
+          # Wait 30 seconds before first attempt
+          echo "Waiting 30 seconds for services to start..."
+          sleep 30
+
+          # Try up to 3 times with 30-second intervals
+          max_attempts=3
+          attempt=1
+
+          while [ $attempt -le $max_attempts ]; do
+            echo "Attempt $attempt of $max_attempts"
+            
+            if test_api; then
+              echo "Success! API is responding correctly."
+              exit 0
+            fi
+            
+            if [ $attempt -lt $max_attempts ]; then
+              echo "Retrying in 30 seconds..."
+              sleep 30
+            fi
+            
+            attempt=$((attempt + 1))
+          done
+
+          # All attempts failed
+          echo "Failed to get healthy response after $max_attempts attempts"
+          exit 1
+
+      - name: Show Container Logs on Failure
+        if: failure()
+        working-directory: ./docker
+        run: |
+          echo "=== Docker Compose Status ==="
+          docker compose ps
+          echo ""
+          echo "=== LangBot Logs ==="
+          docker compose logs langbot
+          echo ""
+          echo "=== Plugin Runtime Logs ==="
+          docker compose logs langbot_plugin_runtime
+
+      - name: Cleanup
+        if: always()
+        working-directory: ./docker
+        run: docker compose down

.github/workflows/test-migrations.yml

@@ -0,0 +1,171 @@
+name: Test Migrations
+
+on:
+  push:
+    branches:
+      - main
+      - master
+      - dev
+    paths:
+      - 'src/langbot/pkg/persistence/**'
+      - 'src/langbot/pkg/entity/persistence/**'
+  pull_request:
+    types: [opened, synchronize, reopened, ready_for_review]
+    paths:
+      - 'src/langbot/pkg/persistence/**'
+      - 'src/langbot/pkg/entity/persistence/**'
+
+jobs:
+  test-migrations-sqlite:
+    name: Migrations (SQLite)
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+
+      - name: Install dependencies
+        run: uv sync --dev
+
+      - name: Test Alembic upgrade (SQLite)
+        run: |
+          uv run python -c "
+          import asyncio
+          from sqlalchemy.ext.asyncio import create_async_engine
+          from langbot.pkg.entity.persistence.base import Base
+          from langbot.pkg.persistence.alembic_runner import run_alembic_upgrade, run_alembic_stamp, get_alembic_current
+
+          async def main():
+              engine = create_async_engine('sqlite+aiosqlite:///test_migrations.db')
+
+              # Create all tables (simulates existing DB)
+              async with engine.begin() as conn:
+                  await conn.run_sync(Base.metadata.create_all)
+
+              # Stamp baseline
+              await run_alembic_stamp(engine, '0001_baseline')
+              rev = await get_alembic_current(engine)
+              assert rev == '0001_baseline', f'Expected 0001_baseline, got {rev}'
+              print(f'Stamped: {rev}')
+
+              # Upgrade to head
+              await run_alembic_upgrade(engine, 'head')
+              rev = await get_alembic_current(engine)
+              print(f'After upgrade: {rev}')
+              assert rev is not None, 'Expected a revision after upgrade'
+
+              # Verify idempotent
+              await run_alembic_upgrade(engine, 'head')
+              rev2 = await get_alembic_current(engine)
+              assert rev2 == rev, f'Expected {rev}, got {rev2}'
+              print(f'Idempotent check passed: {rev2}')
+
+              # Fresh DB: upgrade from scratch
+              engine2 = create_async_engine('sqlite+aiosqlite:///test_migrations_fresh.db')
+              async with engine2.begin() as conn:
+                  await conn.run_sync(Base.metadata.create_all)
+              await run_alembic_upgrade(engine2, 'head')
+              rev3 = await get_alembic_current(engine2)
+              print(f'Fresh DB upgrade: {rev3}')
+              assert rev3 is not None
+
+              print('All SQLite migration tests passed!')
+
+          asyncio.run(main())
+          "
+
+  test-migrations-postgres:
+    name: Migrations (PostgreSQL)
+    runs-on: ubuntu-latest
+    services:
+      postgres:
+        image: postgres:16
+        env:
+          POSTGRES_USER: langbot
+          POSTGRES_PASSWORD: langbot
+          POSTGRES_DB: langbot_test
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd="pg_isready -U langbot"
+          --health-interval=5s
+          --health-timeout=5s
+          --health-retries=5
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+
+      - name: Install dependencies
+        run: uv sync --dev
+
+      - name: Test Alembic upgrade (PostgreSQL)
+        run: |
+          uv run python -c "
+          import asyncio
+          from sqlalchemy.ext.asyncio import create_async_engine
+          from langbot.pkg.entity.persistence.base import Base
+          from langbot.pkg.persistence.alembic_runner import run_alembic_upgrade, run_alembic_stamp, get_alembic_current
+
+          DB_URL = 'postgresql+asyncpg://langbot:langbot@localhost:5432/langbot_test'
+
+          async def main():
+              engine = create_async_engine(DB_URL)
+
+              # Create all tables
+              async with engine.begin() as conn:
+                  await conn.run_sync(Base.metadata.create_all)
+
+              # Stamp baseline
+              await run_alembic_stamp(engine, '0001_baseline')
+              rev = await get_alembic_current(engine)
+              assert rev == '0001_baseline', f'Expected 0001_baseline, got {rev}'
+              print(f'Stamped: {rev}')
+
+              # Upgrade to head
+              await run_alembic_upgrade(engine, 'head')
+              rev = await get_alembic_current(engine)
+              print(f'After upgrade: {rev}')
+              assert rev is not None
+
+              # Verify idempotent
+              await run_alembic_upgrade(engine, 'head')
+              rev2 = await get_alembic_current(engine)
+              assert rev2 == rev, f'Expected {rev}, got {rev2}'
+              print(f'Idempotent check passed: {rev2}')
+
+              # Fresh DB: drop all and upgrade from scratch
+              engine2 = create_async_engine(DB_URL.replace('langbot_test', 'langbot_fresh'))
+
+              # Create fresh database
+              from sqlalchemy import text
+              async with engine.connect() as conn:
+                  await conn.execute(text('COMMIT'))
+                  await conn.execute(text('CREATE DATABASE langbot_fresh'))
+
+              async with engine2.begin() as conn:
+                  await conn.run_sync(Base.metadata.create_all)
+              await run_alembic_upgrade(engine2, 'head')
+              rev3 = await get_alembic_current(engine2)
+              print(f'Fresh DB upgrade: {rev3}')
+              assert rev3 is not None
+
+              print('All PostgreSQL migration tests passed!')
+
+          asyncio.run(main())
+          "

.github/workflows/update-cmdpriv-template.yml

@@ -1,58 +0,0 @@
-name: Update cmdpriv-template
-
-on:
-  push:
-    paths:
-      - 'pkg/qqbot/cmds/**'
-  pull_request:
-    types: [closed]
-    paths:
-      - 'pkg/qqbot/cmds/**'
-
-jobs:
-  update-cmdpriv-template:
-    if: github.event.pull_request.merged == true || github.event_name == 'push'
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: 3.x
-
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        python -m pip install --upgrade  yiri-mirai openai colorlog func_timeout dulwich Pillow CallingGPT tiktoken
-
-    - name: Copy Scripts
-      run: |
-        cp res/scripts/generate_cmdpriv_template.py .  
-
-    - name: Generate Files
-      run: |
-        python main.py
-
-    - name: Run generate_cmdpriv_template.py
-      run: python3 generate_cmdpriv_template.py
-
-    - name: Check for changes in cmdpriv-template.json
-      id: check_changes
-      run: |
-        if git diff --name-only | grep -q "res/templates/cmdpriv-template.json"; then
-          echo "::set-output name=changes_detected::true"
-        else
-          echo "::set-output name=changes_detected::false"
-        fi
-
-    - name: Commit changes to cmdpriv-template.json
-      if: steps.check_changes.outputs.changes_detected == 'true'
-      run: |
-        git config --global user.name "GitHub Actions Bot"
-        git config --global user.email "<github-actions@github.com>"
-        git add res/templates/cmdpriv-template.json
-        git commit -m "Update cmdpriv-template.json"
-        git push

.github/workflows/update-override-all.yml

@@ -1,53 +0,0 @@
-name: Check and Update override_all
-
-on:
-  push:
-    paths:
-      - 'config-template.py'
-  pull_request:
-    types:
-      - closed
-    branches:
-      - master
-    paths:
-      - 'config-template.py'
-
-jobs:
-  update-override-all:
-    name: check and update
-    if: github.event.pull_request.merged == true || github.event_name == 'push'
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v2
-
-      - name: Set up Python
-        uses: actions/setup-python@v2
-        with:
-          python-version: 3.x
-
-      - name: Install dependencies
-        run: |
-          python -m pip install --upgrade pip
-          # 在此处添加您的项目所需的其他依赖
-
-      - name: Copy Scripts
-        run: |
-          cp res/scripts/generate_override_all.py .
-
-      - name: Run generate_override_all.py
-        run: python3 generate_override_all.py
-
-      - name: Check for changes in override-all.json
-        id: check_changes
-        run: |
-          git diff --exit-code override-all.json || echo "::set-output name=changes_detected::true"
-
-      - name: Commit and push changes
-        if: steps.check_changes.outputs.changes_detected == 'true'
-        run: |
-          git config --global user.email "github-actions[bot]@users.noreply.github.com"
-          git config --global user.name "GitHub Actions"
-          git add override-all.json
-          git commit -m "Update override-all.json"
-          git push

.gitignore

@@ -1,11 +1,11 @@
-config.py
+/config.py
 .idea/
 __pycache__/
 database.db
-qchatgpt.log
+langbot.log
 /banlist.py
-plugins/
-!plugins/__init__.py
+/plugins/
+!/plugins/__init__.py
 /revcfg.py
 prompts/
 logs/
@@ -16,18 +16,43 @@ scenario/
 !scenario/default-template.json
 override.json
 cookies.json
-res/announcement_saved
-res/announcement_saved.json
+data/labels/announcement_saved.json
 cmdpriv.json
 tips.py
-.venv
+venv*
 bin/
 .vscode
-test_*
+/test_*
 venv/
 hugchat.json
 qcapi
 claude.json
 bard.json
 /*yaml
-!/docker-compose.yaml
+!.pre-commit-config.yaml
+!components.yaml
+!/docker-compose.yaml
+data/labels/instance_id.json
+.DS_Store
+/data
+botpy.log*
+/poc
+/libs/wecom_api/test.py
+/venv
+test.py
+/web_ui
+.venv/
+/test
+plugins.bak
+coverage.xml
+.coverage
+src/langbot/web/
+testsdk/
+
+# Build artifacts
+/dist
+/build
+*.egg-info
+
+# Next.js build cache (legacy)
+web/.next/

.mcp.json

@@ -0,0 +1,37 @@
+{
+  "mcpServers": {
+    "shadcn": {
+      "command": "npx",
+      "args": [
+        "shadcn@latest",
+        "mcp"
+      ]
+    },
+    "sequential-thinking": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-sequential-thinking"],
+      "env": {}
+    },
+    "github": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-github"],
+      "env": {
+        "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PERSONAL_ACCESS_TOKEN}"
+      }
+    },
+    "fetch": {
+      "type": "stdio",
+      "command": "uvx",
+      "args": ["mcp-server-fetch"],
+      "env": {}
+    },
+    "playwright": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "@playwright/mcp@latest"],
+      "env": {}
+    }
+  }
+}

.pre-commit-config.yaml

@@ -0,0 +1,25 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    # Ruff version.
+    rev: v0.11.7
+    hooks:
+      # Run the linter of backend.
+      - id: ruff
+        args: [--fix]
+      # Run the formatter of backend.
+      - id: ruff-format
+
+  - repo: local
+    hooks:
+      - id: prettier
+        name: prettier
+        entry: npx --prefix web prettier --write --ignore-unknown
+        language: system
+        types_or: [javascript, jsx, ts, tsx, css, scss]
+
+      - id: lint-staged
+        name: lint-staged
+        entry: cd web && pnpm lint-staged
+        language: system
+        types: [javascript, jsx, ts, tsx]
+        pass_filenames: false

AGENTS.md

@@ -0,0 +1,88 @@
+# AGENTS.md
+
+This file is for guiding code agents (like Claude Code, GitHub Copilot, OpenAI Codex, etc.) to work in LangBot project.
+
+## Project Overview
+
+LangBot is a open-source LLM native instant messaging bot development platform, aiming to provide an out-of-the-box IM robot development experience, with Agent, RAG, MCP and other LLM application functions, supporting global instant messaging platforms, and providing rich API interfaces, supporting custom development.
+
+LangBot has a comprehensive frontend, all operations can be performed through the frontend. The project splited into these major parts:
+
+- `./src/langbot`: The main python package of the project, below are the main modules in this package:
+    - `./pkg`: The core python package of the project backend.
+        - `./pkg/platform`: The platform module of the project, containing the logic of message platform adapters, bot managers, message session managers, etc.
+        - `./pkg/provider`: The provider module of the project, containing the logic of LLM providers, tool providers, etc.
+        - `./pkg/pipeline`: The pipeline module of the project, containing the logic of pipelines, stages, query pool, etc.
+        - `./pkg/api`: The api module of the project, containing the http api controllers and services.
+        - `./pkg/plugin`: LangBot bridge for connecting with plugin system.
+    - `./libs`: Some SDKs we previously developed for the project, such as `qq_official_api`, `wecom_api`, etc.
+    - `./templates`: Templates of config files, components, etc.
+    - `./web`: Frontend codebase, built with Next.js + **shadcn** + **Tailwind CSS**.
+    - `./docker`: docker-compose deployment files.
+
+## Backend Development
+
+We use `uv` to manage dependencies.
+
+```bash
+pip install uv
+uv sync --dev
+```
+
+Start the backend and run the project in development mode.
+
+```bash
+uv run main.py
+```
+
+Then you can access the project at `http://127.0.0.1:5300`.
+
+## Frontend Development
+
+We use `pnpm` to manage dependencies.
+
+```bash
+cd web
+cp .env.example .env
+pnpm install
+pnpm dev
+```
+
+Then you can access the project at `http://127.0.0.1:3000`.
+
+## Plugin System Architecture
+
+LangBot is composed of various internal components such as Large Language Model tools, commands, messaging platform adapters, LLM requesters, and more. To meet extensibility and flexibility requirements, we have implemented a production-grade plugin system.
+
+Each plugin runs in an independent process, managed uniformly by the Plugin Runtime. It has two operating modes: `stdio` and `websocket`. When LangBot is started directly by users (not running in a container), it uses `stdio` mode, which is common for personal users or lightweight environments. When LangBot runs in a container, it uses `websocket` mode, designed specifically for production environments.
+
+Plugin Runtime automatically starts each installed plugin and interacts through stdio. In plugin development scenarios, developers can use the lbp command-line tool to start plugins and connect to the running Runtime via WebSocket for debugging.
+
+> Plugin SDK, CLI, Runtime, and entities definitions shared between LangBot and plugins are contained in the [`langbot-plugin-sdk`](https://github.com/langbot-app/langbot-plugin-sdk) repository.
+
+## Some Development Tips and Standards
+
+- LangBot is a global project, any comments in code should be in English, and user experience should be considered in all aspects.
+- Thus you should consider the i18n support in all aspects.
+- LangBot is widely adopted in both toC and toB scenarios, so you should consider the compatibility and security in all aspects.
+- If you were asked to make a commit, please follow the commit message format: 
+    - format: <type>(<scope>): <subject>
+    - type: must be a specific type, such as feat (new feature), fix (bug fix), docs (documentation), style (code style), refactor (refactoring), perf (performance optimization), etc.
+    - scope: the scope of the commit, such as the package name, the file name, the function name, the class name, the module name, etc.
+    - subject: the subject of the commit, such as the description of the commit, the reason for the commit, the impact of the commit, etc.
+- LangBot uses [Alembic](https://alembic.sqlalchemy.org/) to manage database migrations, supporting both SQLite and PostgreSQL. Migration files are located in `src/langbot/pkg/persistence/alembic/versions/`. If you changed the definition of database entities (ORM models), generate a new migration script by running `uv run python -m langbot.pkg.persistence.alembic_runner autogenerate "description of your change"` in the project root (requires `data/config.yaml` to exist). Review and edit the generated script before committing. Migrations are executed automatically on LangBot startup. For data migrations (e.g. modifying JSON field content), you need to manually add the migration code in the generated script.
+
+## Some Principles
+
+- Keep it simple, stupid.
+- Entities should not be multiplied unnecessarily
+- 八荣八耻
+
+    以瞎猜接口为耻，以认真查询为荣。
+    以模糊执行为耻，以寻求确认为荣。
+    以臆想业务为耻，以人类确认为荣。
+    以创造接口为耻，以复用现有为荣。
+    以跳过验证为耻，以主动测试为荣。
+    以破坏架构为耻，以遵循规范为荣。
+    以假装理解为耻，以诚实无知为荣。
+    以盲目修改为耻，以谨慎重构为荣。

CLAUDE.md

@@ -0,0 +1 @@
+AGENTS.md

CONTRIBUTING.md

@@ -5,22 +5,27 @@
 ### 贡献形式
 
 - 提交PR，解决issues中提到的bug或期待的功能
-- 提交PR，实现您设想的功能（请先提出issue与作者沟通）
-- 优化代码架构，使各个模块的组织更加整洁优雅
-- 在issues中提出发现的bug或者期待的功能
+- 提交PR，实现您设想的功能（请先提出issue与项目维护者沟通）
 - 为本项目在其他社交平台撰写文章、制作视频等
 - 为本项目的衍生项目作出贡献，或开发插件增加功能
 
-### 如何开始
+### 沟通语言规范
 
-- 加入本项目交流群，一同探讨项目相关事务
-- 解决本项目或衍生项目的issues中亟待解决的问题
-- 阅读并完善本项目文档
-- 在各个社交媒体撰写本项目教程等
+- 在 PR 和 Commit Message 中请使用全英文
+- 对于中文用户，issue 中可以使用中文
 
-### 代码规范
+<hr/>
 
-- 代码中的注解`务必`符合Google风格的规范
-- 模块顶部的引入代码请遵循`系统模块`、`第三方库模块`、`自定义模块`的顺序进行引入
-- `不要`直接引入模块的特定属性，而是引入这个模块，再通过`xxx.yyy`的形式使用属性
-- 任何作用域的字段`必须`先声明后使用，并在声明处注明类型提示
+## Guidelines
+
+### Contribution
+
+- Submit PRs to solve bugs or features in the issues
+- Submit PRs to implement your ideas (Please create an issue first and communicate with the project maintainer)
+- Write articles or make videos about this project on other social platforms
+- Contribute to the development of derivative projects, or develop plugins to add features
+
+### Spoken Language
+
+- Use English in PRs and Commit Messages
+- For English users, you can use English in issues

Dockerfile

@@ -1,14 +1,23 @@
-FROM python:3.10.13-alpine3.18
-WORKDIR /QChatGPT
+FROM node:22-alpine AS node
 
-COPY . /QChatGPT/
+WORKDIR /app
 
-RUN ls
+COPY web ./web
 
-RUN pip install -r requirements.txt
-RUN pip install -U websockets==10.0
+RUN cd web && npm install && npx vite build
 
-# 生成配置文件
-RUN python main.py
+FROM python:3.12.7-slim
 
-CMD [ "python", "main.py" ]
+WORKDIR /app
+
+COPY . .
+
+COPY --from=node /app/web/dist ./web/dist
+
+RUN apt update \
+    && apt install gcc -y \
+    && python -m pip install --no-cache-dir uv \
+    && uv sync \
+    && touch /.dockerenv
+
+CMD [ "uv", "run", "--no-sync", "main.py" ]

LICENSE

@@ -1,661 +1,201 @@
-                    GNU AFFERO GENERAL PUBLIC LICENSE
-                       Version 3, 19 November 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                            Preamble
-
-  The GNU Affero General Public License is a free, copyleft license for
-software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
-
-  The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works.  By contrast,
-our General Public Licenses are intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-  Developers that use our General Public Licenses protect your rights
-with two steps: (1) assert copyright on the software, and (2) offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
-
-  A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate.  Many developers of free software are heartened and
-encouraged by the resulting cooperation.  However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
-
-  The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community.  It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server.  Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
-
-  An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals.  This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                       TERMS AND CONDITIONS
-
-  0. Definitions.
-
-  "This License" refers to version 3 of the GNU Affero General Public License.
-
-  "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
-
-  To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
-  A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-  To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy.  Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-  To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies.  Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
-  An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License.  If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-  1. Source Code.
-
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
-form of a work.
-
-  A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-  The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form.  A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-  The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities.  However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work.  For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-  The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
-  The Corresponding Source for a work in source code form is that
-same work.
-
-  2. Basic Permissions.
-
-  All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met.  This License explicitly affirms your unlimited
-permission to run the unmodified Program.  The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work.  This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-  You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force.  You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright.  Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-  Conveying under any other circumstances is permitted solely under
-the conditions stated below.  Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-  No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-  When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-  4. Conveying Verbatim Copies.
-
-  You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-  You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-  5. Conveying Modified Source Versions.
-
-  You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-  A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit.  Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-  6. Conveying Non-Source Forms.
-
-  You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-
-  A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source.  The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-  If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information.  But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-  Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-  7. Additional Terms.
-
-  "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law.  If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-  When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it.  (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.)  You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-  Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-
-  All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10.  If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term.  If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-  If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-  Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-  8. Termination.
-
-  You may not propagate or modify a covered work except as expressly
-provided under this License.  Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-  However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-  Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-  Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License.  If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-  9. Acceptance Not Required for Having Copies.
-
-  You are not required to accept this License in order to receive or
-run a copy of the Program.  Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance.  However,
-nothing other than this License grants you permission to propagate or
-modify any covered work.  These actions infringe copyright if you do
-not accept this License.  Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-  10. Automatic Licensing of Downstream Recipients.
-
-  Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License.  You are not responsible
-for enforcing compliance by third parties with this License.
-
-  An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations.  If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-  You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License.  For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-  11. Patents.
-
-  A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based.  The
-work thus licensed is called the contributor's "contributor version".
-
-  A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version.  For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-  Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-  In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement).  To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-  If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients.  "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-  If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-  A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License.  You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-  Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-  12. No Surrender of Others' Freedom.
-
-  If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all.  For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-  13. Remote Network Interaction; Use with the GNU General Public License.
-
-  Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users
-interacting with it remotely through a computer network (if your version
-supports such interaction) an opportunity to receive the Corresponding
-Source of your version by providing access to the Corresponding Source
-from a network server at no charge, through some standard or customary
-means of facilitating copying of software.  This Corresponding Source
-shall include the Corresponding Source for any work covered by version 3
-of the GNU General Public License that is incorporated pursuant to the
-following paragraph.
-
-  Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU General Public License into a single
-combined work, and to convey the resulting work.  The terms of this
-License will continue to apply to the part which is the covered work,
-but the work with which it is combined will remain governed by version
-3 of the GNU General Public License.
-
-  14. Revised Versions of this License.
-
-  The Free Software Foundation may publish revised and/or new versions of
-the GNU Affero General Public License from time to time.  Such new versions
-will be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-  Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU Affero General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation.  If the Program does not specify a version number of the
-GNU Affero General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
-  If the Program specifies that a proxy can decide which future
-versions of the GNU Affero General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
-  Later license versions may give you additional or different
-permissions.  However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-  15. Disclaimer of Warranty.
-
-  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-  16. Limitation of Liability.
-
-  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
-  17. Interpretation of Sections 15 and 16.
-
-  If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-                     END OF TERMS AND CONDITIONS
-
-            How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU Affero General Public License as published
-    by the Free Software Foundation, either version 3 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU Affero General Public License for more details.
-
-    You should have received a copy of the GNU Affero General Public License
-    along with this program.  If not, see <https://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-  If your software can interact with users remotely through a computer
-network, you should also make sure that it provides a way for users to
-get its source.  For example, if your program is a web application, its
-interface could display a "Source" link that leads users to an archive
-of the code.  There are many ways you could offer source, and different
-solutions will be better for different programs; see section 13 for the
-specific requirements.
-
-  You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU AGPL, see
-<https://www.gnu.org/licenses/>.
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

README.md

@@ -1,372 +1,176 @@
-
 <p align="center">
-<img src="res/logo.png" alt="QChatGPT" width="120" />
-</p>
+<a href="https://langbot.app">
+<img width="130" src="res/logo-blue.png" alt="LangBot"/>
+</a>
 
 <div align="center">
 
-# QChatGPT
+<a href="https://www.producthunt.com/products/langbot?utm_source=badge-follow&utm_medium=badge&utm_source=badge-langbot" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/follow.svg?product_id=1077185&theme=light" alt="LangBot - Production&#0045;grade&#0032;IM&#0032;bot&#0032;made&#0032;easy&#0046; | Product Hunt" style="width: 250px; height: 54px;" width="250" height="54" /></a>
 
-<!-- 高稳定性/持续迭代/架构清晰/支持插件/高可自定义的 ChatGPT QQ机器人框架 -->
-“当然！下面是一个使用Java编写的快速排序算法的示例代码”
+<h3>Production-grade platform for building agentic IM bots.</h3>
+<h4>Quickly build, debug, and ship AI bots to Slack, Discord, Telegram, WeChat, and more.</h4>
 
-[![GitHub release (latest by date)](https://img.shields.io/github/v/release/RockChinQ/QChatGPT)](https://github.com/RockChinQ/QChatGPT/releases/latest)
-<a href="https://hub.docker.com/repository/docker/rockchin/qchatgpt">
-    <img src="https://img.shields.io/docker/pulls/rockchin/qchatgpt?color=blue" alt="docker pull">
-  </a>
-![Wakapi Count](https://wakapi.dev/api/badge/RockChinQ/interval:any/project:QChatGPT)
-<img src="https://img.shields.io/badge/python-3.9+-blue.svg" alt="python">
-<a href="https://github.com/RockChinQ/QChatGPT/wiki">
-<img alt="Static Badge" src="https://img.shields.io/badge/%E6%9F%A5%E7%9C%8B-%E9%A1%B9%E7%9B%AEWiki-blue">
-</a><br/>
-<a href="http://qm.qq.com/cgi-bin/qm/qr?_wv=1027&k=66-aWvn8cbP4c1ut_1YYkvvGVeEtyTH8&authKey=pTaKBK5C%2B8dFzQ4XlENf6MHTCLaHnlKcCRx7c14EeVVlpX2nRSaS8lJm8YeM4mCU&noverify=0&group_code=195992197">
-<img alt="Static Badge" src="https://img.shields.io/badge/%E5%AE%98%E6%96%B9%E7%BE%A4-195992197-purple">
-</a>
-<a href="http://qm.qq.com/cgi-bin/qm/qr?_wv=1027&k=nC80H57wmKPwRDLFeQrDDjVl81XuC21P&authKey=2wTUTfoQ5v%2BD4C5zfpuR%2BSPMDqdXgDXA%2FS2wHI1NxTfWIG%2B%2FqK08dgyjMMOzhXa9&noverify=0&group_code=738382634">
-<img alt="Static Badge" src="https://img.shields.io/badge/%E7%A4%BE%E5%8C%BA%E7%BE%A4-738382634-purple">
-</a>
-<a href="https://lazyfree.top/2023/08/16/QChatGPT%E4%BD%BF%E7%94%A8%E6%89%8B%E5%86%8C/">
-<img alt="Static Badge" src="https://img.shields.io/badge/%E6%9F%A5%E7%9C%8B-%E7%A4%BE%E5%8C%BA%E7%BC%96%E5%86%99%E4%BD%BF%E7%94%A8%E6%89%8B%E5%86%8C-blue">
-</a>
-<a href="https://www.bilibili.com/video/BV14h4y1w7TC">
-<img alt="Static Badge" src="https://img.shields.io/badge/%E8%A7%86%E9%A2%91%E6%95%99%E7%A8%8B-208647">
-</a>
-<a href="https://www.bilibili.com/video/BV11h4y1y74H">
-<img alt="Static Badge" src="https://img.shields.io/badge/Linux%E9%83%A8%E7%BD%B2%E8%A7%86%E9%A2%91-208647">
-</a>
+English / [简体中文](README_CN.md) / [繁體中文](README_TW.md) / [日本語](README_JP.md) / [Español](README_ES.md) / [Français](README_FR.md) / [한국어](README_KO.md) / [Русский](README_RU.md) / [Tiếng Việt](README_VI.md)
 
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&labelColor=%20%235462eb&logoColor=%20%23f5f5f5&color=%20%235462eb)](https://discord.gg/wdNEHETs87)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/langbot-app/LangBot)
+[![GitHub release (latest by date)](https://img.shields.io/github/v/release/langbot-app/LangBot)](https://github.com/langbot-app/LangBot/releases/latest)
+<img src="https://img.shields.io/badge/python-3.10 ~ 3.13 -blue.svg" alt="python">
+[![GitHub stars](https://img.shields.io/github/stars/langbot-app/LangBot?style=social)](https://github.com/langbot-app/LangBot/stargazers)
+
+<a href="https://langbot.app">Website</a> ｜
+<a href="https://link.langbot.app/en/docs/features">Features</a> ｜
+<a href="https://link.langbot.app/en/docs/guide">Docs</a> ｜
+<a href="https://link.langbot.app/en/docs/api">API</a> ｜
+<a href="https://space.langbot.app/cloud">Cloud</a> ｜
+<a href="https://space.langbot.app">Plugin Market</a> ｜
+<a href="https://langbot.featurebase.app/roadmap">Roadmap</a>
 
-<details>
-<summary>回复效果演示（带有联网插件）</summary>
-<img alt="联网演示GIF" src="res/webwlkr-demo.gif" width="300px">
-</details>
 </div>
 
-> **NOTE**  
-> 2023/9/13 现已支持通过[One API](https://github.com/songquanpeng/one-api)接入 Azure、Anthropic Claude、Google PaLM 2、智谱 ChatGLM、百度文心一言、讯飞星火认知、阿里通义千问以及 360 智脑等模型，欢迎测试并反馈。  
-> 2023/8/29 [逆向库插件](https://github.com/RockChinQ/revLibs)已支持 gpt4free  
-> 2023/8/14 [逆向库插件](https://github.com/RockChinQ/revLibs)已支持Claude和Bard  
-> 2023/7/29 支持使用GPT的Function Calling功能实现类似ChatGPT Plugin的效果，请见[Wiki内容函数](https://github.com/RockChinQ/QChatGPT/wiki/6-%E6%8F%92%E4%BB%B6%E4%BD%BF%E7%94%A8-%E5%86%85%E5%AE%B9%E5%87%BD%E6%95%B0)  
+</p>
 
-<details>
-<summary>
+---
 
-## 🍺模型一览和功能点
+## What is LangBot?
 
-</summary>
+LangBot is an **open-source, production-grade platform** for building AI-powered instant messaging bots. It connects Large Language Models (LLMs) to any chat platform, enabling you to create intelligent agents that can converse, execute tasks, and integrate with your existing workflows.
 
-### 文字对话
+### Key Capabilities
 
-- OpenAI GPT-3.5模型(ChatGPT API), 本项目原生支持, 默认使用
-- OpenAI GPT-3模型, 本项目原生支持, 部署完成后前往`config.py`切换
-- OpenAI GPT-4模型, 本项目原生支持, 目前需要您的账户通过OpenAI的内测申请, 请前往`config.py`切换
-- ChatGPT网页版GPT-3.5模型, 由[插件](https://github.com/RockChinQ/revLibs)接入
-- ChatGPT网页版GPT-4模型, 目前需要ChatGPT Plus订阅, 由[插件](https://github.com/RockChinQ/revLibs)接入
-- New Bing逆向库, 由[插件](https://github.com/RockChinQ/revLibs)接入
-- HuggingChat, 由[插件](https://github.com/RockChinQ/revLibs)接入, 仅支持英文
-- Claude, 由[插件](https://github.com/RockChinQ/revLibs)接入
-- Google Bard, 由[插件](https://github.com/RockChinQ/revLibs)接入
+- **AI Conversations & Agents** — Multi-turn dialogues, tool calling, multi-modal support, streaming output. Built-in RAG (knowledge base) with deep integration to [Dify](https://dify.ai), [Coze](https://coze.com), [n8n](https://n8n.io), [Langflow](https://langflow.org).
+- **Universal IM Platform Support** — One codebase for Discord, Telegram, Slack, LINE, QQ, WeChat, WeCom, Lark, DingTalk, KOOK.
+- **Production-Ready** — Access control, rate limiting, sensitive word filtering, comprehensive monitoring, and exception handling. Trusted by enterprises.
+- **Plugin Ecosystem** — Hundreds of plugins, event-driven architecture, component extensions, and [MCP protocol](https://modelcontextprotocol.io/) support.
+- **Web Management Panel** — Configure, manage, and monitor your bots through an intuitive browser interface. No YAML editing required.
+- **Multi-Pipeline Architecture** — Different bots for different scenarios, with comprehensive monitoring and exception handling.
 
-### 模型聚合平台
+[→ Learn more about all features](https://link.langbot.app/en/docs/features)
 
-- [One API](https://github.com/songquanpeng/one-api), Azure、Anthropic Claude、Google PaLM 2、智谱 ChatGLM、百度文心一言、讯飞星火认知、阿里通义千问以及 360 智脑等模型的官方接口转换成 OpenAI API 接入，QChatGPT 原生支持，您需要先配置 One API，之后在`config.py`中设置反向代理和`One API`的密钥后使用。
-- [gpt4free](https://github.com/xtekky/gpt4free), 破解以免费使用多个平台的各种文字模型, 由[插件](https://github.com/RockChinQ/revLibs)接入, 无需鉴权, 稳定性较差。
-- [Poe](https://poe.com), 破解免费使用Poe上多个平台的模型, 由[oliverkirk-sudo/ChatPoeBot](https://github.com/oliverkirk-sudo/ChatPoeBot)接入（由于 Poe 上可用的大部分模型现已通过[revLibs插件](https://github.com/RockChinQ/revLubs)或其他方式接入，此插件现已停止维护）。
+---
 
-### 故事续写
+## Quick Start
 
-- NovelAI API, 由[插件](https://github.com/dominoar/QCPNovelAi)接入
+### ☁️ LangBot Cloud (Recommended)
 
-### 图片绘制
+**[LangBot Cloud](https://space.langbot.app/cloud)** — Zero deployment, ready to use.
 
-- OpenAI DALL·E模型, 本项目原生支持, 使用方法查看[Wiki功能使用页](https://github.com/RockChinQ/QChatGPT/wiki/1-%E5%8A%9F%E8%83%BD%E4%BD%BF%E7%94%A8#%E5%8A%9F%E8%83%BD%E7%82%B9%E5%88%97%E4%B8%BE)
-- NovelAI API, 由[插件](https://github.com/dominoar/QCPNovelAi)接入
-
-### 语音生成
-
-- TTS+VITS, 由[插件](https://github.com/dominoar/QChatPlugins)接入
-- Plachta/VITS-Umamusume-voice-synthesizer, 由[插件](https://github.com/oliverkirk-sudo/chat_voice)接入
-
-
-安装[此插件](https://github.com/RockChinQ/Switcher)，即可在使用中切换文字模型。
-
-### 功能点
-
-<details>
-<summary>✅支持敏感词过滤，避免账号风险</summary>
-
-  - 难以监测机器人与用户对话时的内容，故引入此功能以减少机器人风险
-  - 加入了百度云内容审核，在`config.py`中修改`baidu_check`的值，并填写`baidu_api_key`和`baidu_secret_key`以开启此功能
-  - 编辑`sensitive.json`，并在`config.py`中修改`sensitive_word_filter`的值以开启此功能
-</details>
-
-<details>
-<summary>✅群内多种响应规则，不必at</summary>
-
-  - 默认回复`ai`作为前缀或`@`机器人的消息
-  - 详细见`config.py`中的`response_rules`字段
-</details>
-
-<details>
-<summary>✅完善的多api-key管理，超额自动切换</summary>
-
-  - 支持配置多个`api-key`，内部统计使用量并在超额时自动切换
-  - 请在`config.py`中修改`openai_config`的值以设置`api-key`
-  - 可以在`config.py`中修改`api_key_fee_threshold`来自定义切换阈值
-  - 运行期间向机器人说`!usage`以查看当前使用情况
-</details>
-
-<details>
-<summary>✅支持预设指令文字</summary>
-
-  - 支持以自然语言预设文字，自定义机器人人格等信息
-  - 详见`config.py`中的`default_prompt`部分
-  - 支持设置多个预设情景，并通过!reset、!default等指令控制，详细请查看[wiki指令](https://github.com/RockChinQ/QChatGPT/wiki/1-%E5%8A%9F%E8%83%BD%E4%BD%BF%E7%94%A8#%E6%9C%BA%E5%99%A8%E4%BA%BA%E6%8C%87%E4%BB%A4)
-</details>
-
-<details>
-<summary>✅支持对话、绘图等模型，可玩性更高</summary>
-
-  - 现已支持OpenAI的对话`Completion API`和绘图`Image API`
-  - 向机器人发送指令`!draw <prompt>`即可使用绘图模型
-</details>
-<details>
-<summary>✅支持指令控制热重载、热更新</summary>
-
-  - 允许在运行期间修改`config.py`或其他代码后，以管理员账号向机器人发送指令`!reload`进行热重载，无需重启
-  - 运行期间允许以管理员账号向机器人发送指令`!update`进行热更新，拉取远程最新代码并执行热重载
-</details>
-<details>
-<summary>✅支持插件加载🧩</summary>
-
-  - 自行实现插件加载器及相关支持
-  - 支持GPT的Function Calling功能
-  - 详细查看[插件使用页](https://github.com/RockChinQ/QChatGPT/wiki/5-%E6%8F%92%E4%BB%B6%E4%BD%BF%E7%94%A8)
-</details>
-<details>
-<summary>✅私聊、群聊黑名单机制</summary>
-
-  - 支持将人或群聊加入黑名单以忽略其消息
-  - 详见Wiki`加入黑名单`节
-</details>
-<details>
-<summary>✅长消息处理策略</summary>
-
-  - 支持将长消息转换成图片或消息记录组件，避免消息刷屏
-  - 请查看`config.py`中`blob_message_strategy`等字段
-</details>
-<details>
-<summary>✅回复速度限制</summary>
-
-  - 支持限制单会话内每分钟可进行的对话次数
-  - 具有“等待”和“丢弃”两种策略
-    - “等待”策略：在获取到回复后，等待直到此次响应时间达到对话响应时间均值
-    - “丢弃”策略：此分钟内对话次数达到限制时，丢弃之后的对话
-  - 详细请查看config.py中的相关配置
-</details>
-<details>
-<summary>✅支持使用网络代理</summary>
-
-  - 目前已支持正向代理访问接口
-  - 详细请查看config.py中的`openai_config`的说明
-</details>
-<details>
-<summary>✅支持自定义提示内容</summary>
-
-  - 允许用户自定义报错、帮助等提示信息
-  - 请查看`tips.py`
-</details>
-
-### 🏞️截图
-
-<img alt="私聊GPT-3.5" src="res/screenshots/person_gpt3.5.png" width="400"/>
-<br/>
-<img alt="群聊GPT-3.5" src="res/screenshots/group_gpt3.5.png" width="400"/>
-<br/>
-<img alt="New Bing" src="res/screenshots/person_newbing.png" width="400"/>
-
-详情请查看[Wiki功能使用页](https://github.com/RockChinQ/QChatGPT/wiki/1-%E5%8A%9F%E8%83%BD%E4%BD%BF%E7%94%A8)
-
-</details>
-
-<details>
-
-<summary>
-
-## 🚀部署和使用
-
-</summary>
-
-> **NOTE**  
-> - 部署过程中遇到任何问题，请先在[QChatGPT](https://github.com/RockChinQ/QChatGPT/issues)或[qcg-installer](https://github.com/RockChinQ/qcg-installer/issues)的issue里进行搜索  
-> - QChatGPT需要Python版本>=3.9  
-> - 官方群和社区群群号请见文档顶部
-
-### - 注册OpenAI账号
-
-<details>
-<summary>点此查看步骤</summary>
-
-> 若您要直接使用非OpenAI的模型（如New Bing），可跳过此步骤，直接进行之后的部署，完成后按照相关插件的文档进行配置即可
-
-参考以下文章自行注册
-
-> [国内注册ChatGPT的方法(100%可用)](https://www.pythonthree.com/register-openai-chatgpt/)  
-> [手把手教你如何注册ChatGPT，超级详细](https://guxiaobei.com/51461)
-
-注册成功后请前往[个人中心查看](https://beta.openai.com/account/api-keys)api_key  
-完成注册后，使用以下自动化或手动部署步骤
-
-</details>
-
-### - Docker或自动化部署
-
-<details>
-<summary>展开查看，以下方式二选一，Linux首选Docker，Windows首选安装器</summary>
-
-#### Docker方式
-
-> docker方式较为复杂，若您不**熟悉**docker的操作及相关知识，强烈建议您使用其他方式部署，我们**不会且难以**解决您主机上多个容器的连接问题。
-
-请查看[此文档](res/docs/docker_deployment.md)  
-
-#### 安装器方式
-
-使用[此安装器](https://github.com/RockChinQ/qcg-installer)（若无法访问请到[Gitee](https://gitee.com/RockChin/qcg-installer)）进行部署
-
-- 安装器目前仅支持部分平台，请到仓库文档查看，其他平台请手动部署
-
-</details>
-
-### - 手动部署
-<details>
-<summary>手动部署适用于所有平台</summary>
-
-- 请使用Python 3.9.x以上版本   
-
-#### ① 配置QQ登录框架
-
-目前支持mirai和go-cqhttp，配置任意一个即可
-
-<details>
-<summary>mirai</summary>
-
-1. 按照[此教程](https://yiri-mirai.wybxc.cc/tutorials/01/configuration)配置Mirai及mirai-api-http  
-2. 启动mirai-console后，使用`login`命令登录QQ账号，保持mirai-console运行状态  
-3. 在下一步配置主程序时请在config.py中将`msg_source_adapter`设为`yirimirai`
-
-</details>
-
-<details>
-<summary>go-cqhttp</summary>
-
-1. 按照[此文档](https://github.com/RockChinQ/QChatGPT/wiki/9-go-cqhttp%E9%85%8D%E7%BD%AE)配置go-cqhttp
-2. 启动go-cqhttp，确保登录成功，保持运行
-3. 在下一步配置主程序时请在config.py中将`msg_source_adapter`设为`nakuru`
-
-</details>
-
-#### ② 配置主程序
-
-1. 克隆此项目
+### One-Line Launch
 
 ```bash
-git clone https://github.com/RockChinQ/QChatGPT
-cd QChatGPT
+uvx langbot
 ```
 
-2. 安装依赖
+> Requires [uv](https://docs.astral.sh/uv/getting-started/installation/). Visit http://localhost:5300 — done.
+
+### Docker Compose
 
 ```bash
-pip3 install requests yiri-mirai openai colorlog func_timeout dulwich Pillow nakuru-project-idk CallingGPT tiktoken
+git clone https://github.com/langbot-app/LangBot
+cd LangBot/docker
+docker compose up -d
 ```
 
-3. 运行一次主程序，生成配置文件
+### One-Click Cloud Deploy
 
-```bash
-python3 main.py
-```
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/en-US/templates/ZKTBDH)
+[![Deploy on Railway](https://railway.com/button.svg)](https://railway.app/template/yRrAyL?referralCode=vogKPF)
 
-4. 编辑配置文件`config.py`
+**More options:** [Docker](https://link.langbot.app/en/docs/docker) · [Manual](https://link.langbot.app/en/docs/manual-deploy) · [BTPanel](https://link.langbot.app/en/docs/bt-panel) · [Kubernetes](./docker/README_K8S.md)
 
-按照文件内注释填写配置信息
+---
 
-5. 运行主程序
+## Supported Platforms
 
-```bash
-python3 main.py
-```
+| Platform | Status | Notes |
+|----------|--------|-------|
+| Discord | ✅ | Official |
+| Telegram | ✅ | Official |
+| Slack | ✅ | Official |
+| LINE | ✅ | Official |
+| QQ | ✅ | Personal & Official API (Channel, DM, Group) |
+| WeCom | ✅ | Enterprise WeChat, External CS, AI Bot |
+| WeChat | ✅ | Personal & Official Account |
+| Lark | ✅ | Official |
+| DingTalk | ✅ | Official |
+| KOOK | ✅ | Official |
+| Satori | ✅ |  |
+| Email | ✅ | Matrix, Satori |
+| Matrix | ✅ | Supports multiple bridged platforms such as Signal, WhatsApp, Messenger, iMessage, Mattermost, Google Chat, IRC, XMPP, Zulip, and more |
 
-无报错信息即为运行成功
+---
 
-**常见问题**
+## Supported LLMs & Integrations
 
-- mirai登录提示`QQ版本过低`，见[此issue](https://github.com/RockChinQ/QChatGPT/issues/137)
-- 如提示安装`uvicorn`或`hypercorn`请*不要*安装，这两个不是必需的，目前存在未知原因bug
-- 如报错`TypeError: As of 3.10, the *loop* parameter was removed from Lock() since it is no longer necessary`, 请参考 [此处](https://github.com/RockChinQ/QChatGPT/issues/5)
+| Provider                                                                                                          | Type         | Status |
+| ----------------------------------------------------------------------------------------------------------------- | ------------ | ------ |
+| [OpenAI](https://platform.openai.com/)                                                                            | LLM          | ✅     |
+| [Anthropic](https://www.anthropic.com/)                                                                           | LLM          | ✅     |
+| [DeepSeek](https://www.deepseek.com/)                                                                             | LLM          | ✅     |
+| [Google Gemini](https://aistudio.google.com/prompts/new_chat)                                                     | LLM          | ✅     |
+| [xAI](https://x.ai/)                                                                                              | LLM          | ✅     |
+| [Moonshot](https://www.moonshot.cn/)                                                                              | LLM          | ✅     |
+| [Zhipu AI](https://open.bigmodel.cn/)                                                                             | LLM          | ✅     |
+| [Ollama](https://ollama.com/)                                                                                     | Local LLM    | ✅     |
+| [LM Studio](https://lmstudio.ai/)                                                                                 | Local LLM    | ✅     |
+| [Dify](https://dify.ai)                                                                                           | LLMOps       | ✅     |
+| [MCP](https://modelcontextprotocol.io/)                                                                           | Protocol     | ✅     |
+| [SiliconFlow](https://siliconflow.cn/)                                                                            | Gateway      | ✅     |
+| [Aliyun Bailian](https://bailian.console.aliyun.com/)                                                             | Gateway      | ✅     |
+| [Volc Engine Ark](https://console.volcengine.com/ark/region:ark+cn-beijing/model?vendor=Bytedance&view=LIST_VIEW) | Gateway      | ✅     |
+| [ModelScope](https://modelscope.cn/docs/model-service/API-Inference/intro)                                        | Gateway      | ✅     |
+| [GiteeAI](https://ai.gitee.com/)                                                                                  | Gateway      | ✅     |
+| [CompShare](https://www.compshare.cn/?ytag=GPU_YY-gh_langbot)                                                     | GPU Platform | ✅     |
+| [PPIO](https://ppinfra.com/user/register?invited_by=QJKFYD&utm_source=github_langbot)                             | GPU Platform | ✅     |
+| [ShengSuanYun](https://www.shengsuanyun.com/?from=CH_KYIPP758)                                                    | GPU Platform | ✅     |
+| [接口 AI](https://jiekou.ai/)                                                                                     | Gateway      | ✅     |
+| [302.AI](https://share.302.ai/SuTG99)                                                                             | Gateway      | ✅     |
+| [Qiniu](https://www.qiniu.com/ai/agent)                                                                           | Gateway      | ✅     |
 
-</details>
+[→ View all integrations](https://link.langbot.app/en/docs/features)
 
-**部署完成后必看: [指令说明](https://github.com/RockChinQ/QChatGPT/wiki/1-%E5%8A%9F%E8%83%BD%E4%BD%BF%E7%94%A8#%E6%9C%BA%E5%99%A8%E4%BA%BA%E6%8C%87%E4%BB%A4)**  
+---
 
-所有功能查看[Wiki功能使用页](https://github.com/RockChinQ/QChatGPT/wiki/1-%E5%8A%9F%E8%83%BD%E4%BD%BF%E7%94%A8)  
+## Why LangBot?
 
-</details>
+| Use Case                    | How LangBot Helps                                                                          |
+| --------------------------- | ------------------------------------------------------------------------------------------ |
+| **Customer Support**        | Deploy AI agents to Slack/Discord/Telegram that answer questions using your knowledge base |
+| **Internal Tools**          | Connect n8n/Dify workflows to WeCom/DingTalk for automated business processes              |
+| **Community Management**    | Moderate QQ/Discord groups with AI-powered content filtering and interaction               |
+| **Multi-Platform Presence** | One bot, all platforms. Manage from a single dashboard                                     |
 
-<details>
-<summary>
+---
 
-## 🧩插件生态
+## Live Demo
 
-</summary>
+**Try it now:** https://demo.langbot.dev/
 
-⭐我们已经支持了[GPT的Function Calling能力](https://platform.openai.com/docs/guides/gpt/function-calling)，请查看[Wiki内容函数](https://github.com/RockChinQ/QChatGPT/wiki/6-%E6%8F%92%E4%BB%B6%E4%BD%BF%E7%94%A8-%E5%86%85%E5%AE%B9%E5%87%BD%E6%95%B0)  
+- Email: `demo@langbot.app`
+- Password: `langbot123456`
 
-> 使用方法见：[Wiki插件使用](https://github.com/RockChinQ/QChatGPT/wiki/5-%E6%8F%92%E4%BB%B6%E4%BD%BF%E7%94%A8)  
-> 开发教程见：[Wiki插件开发](https://github.com/RockChinQ/QChatGPT/wiki/7-%E6%8F%92%E4%BB%B6%E5%BC%80%E5%8F%91)
+_Note: Public demo environment. Do not enter sensitive information._
 
+---
 
-[所有插件列表](https://github.com/stars/RockChinQ/lists/qchatgpt-%E6%8F%92%E4%BB%B6)，欢迎提出issue以提交新的插件
+## Community
 
-### 部分插件
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&label=Discord)](https://discord.gg/wdNEHETs87)
 
-- [WebwlkrPlugin](https://github.com/RockChinQ/WebwlkrPlugin) - 让机器人能联网！！
-- [revLibs](https://github.com/RockChinQ/revLibs) - 将ChatGPT网页版、Claude、Bard、Hugging Chat等破解版接入此项目，关于[官方接口和网页版有什么区别](https://github.com/RockChinQ/QChatGPT/wiki/8-%E5%AE%98%E6%96%B9%E6%8E%A5%E5%8F%A3%E3%80%81ChatGPT%E7%BD%91%E9%A1%B5%E7%89%88%E3%80%81ChatGPT-API%E5%8C%BA%E5%88%AB)
-- [Switcher](https://github.com/RockChinQ/Switcher) - 支持通过指令切换使用的模型
-- [hello_plugin](https://github.com/RockChinQ/hello_plugin) - `hello_plugin` 的储存库形式，插件开发模板
-- [dominoar/QChatPlugins](https://github.com/dominoar/QchatPlugins) - dominoar编写的诸多新功能插件（语音输出、Ranimg、屏蔽词规则等）
-- [dominoar/QCP-NovelAi](https://github.com/dominoar/QCP-NovelAi) - NovelAI 故事叙述与绘画
-- [oliverkirk-sudo/chat_voice](https://github.com/oliverkirk-sudo/chat_voice) - 文字转语音输出，支持HuggingFace上的[VITS模型](https://huggingface.co/spaces/Plachta/VITS-Umamusume-voice-synthesizer),azure语音合成,vits本地语音合成,sovits语音合成
-- [RockChinQ/WaitYiYan](https://github.com/RockChinQ/WaitYiYan) - 实时获取百度`文心一言`等待列表人数
-- [chordfish-k/QChartGPT_Emoticon_Plugin](https://github.com/chordfish-k/QChartGPT_Emoticon_Plugin) - 使机器人根据回复内容发送表情包
-- [oliverkirk-sudo/ChatPoeBot](https://github.com/oliverkirk-sudo/ChatPoeBot) - 接入[Poe](https://poe.com/)上的机器人
-- [lieyanqzu/WeatherPlugin](https://github.com/lieyanqzu/WeatherPlugin) - 天气查询插件
-- [SysStatPlugin](https://github.com/RockChinQ/SysStatPlugin) - 查看系统状态
-- [oliverkirk-sudo/qchat_system_status](https://github.com/oliverkirk-sudo/qchat_system_status) - 以图片的形式输出系统状态
-- [oliverkirk-sudo/QChatAIPaint](https://github.com/oliverkirk-sudo/QChatAIPaint) - 基于[Holara](https://holara.ai/)的ai绘图插件
-- [oliverkirk-sudo/QChatCodeRunner](https://github.com/oliverkirk-sudo/QChatCodeRunner) - 基于[CodeRunner-Plugin](https://github.com/oliverkirk-sudo/CodeRunner-Plugin)的代码运行与图表生成插件
-- [oliverkirk-sudo/QChatWeather](https://github.com/oliverkirk-sudo/QChatWeather) - 生成好看的天气图片，基于和风天气
-- [oliverkirk-sudo/QChatMarkdown](https://github.com/oliverkirk-sudo/QChatMarkdown) - 将机器人输出的markdown转换为图片，基于[playwright](https://playwright.dev/python/docs/intro)
-- [ruuuux/WikipediaSearch](https://github.com/ruuuux/WikipediaSearch) - Wikipedia 搜索插件
+- [Discord Community](https://discord.gg/wdNEHETs87)
 
-</details>
+---
 
-<details>
+## Star History
 
-<summary>
+[![Star History Chart](https://api.star-history.com/svg?repos=langbot-app/LangBot&type=Date)](https://star-history.com/#langbot-app/LangBot&Date)
 
-## 😘致谢和赞赏
+---
 
-</summary>
+## Contributors
 
-- [@the-lazy-me](https://github.com/the-lazy-me) 为本项目制作[视频教程](https://www.bilibili.com/video/BV1Y14y1Q7kQ)
-- [@mikumifa](https://github.com/mikumifa) 本项目Docker部署仓库开发者
-- [@dominoar](https://github.com/dominoar) 为本项目开发多种插件
-- [@万神的星空](https://github.com/qq255204159)  整合包发行
-- [@ljcduo](https://github.com/ljcduo)  GPT-4 API内测账号提供
+Thanks to all [contributors](https://github.com/langbot-app/LangBot/graphs/contributors) who have helped make LangBot better:
 
-以及所有[贡献者](https://github.com/RockChinQ/QChatGPT/graphs/contributors)和其他为本项目提供支持的朋友们。
-
-<img alt="赞赏码" src="res/mm_reward_qrcode_1672840549070.png" width="400" height="400"/>
-
-</details>
+<a href="https://github.com/langbot-app/LangBot/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=langbot-app/LangBot" />
+</a>

README_CN.md

@@ -0,0 +1,199 @@
+<p align="center">
+<a href="https://langbot.app">
+<img width="130" src="res/logo-blue.png" alt="LangBot"/>
+</a>
+
+<div align="center">
+
+<a href="https://hellogithub.com/repository/langbot-app/LangBot" target="_blank"><img src="https://abroad.hellogithub.com/v1/widgets/recommend.svg?rid=5ce8ae2aa4f74316bf393b57b952433c&claim_uid=gtmc6YWjMZkT21R" alt="Featured｜HelloGitHub" style="width: 250px; height: 54px;" width="250" height="54" /></a>
+
+<h3>生产级 AI 即时通信机器人开发平台。</h3>
+<h4>快速构建、调试和部署 AI 机器人到微信、QQ、飞书、Slack、Discord、Telegram 等平台。</h4>
+
+[English](README.md) / 简体中文 / [繁體中文](README_TW.md) / [日本語](README_JP.md) / [Español](README_ES.md) / [Français](README_FR.md) / [한국어](README_KO.md) / [Русский](README_RU.md) / [Tiếng Việt](README_VI.md)
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&labelColor=%20%235462eb&logoColor=%20%23f5f5f5&color=%20%235462eb)](https://discord.gg/wdNEHETs87)
+[![QQ Group](https://img.shields.io/badge/%E7%A4%BE%E5%8C%BAQQ%E7%BE%A4-1030838208-blue)](https://qm.qq.com/q/DxZZcNxM1W)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/langbot-app/LangBot)
+[![GitHub release (latest by date)](https://img.shields.io/github/v/release/langbot-app/LangBot)](https://github.com/langbot-app/LangBot/releases/latest)
+<img src="https://img.shields.io/badge/python-3.10 ~ 3.13 -blue.svg" alt="python">
+[![GitHub stars](https://img.shields.io/github/stars/langbot-app/LangBot?style=social)](https://github.com/langbot-app/LangBot/stargazers)
+[![star](https://gitcode.com/RockChinQ/LangBot/star/badge.svg)](https://gitcode.com/RockChinQ/LangBot)
+
+<a href="https://langbot.app">官网</a> ｜
+<a href="https://link.langbot.app/zh/docs/features">特性</a> ｜
+<a href="https://link.langbot.app/zh/docs/guide">文档</a> ｜
+<a href="https://link.langbot.app/zh/docs/api">API</a> ｜
+<a href="https://space.langbot.app/cloud">Cloud</a> ｜
+<a href="https://space.langbot.app">插件市场</a> ｜
+<a href="https://langbot.featurebase.app/roadmap">路线图</a>
+
+</div>
+
+</p>
+
+---
+
+LangBot 是一个**开源的生产级平台**，用于构建 AI 驱动的即时通信机器人。它将大语言模型（LLM）连接到各种聊天平台，帮助你创建能够对话、执行任务、并集成到现有工作流程中的智能 Agent。
+
+### 核心能力
+
+- **AI 对话与 Agent** — 多轮对话、工具调用、多模态、流式输出。自带 RAG（知识库），深度集成 [Dify](https://dify.ai)、[Coze](https://coze.com)、[n8n](https://n8n.io)、[Langflow](https://langflow.org) 等 LLMOps 平台。
+- **全平台支持** — 一套代码，覆盖 QQ、微信、企业微信、飞书、钉钉、Discord、Telegram、Slack、LINE、KOOK 等平台。
+- **生产就绪** — 访问控制、限速、敏感词过滤、全面监控与异常处理，已被多家企业采用。
+- **插件生态** — 数百个插件，跨进程的事件驱动架构，组件扩展，适配 [MCP 协议](https://modelcontextprotocol.io/)。
+- **Web 管理面板** — 通过浏览器直观地配置、管理和监控机器人，无需手动编辑配置文件。
+- **多流水线架构** — 不同机器人用于不同场景，具备全面的监控和异常处理能力。
+
+[→ 了解更多功能特性](https://link.langbot.app/zh/docs/features)
+
+---
+
+## 快速开始
+
+### ☁️ LangBot Cloud（推荐）
+
+**[LangBot Cloud](https://space.langbot.app/cloud)** — 免部署，开箱即用。
+
+### 一键启动
+
+```bash
+uvx langbot
+```
+
+> 需要安装 [uv](https://docs.astral.sh/uv/getting-started/installation/)。访问 http://localhost:5300 即可使用。
+
+### Docker Compose
+
+```bash
+git clone https://github.com/langbot-app/LangBot
+cd LangBot/docker
+docker compose up -d
+```
+
+### 一键云部署
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/zh-CN/templates/ZKTBDH)
+[![Deploy on Railway](https://railway.com/button.svg)](https://railway.app/template/yRrAyL?referralCode=vogKPF)
+
+**更多方式：** [Docker](https://link.langbot.app/zh/docs/docker) · [手动部署](https://link.langbot.app/zh/docs/manual-deploy) · [宝塔面板](https://link.langbot.app/zh/docs/bt-panel) · [Kubernetes](./docker/README_K8S.md)
+
+---
+
+## 支持的平台
+
+| 平台 | 状态 | 备注 |
+|------|------|------|
+| QQ | ✅ | 个人号、官方机器人（频道、私聊、群聊） |
+| 微信 | ✅ | 个人微信、微信公众号 |
+| 企业微信 | ✅ | 应用消息、对外客服、智能机器人 |
+| 飞书 | ✅ | 官方 |
+| 钉钉 | ✅ | 官方 |
+| Satori | ✅ |  |
+| Discord | ✅ | 官方 |
+| Telegram | ✅ | 官方 |
+| Slack | ✅ | 官方 |
+| LINE | ✅ | 官方 |
+| KOOK | ✅ | 官方 |
+| Email | ✅ | 只 Matrix、Satori |
+| Matrix | ✅ | 支持多种桥接平台，如 Signal、WhatsApp、Messenger、iMessage、Mattermost、Google Chat、IRC、XMPP、Zulip 等 |
+
+---
+
+## 支持的大模型与集成
+
+| 提供商 | 类型 | 状态 |
+|--------|------|------|
+| [OpenAI](https://platform.openai.com/) | LLM | ✅ |
+| [Anthropic](https://www.anthropic.com/) | LLM | ✅ |
+| [DeepSeek](https://www.deepseek.com/) | LLM | ✅ |
+| [Google Gemini](https://aistudio.google.com/prompts/new_chat) | LLM | ✅ |
+| [xAI](https://x.ai/) | LLM | ✅ |
+| [Moonshot](https://www.moonshot.cn/) | LLM | ✅ |
+| [智谱AI](https://open.bigmodel.cn/) | LLM | ✅ |
+| [Ollama](https://ollama.com/) | 本地 LLM | ✅ |
+| [LM Studio](https://lmstudio.ai/) | 本地 LLM | ✅ |
+| [Dify](https://dify.ai) | LLMOps | ✅ |
+| [MCP](https://modelcontextprotocol.io/) | 协议 | ✅ |
+| [SiliconFlow](https://siliconflow.cn/) | 聚合平台 | ✅ |
+| [阿里云百炼](https://bailian.console.aliyun.com/) | 聚合平台 | ✅ |
+| [火山方舟](https://console.volcengine.com/ark/region:ark+cn-beijing/model?vendor=Bytedance&view=LIST_VIEW) | 聚合平台 | ✅ |
+| [ModelScope](https://modelscope.cn/docs/model-service/API-Inference/intro) | 聚合平台 | ✅ |
+| [GiteeAI](https://ai.gitee.com/) | 聚合平台 | ✅ |
+| [胜算云](https://www.shengsuanyun.com/?from=CH_KYIPP758) | GPU 平台 | ✅ |
+| [优云智算](https://www.compshare.cn/?ytag=GPU_YY-gh_langbot) | GPU 平台 | ✅ |
+| [PPIO](https://ppinfra.com/user/register?invited_by=QJKFYD&utm_source=github_langbot) | GPU 平台 | ✅ |
+| [接口 AI](https://jiekou.ai/) | 聚合平台 | ✅ |
+| [302.AI](https://share.302.ai/SuTG99) | 聚合平台 | ✅ |
+| [小马算力](https://www.tokenpony.cn/453z1) | 聚合平台 | ✅ |
+| [百宝箱Tbox](https://www.tbox.cn/open) | 智能体平台 | ✅ |
+| [七牛云Qiniu](https://www.qiniu.com/ai/agent) | 聚合平台 | ✅ |
+
+[→ 查看完整集成列表](https://link.langbot.app/zh/docs/features)
+
+### TTS（语音合成）
+
+| 平台/模型 | 备注 |
+|-----------|------|
+| [FishAudio](https://fish.audio/zh-CN/discovery/) | [插件](https://github.com/the-lazy-me/NewChatVoice) |
+| [海豚 AI](https://www.ttson.cn/?source=thelazy) | [插件](https://github.com/the-lazy-me/NewChatVoice) |
+| [AzureTTS](https://portal.azure.com/) | [插件](https://github.com/Ingnaryk/LangBot_AzureTTS) |
+
+### 文生图
+
+| 平台/模型 | 备注 |
+|-----------|------|
+| 阿里云百炼 | [插件](https://github.com/Thetail001/LangBot_BailianTextToImagePlugin) |
+
+---
+
+## 为什么选择 LangBot？
+
+| 使用场景 | LangBot 如何帮助 |
+|----------|------------------|
+| **客户服务** | 将 AI Agent 部署到微信/企微/钉钉/飞书，基于知识库自动回答用户问题 |
+| **内部工具** | 将 n8n/Dify 工作流接入企微/钉钉，实现业务流程自动化 |
+| **社群运营** | 在 QQ/Discord 群中使用 AI 驱动的内容审核与智能互动 |
+| **多平台触达** | 一个机器人，覆盖所有平台。通过统一面板集中管理 |
+
+---
+
+## 在线演示
+
+**立即体验：** https://demo.langbot.dev/
+- 邮箱：`demo@langbot.app`
+- 密码：`langbot123456`
+
+*注意：公开演示环境，请不要在其中填入任何敏感信息。*
+
+---
+
+## 社区
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&label=Discord)](https://discord.gg/wdNEHETs87)
+[![QQ Group](https://img.shields.io/badge/%E7%A4%BE%E5%8C%BAQQ%E7%BE%A4-1030838208-blue)](https://qm.qq.com/q/DxZZcNxM1W)
+
+- [Discord 社区](https://discord.gg/wdNEHETs87)
+- [QQ 社区群](https://qm.qq.com/q/DxZZcNxM1W)
+
+---
+
+## Star 趋势
+
+[![Star History Chart](https://api.star-history.com/svg?repos=langbot-app/LangBot&type=Date)](https://star-history.com/#langbot-app/LangBot&Date)
+
+---
+
+## 贡献者
+
+感谢所有[贡献者](https://github.com/langbot-app/LangBot/graphs/contributors)对 LangBot 的帮助：
+
+<a href="https://github.com/langbot-app/LangBot/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=langbot-app/LangBot" />
+</a>
+
+<!--
+## For Code Agents
+
+If you're a code agent based on LLM, you should read [AGENTS.md](AGENTS.md) to understand the project structure and development process before you start any development.
+-->

README_ES.md

@@ -0,0 +1,174 @@
+<p align="center">
+<a href="https://langbot.app">
+<img width="130" src="res/logo-blue.png" alt="LangBot"/>
+</a>
+
+<div align="center">
+
+<a href="https://www.producthunt.com/products/langbot?utm_source=badge-follow&utm_medium=badge&utm_source=badge-langbot" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/follow.svg?product_id=1077185&theme=light" alt="LangBot - Production&#0045;grade&#0032;IM&#0032;bot&#0032;made&#0032;easy&#0046; | Product Hunt" style="width: 250px; height: 54px;" width="250" height="54" /></a>
+
+<h3>Plataforma de grado de producción para construir bots de mensajería instantánea con agentes de IA.</h3>
+<h4>Construya, depure y despliegue bots de IA rápidamente en Slack, Discord, Telegram, WeChat y más.</h4>
+
+[English](README.md) / [简体中文](README_CN.md) / [繁體中文](README_TW.md) / [日本語](README_JP.md) / Español / [Français](README_FR.md) / [한국어](README_KO.md) / [Русский](README_RU.md) / [Tiếng Việt](README_VI.md)
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&labelColor=%20%235462eb&logoColor=%20%23f5f5f5&color=%20%235462eb)](https://discord.gg/wdNEHETs87)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/langbot-app/LangBot)
+[![GitHub release (latest by date)](https://img.shields.io/github/v/release/langbot-app/LangBot)](https://github.com/langbot-app/LangBot/releases/latest)
+<img src="https://img.shields.io/badge/python-3.10 ~ 3.13 -blue.svg" alt="python">
+[![GitHub stars](https://img.shields.io/github/stars/langbot-app/LangBot?style=social)](https://github.com/langbot-app/LangBot/stargazers)
+
+<a href="https://langbot.app">Inicio</a> ｜
+<a href="https://link.langbot.app/en/docs/features">Características</a> ｜
+<a href="https://link.langbot.app/en/docs/guide">Documentación</a> ｜
+<a href="https://link.langbot.app/en/docs/api">API</a> ｜
+<a href="https://space.langbot.app">Mercado de Plugins</a> ｜
+<a href="https://langbot.featurebase.app/roadmap">Hoja de Ruta</a>
+
+</div>
+
+</p>
+
+---
+
+## ¿Qué es LangBot?
+
+LangBot es una **plataforma de código abierto y grado de producción** para construir bots de mensajería instantánea impulsados por IA. Conecta modelos de lenguaje de gran escala (LLMs) con cualquier plataforma de chat, permitiéndole crear agentes inteligentes que pueden conversar, ejecutar tareas e integrarse con sus flujos de trabajo existentes.
+
+### Capacidades Clave
+
+- **Conversaciones e Agentes IA** — Diálogos de múltiples turnos, llamadas a herramientas, soporte multimodal, salida en streaming. RAG (base de conocimientos) incorporado con integración profunda con [Dify](https://dify.ai), [Coze](https://coze.com), [n8n](https://n8n.io), [Langflow](https://langflow.org).
+- **Soporte Universal de Plataformas de MI** — Un solo código base para Discord, Telegram, Slack, LINE, QQ, WeChat, WeCom, Lark, DingTalk, KOOK.
+- **Listo para Producción** — Control de acceso, limitación de velocidad, filtrado de palabras sensibles, monitoreo completo y manejo de excepciones. De confianza para empresas.
+- **Ecosistema de Plugins** — Cientos de plugins, arquitectura basada en eventos, extensiones de componentes y soporte del [protocolo MCP](https://modelcontextprotocol.io/).
+- **Panel de Gestión Web** — Configure, gestione y monitoree sus bots a través de una interfaz de navegador intuitiva. Sin necesidad de editar YAML.
+- **Arquitectura Multi-Pipeline** — Diferentes bots para diferentes escenarios, con monitoreo completo y manejo de excepciones.
+
+[→ Conocer más sobre todas las funcionalidades](https://link.langbot.app/en/docs/features)
+
+---
+
+## Inicio Rápido
+
+### ☁️ LangBot Cloud (Recomendado)
+
+**[LangBot Cloud](https://space.langbot.app/cloud)** — Sin despliegue, listo para usar.
+
+### Lanzamiento en una línea
+
+```bash
+uvx langbot
+```
+
+> Requiere [uv](https://docs.astral.sh/uv/getting-started/installation/). Visite http://localhost:5300 — listo.
+
+### Docker Compose
+
+```bash
+git clone https://github.com/langbot-app/LangBot
+cd LangBot/docker
+docker compose up -d
+```
+
+### Despliegue en la Nube con un Clic
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/en-US/templates/ZKTBDH)
+[![Deploy on Railway](https://railway.com/button.svg)](https://railway.app/template/yRrAyL?referralCode=vogKPF)
+
+**Más opciones:** [Docker](https://link.langbot.app/en/docs/docker) · [Manual](https://link.langbot.app/en/docs/manual-deploy) · [BTPanel](https://link.langbot.app/en/docs/bt-panel) · [Kubernetes](./docker/README_K8S.md)
+
+---
+
+## Plataformas Soportadas
+
+| Plataforma | Estado | Notas |
+|----------|--------|-------|
+| Discord | ✅ | Oficial |
+| Telegram | ✅ | Oficial |
+| Slack | ✅ | Oficial |
+| LINE | ✅ | Oficial |
+| QQ | ✅ | Personal y API Oficial (Canal, DM, Grupo) |
+| WeCom | ✅ | WeChat Empresarial, CS Externo, AI Bot |
+| WeChat | ✅ | Personal y Cuenta Oficial |
+| Lark | ✅ | Oficial |
+| DingTalk | ✅ | Oficial |
+| KOOK | ✅ | Oficial |
+| Satori | ✅ |  |
+| Email | ✅ | Matrix, Satori |
+| Matrix | ✅ | Admite varias plataformas puenteadas como Signal, WhatsApp, Messenger, iMessage, Mattermost, Google Chat, IRC, XMPP, Zulip y más |
+
+---
+
+## LLMs e Integraciones Soportadas
+
+| Proveedor | Tipo | Estado |
+|----------|------|--------|
+| [OpenAI](https://platform.openai.com/) | LLM | ✅ |
+| [Anthropic](https://www.anthropic.com/) | LLM | ✅ |
+| [DeepSeek](https://www.deepseek.com/) | LLM | ✅ |
+| [Google Gemini](https://aistudio.google.com/prompts/new_chat) | LLM | ✅ |
+| [xAI](https://x.ai/) | LLM | ✅ |
+| [Moonshot](https://www.moonshot.cn/) | LLM | ✅ |
+| [Zhipu AI](https://open.bigmodel.cn/) | LLM | ✅ |
+| [Ollama](https://ollama.com/) | LLM Local | ✅ |
+| [LM Studio](https://lmstudio.ai/) | LLM Local | ✅ |
+| [Dify](https://dify.ai) | LLMOps | ✅ |
+| [MCP](https://modelcontextprotocol.io/) | Protocolo | ✅ |
+| [SiliconFlow](https://siliconflow.cn/) | Pasarela | ✅ |
+| [Aliyun Bailian](https://bailian.console.aliyun.com/) | Pasarela | ✅ |
+| [Volc Engine Ark](https://console.volcengine.com/ark/region:ark+cn-beijing/model?vendor=Bytedance&view=LIST_VIEW) | Pasarela | ✅ |
+| [ModelScope](https://modelscope.cn/docs/model-service/API-Inference/intro) | Pasarela | ✅ |
+| [GiteeAI](https://ai.gitee.com/) | Pasarela | ✅ |
+| [CompShare](https://www.compshare.cn/?ytag=GPU_YY-gh_langbot) | Plataforma GPU | ✅ |
+| [PPIO](https://ppinfra.com/user/register?invited_by=QJKFYD&utm_source=github_langbot) | Plataforma GPU | ✅ |
+| [ShengSuanYun](https://www.shengsuanyun.com/?from=CH_KYIPP758) | Plataforma GPU | ✅ |
+| [接口 AI](https://jiekou.ai/) | Pasarela | ✅ |
+| [302.AI](https://share.302.ai/SuTG99) | Pasarela | ✅ |
+| [Qiniu](https://www.qiniu.com/ai/agent) | Pasarela | ✅ |
+
+[→ Ver todas las integraciones](https://link.langbot.app/en/docs/features)
+
+---
+
+## ¿Por qué LangBot?
+
+| Caso de Uso | Cómo Ayuda LangBot |
+|----------|-------------------|
+| **Atención al cliente** | Despliegue agentes de IA en Slack/Discord/Telegram que respondan preguntas usando su base de conocimientos |
+| **Herramientas internas** | Conecte flujos de trabajo de n8n/Dify a WeCom/DingTalk para procesos empresariales automatizados |
+| **Gestión de comunidades** | Modere grupos de QQ/Discord con filtrado de contenido e interacción impulsados por IA |
+| **Presencia multiplataforma** | Un solo bot, todas las plataformas. Gestione desde un único panel de control |
+
+---
+
+## Demo en Vivo
+
+**Pruébelo ahora:** https://demo.langbot.dev/
+- Correo electrónico: `demo@langbot.app`
+- Contraseña: `langbot123456`
+
+*Nota: Entorno de demostración público. No ingrese información confidencial.*
+
+---
+
+## Comunidad
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&label=Discord)](https://discord.gg/wdNEHETs87)
+
+- [Comunidad de Discord](https://discord.gg/wdNEHETs87)
+
+---
+
+## Historial de Stars
+
+[![Star History Chart](https://api.star-history.com/svg?repos=langbot-app/LangBot&type=Date)](https://star-history.com/#langbot-app/LangBot&Date)
+
+---
+
+## Colaboradores
+
+Gracias a todos los [colaboradores](https://github.com/langbot-app/LangBot/graphs/contributors) que han ayudado a mejorar LangBot:
+
+<a href="https://github.com/langbot-app/LangBot/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=langbot-app/LangBot" />
+</a>

README_FR.md

@@ -0,0 +1,174 @@
+<p align="center">
+<a href="https://langbot.app">
+<img width="130" src="res/logo-blue.png" alt="LangBot"/>
+</a>
+
+<div align="center">
+
+<a href="https://www.producthunt.com/products/langbot?utm_source=badge-follow&utm_medium=badge&utm_source=badge-langbot" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/follow.svg?product_id=1077185&theme=light" alt="LangBot - Production&#0045;grade&#0032;IM&#0032;bot&#0032;made&#0032;easy&#0046; | Product Hunt" style="width: 250px; height: 54px;" width="250" height="54" /></a>
+
+<h3>Plateforme de niveau production pour construire des bots de messagerie instantanée avec agents IA.</h3>
+<h4>Créez, déboguez et déployez rapidement des bots IA sur Slack, Discord, Telegram, WeChat et plus.</h4>
+
+[English](README.md) / [简体中文](README_CN.md) / [繁體中文](README_TW.md) / [日本語](README_JP.md) / [Español](README_ES.md) / Français / [한국어](README_KO.md) / [Русский](README_RU.md) / [Tiếng Việt](README_VI.md)
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&labelColor=%20%235462eb&logoColor=%20%23f5f5f5&color=%20%235462eb)](https://discord.gg/wdNEHETs87)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/langbot-app/LangBot)
+[![GitHub release (latest by date)](https://img.shields.io/github/v/release/langbot-app/LangBot)](https://github.com/langbot-app/LangBot/releases/latest)
+<img src="https://img.shields.io/badge/python-3.10 ~ 3.13 -blue.svg" alt="python">
+[![GitHub stars](https://img.shields.io/github/stars/langbot-app/LangBot?style=social)](https://github.com/langbot-app/LangBot/stargazers)
+
+<a href="https://langbot.app">Accueil</a> ｜
+<a href="https://link.langbot.app/en/docs/features">Fonctionnalités</a> ｜
+<a href="https://link.langbot.app/en/docs/guide">Documentation</a> ｜
+<a href="https://link.langbot.app/en/docs/api">API</a> ｜
+<a href="https://space.langbot.app">Marché des Plugins</a> ｜
+<a href="https://langbot.featurebase.app/roadmap">Feuille de Route</a>
+
+</div>
+
+</p>
+
+---
+
+## Qu'est-ce que LangBot ?
+
+LangBot est une **plateforme open-source de niveau production** pour créer des bots de messagerie instantanée alimentés par l'IA. Elle connecte les grands modèles de langage (LLMs) à n'importe quelle plateforme de chat, vous permettant de créer des agents intelligents capables de converser, d'exécuter des tâches et de s'intégrer à vos workflows existants.
+
+### Capacités Clés
+
+- **Conversations IA & Agents** — Dialogues multi-tours, appels d'outils, support multimodal, sortie en streaming. RAG (base de connaissances) intégré avec intégration profonde de [Dify](https://dify.ai), [Coze](https://coze.com), [n8n](https://n8n.io), [Langflow](https://langflow.org).
+- **Support Universel des Plateformes de MI** — Un seul code pour Discord, Telegram, Slack, LINE, QQ, WeChat, WeCom, Lark, DingTalk, KOOK.
+- **Prêt pour la Production** — Contrôle d'accès, limitation de débit, filtrage de mots sensibles, surveillance complète et gestion des exceptions. Approuvé par les entreprises.
+- **Écosystème de Plugins** — Des centaines de plugins, architecture événementielle, extensions de composants, et support du [protocole MCP](https://modelcontextprotocol.io/).
+- **Panneau de Gestion Web** — Configurez, gérez et surveillez vos bots via une interface navigateur intuitive. Aucune édition de YAML requise.
+- **Architecture Multi-Pipeline** — Différents bots pour différents scénarios, avec surveillance complète et gestion des exceptions.
+
+[→ En savoir plus sur toutes les fonctionnalités](https://link.langbot.app/en/docs/features)
+
+---
+
+## Démarrage Rapide
+
+### ☁️ LangBot Cloud (Recommandé)
+
+**[LangBot Cloud](https://space.langbot.app/cloud)** — Sans déploiement, prêt à utiliser.
+
+### Lancement en une ligne
+
+```bash
+uvx langbot
+```
+
+> Nécessite [uv](https://docs.astral.sh/uv/getting-started/installation/). Visitez http://localhost:5300 — c'est prêt.
+
+### Docker Compose
+
+```bash
+git clone https://github.com/langbot-app/LangBot
+cd LangBot/docker
+docker compose up -d
+```
+
+### Déploiement Cloud en un Clic
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/en-US/templates/ZKTBDH)
+[![Deploy on Railway](https://railway.com/button.svg)](https://railway.app/template/yRrAyL?referralCode=vogKPF)
+
+**Plus d'options :** [Docker](https://link.langbot.app/en/docs/docker) · [Manuel](https://link.langbot.app/en/docs/manual-deploy) · [BTPanel](https://link.langbot.app/en/docs/bt-panel) · [Kubernetes](./docker/README_K8S.md)
+
+---
+
+## Plateformes Supportées
+
+| Plateforme | Statut | Notes |
+|----------|--------|-------|
+| Discord | ✅ | Officiel |
+| Telegram | ✅ | Officiel |
+| Slack | ✅ | Officiel |
+| LINE | ✅ | Officiel |
+| QQ | ✅ | Personnel & API Officielle (Canal, DM, Groupe) |
+| WeCom | ✅ | WeChat Entreprise, CS Externe, AI Bot |
+| WeChat | ✅ | Personnel & Compte Officiel |
+| Lark | ✅ | Officiel |
+| DingTalk | ✅ | Officiel |
+| KOOK | ✅ | Officiel |
+| Satori | ✅ |  |
+| Email | ✅ | Matrix, Satori |
+| Matrix | ✅ | Prend en charge plusieurs plateformes via ponts, comme Signal, WhatsApp, Messenger, iMessage, Mattermost, Google Chat, IRC, XMPP, Zulip, etc. |
+
+---
+
+## LLMs et Intégrations Supportés
+
+| Fournisseur | Type | Statut |
+|----------|------|--------|
+| [OpenAI](https://platform.openai.com/) | LLM | ✅ |
+| [Anthropic](https://www.anthropic.com/) | LLM | ✅ |
+| [DeepSeek](https://www.deepseek.com/) | LLM | ✅ |
+| [Google Gemini](https://aistudio.google.com/prompts/new_chat) | LLM | ✅ |
+| [xAI](https://x.ai/) | LLM | ✅ |
+| [Moonshot](https://www.moonshot.cn/) | LLM | ✅ |
+| [Zhipu AI](https://open.bigmodel.cn/) | LLM | ✅ |
+| [Ollama](https://ollama.com/) | LLM Local | ✅ |
+| [LM Studio](https://lmstudio.ai/) | LLM Local | ✅ |
+| [Dify](https://dify.ai) | LLMOps | ✅ |
+| [MCP](https://modelcontextprotocol.io/) | Protocole | ✅ |
+| [SiliconFlow](https://siliconflow.cn/) | Passerelle | ✅ |
+| [Aliyun Bailian](https://bailian.console.aliyun.com/) | Passerelle | ✅ |
+| [Volc Engine Ark](https://console.volcengine.com/ark/region:ark+cn-beijing/model?vendor=Bytedance&view=LIST_VIEW) | Passerelle | ✅ |
+| [ModelScope](https://modelscope.cn/docs/model-service/API-Inference/intro) | Passerelle | ✅ |
+| [GiteeAI](https://ai.gitee.com/) | Passerelle | ✅ |
+| [接口 AI](https://jiekou.ai/) | Passerelle | ✅ |
+| [302.AI](https://share.302.ai/SuTG99) | Passerelle | ✅ |
+| [CompShare](https://www.compshare.cn/?ytag=GPU_YY-gh_langbot) | Plateforme GPU | ✅ |
+| [PPIO](https://ppinfra.com/user/register?invited_by=QJKFYD&utm_source=github_langbot) | Plateforme GPU | ✅ |
+| [ShengSuanYun](https://www.shengsuanyun.com/?from=CH_KYIPP758) | Plateforme GPU | ✅ |
+| [Qiniu](https://www.qiniu.com/ai/agent) | Passerelle | ✅ |
+
+[→ Voir toutes les intégrations](https://link.langbot.app/en/docs/features)
+
+---
+
+## Pourquoi LangBot ?
+
+| Cas d'Usage | Comment LangBot Aide |
+|----------|-------------------|
+| **Support Client** | Déployez des agents IA sur Slack/Discord/Telegram qui répondent aux questions en utilisant votre base de connaissances |
+| **Outils Internes** | Connectez les workflows n8n/Dify à WeCom/DingTalk pour automatiser vos processus métier |
+| **Gestion de Communauté** | Modérez les groupes QQ/Discord avec un filtrage de contenu et des interactions alimentés par l'IA |
+| **Présence Multi-plateforme** | Un seul bot, toutes les plateformes. Gérez tout depuis un tableau de bord unique |
+
+---
+
+## Démo en Ligne
+
+**Essayez maintenant :** https://demo.langbot.dev/
+- Email : `demo@langbot.app`
+- Mot de passe : `langbot123456`
+
+*Note : Environnement de démonstration public. Ne saisissez pas d'informations sensibles.*
+
+---
+
+## Communauté
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&label=Discord)](https://discord.gg/wdNEHETs87)
+
+- [Communauté Discord](https://discord.gg/wdNEHETs87)
+
+---
+
+## Historique des Stars
+
+[![Star History Chart](https://api.star-history.com/svg?repos=langbot-app/LangBot&type=Date)](https://star-history.com/#langbot-app/LangBot&Date)
+
+---
+
+## Contributeurs
+
+Merci à tous les [contributeurs](https://github.com/langbot-app/LangBot/graphs/contributors) qui ont aidé à améliorer LangBot :
+
+<a href="https://github.com/langbot-app/LangBot/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=langbot-app/LangBot" />
+</a>

README_JP.md

@@ -0,0 +1,174 @@
+<p align="center">
+<a href="https://langbot.app">
+<img width="130" src="res/logo-blue.png" alt="LangBot"/>
+</a>
+
+<div align="center">
+
+<a href="https://www.producthunt.com/products/langbot?utm_source=badge-follow&utm_medium=badge&utm_source=badge-langbot" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/follow.svg?product_id=1077185&theme=light" alt="LangBot - Production&#0045;grade&#0032;IM&#0032;bot&#0032;made&#0032;easy&#0046; | Product Hunt" style="width: 250px; height: 54px;" width="250" height="54" /></a>
+
+<h3>AIエージェント搭載IMボットを構築するための本番グレードプラットフォーム。</h3>
+<h4>Slack、Discord、Telegram、WeChat などに AI ボットを素早く構築、デバッグ、デプロイ。</h4>
+
+[English](README.md) / [简体中文](README_CN.md) / [繁體中文](README_TW.md) / 日本語 / [Español](README_ES.md) / [Français](README_FR.md) / [한국어](README_KO.md) / [Русский](README_RU.md) / [Tiếng Việt](README_VI.md)
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&labelColor=%20%235462eb&logoColor=%20%23f5f5f5&color=%20%235462eb)](https://discord.gg/wdNEHETs87)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/langbot-app/LangBot)
+[![GitHub release (latest by date)](https://img.shields.io/github/v/release/langbot-app/LangBot)](https://github.com/langbot-app/LangBot/releases/latest)
+<img src="https://img.shields.io/badge/python-3.10 ~ 3.13 -blue.svg" alt="python">
+[![GitHub stars](https://img.shields.io/github/stars/langbot-app/LangBot?style=social)](https://github.com/langbot-app/LangBot/stargazers)
+
+<a href="https://langbot.app">ホーム</a> ｜
+<a href="https://link.langbot.app/ja/docs/features">機能</a> ｜
+<a href="https://link.langbot.app/ja/docs/guide">ドキュメント</a> ｜
+<a href="https://link.langbot.app/ja/docs/api">API</a> ｜
+<a href="https://space.langbot.app">プラグインマーケット</a> ｜
+<a href="https://langbot.featurebase.app/roadmap">ロードマップ</a>
+
+</div>
+
+</p>
+
+---
+
+## LangBot とは？
+
+LangBot は、AI搭載のインスタントメッセージングボットを構築するための**オープンソースの本番グレードプラットフォーム**です。大規模言語モデル（LLM）をあらゆるチャットプラットフォームに接続し、会話、タスク実行、既存のワークフローとの統合が可能なインテリジェントエージェントを作成できます。
+
+### 主な機能
+
+- **AI対話とエージェント** — マルチターン対話、ツール呼び出し、マルチモーダル対応、ストリーミング出力。RAG（ナレッジベース）を内蔵し、[Dify](https://dify.ai)、[Coze](https://coze.com)、[n8n](https://n8n.io)、[Langflow](https://langflow.org) と深く統合。
+- **ユニバーサルIMプラットフォーム対応** — 単一のコードベースで Discord、Telegram、Slack、LINE、QQ、WeChat、WeCom、Lark、DingTalk、KOOK に対応。
+- **本番環境対応** — アクセス制御、レート制限、センシティブワードフィルタリング、包括的な監視、例外処理を搭載。エンタープライズの信頼に応える品質。
+- **プラグインエコシステム** — 数百のプラグイン、イベント駆動アーキテクチャ、コンポーネント拡張、[MCPプロトコル](https://modelcontextprotocol.io/)対応。
+- **Web管理パネル** — 直感的なブラウザインターフェースからボットの設定、管理、監視が可能。YAML編集は不要。
+- **マルチパイプラインアーキテクチャ** — 異なるシナリオに異なるボットを配置し、包括的な監視と例外処理を実現。
+
+[→ すべての機能について詳しく見る](https://link.langbot.app/ja/docs/features)
+
+---
+
+## クイックスタート
+
+### ☁️ LangBot Cloud（推奨）
+
+**[LangBot Cloud](https://space.langbot.app/cloud)** — デプロイ不要、すぐに使えます。
+
+### ワンライン起動
+
+```bash
+uvx langbot
+```
+
+> [uv](https://docs.astral.sh/uv/getting-started/installation/) が必要です。http://localhost:5300 にアクセスして完了。
+
+### Docker Compose
+
+```bash
+git clone https://github.com/langbot-app/LangBot
+cd LangBot/docker
+docker compose up -d
+```
+
+### ワンクリッククラウドデプロイ
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/en-US/templates/ZKTBDH)
+[![Deploy on Railway](https://railway.com/button.svg)](https://railway.app/template/yRrAyL?referralCode=vogKPF)
+
+**その他:** [Docker](https://link.langbot.app/en/docs/docker) · [手動デプロイ](https://link.langbot.app/en/docs/manual-deploy) · [BTPanel](https://link.langbot.app/en/docs/bt-panel) · [Kubernetes](./docker/README_K8S.md)
+
+---
+
+## 対応プラットフォーム
+
+| プラットフォーム | ステータス | 備考 |
+|----------|--------|-------|
+| Discord | ✅ | 公式 |
+| Telegram | ✅ | 公式 |
+| Slack | ✅ | 公式 |
+| LINE | ✅ | 公式 |
+| QQ | ✅ | 個人・公式API（チャンネル・DM・グループ） |
+| WeCom | ✅ | 企業WeChat、外部CS、AIボット |
+| WeChat | ✅ | 個人・公式アカウント |
+| Lark | ✅ | 公式 |
+| DingTalk | ✅ | 公式 |
+| KOOK | ✅ | 公式 |
+| Satori | ✅ |  |
+| Email | ✅ | Matrix、Satori |
+| Matrix | ✅ | Signal、WhatsApp、Messenger、iMessage、Mattermost、Google Chat、IRC、XMPP、Zulip など複数のブリッジ先プラットフォームに対応 |
+
+---
+
+## 対応LLMと統合
+
+| プロバイダー | タイプ | ステータス |
+|----------|------|--------|
+| [OpenAI](https://platform.openai.com/) | LLM | ✅ |
+| [Anthropic](https://www.anthropic.com/) | LLM | ✅ |
+| [DeepSeek](https://www.deepseek.com/) | LLM | ✅ |
+| [Google Gemini](https://aistudio.google.com/prompts/new_chat) | LLM | ✅ |
+| [xAI](https://x.ai/) | LLM | ✅ |
+| [Moonshot](https://www.moonshot.cn/) | LLM | ✅ |
+| [Zhipu AI](https://open.bigmodel.cn/) | LLM | ✅ |
+| [Ollama](https://ollama.com/) | ローカルLLM | ✅ |
+| [LM Studio](https://lmstudio.ai/) | ローカルLLM | ✅ |
+| [Dify](https://dify.ai) | LLMOps | ✅ |
+| [MCP](https://modelcontextprotocol.io/) | プロトコル | ✅ |
+| [SiliconFlow](https://siliconflow.cn/) | ゲートウェイ | ✅ |
+| [Aliyun Bailian](https://bailian.console.aliyun.com/) | ゲートウェイ | ✅ |
+| [Volc Engine Ark](https://console.volcengine.com/ark/region:ark+cn-beijing/model?vendor=Bytedance&view=LIST_VIEW) | ゲートウェイ | ✅ |
+| [ModelScope](https://modelscope.cn/docs/model-service/API-Inference/intro) | ゲートウェイ | ✅ |
+| [GiteeAI](https://ai.gitee.com/) | ゲートウェイ | ✅ |
+| [CompShare](https://www.compshare.cn/?ytag=GPU_YY-gh_langbot) | GPUプラットフォーム | ✅ |
+| [PPIO](https://ppinfra.com/user/register?invited_by=QJKFYD&utm_source=github_langbot) | GPUプラットフォーム | ✅ |
+| [ShengSuanYun](https://www.shengsuanyun.com/?from=CH_KYIPP758) | GPUプラットフォーム | ✅ |
+| [接口 AI](https://jiekou.ai/) | ゲートウェイ | ✅ |
+| [302.AI](https://share.302.ai/SuTG99) | ゲートウェイ | ✅ |
+| [Qiniu](https://www.qiniu.com/ai/agent) | ゲートウェイ | ✅ |
+
+[→ すべての統合を表示](https://link.langbot.app/en/docs/features)
+
+---
+
+## なぜ LangBot？
+
+| ユースケース | LangBot の活用方法 |
+|----------|-------------------|
+| **カスタマーサポート** | ナレッジベースを活用して質問に回答するAIエージェントをSlack/Discord/Telegramにデプロイ |
+| **社内ツール** | n8n/Difyのワークフローを WeCom/DingTalk に接続し、業務プロセスを自動化 |
+| **コミュニティ管理** | AI搭載のコンテンツフィルタリングとインタラクションでQQ/Discordグループをモデレーション |
+| **マルチプラットフォーム展開** | 1つのボットで全プラットフォームに対応。単一のダッシュボードから管理 |
+
+---
+
+## ライブデモ
+
+**今すぐ試す:** https://demo.langbot.dev/
+- メール: `demo@langbot.app`
+- パスワード: `langbot123456`
+
+*注意: 公開デモ環境です。機密情報を入力しないでください。*
+
+---
+
+## コミュニティ
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&label=Discord)](https://discord.gg/wdNEHETs87)
+
+- [Discord コミュニティ](https://discord.gg/wdNEHETs87)
+
+---
+
+## Star 推移
+
+[![Star History Chart](https://api.star-history.com/svg?repos=langbot-app/LangBot&type=Date)](https://star-history.com/#langbot-app/LangBot&Date)
+
+---
+
+## コントリビューター
+
+LangBot をより良くするために貢献してくださったすべての[コントリビューター](https://github.com/langbot-app/LangBot/graphs/contributors)に感謝します:
+
+<a href="https://github.com/langbot-app/LangBot/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=langbot-app/LangBot" />
+</a>

README_KO.md

@@ -0,0 +1,174 @@
+<p align="center">
+<a href="https://langbot.app">
+<img width="130" src="res/logo-blue.png" alt="LangBot"/>
+</a>
+
+<div align="center">
+
+<a href="https://www.producthunt.com/products/langbot?utm_source=badge-follow&utm_medium=badge&utm_source=badge-langbot" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/follow.svg?product_id=1077185&theme=light" alt="LangBot - Production&#0045;grade&#0032;IM&#0032;bot&#0032;made&#0032;easy&#0046; | Product Hunt" style="width: 250px; height: 54px;" width="250" height="54" /></a>
+
+<h3>AI 에이전트 IM 봇 구축을 위한 프로덕션 등급 플랫폼.</h3>
+<h4>Slack, Discord, Telegram, WeChat 등에 AI 봇을 빠르게 구축, 디버그 및 배포.</h4>
+
+[English](README.md) / [简体中文](README_CN.md) / [繁體中文](README_TW.md) / [日本語](README_JP.md) / [Español](README_ES.md) / [Français](README_FR.md) / 한국어 / [Русский](README_RU.md) / [Tiếng Việt](README_VI.md)
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&labelColor=%20%235462eb&logoColor=%20%23f5f5f5&color=%20%235462eb)](https://discord.gg/wdNEHETs87)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/langbot-app/LangBot)
+[![GitHub release (latest by date)](https://img.shields.io/github/v/release/langbot-app/LangBot)](https://github.com/langbot-app/LangBot/releases/latest)
+<img src="https://img.shields.io/badge/python-3.10 ~ 3.13 -blue.svg" alt="python">
+[![GitHub stars](https://img.shields.io/github/stars/langbot-app/LangBot?style=social)](https://github.com/langbot-app/LangBot/stargazers)
+
+<a href="https://langbot.app">홈</a> ｜
+<a href="https://link.langbot.app/en/docs/features">기능</a> ｜
+<a href="https://link.langbot.app/en/docs/guide">문서</a> ｜
+<a href="https://link.langbot.app/en/docs/api">API</a> ｜
+<a href="https://space.langbot.app">플러그인 마켓</a> ｜
+<a href="https://langbot.featurebase.app/roadmap">로드맵</a>
+
+</div>
+
+</p>
+
+---
+
+## LangBot이란?
+
+LangBot은 AI 기반 인스턴트 메시징 봇을 구축하기 위한 **오픈소스 프로덕션 등급 플랫폼**입니다. 대규모 언어 모델(LLM)을 모든 채팅 플랫폼에 연결하여 대화, 작업 실행, 기존 워크플로우와의 통합이 가능한 지능형 에이전트를 만들 수 있습니다.
+
+### 핵심 기능
+
+- **AI 대화 및 에이전트** — 멀티턴 대화, 도구 호출, 멀티모달 지원, 스트리밍 출력. 내장 RAG(지식 베이스)와 [Dify](https://dify.ai), [Coze](https://coze.com), [n8n](https://n8n.io), [Langflow](https://langflow.org) 심층 통합.
+- **유니버설 IM 플랫폼 지원** — 단일 코드베이스로 Discord, Telegram, Slack, LINE, QQ, WeChat, WeCom, Lark, DingTalk, KOOK 지원.
+- **프로덕션 레디** — 접근 제어, 속도 제한, 민감어 필터링, 종합 모니터링 및 예외 처리. 기업 환경에서 검증됨.
+- **플러그인 생태계** — 수백 개의 플러그인, 이벤트 기반 아키텍처, 컴포넌트 확장, [MCP 프로토콜](https://modelcontextprotocol.io/) 지원.
+- **웹 관리 패널** — 직관적인 브라우저 인터페이스로 봇을 구성, 관리 및 모니터링. YAML 편집 불필요.
+- **멀티 파이프라인 아키텍처** — 다양한 시나리오에 맞는 다양한 봇 구성, 종합 모니터링 및 예외 처리.
+
+[→ 모든 기능 자세히 보기](https://link.langbot.app/en/docs/features)
+
+---
+
+## 빠른 시작
+
+### ☁️ LangBot Cloud (추천)
+
+**[LangBot Cloud](https://space.langbot.app/cloud)** — 배포 없이 바로 사용.
+
+### 원라인 실행
+
+```bash
+uvx langbot
+```
+
+> [uv](https://docs.astral.sh/uv/getting-started/installation/) 설치 필요. http://localhost:5300 방문 — 완료.
+
+### Docker Compose
+
+```bash
+git clone https://github.com/langbot-app/LangBot
+cd LangBot/docker
+docker compose up -d
+```
+
+### 원클릭 클라우드 배포
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/en-US/templates/ZKTBDH)
+[![Deploy on Railway](https://railway.com/button.svg)](https://railway.app/template/yRrAyL?referralCode=vogKPF)
+
+**더 많은 옵션:** [Docker](https://link.langbot.app/en/docs/docker) · [수동 배포](https://link.langbot.app/en/docs/manual-deploy) · [BTPanel](https://link.langbot.app/en/docs/bt-panel) · [Kubernetes](./docker/README_K8S.md)
+
+---
+
+## 지원 플랫폼
+
+| 플랫폼 | 상태 | 비고 |
+|--------|------|------|
+| Discord | ✅ | 공식 |
+| Telegram | ✅ | 공식 |
+| Slack | ✅ | 공식 |
+| LINE | ✅ | 공식 |
+| QQ | ✅ | 개인 및 공식 API (채널, DM, 그룹) |
+| WeCom | ✅ | 기업 WeChat, 외부 CS, AI Bot |
+| WeChat | ✅ | 개인 및 공식 계정 |
+| Lark | ✅ | 공식 |
+| DingTalk | ✅ | 공식 |
+| KOOK | ✅ | 공식 |
+| Satori | ✅ |  |
+| Email | ✅ | Matrix, Satori |
+| Matrix | ✅ | Signal, WhatsApp, Messenger, iMessage, Mattermost, Google Chat, IRC, XMPP, Zulip 등 여러 브리지 플랫폼 지원 |
+
+---
+
+## 지원 LLM 및 통합
+
+| 제공자 | 유형 | 상태 |
+|--------|------|------|
+| [OpenAI](https://platform.openai.com/) | LLM | ✅ |
+| [Anthropic](https://www.anthropic.com/) | LLM | ✅ |
+| [DeepSeek](https://www.deepseek.com/) | LLM | ✅ |
+| [Google Gemini](https://aistudio.google.com/prompts/new_chat) | LLM | ✅ |
+| [xAI](https://x.ai/) | LLM | ✅ |
+| [Moonshot](https://www.moonshot.cn/) | LLM | ✅ |
+| [Zhipu AI](https://open.bigmodel.cn/) | LLM | ✅ |
+| [Ollama](https://ollama.com/) | 로컬 LLM | ✅ |
+| [LM Studio](https://lmstudio.ai/) | 로컬 LLM | ✅ |
+| [Dify](https://dify.ai) | LLMOps | ✅ |
+| [MCP](https://modelcontextprotocol.io/) | 프로토콜 | ✅ |
+| [SiliconFlow](https://siliconflow.cn/) | 게이트웨이 | ✅ |
+| [Aliyun Bailian](https://bailian.console.aliyun.com/) | 게이트웨이 | ✅ |
+| [Volc Engine Ark](https://console.volcengine.com/ark/region:ark+cn-beijing/model?vendor=Bytedance&view=LIST_VIEW) | 게이트웨이 | ✅ |
+| [ModelScope](https://modelscope.cn/docs/model-service/API-Inference/intro) | 게이트웨이 | ✅ |
+| [GiteeAI](https://ai.gitee.com/) | 게이트웨이 | ✅ |
+| [CompShare](https://www.compshare.cn/?ytag=GPU_YY-gh_langbot) | GPU 플랫폼 | ✅ |
+| [PPIO](https://ppinfra.com/user/register?invited_by=QJKFYD&utm_source=github_langbot) | GPU 플랫폼 | ✅ |
+| [ShengSuanYun](https://www.shengsuanyun.com/?from=CH_KYIPP758) | GPU 플랫폼 | ✅ |
+| [接口 AI](https://jiekou.ai/) | 게이트웨이 | ✅ |
+| [302.AI](https://share.302.ai/SuTG99) | 게이트웨이 | ✅ |
+| [Qiniu](https://www.qiniu.com/ai/agent) | 게이트웨이 | ✅ |
+
+[→ 모든 통합 보기](https://link.langbot.app/en/docs/features)
+
+---
+
+## 왜 LangBot인가?
+
+| 사용 사례 | LangBot 활용 방법 |
+|-----------|-------------------|
+| **고객 지원** | 지식 베이스를 활용하여 질문에 답변하는 AI 에이전트를 Slack/Discord/Telegram에 배포 |
+| **내부 도구** | n8n/Dify 워크플로우를 WeCom/DingTalk에 연결하여 비즈니스 프로세스 자동화 |
+| **커뮤니티 관리** | AI 기반 콘텐츠 필터링 및 상호작용으로 QQ/Discord 그룹 관리 |
+| **멀티 플랫폼** | 하나의 봇으로 모든 플랫폼 지원. 단일 대시보드에서 관리 |
+
+---
+
+## 라이브 데모
+
+**지금 체험:** https://demo.langbot.dev/
+- 이메일: `demo@langbot.app`
+- 비밀번호: `langbot123456`
+
+*참고: 공개 데모 환경입니다. 민감한 정보를 입력하지 마세요.*
+
+---
+
+## 커뮤니티
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&label=Discord)](https://discord.gg/wdNEHETs87)
+
+- [Discord 커뮤니티](https://discord.gg/wdNEHETs87)
+
+---
+
+## Star 추이
+
+[![Star History Chart](https://api.star-history.com/svg?repos=langbot-app/LangBot&type=Date)](https://star-history.com/#langbot-app/LangBot&Date)
+
+---
+
+## 기여자
+
+LangBot을 더 나은 프로젝트로 만들어 주신 모든 [기여자](https://github.com/langbot-app/LangBot/graphs/contributors)분들께 감사드립니다:
+
+<a href="https://github.com/langbot-app/LangBot/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=langbot-app/LangBot" />
+</a>

README_RU.md

@@ -0,0 +1,174 @@
+<p align="center">
+<a href="https://langbot.app">
+<img width="130" src="res/logo-blue.png" alt="LangBot"/>
+</a>
+
+<div align="center">
+
+<a href="https://www.producthunt.com/products/langbot?utm_source=badge-follow&utm_medium=badge&utm_source=badge-langbot" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/follow.svg?product_id=1077185&theme=light" alt="LangBot - Production&#0045;grade&#0032;IM&#0032;bot&#0032;made&#0032;easy&#0046; | Product Hunt" style="width: 250px; height: 54px;" width="250" height="54" /></a>
+
+<h3>Платформа производственного уровня для создания агентных IM-ботов.</h3>
+<h4>Быстро создавайте, отлаживайте и развертывайте ИИ-ботов в Slack, Discord, Telegram, WeChat и других платформах.</h4>
+
+[English](README.md) / [简体中文](README_CN.md) / [繁體中文](README_TW.md) / [日本語](README_JP.md) / [Español](README_ES.md) / [Français](README_FR.md) / [한국어](README_KO.md) / Русский / [Tiếng Việt](README_VI.md)
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&labelColor=%20%235462eb&logoColor=%20%23f5f5f5&color=%20%235462eb)](https://discord.gg/wdNEHETs87)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/langbot-app/LangBot)
+[![GitHub release (latest by date)](https://img.shields.io/github/v/release/langbot-app/LangBot)](https://github.com/langbot-app/LangBot/releases/latest)
+<img src="https://img.shields.io/badge/python-3.10 ~ 3.13 -blue.svg" alt="python">
+[![GitHub stars](https://img.shields.io/github/stars/langbot-app/LangBot?style=social)](https://github.com/langbot-app/LangBot/stargazers)
+
+<a href="https://langbot.app">Главная</a> ｜
+<a href="https://link.langbot.app/en/docs/features">Возможности</a> ｜
+<a href="https://link.langbot.app/en/docs/guide">Документация</a> ｜
+<a href="https://link.langbot.app/en/docs/api">API</a> ｜
+<a href="https://space.langbot.app">Магазин плагинов</a> ｜
+<a href="https://langbot.featurebase.app/roadmap">Дорожная карта</a>
+
+</div>
+
+</p>
+
+---
+
+## Что такое LangBot?
+
+LangBot — это **платформа с открытым исходным кодом производственного уровня** для создания ИИ-ботов в мессенджерах. Она связывает большие языковые модели (LLM) с любой чат-платформой, позволяя создавать интеллектуальных агентов, которые могут вести диалоги, выполнять задачи и интегрироваться с вашими существующими рабочими процессами.
+
+### Ключевые возможности
+
+- **ИИ-диалоги и агенты** — Многораундовые диалоги, вызов инструментов, мультимодальная поддержка, потоковый вывод. Встроенная реализация RAG (база знаний) с глубокой интеграцией в [Dify](https://dify.ai), [Coze](https://coze.com), [n8n](https://n8n.io), [Langflow](https://langflow.org).
+- **Универсальная поддержка IM-платформ** — Единая кодовая база для Discord, Telegram, Slack, LINE, QQ, WeChat, WeCom, Lark, DingTalk, KOOK.
+- **Готовность к продакшену** — Контроль доступа, ограничение скорости, фильтрация чувствительных слов, комплексный мониторинг и обработка исключений. Проверено в корпоративной среде.
+- **Экосистема плагинов** — Сотни плагинов, событийно-ориентированная архитектура, расширения компонентов и поддержка [протокола MCP](https://modelcontextprotocol.io/).
+- **Веб-панель управления** — Настраивайте, управляйте и мониторьте ваших ботов через интуитивный браузерный интерфейс. Ручное редактирование YAML не требуется.
+- **Мультиконвейерная архитектура** — Разные боты для разных сценариев с комплексным мониторингом и обработкой исключений.
+
+[→ Подробнее обо всех возможностях](https://link.langbot.app/en/docs/features)
+
+---
+
+## Быстрый старт
+
+### ☁️ LangBot Cloud (Рекомендуется)
+
+**[LangBot Cloud](https://space.langbot.app/cloud)** — Без развёртывания, готово к использованию.
+
+### Запуск одной командой
+
+```bash
+uvx langbot
+```
+
+> Требуется [uv](https://docs.astral.sh/uv/getting-started/installation/). Откройте http://localhost:5300 — готово.
+
+### Docker Compose
+
+```bash
+git clone https://github.com/langbot-app/LangBot
+cd LangBot/docker
+docker compose up -d
+```
+
+### Облачное развертывание одним кликом
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/en-US/templates/ZKTBDH)
+[![Deploy on Railway](https://railway.com/button.svg)](https://railway.app/template/yRrAyL?referralCode=vogKPF)
+
+**Другие варианты:** [Docker](https://link.langbot.app/en/docs/docker) · [Ручная установка](https://link.langbot.app/en/docs/manual-deploy) · [BTPanel](https://link.langbot.app/en/docs/bt-panel) · [Kubernetes](./docker/README_K8S.md)
+
+---
+
+## Поддерживаемые платформы
+
+| Платформа | Статус | Примечания |
+|-----------|--------|------------|
+| Discord | ✅ | Официальный |
+| Telegram | ✅ | Официальный |
+| Slack | ✅ | Официальный |
+| LINE | ✅ | Официальный |
+| QQ | ✅ | Личный и официальный API (Канал, ЛС, Группа) |
+| WeCom | ✅ | Корпоративный WeChat, внешний CS, AI-бот |
+| WeChat | ✅ | Личный и официальный аккаунт |
+| Lark | ✅ | Официальный |
+| DingTalk | ✅ | Официальный |
+| KOOK | ✅ | Официальный |
+| Satori | ✅ |  |
+| Email | ✅ | Matrix, Satori |
+| Matrix | ✅ | Поддерживает несколько платформ через мосты, включая Signal, WhatsApp, Messenger, iMessage, Mattermost, Google Chat, IRC, XMPP, Zulip и другие |
+
+---
+
+## Поддерживаемые LLM и интеграции
+
+| Провайдер | Тип | Статус |
+|-----------|-----|--------|
+| [OpenAI](https://platform.openai.com/) | LLM | ✅ |
+| [Anthropic](https://www.anthropic.com/) | LLM | ✅ |
+| [DeepSeek](https://www.deepseek.com/) | LLM | ✅ |
+| [Google Gemini](https://aistudio.google.com/prompts/new_chat) | LLM | ✅ |
+| [xAI](https://x.ai/) | LLM | ✅ |
+| [Moonshot](https://www.moonshot.cn/) | LLM | ✅ |
+| [Zhipu AI](https://open.bigmodel.cn/) | LLM | ✅ |
+| [Ollama](https://ollama.com/) | Локальный LLM | ✅ |
+| [LM Studio](https://lmstudio.ai/) | Локальный LLM | ✅ |
+| [Dify](https://dify.ai) | LLMOps | ✅ |
+| [MCP](https://modelcontextprotocol.io/) | Протокол | ✅ |
+| [SiliconFlow](https://siliconflow.cn/) | Шлюз | ✅ |
+| [Aliyun Bailian](https://bailian.console.aliyun.com/) | Шлюз | ✅ |
+| [Volc Engine Ark](https://console.volcengine.com/ark/region:ark+cn-beijing/model?vendor=Bytedance&view=LIST_VIEW) | Шлюз | ✅ |
+| [ModelScope](https://modelscope.cn/docs/model-service/API-Inference/intro) | Шлюз | ✅ |
+| [GiteeAI](https://ai.gitee.com/) | Шлюз | ✅ |
+| [302.AI](https://share.302.ai/SuTG99) | Шлюз | ✅ |
+| [接口 AI](https://jiekou.ai/) | Шлюз | ✅ |
+| [CompShare](https://www.compshare.cn/?ytag=GPU_YY-gh_langbot) | Платформа GPU | ✅ |
+| [PPIO](https://ppinfra.com/user/register?invited_by=QJKFYD&utm_source=github_langbot) | Платформа GPU | ✅ |
+| [ShengSuanYun](https://www.shengsuanyun.com/?from=CH_KYIPP758) | Платформа GPU | ✅ |
+| [Qiniu](https://www.qiniu.com/ai/agent) | Шлюз | ✅ |
+
+[→ Смотреть все интеграции](https://link.langbot.app/en/docs/features)
+
+---
+
+## Почему LangBot?
+
+| Сценарий использования | Как помогает LangBot |
+|------------------------|----------------------|
+| **Поддержка клиентов** | Разверните ИИ-агентов в Slack/Discord/Telegram, которые отвечают на вопросы, используя вашу базу знаний |
+| **Внутренние инструменты** | Подключите рабочие процессы n8n/Dify к WeCom/DingTalk для автоматизации бизнес-процессов |
+| **Управление сообществом** | Модерируйте группы QQ/Discord с помощью ИИ-фильтрации контента и взаимодействия |
+| **Мультиплатформенное присутствие** | Один бот — все платформы. Управляйте из единой панели |
+
+---
+
+## Демо
+
+**Попробуйте прямо сейчас:** https://demo.langbot.dev/
+- Email: `demo@langbot.app`
+- Пароль: `langbot123456`
+
+*Примечание: Публичная демо-среда. Не вводите конфиденциальную информацию.*
+
+---
+
+## Сообщество
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&label=Discord)](https://discord.gg/wdNEHETs87)
+
+- [Сообщество Discord](https://discord.gg/wdNEHETs87)
+
+---
+
+## История Stars
+
+[![Star History Chart](https://api.star-history.com/svg?repos=langbot-app/LangBot&type=Date)](https://star-history.com/#langbot-app/LangBot&Date)
+
+---
+
+## Участники
+
+Спасибо всем [участникам](https://github.com/langbot-app/LangBot/graphs/contributors), которые помогли сделать LangBot лучше:
+
+<a href="https://github.com/langbot-app/LangBot/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=langbot-app/LangBot" />
+</a>

README_TW.md

@@ -0,0 +1,192 @@
+<p align="center">
+<a href="https://langbot.app">
+<img width="130" src="res/logo-blue.png" alt="LangBot"/>
+</a>
+
+<div align="center">
+
+<a href="https://hellogithub.com/repository/langbot-app/LangBot" target="_blank"><img src="https://abroad.hellogithub.com/v1/widgets/recommend.svg?rid=5ce8ae2aa4f74316bf393b57b952433c&claim_uid=gtmc6YWjMZkT21R" alt="Featured｜HelloGitHub" style="width: 250px; height: 54px;" width="250" height="54" /></a>
+
+<h3>生產級 AI 即時通訊機器人開發平台。</h3>
+<h4>快速建構、除錯和部署 AI 機器人到微信、QQ、飛書、Slack、Discord、Telegram 等平台。</h4>
+
+[English](README.md) / [简体中文](README_CN.md) / 繁體中文 / [日本語](README_JP.md) / [Español](README_ES.md) / [Français](README_FR.md) / [한국어](README_KO.md) / [Русский](README_RU.md) / [Tiếng Việt](README_VI.md)
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&labelColor=%20%235462eb&logoColor=%20%23f5f5f5&color=%20%235462eb)](https://discord.gg/wdNEHETs87)
+[![QQ Group](https://img.shields.io/badge/%E7%A4%BE%E5%8C%BAQQ%E7%BE%A4-966235608-blue)](https://qm.qq.com/q/JLi38whHum)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/langbot-app/LangBot)
+[![GitHub release (latest by date)](https://img.shields.io/github/v/release/langbot-app/LangBot)](https://github.com/langbot-app/LangBot/releases/latest)
+<img src="https://img.shields.io/badge/python-3.10 ~ 3.13 -blue.svg" alt="python">
+[![GitHub stars](https://img.shields.io/github/stars/langbot-app/LangBot?style=social)](https://github.com/langbot-app/LangBot/stargazers)
+[![star](https://gitcode.com/RockChinQ/LangBot/star/badge.svg)](https://gitcode.com/RockChinQ/LangBot)
+
+<a href="https://langbot.app">官網</a> ｜
+<a href="https://link.langbot.app/zh/docs/features">特性</a> ｜
+<a href="https://link.langbot.app/zh/docs/guide">文件</a> ｜
+<a href="https://link.langbot.app/zh/docs/api">API</a> ｜
+<a href="https://space.langbot.app">外掛市場</a> ｜
+<a href="https://langbot.featurebase.app/roadmap">路線圖</a>
+
+</div>
+
+</p>
+
+---
+
+## 什麼是 LangBot？
+
+LangBot 是一個**開源的生產級平台**，用於建構 AI 驅動的即時通訊機器人。它將大語言模型（LLM）連接到各種聊天平台，幫助你創建能夠對話、執行任務、並整合到現有工作流程中的智能 Agent。
+
+### 核心能力
+
+- **AI 對話與 Agent** — 多輪對話、工具調用、多模態、流式輸出。自帶 RAG（知識庫），深度整合 [Dify](https://dify.ai)、[Coze](https://coze.com)、[n8n](https://n8n.io)、[Langflow](https://langflow.org) 等 LLMOps 平台。
+- **全平台支援** — 一套程式碼，覆蓋 QQ、微信、企業微信、飛書、釘釘、Discord、Telegram、Slack、LINE、KOOK 等平台。
+- **生產就緒** — 存取控制、限速、敏感詞過濾、全面監控與異常處理，已被多家企業採用。
+- **外掛生態** — 數百個外掛，事件驅動架構，組件擴展，適配 [MCP 協議](https://modelcontextprotocol.io/)。
+- **Web 管理面板** — 透過瀏覽器直觀地配置、管理和監控機器人，無需手動編輯設定檔。
+- **多流水線架構** — 不同機器人用於不同場景，具備全面的監控和異常處理能力。
+
+[→ 了解更多功能特性](https://link.langbot.app/zh/docs/features)
+
+---
+
+## 快速開始
+
+### ☁️ LangBot Cloud（推薦）
+
+**[LangBot Cloud](https://space.langbot.app/cloud)** — 免部署，開箱即用。
+
+### 一鍵啟動
+
+```bash
+uvx langbot
+```
+
+> 需要安裝 [uv](https://docs.astral.sh/uv/getting-started/installation/)。訪問 http://localhost:5300 即可使用。
+
+### Docker Compose
+
+```bash
+git clone https://github.com/langbot-app/LangBot
+cd LangBot/docker
+docker compose up -d
+```
+
+### 一鍵雲端部署
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/zh-CN/templates/ZKTBDH)
+[![Deploy on Railway](https://railway.com/button.svg)](https://railway.app/template/yRrAyL?referralCode=vogKPF)
+
+**更多方式：** [Docker](https://link.langbot.app/zh/docs/docker) · [手動部署](https://link.langbot.app/zh/docs/manual-deploy) · [寶塔面板](https://link.langbot.app/zh/docs/bt-panel) · [Kubernetes](./docker/README_K8S.md)
+
+---
+
+## 支援的平台
+
+| 平台 | 狀態 | 備註 |
+|------|------|------|
+| Discord | ✅ | 官方 |
+| Telegram | ✅ | 官方 |
+| Slack | ✅ | 官方 |
+| LINE | ✅ | 官方 |
+| QQ | ✅ | 個人號、官方機器人（頻道、私聊、群聊） |
+| 企業微信 | ✅ | 應用訊息、對外客服、智能機器人 |
+| 微信 | ✅ | 個人微信、微信公眾號 |
+| 飛書 | ✅ | 官方 |
+| 釘釘 | ✅ | 官方 |
+| KOOK | ✅ | 官方 |
+| Satori | ✅ |  |
+| Email | ✅ | 只 Matrix、Satori |
+| Matrix | ✅ | 支援多種橋接平台，如 Signal、WhatsApp、Messenger、iMessage、Mattermost、Google Chat、IRC、XMPP、Zulip 等 |
+
+---
+
+## 支援的大模型與整合
+
+| 提供商 | 類型 | 狀態 |
+|--------|------|------|
+| [OpenAI](https://platform.openai.com/) | LLM | ✅ |
+| [Anthropic](https://www.anthropic.com/) | LLM | ✅ |
+| [DeepSeek](https://www.deepseek.com/) | LLM | ✅ |
+| [Google Gemini](https://aistudio.google.com/prompts/new_chat) | LLM | ✅ |
+| [xAI](https://x.ai/) | LLM | ✅ |
+| [Moonshot](https://www.moonshot.cn/) | LLM | ✅ |
+| [智譜AI](https://open.bigmodel.cn/) | LLM | ✅ |
+| [Ollama](https://ollama.com/) | 本地 LLM | ✅ |
+| [LM Studio](https://lmstudio.ai/) | 本地 LLM | ✅ |
+| [Dify](https://dify.ai) | LLMOps | ✅ |
+| [MCP](https://modelcontextprotocol.io/) | 協議 | ✅ |
+| [SiliconFlow](https://siliconflow.cn/) | 聚合平台 | ✅ |
+| [阿里雲百煉](https://bailian.console.aliyun.com/) | 聚合平台 | ✅ |
+| [火山方舟](https://console.volcengine.com/ark/region:ark+cn-beijing/model?vendor=Bytedance&view=LIST_VIEW) | 聚合平台 | ✅ |
+| [ModelScope](https://modelscope.cn/docs/model-service/API-Inference/intro) | 聚合平台 | ✅ |
+| [GiteeAI](https://ai.gitee.com/) | 聚合平台 | ✅ |
+| [勝算雲](https://www.shengsuanyun.com/?from=CH_KYIPP758) | GPU 平台 | ✅ |
+| [優雲智算](https://www.compshare.cn/?ytag=GPU_YY-gh_langbot) | GPU 平台 | ✅ |
+| [PPIO](https://ppinfra.com/user/register?invited_by=QJKFYD&utm_source=github_langbot) | GPU 平台 | ✅ |
+| [接口 AI](https://jiekou.ai/) | 聚合平台 | ✅ |
+| [302.AI](https://share.302.ai/SuTG99) | 聚合平台 | ✅ |
+| [Qiniu](https://www.qiniu.com/ai/agent) | 聚合平台 | ✅ |
+
+### TTS（語音合成）
+
+| 平台/模型 | 備註 |
+|-----------|------|
+| [FishAudio](https://fish.audio/zh-CN/discovery/) | [外掛](https://github.com/the-lazy-me/NewChatVoice) |
+| [海豚 AI](https://www.ttson.cn/?source=thelazy) | [外掛](https://github.com/the-lazy-me/NewChatVoice) |
+| [AzureTTS](https://portal.azure.com/) | [外掛](https://github.com/Ingnaryk/LangBot_AzureTTS) |
+
+### 文生圖
+
+| 平台/模型 | 備註 |
+|-----------|------|
+| 阿里雲百煉 | [外掛](https://github.com/Thetail001/LangBot_BailianTextToImagePlugin) |
+
+[→ 查看完整整合列表](https://link.langbot.app/zh/docs/features)
+
+---
+
+## 為什麼選擇 LangBot？
+
+| 使用場景 | LangBot 如何幫助 |
+|----------|------------------|
+| **客戶服務** | 將 AI Agent 部署到微信/企微/釘釘/飛書，基於知識庫自動回答使用者問題 |
+| **內部工具** | 將 n8n/Dify 工作流接入企微/釘釘，實現業務流程自動化 |
+| **社群運營** | 在 QQ/Discord 群中使用 AI 驅動的內容審核與智能互動 |
+| **多平台觸達** | 一個機器人，覆蓋所有平台。透過統一面板集中管理 |
+
+---
+
+## 線上演示
+
+**立即體驗：** https://demo.langbot.dev/
+- 信箱：`demo@langbot.app`
+- 密碼：`langbot123456`
+
+*注意：公開演示環境，請不要在其中填入任何敏感資訊。*
+
+---
+
+## 社群
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&label=Discord)](https://discord.gg/wdNEHETs87)
+[![QQ Group](https://img.shields.io/badge/%E7%A4%BE%E5%8C%BAQQ%E7%BE%A4-966235608-blue)](https://qm.qq.com/q/JLi38whHum)
+
+- [Discord 社群](https://discord.gg/wdNEHETs87)
+- [QQ 社群群](https://qm.qq.com/q/JLi38whHum)
+
+---
+
+## Star 趨勢
+
+[![Star History Chart](https://api.star-history.com/svg?repos=langbot-app/LangBot&type=Date)](https://star-history.com/#langbot-app/LangBot&Date)
+
+---
+
+## 貢獻者
+
+感謝所有[貢獻者](https://github.com/langbot-app/LangBot/graphs/contributors)對 LangBot 的幫助：
+
+<a href="https://github.com/langbot-app/LangBot/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=langbot-app/LangBot" />
+</a>

README_VI.md

@@ -0,0 +1,174 @@
+<p align="center">
+<a href="https://langbot.app">
+<img width="130" src="res/logo-blue.png" alt="LangBot"/>
+</a>
+
+<div align="center">
+
+<a href="https://www.producthunt.com/products/langbot?utm_source=badge-follow&utm_medium=badge&utm_source=badge-langbot" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/follow.svg?product_id=1077185&theme=light" alt="LangBot - Production&#0045;grade&#0032;IM&#0032;bot&#0032;made&#0032;easy&#0046; | Product Hunt" style="width: 250px; height: 54px;" width="250" height="54" /></a>
+
+<h3>Nền tảng cấp sản xuất để xây dựng bot IM với AI agent.</h3>
+<h4>Xây dựng, gỡ lỗi và triển khai bot AI nhanh chóng trên Slack, Discord, Telegram, WeChat và nhiều nền tảng khác.</h4>
+
+[English](README.md) / [简体中文](README_CN.md) / [繁體中文](README_TW.md) / [日本語](README_JP.md) / [Español](README_ES.md) / [Français](README_FR.md) / [한국어](README_KO.md) / [Русский](README_RU.md) / Tiếng Việt
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&labelColor=%20%235462eb&logoColor=%20%23f5f5f5&color=%20%235462eb)](https://discord.gg/wdNEHETs87)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/langbot-app/LangBot)
+[![GitHub release (latest by date)](https://img.shields.io/github/v/release/langbot-app/LangBot)](https://github.com/langbot-app/LangBot/releases/latest)
+<img src="https://img.shields.io/badge/python-3.10 ~ 3.13 -blue.svg" alt="python">
+[![GitHub stars](https://img.shields.io/github/stars/langbot-app/LangBot?style=social)](https://github.com/langbot-app/LangBot/stargazers)
+
+<a href="https://langbot.app">Trang chủ</a> ｜
+<a href="https://link.langbot.app/en/docs/features">Tính năng</a> ｜
+<a href="https://link.langbot.app/en/docs/guide">Tài liệu</a> ｜
+<a href="https://link.langbot.app/en/docs/api">API</a> ｜
+<a href="https://space.langbot.app">Chợ Plugin</a> ｜
+<a href="https://langbot.featurebase.app/roadmap">Lộ trình</a>
+
+</div>
+
+</p>
+
+---
+
+## LangBot là gì?
+
+LangBot là một **nền tảng mã nguồn mở, cấp sản xuất** để xây dựng bot nhắn tin tức thời được hỗ trợ bởi AI. Nó kết nối các Mô hình Ngôn ngữ Lớn (LLM) với bất kỳ nền tảng chat nào, cho phép bạn tạo các agent thông minh có thể trò chuyện, thực hiện tác vụ và tích hợp với quy trình làm việc hiện có của bạn.
+
+### Khả năng chính
+
+- **Hội thoại AI & Agent** — Đối thoại nhiều lượt, gọi công cụ, hỗ trợ đa phương thức, đầu ra streaming. RAG (cơ sở kiến thức) tích hợp sẵn với tích hợp sâu vào [Dify](https://dify.ai), [Coze](https://coze.com), [n8n](https://n8n.io), [Langflow](https://langflow.org).
+- **Hỗ trợ đa nền tảng IM** — Một mã nguồn cho Discord, Telegram, Slack, LINE, QQ, WeChat, WeCom, Lark, DingTalk, KOOK.
+- **Sẵn sàng cho sản xuất** — Kiểm soát truy cập, giới hạn tốc độ, lọc từ nhạy cảm, giám sát toàn diện và xử lý ngoại lệ. Được doanh nghiệp tin dùng.
+- **Hệ sinh thái Plugin** — Hàng trăm plugin, kiến trúc hướng sự kiện, mở rộng thành phần, và hỗ trợ [giao thức MCP](https://modelcontextprotocol.io/).
+- **Bảng quản lý Web** — Cấu hình, quản lý và giám sát bot thông qua giao diện trình duyệt trực quan. Không cần chỉnh sửa YAML.
+- **Kiến trúc đa Pipeline** — Các bot khác nhau cho các kịch bản khác nhau, với giám sát toàn diện và xử lý ngoại lệ.
+
+[→ Tìm hiểu thêm về tất cả tính năng](https://link.langbot.app/en/docs/features)
+
+---
+
+## Bắt đầu nhanh
+
+### ☁️ LangBot Cloud (Khuyên dùng)
+
+**[LangBot Cloud](https://space.langbot.app/cloud)** — Không cần triển khai, sẵn sàng sử dụng.
+
+### Khởi chạy một dòng
+
+```bash
+uvx langbot
+```
+
+> Yêu cầu [uv](https://docs.astral.sh/uv/getting-started/installation/). Truy cập http://localhost:5300 — xong.
+
+### Docker Compose
+
+```bash
+git clone https://github.com/langbot-app/LangBot
+cd LangBot/docker
+docker compose up -d
+```
+
+### Triển khai đám mây một cú nhấp
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/en-US/templates/ZKTBDH)
+[![Deploy on Railway](https://railway.com/button.svg)](https://railway.app/template/yRrAyL?referralCode=vogKPF)
+
+**Thêm tùy chọn:** [Docker](https://link.langbot.app/en/docs/docker) · [Thủ công](https://link.langbot.app/en/docs/manual-deploy) · [BTPanel](https://link.langbot.app/en/docs/bt-panel) · [Kubernetes](./docker/README_K8S.md)
+
+---
+
+## Nền tảng được hỗ trợ
+
+| Nền tảng | Trạng thái | Ghi chú |
+|----------|--------|-------|
+| Discord | ✅ | Chính thức |
+| Telegram | ✅ | Chính thức |
+| Slack | ✅ | Chính thức |
+| LINE | ✅ | Chính thức |
+| QQ | ✅ | Cá nhân & API chính thức (Kênh, DM, Nhóm) |
+| WeCom | ✅ | WeChat doanh nghiệp, CS bên ngoài, AI Bot |
+| WeChat | ✅ | Cá nhân & Tài khoản công khai |
+| Lark | ✅ | Chính thức |
+| DingTalk | ✅ | Chính thức |
+| KOOK | ✅ | Chính thức |
+| Satori | ✅ |  |
+| Email | ✅ | Matrix, Satori |
+| Matrix | ✅ | Hỗ trợ nhiều nền tảng qua bridge như Signal, WhatsApp, Messenger, iMessage, Mattermost, Google Chat, IRC, XMPP, Zulip và hơn thế nữa |
+
+---
+
+## LLM và tích hợp được hỗ trợ
+
+| Nhà cung cấp | Loại | Trạng thái |
+|----------|------|--------|
+| [OpenAI](https://platform.openai.com/) | LLM | ✅ |
+| [Anthropic](https://www.anthropic.com/) | LLM | ✅ |
+| [DeepSeek](https://www.deepseek.com/) | LLM | ✅ |
+| [Google Gemini](https://aistudio.google.com/prompts/new_chat) | LLM | ✅ |
+| [xAI](https://x.ai/) | LLM | ✅ |
+| [Moonshot](https://www.moonshot.cn/) | LLM | ✅ |
+| [Zhipu AI](https://open.bigmodel.cn/) | LLM | ✅ |
+| [Ollama](https://ollama.com/) | LLM cục bộ | ✅ |
+| [LM Studio](https://lmstudio.ai/) | LLM cục bộ | ✅ |
+| [Dify](https://dify.ai) | LLMOps | ✅ |
+| [MCP](https://modelcontextprotocol.io/) | Giao thức | ✅ |
+| [SiliconFlow](https://siliconflow.cn/) | Cổng | ✅ |
+| [Aliyun Bailian](https://bailian.console.aliyun.com/) | Cổng | ✅ |
+| [Volc Engine Ark](https://console.volcengine.com/ark/region:ark+cn-beijing/model?vendor=Bytedance&view=LIST_VIEW) | Cổng | ✅ |
+| [ModelScope](https://modelscope.cn/docs/model-service/API-Inference/intro) | Cổng | ✅ |
+| [GiteeAI](https://ai.gitee.com/) | Cổng | ✅ |
+| [CompShare](https://www.compshare.cn/?ytag=GPU_YY-gh_langbot) | Nền tảng GPU | ✅ |
+| [PPIO](https://ppinfra.com/user/register?invited_by=QJKFYD&utm_source=github_langbot) | Nền tảng GPU | ✅ |
+| [ShengSuanYun](https://www.shengsuanyun.com/?from=CH_KYIPP758) | Nền tảng GPU | ✅ |
+| [接口 AI](https://jiekou.ai/) | Cổng | ✅ |
+| [302.AI](https://share.302.ai/SuTG99) | Cổng | ✅ |
+| [Qiniu](https://www.qiniu.com/ai/agent) | Cổng | ✅ |
+
+[→ Xem tất cả tích hợp](https://link.langbot.app/en/docs/features)
+
+---
+
+## Tại sao chọn LangBot?
+
+| Trường hợp sử dụng | LangBot giúp như thế nào |
+|----------|-------------------|
+| **Hỗ trợ khách hàng** | Triển khai agent AI trên Slack/Discord/Telegram để trả lời câu hỏi bằng cơ sở kiến thức của bạn |
+| **Công cụ nội bộ** | Kết nối quy trình n8n/Dify với WeCom/DingTalk để tự động hóa quy trình kinh doanh |
+| **Quản lý cộng đồng** | Quản lý nhóm QQ/Discord với tính năng lọc nội dung và tương tác được hỗ trợ bởi AI |
+| **Đa nền tảng** | Một bot, tất cả nền tảng. Quản lý từ một bảng điều khiển duy nhất |
+
+---
+
+## Demo trực tuyến
+
+**Thử ngay:** https://demo.langbot.dev/
+- Email: `demo@langbot.app`
+- Mật khẩu: `langbot123456`
+
+*Lưu ý: Môi trường demo công khai. Không nhập thông tin nhạy cảm.*
+
+---
+
+## Cộng đồng
+
+[![Discord](https://img.shields.io/discord/1335141740050649118?logo=discord&label=Discord)](https://discord.gg/wdNEHETs87)
+
+- [Cộng đồng Discord](https://discord.gg/wdNEHETs87)
+
+---
+
+## Lịch sử Star
+
+[![Star History Chart](https://api.star-history.com/svg?repos=langbot-app/LangBot&type=Date)](https://star-history.com/#langbot-app/LangBot&Date)
+
+---
+
+## Người đóng góp
+
+Cảm ơn tất cả [người đóng góp](https://github.com/langbot-app/LangBot/graphs/contributors) đã giúp LangBot trở nên tốt hơn:
+
+<a href="https://github.com/langbot-app/LangBot/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=langbot-app/LangBot" />
+</a>

README_en.md

@@ -1,215 +0,0 @@
-# QChatGPT🤖
-
-<p align="center">
-<img src="res/social.png" alt="QChatGPT" width="640" />
-</p>
-
-English | [简体中文](README.md)
-
-[![GitHub release (latest by date)](https://img.shields.io/github/v/release/RockChinQ/QChatGPT?style=flat-square)](https://github.com/RockChinQ/QChatGPT/releases/latest)
-![Wakapi Count](https://wakapi.dev/api/badge/RockChinQ/interval:any/project:QChatGPT)
-
-- Refer to [Wiki](https://github.com/RockChinQ/QChatGPT/wiki) to get further information.  
-- Official QQ group: 656285629  
-- Community QQ group: 362515018
-- QQ channel robot: [QQChannelChatGPT](https://github.com/Soulter/QQChannelChatGPT)
-- Any contribution is welcome, please refer to [CONTRIBUTING.md](CONTRIBUTING.md)
-
-## 🍺List of supported models
-
-<details>
-<summary>Details</summary>
-
-### Chat
-
-- OpenAI GPT-3.5 (ChatGPT API), default model
-- OpenAI GPT-3, supported natively, switch to it in `config.py`
-- OpenAI GPT-4, supported natively, qualification for internal testing required, switch to it in `config.py`
-- ChatGPT website edition (GPT-3.5), see [revLibs plugin](https://github.com/RockChinQ/revLibs)
-- ChatGPT website edition (GPT-4), ChatGPT plus subscription required, see [revLibs plugin](https://github.com/RockChinQ/revLibs)
-- New Bing, see [revLibs plugin](https://github.com/RockChinQ/revLibs)
-- HuggingChat, see [revLibs plugin](https://github.com/RockChinQ/revLibs), English only
-
-### Story
-
-- NovelAI API, see [QCPNovelAi plugin](https://github.com/dominoar/QCPNovelAi)
-
-### Image
-
-- OpenAI DALL·E, supported natively, see [Wiki(cn)](https://github.com/RockChinQ/QChatGPT/wiki/%E5%8A%9F%E8%83%BD%E4%BD%BF%E7%94%A8#%E5%8A%9F%E8%83%BD%E7%82%B9%E5%88%97%E4%B8%BE)
-- NovelAI API, see [QCPNovelAi plugin](https://github.com/dominoar/QCPNovelAi)
-
-### Voice
-
-- TTS+VITS, see [QChatPlugins](https://github.com/dominoar/QChatPlugins)
-- Plachta/VITS-Umamusume-voice-synthesizer, see [chat_voice plugin](https://github.com/oliverkirk-sudo/chat_voice)
-
-
-</details>
-
-Install this [plugin](https://github.com/RockChinQ/Switcher) to switch between different models.
-
-## ✅Function Points
-
-<details>
-<summary>Details</summary>
-
- - ✅Sensitive word filtering, avoid being banned
- - ✅Multiple responding rules, including regular expression matching
- - ✅Multiple api-key management, automatic switching when exceeding
- - ✅Support for customizing the preset prompt text
- - ✅Chat, story, image, voice, etc. models are supported
- - ✅Support for hot reloading and hot updating
- - ✅Support for plugin loading
- - ✅Blacklist mechanism for private chat and group chat
- - ✅Excellent long message processing strategy
- - ✅Reply rate limitation
- - ✅Support for network proxy
- - ✅Support for customizing the output format
-</details>
-
-More details, see [Wiki(cn)](https://github.com/RockChinQ/QChatGPT/wiki/%E5%8A%9F%E8%83%BD%E4%BD%BF%E7%94%A8#%E5%8A%9F%E8%83%BD%E7%82%B9%E5%88%97%E4%B8%BE)
-
-## 🔩Deployment
-
-**If you encounter any problems during deployment, please search in the issue of [QChatGPT](https://github.com/RockChinQ/QChatGPT/issues) or [qcg-installer](https://github.com/RockChinQ/qcg-installer/issues) first.**
-
-### - Register OpenAI account
-
-> If you want to use a model other than OpenAI (such as New Bing), you can skip this step and directly refer to following steps, and then configure it according to the relevant plugin documentation.
-
-To register OpenAI account, please refer to the following articles(in Chinese):
-
-> [国内注册ChatGPT的方法(100%可用)](https://www.pythonthree.com/register-openai-chatgpt/)  
-> [手把手教你如何注册ChatGPT，超级详细](https://guxiaobei.com/51461)
-
-Check your api-key in [personal center](https://beta.openai.com/account/api-keys) after registration, and then follow the following steps to deploy.
-
-### - Deploy Automatically
-
-<details>
-<summary>Details</summary>
-
-#### Docker
-
-See [this document(cn)](res/docs/docker_deploy.md)  
-Contributed by [@mikumifa](https://github.com/mikumifa)
-
-#### Installer
-
-Use [this installer](https://github.com/RockChinQ/qcg-installer) to deploy.
-
-- The installer currently only supports some platforms, please refer to the repository document for details, and manually deploy for other platforms
-
-</details>
-
-### - Deploy Manually
-<details>
-<summary>Manually deployment supports any platforms</summary>
-
-- Python 3.9.x or higher
-
-#### 配置QQ登录框架
-
-Currently supports mirai and go-cqhttp, configure either one
-
-<details>
-<summary>mirai</summary>
-
-Follow [this tutorial(cn)](https://yiri-mirai.wybxc.cc/tutorials/01/configuration) to configure Mirai and YiriMirai.  
-After starting mirai-console, use the `login` command to log in to the QQ account, and keep the mirai-console running.
-
-</details>
-
-<details>
-<summary>go-cqhttp</summary>
-
-1. Follow [this tutorial(cn)](https://github.com/RockChinQ/QChatGPT/wiki/go-cqhttp%E9%85%8D%E7%BD%AE) to configure go-cqhttp.
-2. Start go-cqhttp, make sure it is logged in and running.
-
-</details>
-
-#### Configure QChatGPT
-
-1. Clone the repository
-
-```bash
-git clone https://github.com/RockChinQ/QChatGPT
-cd QChatGPT
-```
-
-2. Install dependencies
-
-```bash
-pip3 install requests yiri-mirai openai colorlog func_timeout dulwich Pillow nakuru-project-idk
-```
-
-3. Generate `config.py`
-
-```bash
-python3 main.py
-```
-
-4. Edit `config.py`
-
-5. Run
-
-```bash
-python3 main.py
-```
-
-Any problems, please refer to the issues page.
-
-</details>
-
-## 🚀Usage
-
-**After deployment, please read: [Commands(cn)](https://github.com/RockChinQ/QChatGPT/wiki/%E5%8A%9F%E8%83%BD%E4%BD%BF%E7%94%A8#%E6%9C%BA%E5%99%A8%E4%BA%BA%E6%8C%87%E4%BB%A4)**  
-
-**For more details, please refer to the [Wiki(cn)](https://github.com/RockChinQ/QChatGPT/wiki/%E5%8A%9F%E8%83%BD%E4%BD%BF%E7%94%A8#%E4%BD%BF%E7%94%A8%E6%96%B9%E5%BC%8F)**
-
-
-## 🧩Plugin Ecosystem
-
-Plugin [usage](https://github.com/RockChinQ/QChatGPT/wiki/%E6%8F%92%E4%BB%B6%E4%BD%BF%E7%94%A8) and [development](https://github.com/RockChinQ/QChatGPT/wiki/%E6%8F%92%E4%BB%B6%E5%BC%80%E5%8F%91) are supported.
-
-<details>
-<summary>List of plugins (cn)</summary>
-
-### Examples
-
-在`tests/plugin_examples`目录下，将其整个目录复制到`plugins`目录下即可使用
-
-- `cmdcn` - 主程序指令中文形式
-- `hello_plugin` - 在收到消息`hello`时回复相应消息
-- `urlikethisijustsix` - 收到冒犯性消息时回复相应消息
-
-### More Plugins
-
-欢迎提交新的插件
-
-- [revLibs](https://github.com/RockChinQ/revLibs) - 将ChatGPT网页版接入此项目，关于[官方接口和网页版有什么区别](https://github.com/RockChinQ/QChatGPT/wiki/%E5%AE%98%E6%96%B9%E6%8E%A5%E5%8F%A3%E4%B8%8EChatGPT%E7%BD%91%E9%A1%B5%E7%89%88)
-- [Switcher](https://github.com/RockChinQ/Switcher) - 支持通过指令切换使用的模型
-- [hello_plugin](https://github.com/RockChinQ/hello_plugin) - `hello_plugin` 的储存库形式，插件开发模板
-- [dominoar/QChatPlugins](https://github.com/dominoar/QchatPlugins) - dominoar编写的诸多新功能插件（语音输出、Ranimg、屏蔽词规则等）
-- [dominoar/QCP-NovelAi](https://github.com/dominoar/QCP-NovelAi) - NovelAI 故事叙述与绘画
-- [oliverkirk-sudo/chat_voice](https://github.com/oliverkirk-sudo/chat_voice) - 文字转语音输出，使用HuggingFace上的[VITS-Umamusume-voice-synthesizer模型](https://huggingface.co/spaces/Plachta/VITS-Umamusume-voice-synthesizer)
-- [RockChinQ/WaitYiYan](https://github.com/RockChinQ/WaitYiYan) - 实时获取百度`文心一言`等待列表人数
-- [chordfish-k/QChartGPT_Emoticon_Plugin](https://github.com/chordfish-k/QChartGPT_Emoticon_Plugin) - 使机器人根据回复内容发送表情包
-- [oliverkirk-sudo/ChatPoeBot](https://github.com/oliverkirk-sudo/ChatPoeBot) - 接入[Poe](https://poe.com/)上的机器人
-- [lieyanqzu/WeatherPlugin](https://github.com/lieyanqzu/WeatherPlugin) - 天气查询插件
-</details>
-
-## 😘Thanks
-
-- [@the-lazy-me](https://github.com/the-lazy-me) video tutorial creator
-- [@mikumifa](https://github.com/mikumifa) Docker deployment
-- [@dominoar](https://github.com/dominoar) Plugin development
-- [@万神的星空](https://github.com/qq255204159) Packages publisher
-- [@ljcduo](https://github.com/ljcduo)  GPT-4 API internal test account
-
-And all [contributors](https://github.com/RockChinQ/QChatGPT/graphs/contributors) and other friends who support this project.
-
-<!-- ## 👍赞赏
-
-<img alt="赞赏码" src="res/mm_reward_qrcode_1672840549070.png" width="400" height="400"/> -->

codecov.yml

@@ -0,0 +1,4 @@
+coverage:
+  status:
+    project: off
+    patch: off

config-template.py

@@ -1,362 +0,0 @@
-# 配置文件: 注释里标[必需]的参数必须修改, 其他参数根据需要修改, 但请勿删除
-import logging
-
-# 消息处理协议适配器
-# 目前支持以下适配器:
-# - "yirimirai": mirai的通信框架，YiriMirai框架适配器, 请同时填写下方mirai_http_api_config
-# - "nakuru": go-cqhttp通信框架，请同时填写下方nakuru_config
-msg_source_adapter = "yirimirai"
-
-# [必需(与nakuru二选一，取决于msg_source_adapter)] Mirai的配置
-# 请到配置mirai的步骤中的教程查看每个字段的信息
-# adapter: 选择适配器，目前支持HTTPAdapter和WebSocketAdapter
-# host: 运行mirai的主机地址
-# port: 运行mirai的主机端口
-# verifyKey: mirai-api-http的verifyKey
-# qq: 机器人的QQ号
-#
-# 注意: QQ机器人配置不支持热重载及热更新
-mirai_http_api_config = {
-    "adapter": "WebSocketAdapter",
-    "host": "localhost",
-    "port": 8080,
-    "verifyKey": "yirimirai",
-    "qq": 1234567890
-}
-
-# [必需(与mirai二选一，取决于msg_source_adapter)]
-# 使用nakuru-project框架连接go-cqhttp的配置
-nakuru_config = {
-    "host": "localhost",  # go-cqhttp的地址
-    "port": 6700,  # go-cqhttp的正向websocket端口
-    "http_port": 5700,  # go-cqhttp的正向http端口
-    "token": ""  # 若在go-cqhttp的config.yml设置了access_token, 则填写此处
-}
-
-# [必需] OpenAI的配置
-# api_key: OpenAI的API Key
-# http_proxy: 请求OpenAI时使用的代理，None为不使用，https和socks5暂不能使用
-# 若只有一个api-key，请直接修改以下内容中的"openai_api_key"为你的api-key
-#
-# 如准备了多个api-key，可以以字典的形式填写，程序会自动选择可用的api-key
-# 例如
-# openai_config = {
-#     "api_key": {
-#         "default": "sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
-#         "key1": "sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
-#         "key2": "sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
-#     },
-#     "http_proxy": "http://127.0.0.1:12345"
-# }
-# 
-# 现已支持反向代理，可以添加reverse_proxy字段以使用反向代理
-# 使用反向代理可以在国内使用OpenAI的API，反向代理的配置请参考 
-# https://github.com/Ice-Hazymoon/openai-scf-proxy
-#
-# 反向代理填写示例：
-# openai_config = {
-#     "api_key": {
-#         "default": "sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
-#         "key1": "sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
-#         "key2": "sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
-#     },
-#     "reverse_proxy": "http://example.com:12345/v1"
-# }
-#
-# 作者开设公用反向代理地址: https://api.openai.rockchin.top/v1
-# 随时可能关闭，仅供测试使用，有条件建议使用正向代理或者自建反向代理
-openai_config = {
-    "api_key": {
-        "default": "openai_api_key"
-    },
-    "http_proxy": None,
-    "reverse_proxy": None
-}
-
-# api-key切换策略
-# active：每次请求时都会切换api-key
-# passive：仅当api-key超额时才会切换api-key
-switch_strategy = "active"
-
-# [必需] 管理员QQ号，用于接收报错等通知及执行管理员级别指令
-# 支持多个管理员，可以使用list形式设置，例如：
-# admin_qq = [12345678, 87654321]
-admin_qq = 0
-
-# 情景预设（机器人人格）
-# 每个会话的预设信息，影响所有会话，无视指令重置
-# 可以通过这个字段指定某些情况的回复，可直接用自然语言描述指令
-# 例如: 
-# default_prompt = "如果我之后想获取帮助，请你说“输入!help获取帮助”"
-#   这样用户在不知所措的时候机器人就会提示其输入!help获取帮助
-# 可参考 https://github.com/PlexPt/awesome-chatgpt-prompts-zh
-#
-# 如果需要多个情景预设，并在运行期间方便切换，请使用字典的形式填写，例如
-# default_prompt = {
-#   "default": "如果我之后想获取帮助，请你说“输入!help获取帮助”",
-#   "linux-terminal": "我想让你充当 Linux 终端。我将输入命令，您将回复终端应显示的内容。",
-#   "en-dict": "我想让你充当英英词典，对于给出的英文单词，你要给出其中文意思以及英文解释，并且给出一个例句，此外不要有其他反馈。",
-# }
-#
-# 在使用期间即可通过指令：
-# !reset [名称]
-#   来使用指定的情景预设重置会话
-# 例如：
-# !reset linux-terminal
-# 若不指定名称，则使用默认情景预设
-# 
-# 也可以使用指令：
-# !default <名称>
-#   将指定的情景预设设置为默认情景预设
-# 例如：
-# !default linux-terminal
-# 之后的会话重置时若不指定名称，则使用linux-terminal情景预设
-# 
-# 还可以加载文件中的预设文字，使用方法请查看：https://github.com/RockChinQ/QChatGPT/wiki/%E5%8A%9F%E8%83%BD%E4%BD%BF%E7%94%A8#%E9%A2%84%E8%AE%BE%E6%96%87%E5%AD%97
-default_prompt = {
-    "default": "如果我之后想获取帮助，请你说“输入!help获取帮助”",
-}
-
-# 情景预设格式
-# 参考值：默认方式：normal | 完整情景：full_scenario
-# 默认方式 的格式为上述default_prompt中的内容，或prompts目录下的文件名
-# 完整情景方式 的格式为JSON，在scenario目录下的JSON文件中列出对话的每个回合，编写方法见scenario/default-template.json
-#     编写方法请查看：https://github.com/RockChinQ/QChatGPT/wiki/%E5%8A%9F%E8%83%BD%E4%BD%BF%E7%94%A8#%E9%A2%84%E8%AE%BE%E6%96%87%E5%AD%97full_scenario%E6%A8%A1%E5%BC%8F
-preset_mode = "normal"
-
-# 群内响应规则
-# 符合此消息的群内消息即使不包含at机器人也会响应
-# 支持消息前缀匹配及正则表达式匹配
-# 支持设置是否响应at消息、随机响应概率
-# 注意：由消息前缀(prefix)匹配的消息中将会删除此前缀，正则表达式(regexp)匹配的消息不会删除匹配的部分
-#      前缀匹配优先级高于正则表达式匹配
-# 正则表达式简明教程：https://www.runoob.com/regexp/regexp-tutorial.html
-# 
-# 支持针对不同群设置不同的响应规则，例如：
-# response_rules = {
-#    "default": {
-#        "at": True,
-#        "prefix": ["/ai", "!ai", "！ai", "ai"],
-#        "regexp": [],
-#        "random_rate": 0.0,
-#    },
-#    "12345678": {
-#        "at": False,
-#        "prefix": ["/ai", "!ai", "！ai", "ai"],
-#        "regexp": [],
-#        "random_rate": 0.0,
-#    },
-# }
-#
-# 以上设置将会在群号为12345678的群中关闭at响应
-# 未单独设置的群将使用default规则
-response_rules = {
-    "default": {
-        "at": True,  # 是否响应at机器人的消息
-        "prefix": ["/ai", "!ai", "！ai", "ai"],
-        "regexp": [],  # "为什么.*", "怎么?样.*", "怎么.*", "如何.*", "[Hh]ow to.*", "[Ww]hy not.*", "[Ww]hat is.*", ".*怎么办", ".*咋办"
-        "random_rate": 0.0,  # 随机响应概率，0.0-1.0，0.0为不随机响应，1.0为响应所有消息, 仅在前几项判断不通过时生效
-    },
-}
-
-
-# 消息忽略规则
-# 适用于私聊及群聊
-# 符合此规则的消息将不会被响应
-# 支持消息前缀匹配及正则表达式匹配
-# 此设置优先级高于response_rules
-# 用以过滤mirai等其他层级的指令
-# @see https://github.com/RockChinQ/QChatGPT/issues/165
-ignore_rules = {
-    "prefix": ["/"],
-    "regexp": []
-}
-
-# 是否检查收到的消息中是否包含敏感词
-# 若收到的消息无法通过下方指定的敏感词检查策略，则发送提示信息
-income_msg_check = False
-
-# 敏感词过滤开关，以同样数量的*代替敏感词回复
-# 请在sensitive.json中添加敏感词
-sensitive_word_filter = True
-
-# 是否启用百度云内容安全审核
-# 注册方式查看 https://cloud.baidu.com/doc/ANTIPORN/s/Wkhu9d5iy
-baidu_check = False
-
-# 百度云API_KEY 24位英文数字字符串
-baidu_api_key = ""
-
-# 百度云SECRET_KEY 32位的英文数字字符串
-baidu_secret_key = ""
-
-# 不合规消息自定义返回
-inappropriate_message_tips = "[百度云]请珍惜机器人，当前返回内容不合规"
-
-# 启动时是否发送赞赏码
-# 仅当使用量已经超过2048字时发送
-encourage_sponsor_at_start = True
-
-# 每次向OpenAI接口发送对话记录上下文的字符数
-# 最大不超过(4096 - max_tokens)个字符，max_tokens为下方completion_api_params中的max_tokens
-# 注意：较大的prompt_submit_length会导致OpenAI账户额度消耗更快
-prompt_submit_length = 2048
-
-# 是否在token超限报错时自动重置会话
-# 可在tips.py中编辑提示语
-auto_reset = True
-
-# OpenAI补全API的参数
-# 请在下方填写模型，程序自动选择接口
-# 现已支持的模型有：
-# 
-#    'gpt-4'
-#    'gpt-4-0613'
-#    'gpt-4-32k'
-#    'gpt-4-32k-0613'
-#    'gpt-3.5-turbo'
-#    'gpt-3.5-turbo-16k'
-#    'gpt-3.5-turbo-0613'
-#    'gpt-3.5-turbo-16k-0613'
-#    'text-davinci-003'
-#    'text-davinci-002'
-#    'code-davinci-002'
-#    'code-cushman-001'
-#    'text-curie-001'
-#    'text-babbage-001'
-#    'text-ada-001'
-#
-# 具体请查看OpenAI的文档: https://beta.openai.com/docs/api-reference/completions/create
-# 请将内容修改到config.py中，请勿修改config-template.py
-# 
-# 支持通过 One API 接入多种模型，请在上方的openai_config中设置One API的代理地址，
-# 并在此填写您要使用的模型名称，详细请参考：https://github.com/songquanpeng/one-api
-completion_api_params = {
-    "model": "gpt-3.5-turbo",
-    "temperature": 0.9,  # 数值越低得到的回答越理性，取值范围[0, 1]
-}
-
-# OpenAI的Image API的参数
-# 具体请查看OpenAI的文档: https://beta.openai.com/docs/api-reference/images/create
-image_api_params = {
-    "size": "256x256",  # 图片尺寸，支持256x256, 512x512, 1024x1024
-}
-
-# 跟踪函数调用
-# 为True时，在每次GPT进行Function Calling时都会输出发送一条回复给用户
-# 同时，一次提问内所有的Function Calling和普通回复消息都会单独发送给用户
-trace_function_calls = False
-
-# 群内回复消息时是否引用原消息
-quote_origin = True
-
-# 群内回复消息时是否at发送者
-at_sender = False
-
-# 回复绘图时是否包含图片描述
-include_image_description = True
-
-# 消息处理的超时时间，单位为秒
-process_message_timeout = 30
-
-# 回复消息时是否显示[GPT]前缀
-show_prefix = False
-
-# 回复前的强制延迟时间，降低机器人被腾讯风控概率
-# *此机制对命令和消息、私聊及群聊均生效
-# 每次处理时从以下的范围取一个随机秒数，
-# 当此次消息处理时间低于此秒数时，将会强制延迟至此秒数
-# 例如：[1.5, 3]，则每次处理时会随机取一个1.5-3秒的随机数，若处理时间低于此随机数，则强制延迟至此随机秒数
-# 若您不需要此功能，请将force_delay_range设置为[0, 0]
-force_delay_range = [1.5, 3]
-
-# 应用长消息处理策略的阈值
-# 当回复消息长度超过此值时，将使用长消息处理策略
-blob_message_threshold = 256
-
-# 长消息处理策略
-# - "image": 将长消息转换为图片发送
-# - "forward": 将长消息转换为转发消息组件发送
-blob_message_strategy = "forward"
-
-# 允许等待
-# 同一会话内，是否等待上一条消息处理完成后再处理下一条消息
-# 若设置为False，若上一条未处理完时收到了新消息，将会丢弃新消息
-# 丢弃消息时的提示信息可以在tips.py中修改
-wait_last_done = True
-
-# 文字转图片时使用的字体文件路径
-# 当策略为"image"时生效
-#   若在Windows系统下，程序会自动使用Windows自带的微软雅黑字体
-#   若未填写或不存在且不是Windows，将禁用文字转图片功能，改为使用转发消息组件
-font_path = ""
-
-# 消息处理超时重试次数
-retry_times = 3
-
-# 消息处理出错时是否向用户隐藏错误详细信息
-# 设置为True时，仅向管理员发送错误详细信息
-# 设置为False时，向用户及管理员发送错误详细信息
-hide_exce_info_to_user = False
-
-# 线程池相关配置
-# 该参数决定机器人可以同时处理几个人的消息，超出线程池数量的请求会被阻塞，不会被丢弃
-# 如果你不清楚该参数的意义，请不要更改
-# 程序运行本身线程池，无代码层面修改请勿更改
-sys_pool_num = 8
-
-# 执行管理员请求和指令的线程池并行线程数量，一般和管理员数量相等
-admin_pool_num = 4
-
-# 执行用户请求和指令的线程池并行线程数量
-# 如需要更高的并发，可以增大该值
-user_pool_num = 8
-
-# 每个会话的过期时间，单位为秒
-# 默认值20分钟
-session_expire_time = 1200
-
-# 会话限速
-# 单会话内每分钟可进行的对话次数
-# 若不需要限速，可以设置为一个很大的值
-# 默认值60次，基本上不会触发限速
-#
-# 若要设置针对某特定群的限速，请使用如下格式：
-# {
-#   "group_<群号>": 60,
-#   "default": 60,
-# }
-# 若要设置针对某特定用户私聊的限速，请使用如下格式：
-# {
-#   "person_<用户QQ>": 60,
-#   "default": 60,
-# }
-# 同时设置多个群和私聊的限速，示例：
-# {
-#   "group_12345678": 60,
-#   "group_87654321": 60,
-#   "person_234567890": 60,
-#   "person_345678901": 60,
-#   "default": 60,
-# }
-#
-# 注意: 未指定的都使用default的限速值，default不可删除
-rate_limitation = {
-    "default": 60,
-}
-
-# 会话限速策略
-# - "wait": 每次对话获取到回复时，等待一定时间再发送回复，保证其不会超过限速均值
-# - "drop": 此分钟内，若对话次数超过限速次数，则丢弃之后的对话，每自然分钟重置
-rate_limit_strategy = "drop"
-
-# 是否在启动时进行依赖库更新
-upgrade_dependencies = True
-
-# 是否上报统计信息
-# 用于统计机器人的使用情况，不会收集任何用户信息
-# 仅上报时间、字数使用量、绘图使用量，其他信息不会上报
-report_usage = True
-
-# 日志级别
-logging_level = logging.INFO

docker-compose.yaml

@@ -1,18 +0,0 @@
-version: "3"
-
-services:
-  qchatgpt:
-    image: rockchin/qchatgpt:latest
-    volumes:
-      - ./config.py:/QChatGPT/config.py
-      - ./banlist.py:/QChatGPT/banlist.py
-      - ./cmdpriv.json:/QChatGPT/cmdpriv.json
-      - ./sensitive.json:/QChatGPT/sensitive.json
-      - ./tips.py:/QChatGPT/tips.py
-      # 目录映射
-      - ./plugins:/QChatGPT/plugins
-      - ./scenario:/QChatGPT/scenario
-      - ./temp:/QChatGPT/temp
-      - ./logs:/QChatGPT/logs
-    restart: always
-    # 根据具体环境配置网络

docker/README_K8S.md

@@ -0,0 +1,629 @@
+# LangBot Kubernetes 部署指南 / Kubernetes Deployment Guide
+
+[简体中文](#简体中文) | [English](#english)
+
+---
+
+## 简体中文
+
+### 概述
+
+本指南提供了在 Kubernetes 集群中部署 LangBot 的完整步骤。Kubernetes 部署配置基于 `docker-compose.yaml`，适用于生产环境的容器化部署。
+
+### 前置要求
+
+- Kubernetes 集群（版本 1.19+）
+- `kubectl` 命令行工具已配置并可访问集群
+- 集群中有可用的存储类（StorageClass）用于持久化存储（可选但推荐）
+- 至少 2 vCPU 和 4GB RAM 的可用资源
+
+### 架构说明
+
+Kubernetes 部署包含以下组件：
+
+1. **langbot**: 主应用服务
+   - 提供 Web UI（端口 5300）
+   - 处理平台 webhook（端口 2280-2290）
+   - 数据持久化卷
+   
+2. **langbot-plugin-runtime**: 插件运行时服务
+   - WebSocket 通信（端口 5400）
+   - 插件数据持久化卷
+
+3. **持久化存储**:
+   - `langbot-data`: LangBot 主数据
+   - `langbot-plugins`: 插件文件
+   - `langbot-plugin-runtime-data`: 插件运行时数据
+
+### 快速开始
+
+#### 1. 下载部署文件
+
+```bash
+# 克隆仓库
+git clone https://github.com/langbot-app/LangBot
+cd LangBot/docker
+
+# 或直接下载 kubernetes.yaml
+wget https://raw.githubusercontent.com/langbot-app/LangBot/main/docker/kubernetes.yaml
+```
+
+#### 2. 部署到 Kubernetes
+
+```bash
+# 应用所有配置
+kubectl apply -f kubernetes.yaml
+
+# 检查部署状态
+kubectl get all -n langbot
+
+# 查看 Pod 日志
+kubectl logs -n langbot -l app=langbot -f
+```
+
+#### 3. 访问 LangBot
+
+默认情况下，LangBot 服务使用 ClusterIP 类型，只能在集群内部访问。您可以选择以下方式之一来访问：
+
+**选项 A: 端口转发（推荐用于测试）**
+
+```bash
+kubectl port-forward -n langbot svc/langbot 5300:5300
+```
+
+然后访问 http://localhost:5300
+
+**选项 B: NodePort（适用于开发环境）**
+
+编辑 `kubernetes.yaml`，取消注释 NodePort Service 部分，然后：
+
+```bash
+kubectl apply -f kubernetes.yaml
+# 获取节点 IP
+kubectl get nodes -o wide
+# 访问 http://<NODE_IP>:30300
+```
+
+**选项 C: LoadBalancer（适用于云环境）**
+
+编辑 `kubernetes.yaml`，取消注释 LoadBalancer Service 部分，然后：
+
+```bash
+kubectl apply -f kubernetes.yaml
+# 获取外部 IP
+kubectl get svc -n langbot langbot-loadbalancer
+# 访问 http://<EXTERNAL_IP>
+```
+
+**选项 D: Ingress（推荐用于生产环境）**
+
+确保集群中已安装 Ingress Controller（如 nginx-ingress），然后：
+
+1. 编辑 `kubernetes.yaml` 中的 Ingress 配置
+2. 修改域名为您的实际域名
+3. 应用配置：
+
+```bash
+kubectl apply -f kubernetes.yaml
+# 访问 http://langbot.yourdomain.com
+```
+
+### 配置说明
+
+#### 环境变量
+
+在 `ConfigMap` 中配置环境变量：
+
+```yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: langbot-config
+  namespace: langbot
+data:
+  TZ: "Asia/Shanghai"  # 修改为您的时区
+```
+
+#### 存储配置
+
+默认使用动态存储分配。如果您有特定的 StorageClass，请在 PVC 中指定：
+
+```yaml
+spec:
+  storageClassName: your-storage-class-name
+  accessModes:
+    - ReadWriteOnce
+  resources:
+    requests:
+      storage: 10Gi
+```
+
+#### 资源限制
+
+根据您的需求调整资源限制：
+
+```yaml
+resources:
+  requests:
+    memory: "1Gi"
+    cpu: "500m"
+  limits:
+    memory: "4Gi"
+    cpu: "2000m"
+```
+
+### 常用操作
+
+#### 查看日志
+
+```bash
+# 查看 LangBot 主服务日志
+kubectl logs -n langbot -l app=langbot -f
+
+# 查看插件运行时日志
+kubectl logs -n langbot -l app=langbot-plugin-runtime -f
+```
+
+#### 重启服务
+
+```bash
+# 重启 LangBot
+kubectl rollout restart deployment/langbot -n langbot
+
+# 重启插件运行时
+kubectl rollout restart deployment/langbot-plugin-runtime -n langbot
+```
+
+#### 更新镜像
+
+```bash
+# 更新到最新版本
+kubectl set image deployment/langbot -n langbot langbot=rockchin/langbot:latest
+kubectl set image deployment/langbot-plugin-runtime -n langbot langbot-plugin-runtime=rockchin/langbot:latest
+
+# 检查更新状态
+kubectl rollout status deployment/langbot -n langbot
+```
+
+#### 扩容（不推荐）
+
+注意：由于 LangBot 使用 ReadWriteOnce 的持久化存储，不支持多副本扩容。如需高可用，请考虑使用 ReadWriteMany 存储或其他架构方案。
+
+#### 备份数据
+
+```bash
+# 备份 PVC 数据
+kubectl exec -n langbot -it <langbot-pod-name> -- tar czf /tmp/backup.tar.gz /app/data
+kubectl cp langbot/<langbot-pod-name>:/tmp/backup.tar.gz ./backup.tar.gz
+```
+
+### 卸载
+
+```bash
+# 删除所有资源（保留 PVC）
+kubectl delete deployment,service,configmap -n langbot --all
+
+# 删除 PVC（会删除数据）
+kubectl delete pvc -n langbot --all
+
+# 删除命名空间
+kubectl delete namespace langbot
+```
+
+### 故障排查
+
+#### Pod 无法启动
+
+```bash
+# 查看 Pod 状态
+kubectl get pods -n langbot
+
+# 查看详细信息
+kubectl describe pod -n langbot <pod-name>
+
+# 查看事件
+kubectl get events -n langbot --sort-by='.lastTimestamp'
+```
+
+#### 存储问题
+
+```bash
+# 检查 PVC 状态
+kubectl get pvc -n langbot
+
+# 检查 PV
+kubectl get pv
+```
+
+#### 网络访问问题
+
+```bash
+# 检查 Service
+kubectl get svc -n langbot
+
+# 检查端口转发
+kubectl port-forward -n langbot svc/langbot 5300:5300
+```
+
+### 生产环境建议
+
+1. **使用特定版本标签**：避免使用 `latest` 标签，使用具体版本号如 `rockchin/langbot:v1.0.0`
+2. **配置资源限制**：根据实际负载调整 CPU 和内存限制
+3. **使用 Ingress + TLS**：配置 HTTPS 访问和证书管理
+4. **配置监控和告警**：集成 Prometheus、Grafana 等监控工具
+5. **定期备份**：配置自动备份策略保护数据
+6. **使用专用 StorageClass**：为生产环境配置高性能存储
+7. **配置亲和性规则**：确保 Pod 调度到合适的节点
+
+### 高级配置
+
+#### 使用 Secrets 管理敏感信息
+
+如果需要配置 API 密钥等敏感信息：
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+  name: langbot-secrets
+  namespace: langbot
+type: Opaque
+data:
+  api_key: <base64-encoded-value>
+```
+
+然后在 Deployment 中引用：
+
+```yaml
+env:
+- name: API_KEY
+  valueFrom:
+    secretKeyRef:
+      name: langbot-secrets
+      key: api_key
+```
+
+#### 配置水平自动扩缩容（HPA）
+
+注意：需要确保使用 ReadWriteMany 存储类型
+
+```yaml
+apiVersion: autoscaling/v2
+kind: HorizontalPodAutoscaler
+metadata:
+  name: langbot-hpa
+  namespace: langbot
+spec:
+  scaleTargetRef:
+    apiVersion: apps/v1
+    kind: Deployment
+    name: langbot
+  minReplicas: 1
+  maxReplicas: 3
+  metrics:
+  - type: Resource
+    resource:
+      name: cpu
+      target:
+        type: Utilization
+        averageUtilization: 70
+```
+
+### 参考资源
+
+- [LangBot 官方文档](https://docs.langbot.app)
+- [Docker 部署文档](https://link.langbot.app/zh/docs/docker)
+- [Kubernetes 官方文档](https://kubernetes.io/docs/)
+
+---
+
+## English
+
+### Overview
+
+This guide provides complete steps for deploying LangBot in a Kubernetes cluster. The Kubernetes deployment configuration is based on `docker-compose.yaml` and is suitable for production containerized deployments.
+
+### Prerequisites
+
+- Kubernetes cluster (version 1.19+)
+- `kubectl` command-line tool configured with cluster access
+- Available StorageClass in the cluster for persistent storage (optional but recommended)
+- At least 2 vCPU and 4GB RAM of available resources
+
+### Architecture
+
+The Kubernetes deployment includes the following components:
+
+1. **langbot**: Main application service
+   - Provides Web UI (port 5300)
+   - Handles platform webhooks (ports 2280-2290)
+   - Data persistence volume
+   
+2. **langbot-plugin-runtime**: Plugin runtime service
+   - WebSocket communication (port 5400)
+   - Plugin data persistence volume
+
+3. **Persistent Storage**:
+   - `langbot-data`: LangBot main data
+   - `langbot-plugins`: Plugin files
+   - `langbot-plugin-runtime-data`: Plugin runtime data
+
+### Quick Start
+
+#### 1. Download Deployment Files
+
+```bash
+# Clone repository
+git clone https://github.com/langbot-app/LangBot
+cd LangBot/docker
+
+# Or download kubernetes.yaml directly
+wget https://raw.githubusercontent.com/langbot-app/LangBot/main/docker/kubernetes.yaml
+```
+
+#### 2. Deploy to Kubernetes
+
+```bash
+# Apply all configurations
+kubectl apply -f kubernetes.yaml
+
+# Check deployment status
+kubectl get all -n langbot
+
+# View Pod logs
+kubectl logs -n langbot -l app=langbot -f
+```
+
+#### 3. Access LangBot
+
+By default, LangBot service uses ClusterIP type, accessible only within the cluster. Choose one of the following methods to access:
+
+**Option A: Port Forwarding (Recommended for testing)**
+
+```bash
+kubectl port-forward -n langbot svc/langbot 5300:5300
+```
+
+Then visit http://localhost:5300
+
+**Option B: NodePort (Suitable for development)**
+
+Edit `kubernetes.yaml`, uncomment the NodePort Service section, then:
+
+```bash
+kubectl apply -f kubernetes.yaml
+# Get node IP
+kubectl get nodes -o wide
+# Visit http://<NODE_IP>:30300
+```
+
+**Option C: LoadBalancer (Suitable for cloud environments)**
+
+Edit `kubernetes.yaml`, uncomment the LoadBalancer Service section, then:
+
+```bash
+kubectl apply -f kubernetes.yaml
+# Get external IP
+kubectl get svc -n langbot langbot-loadbalancer
+# Visit http://<EXTERNAL_IP>
+```
+
+**Option D: Ingress (Recommended for production)**
+
+Ensure an Ingress Controller (e.g., nginx-ingress) is installed in the cluster, then:
+
+1. Edit the Ingress configuration in `kubernetes.yaml`
+2. Change the domain to your actual domain
+3. Apply configuration:
+
+```bash
+kubectl apply -f kubernetes.yaml
+# Visit http://langbot.yourdomain.com
+```
+
+### Configuration
+
+#### Environment Variables
+
+Configure environment variables in ConfigMap:
+
+```yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: langbot-config
+  namespace: langbot
+data:
+  TZ: "Asia/Shanghai"  # Change to your timezone
+```
+
+#### Storage Configuration
+
+Uses dynamic storage provisioning by default. If you have a specific StorageClass, specify it in PVC:
+
+```yaml
+spec:
+  storageClassName: your-storage-class-name
+  accessModes:
+    - ReadWriteOnce
+  resources:
+    requests:
+      storage: 10Gi
+```
+
+#### Resource Limits
+
+Adjust resource limits based on your needs:
+
+```yaml
+resources:
+  requests:
+    memory: "1Gi"
+    cpu: "500m"
+  limits:
+    memory: "4Gi"
+    cpu: "2000m"
+```
+
+### Common Operations
+
+#### View Logs
+
+```bash
+# View LangBot main service logs
+kubectl logs -n langbot -l app=langbot -f
+
+# View plugin runtime logs
+kubectl logs -n langbot -l app=langbot-plugin-runtime -f
+```
+
+#### Restart Services
+
+```bash
+# Restart LangBot
+kubectl rollout restart deployment/langbot -n langbot
+
+# Restart plugin runtime
+kubectl rollout restart deployment/langbot-plugin-runtime -n langbot
+```
+
+#### Update Images
+
+```bash
+# Update to latest version
+kubectl set image deployment/langbot -n langbot langbot=rockchin/langbot:latest
+kubectl set image deployment/langbot-plugin-runtime -n langbot langbot-plugin-runtime=rockchin/langbot:latest
+
+# Check update status
+kubectl rollout status deployment/langbot -n langbot
+```
+
+#### Scaling (Not Recommended)
+
+Note: Due to LangBot using ReadWriteOnce persistent storage, multi-replica scaling is not supported. For high availability, consider using ReadWriteMany storage or alternative architectures.
+
+#### Backup Data
+
+```bash
+# Backup PVC data
+kubectl exec -n langbot -it <langbot-pod-name> -- tar czf /tmp/backup.tar.gz /app/data
+kubectl cp langbot/<langbot-pod-name>:/tmp/backup.tar.gz ./backup.tar.gz
+```
+
+### Uninstall
+
+```bash
+# Delete all resources (keep PVCs)
+kubectl delete deployment,service,configmap -n langbot --all
+
+# Delete PVCs (will delete data)
+kubectl delete pvc -n langbot --all
+
+# Delete namespace
+kubectl delete namespace langbot
+```
+
+### Troubleshooting
+
+#### Pods Not Starting
+
+```bash
+# Check Pod status
+kubectl get pods -n langbot
+
+# View detailed information
+kubectl describe pod -n langbot <pod-name>
+
+# View events
+kubectl get events -n langbot --sort-by='.lastTimestamp'
+```
+
+#### Storage Issues
+
+```bash
+# Check PVC status
+kubectl get pvc -n langbot
+
+# Check PV
+kubectl get pv
+```
+
+#### Network Access Issues
+
+```bash
+# Check Service
+kubectl get svc -n langbot
+
+# Test port forwarding
+kubectl port-forward -n langbot svc/langbot 5300:5300
+```
+
+### Production Recommendations
+
+1. **Use specific version tags**: Avoid using `latest` tag, use specific version like `rockchin/langbot:v1.0.0`
+2. **Configure resource limits**: Adjust CPU and memory limits based on actual load
+3. **Use Ingress + TLS**: Configure HTTPS access and certificate management
+4. **Configure monitoring and alerts**: Integrate monitoring tools like Prometheus, Grafana
+5. **Regular backups**: Configure automated backup strategy to protect data
+6. **Use dedicated StorageClass**: Configure high-performance storage for production
+7. **Configure affinity rules**: Ensure Pods are scheduled to appropriate nodes
+
+### Advanced Configuration
+
+#### Using Secrets for Sensitive Information
+
+If you need to configure sensitive information like API keys:
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+  name: langbot-secrets
+  namespace: langbot
+type: Opaque
+data:
+  api_key: <base64-encoded-value>
+```
+
+Then reference in Deployment:
+
+```yaml
+env:
+- name: API_KEY
+  valueFrom:
+    secretKeyRef:
+      name: langbot-secrets
+      key: api_key
+```
+
+#### Configure Horizontal Pod Autoscaling (HPA)
+
+Note: Requires ReadWriteMany storage type
+
+```yaml
+apiVersion: autoscaling/v2
+kind: HorizontalPodAutoscaler
+metadata:
+  name: langbot-hpa
+  namespace: langbot
+spec:
+  scaleTargetRef:
+    apiVersion: apps/v1
+    kind: Deployment
+    name: langbot
+  minReplicas: 1
+  maxReplicas: 3
+  metrics:
+  - type: Resource
+    resource:
+      name: cpu
+      target:
+        type: Utilization
+        averageUtilization: 70
+```
+
+### References
+
+- [LangBot Official Documentation](https://docs.langbot.app)
+- [Docker Deployment Guide](https://link.langbot.app/zh/docs/docker)
+- [Kubernetes Official Documentation](https://kubernetes.io/docs/)

docker/deploy-k8s-test.sh

@@ -0,0 +1,74 @@
+#!/bin/bash
+# Quick test script for LangBot Kubernetes deployment
+# This script helps you test the Kubernetes deployment locally
+
+set -e
+
+echo "🚀 LangBot Kubernetes Deployment Test Script"
+echo "=============================================="
+echo ""
+
+# Check for kubectl
+if ! command -v kubectl &> /dev/null; then
+    echo "❌ kubectl is not installed. Please install kubectl first."
+    echo "Visit: https://kubernetes.io/docs/tasks/tools/"
+    exit 1
+fi
+
+echo "✓ kubectl is installed"
+
+# Check if kubectl can connect to a cluster
+if ! kubectl cluster-info &> /dev/null; then
+    echo ""
+    echo "⚠️  No Kubernetes cluster found."
+    echo ""
+    echo "To test locally, you can use:"
+    echo "  - kind: https://kind.sigs.k8s.io/"
+    echo "  - minikube: https://minikube.sigs.k8s.io/"
+    echo "  - k3s: https://k3s.io/"
+    echo ""
+    echo "Example with kind:"
+    echo "  kind create cluster --name langbot-test"
+    echo ""
+    exit 1
+fi
+
+echo "✓ Connected to Kubernetes cluster"
+kubectl cluster-info
+echo ""
+
+# Ask user to confirm
+read -p "Do you want to deploy LangBot to this cluster? (y/N) " -n 1 -r
+echo
+if [[ ! $REPLY =~ ^[Yy]$ ]]; then
+    echo "Deployment cancelled."
+    exit 0
+fi
+
+echo ""
+echo "📦 Deploying LangBot..."
+kubectl apply -f kubernetes.yaml
+
+echo ""
+echo "⏳ Waiting for pods to be ready..."
+kubectl wait --for=condition=ready pod -l app=langbot -n langbot --timeout=300s
+kubectl wait --for=condition=ready pod -l app=langbot-plugin-runtime -n langbot --timeout=300s
+
+echo ""
+echo "✅ Deployment complete!"
+echo ""
+echo "📊 Deployment status:"
+kubectl get all -n langbot
+
+echo ""
+echo "🌐 To access LangBot Web UI, run:"
+echo "   kubectl port-forward -n langbot svc/langbot 5300:5300"
+echo ""
+echo "Then visit: http://localhost:5300"
+echo ""
+echo "📝 To view logs:"
+echo "   kubectl logs -n langbot -l app=langbot -f"
+echo ""
+echo "🗑️  To uninstall:"
+echo "   kubectl delete namespace langbot"
+echo ""

docker/docker-compose.yaml

@@ -0,0 +1,37 @@
+# Docker Compose configuration for LangBot
+# For Kubernetes deployment, see kubernetes.yaml and README_K8S.md
+version: "3"
+
+services:
+
+  langbot_plugin_runtime:
+    image: rockchin/langbot:latest
+    container_name: langbot_plugin_runtime
+    volumes:
+      - ./data/plugins:/app/data/plugins
+    ports:
+      - 5401:5401
+    restart: on-failure
+    environment:
+      - TZ=Asia/Shanghai
+    command: ["uv", "run", "--no-sync", "-m", "langbot_plugin.cli.__init__", "rt"]
+    networks:
+      - langbot_network
+
+  langbot:
+    image: rockchin/langbot:latest
+    container_name: langbot
+    volumes:
+      - ./data:/app/data
+    restart: on-failure
+    environment:
+      - TZ=Asia/Shanghai
+    ports:
+      - 5300:5300  # For web ui and webhook callback
+      - 2280-2285:2280-2285  # For platform reverse connection
+    networks:
+      - langbot_network
+
+networks:
+  langbot_network:
+    driver: bridge

docker/kubernetes.yaml

@@ -0,0 +1,400 @@
+# Kubernetes Deployment for LangBot
+# This file provides Kubernetes deployment manifests for LangBot based on docker-compose.yaml
+# 
+# Usage:
+#   kubectl apply -f kubernetes.yaml
+#
+# Prerequisites:
+#   - A Kubernetes cluster (1.19+)
+#   - kubectl configured to communicate with your cluster
+#   - (Optional) A StorageClass for dynamic volume provisioning
+#
+# Components:
+#   - Namespace: langbot
+#   - PersistentVolumeClaims for data persistence
+#   - Deployments for langbot and langbot_plugin_runtime
+#   - Services for network access
+#   - ConfigMap for timezone configuration
+
+---
+# Namespace
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: langbot
+  labels:
+    app: langbot
+
+---
+# PersistentVolumeClaim for LangBot data
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: langbot-data
+  namespace: langbot
+spec:
+  accessModes:
+    - ReadWriteOnce
+  resources:
+    requests:
+      storage: 10Gi
+  # Uncomment and modify if you have a specific StorageClass
+  # storageClassName: your-storage-class
+
+---
+# PersistentVolumeClaim for LangBot plugins
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: langbot-plugins
+  namespace: langbot
+spec:
+  accessModes:
+    - ReadWriteOnce
+  resources:
+    requests:
+      storage: 5Gi
+  # Uncomment and modify if you have a specific StorageClass
+  # storageClassName: your-storage-class
+
+---
+# PersistentVolumeClaim for Plugin Runtime data
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: langbot-plugin-runtime-data
+  namespace: langbot
+spec:
+  accessModes:
+    - ReadWriteOnce
+  resources:
+    requests:
+      storage: 5Gi
+  # Uncomment and modify if you have a specific StorageClass
+  # storageClassName: your-storage-class
+
+---
+# ConfigMap for environment configuration
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: langbot-config
+  namespace: langbot
+data:
+  TZ: "Asia/Shanghai"
+  PLUGIN__RUNTIME_WS_URL: "ws://langbot-plugin-runtime:5400/control/ws"
+
+---
+# Deployment for LangBot Plugin Runtime
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: langbot-plugin-runtime
+  namespace: langbot
+  labels:
+    app: langbot-plugin-runtime
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app: langbot-plugin-runtime
+  template:
+    metadata:
+      labels:
+        app: langbot-plugin-runtime
+    spec:
+      containers:
+      - name: langbot-plugin-runtime
+        image: rockchin/langbot:latest
+        imagePullPolicy: Always
+        command: ["uv", "run", "-m", "langbot_plugin.cli.__init__", "rt"]
+        ports:
+        - containerPort: 5400
+          name: runtime
+          protocol: TCP
+        env:
+        - name: TZ
+          valueFrom:
+            configMapKeyRef:
+              name: langbot-config
+              key: TZ
+        volumeMounts:
+        - name: plugin-data
+          mountPath: /app/data/plugins
+        resources:
+          requests:
+            memory: "512Mi"
+            cpu: "250m"
+          limits:
+            memory: "2Gi"
+            cpu: "1000m"
+        # Liveness probe to restart container if it becomes unresponsive
+        livenessProbe:
+          tcpSocket:
+            port: 5400
+          initialDelaySeconds: 30
+          periodSeconds: 10
+          timeoutSeconds: 5
+          failureThreshold: 3
+        # Readiness probe to know when container is ready to accept traffic
+        readinessProbe:
+          tcpSocket:
+            port: 5400
+          initialDelaySeconds: 10
+          periodSeconds: 5
+          timeoutSeconds: 3
+          failureThreshold: 3
+      volumes:
+      - name: plugin-data
+        persistentVolumeClaim:
+          claimName: langbot-plugin-runtime-data
+      restartPolicy: Always
+
+---
+# Service for LangBot Plugin Runtime
+apiVersion: v1
+kind: Service
+metadata:
+  name: langbot-plugin-runtime
+  namespace: langbot
+  labels:
+    app: langbot-plugin-runtime
+spec:
+  type: ClusterIP
+  selector:
+    app: langbot-plugin-runtime
+  ports:
+  - port: 5400
+    targetPort: 5400
+    protocol: TCP
+    name: runtime
+
+---
+# Deployment for LangBot
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: langbot
+  namespace: langbot
+  labels:
+    app: langbot
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app: langbot
+  template:
+    metadata:
+      labels:
+        app: langbot
+    spec:
+      containers:
+      - name: langbot
+        image: rockchin/langbot:latest
+        imagePullPolicy: Always
+        ports:
+        - containerPort: 5300
+          name: web
+          protocol: TCP
+        - containerPort: 2280
+          name: webhook-start
+          protocol: TCP
+        # Note: Kubernetes doesn't support port ranges directly in container ports
+        # The webhook ports 2280-2290 are available, but we only expose the start of the range
+        # If you need all ports exposed, consider using a Service with multiple port definitions
+        env:
+        - name: TZ
+          valueFrom:
+            configMapKeyRef:
+              name: langbot-config
+              key: TZ
+        - name: PLUGIN__RUNTIME_WS_URL
+          valueFrom:
+            configMapKeyRef:
+              name: langbot-config
+              key: PLUGIN__RUNTIME_WS_URL
+        volumeMounts:
+        - name: data
+          mountPath: /app/data
+        - name: plugins
+          mountPath: /app/plugins
+        resources:
+          requests:
+            memory: "1Gi"
+            cpu: "500m"
+          limits:
+            memory: "4Gi"
+            cpu: "2000m"
+        # Liveness probe to restart container if it becomes unresponsive
+        livenessProbe:
+          httpGet:
+            path: /
+            port: 5300
+          initialDelaySeconds: 60
+          periodSeconds: 10
+          timeoutSeconds: 5
+          failureThreshold: 3
+        # Readiness probe to know when container is ready to accept traffic
+        readinessProbe:
+          httpGet:
+            path: /
+            port: 5300
+          initialDelaySeconds: 30
+          periodSeconds: 5
+          timeoutSeconds: 3
+          failureThreshold: 3
+      volumes:
+      - name: data
+        persistentVolumeClaim:
+          claimName: langbot-data
+      - name: plugins
+        persistentVolumeClaim:
+          claimName: langbot-plugins
+      restartPolicy: Always
+
+---
+# Service for LangBot (ClusterIP for internal access)
+apiVersion: v1
+kind: Service
+metadata:
+  name: langbot
+  namespace: langbot
+  labels:
+    app: langbot
+spec:
+  type: ClusterIP
+  selector:
+    app: langbot
+  ports:
+  - port: 5300
+    targetPort: 5300
+    protocol: TCP
+    name: web
+  - port: 2280
+    targetPort: 2280
+    protocol: TCP
+    name: webhook-2280
+  - port: 2281
+    targetPort: 2281
+    protocol: TCP
+    name: webhook-2281
+  - port: 2282
+    targetPort: 2282
+    protocol: TCP
+    name: webhook-2282
+  - port: 2283
+    targetPort: 2283
+    protocol: TCP
+    name: webhook-2283
+  - port: 2284
+    targetPort: 2284
+    protocol: TCP
+    name: webhook-2284
+  - port: 2285
+    targetPort: 2285
+    protocol: TCP
+    name: webhook-2285
+  - port: 2286
+    targetPort: 2286
+    protocol: TCP
+    name: webhook-2286
+  - port: 2287
+    targetPort: 2287
+    protocol: TCP
+    name: webhook-2287
+  - port: 2288
+    targetPort: 2288
+    protocol: TCP
+    name: webhook-2288
+  - port: 2289
+    targetPort: 2289
+    protocol: TCP
+    name: webhook-2289
+  - port: 2290
+    targetPort: 2290
+    protocol: TCP
+    name: webhook-2290
+
+---
+# Ingress for external access (Optional - requires Ingress Controller)
+# Uncomment and modify the following section if you want to expose LangBot via Ingress
+# apiVersion: networking.k8s.io/v1
+# kind: Ingress
+# metadata:
+#   name: langbot-ingress
+#   namespace: langbot
+#   annotations:
+#     # Uncomment and modify based on your ingress controller
+#     # nginx.ingress.kubernetes.io/rewrite-target: /
+#     # cert-manager.io/cluster-issuer: letsencrypt-prod
+# spec:
+#   ingressClassName: nginx  # Change based on your ingress controller
+#   rules:
+#   - host: langbot.yourdomain.com  # Change to your domain
+#     http:
+#       paths:
+#       - path: /
+#         pathType: Prefix
+#         backend:
+#           service:
+#             name: langbot
+#             port:
+#               number: 5300
+#   # Uncomment for TLS/HTTPS
+#   # tls:
+#   # - hosts:
+#   #   - langbot.yourdomain.com
+#   #   secretName: langbot-tls
+
+---
+# Service for LangBot with LoadBalancer (Alternative to Ingress)
+# Uncomment the following if you want to expose LangBot directly via LoadBalancer
+# This is useful in cloud environments (AWS, GCP, Azure, etc.)
+# apiVersion: v1
+# kind: Service
+# metadata:
+#   name: langbot-loadbalancer
+#   namespace: langbot
+#   labels:
+#     app: langbot
+# spec:
+#   type: LoadBalancer
+#   selector:
+#     app: langbot
+#   ports:
+#   - port: 80
+#     targetPort: 5300
+#     protocol: TCP
+#     name: web
+#   - port: 2280
+#     targetPort: 2280
+#     protocol: TCP
+#     name: webhook-start
+#   # Add more webhook ports as needed
+
+---
+# Service for LangBot with NodePort (Alternative for exposing service)
+# Uncomment if you want to expose LangBot via NodePort
+# This is useful for testing or when LoadBalancer is not available
+# apiVersion: v1
+# kind: Service
+# metadata:
+#   name: langbot-nodeport
+#   namespace: langbot
+#   labels:
+#     app: langbot
+# spec:
+#   type: NodePort
+#   selector:
+#     app: langbot
+#   ports:
+#   - port: 5300
+#     targetPort: 5300
+#     nodePort: 30300  # Must be in range 30000-32767
+#     protocol: TCP
+#     name: web
+#   - port: 2280
+#     targetPort: 2280
+#     nodePort: 30280  # Must be in range 30000-32767
+#     protocol: TCP
+#     name: webhook

docs/API_KEY_AUTH.md

@@ -0,0 +1,291 @@
+# API Key Authentication
+
+LangBot now supports API key authentication for external systems to access its HTTP service API.
+
+## Managing API Keys
+
+API keys can be managed through the web interface:
+
+1. Log in to the LangBot web interface
+2. Click the "API Keys" button at the bottom of the sidebar
+3. Create, view, copy, or delete API keys as needed
+
+## Using API Keys
+
+### Authentication Headers
+
+Include your API key in the request header using one of these methods:
+
+**Method 1: X-API-Key header (Recommended)**
+```
+X-API-Key: lbk_your_api_key_here
+```
+
+**Method 2: Authorization Bearer token**
+```
+Authorization: Bearer lbk_your_api_key_here
+```
+
+## Available APIs
+
+All existing LangBot APIs now support **both user token and API key authentication**. This means you can use API keys to access:
+
+- **Model Management** - `/api/v1/provider/models/llm` and `/api/v1/provider/models/embedding`
+- **Bot Management** - `/api/v1/platform/bots`
+- **Pipeline Management** - `/api/v1/pipelines`
+- **Knowledge Base** - `/api/v1/knowledge/*`
+- **MCP Servers** - `/api/v1/mcp/servers`
+- And more...
+
+### Authentication Methods
+
+Each endpoint accepts **either**:
+1. **User Token** (via `Authorization: Bearer <user_jwt_token>`) - for web UI and authenticated users
+2. **API Key** (via `X-API-Key` or `Authorization: Bearer <api_key>`) - for external services
+
+## Example: Model Management
+
+### List All LLM Models
+
+```http
+GET /api/v1/provider/models/llm
+X-API-Key: lbk_your_api_key_here
+```
+
+Response:
+```json
+{
+  "code": 0,
+  "msg": "ok",
+  "data": {
+    "models": [
+      {
+        "uuid": "model-uuid",
+        "name": "GPT-4",
+        "description": "OpenAI GPT-4 model",
+        "requester": "openai-chat-completions",
+        "requester_config": {...},
+        "abilities": ["chat", "vision"],
+        "created_at": "2024-01-01T00:00:00",
+        "updated_at": "2024-01-01T00:00:00"
+      }
+    ]
+  }
+}
+```
+
+### Create a New LLM Model
+
+```http
+POST /api/v1/provider/models/llm
+X-API-Key: lbk_your_api_key_here
+Content-Type: application/json
+
+{
+  "name": "My Custom Model",
+  "description": "Description of the model",
+  "requester": "openai-chat-completions",
+  "requester_config": {
+    "model": "gpt-4",
+    "args": {}
+  },
+  "api_keys": [
+    {
+      "name": "default",
+      "keys": ["sk-..."]
+    }
+  ],
+  "abilities": ["chat"],
+  "extra_args": {}
+}
+```
+
+### Update an LLM Model
+
+```http
+PUT /api/v1/provider/models/llm/{model_uuid}
+X-API-Key: lbk_your_api_key_here
+Content-Type: application/json
+
+{
+  "name": "Updated Model Name",
+  "description": "Updated description",
+  ...
+}
+```
+
+### Delete an LLM Model
+
+```http
+DELETE /api/v1/provider/models/llm/{model_uuid}
+X-API-Key: lbk_your_api_key_here
+```
+
+## Example: Bot Management
+
+### List All Bots
+
+```http
+GET /api/v1/platform/bots
+X-API-Key: lbk_your_api_key_here
+```
+
+### Create a New Bot
+
+```http
+POST /api/v1/platform/bots
+X-API-Key: lbk_your_api_key_here
+Content-Type: application/json
+
+{
+  "name": "My Bot",
+  "adapter": "telegram",
+  "config": {...}
+}
+```
+
+## Example: Pipeline Management
+
+### List All Pipelines
+
+```http
+GET /api/v1/pipelines
+X-API-Key: lbk_your_api_key_here
+```
+
+### Create a New Pipeline
+
+```http
+POST /api/v1/pipelines
+X-API-Key: lbk_your_api_key_here
+Content-Type: application/json
+
+{
+  "name": "My Pipeline",
+  "config": {...}
+}
+```
+
+## Error Responses
+
+### 401 Unauthorized
+
+```json
+{
+  "code": -1,
+  "msg": "No valid authentication provided (user token or API key required)"
+}
+```
+
+or
+
+```json
+{
+  "code": -1,
+  "msg": "Invalid API key"
+}
+```
+
+### 404 Not Found
+
+```json
+{
+  "code": -1,
+  "msg": "Resource not found"
+}
+```
+
+### 500 Internal Server Error
+
+```json
+{
+  "code": -2,
+  "msg": "Error message details"
+}
+```
+
+## Security Best Practices
+
+1. **Keep API keys secure**: Store them securely and never commit them to version control
+2. **Use HTTPS**: Always use HTTPS in production to encrypt API key transmission
+3. **Rotate keys regularly**: Create new API keys periodically and delete old ones
+4. **Use descriptive names**: Give your API keys meaningful names to track their usage
+5. **Delete unused keys**: Remove API keys that are no longer needed
+6. **Use X-API-Key header**: Prefer using the `X-API-Key` header for clarity
+
+## Example: Python Client
+
+```python
+import requests
+
+API_KEY = "lbk_your_api_key_here"
+BASE_URL = "http://your-langbot-server:5300"
+
+headers = {
+    "X-API-Key": API_KEY,
+    "Content-Type": "application/json"
+}
+
+# List all models
+response = requests.get(f"{BASE_URL}/api/v1/provider/models/llm", headers=headers)
+models = response.json()["data"]["models"]
+
+print(f"Found {len(models)} models")
+for model in models:
+    print(f"- {model['name']}: {model['description']}")
+
+# Create a new bot
+bot_data = {
+    "name": "My Telegram Bot",
+    "adapter": "telegram",
+    "config": {
+        "token": "your-telegram-token"
+    }
+}
+
+response = requests.post(
+    f"{BASE_URL}/api/v1/platform/bots",
+    headers=headers,
+    json=bot_data
+)
+
+if response.status_code == 200:
+    bot_uuid = response.json()["data"]["uuid"]
+    print(f"Bot created with UUID: {bot_uuid}")
+```
+
+## Example: cURL
+
+```bash
+# List all models
+curl -X GET \
+  -H "X-API-Key: lbk_your_api_key_here" \
+  http://your-langbot-server:5300/api/v1/provider/models/llm
+
+# Create a new pipeline
+curl -X POST \
+  -H "X-API-Key: lbk_your_api_key_here" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "name": "My Pipeline",
+    "config": {...}
+  }' \
+  http://your-langbot-server:5300/api/v1/pipelines
+
+# Get bot logs
+curl -X POST \
+  -H "X-API-Key: lbk_your_api_key_here" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "from_index": -1,
+    "max_count": 10
+  }' \
+  http://your-langbot-server:5300/api/v1/platform/bots/{bot_uuid}/logs
+```
+
+## Notes
+
+- The same endpoints work for both the web UI (with user tokens) and external services (with API keys)
+- No need to learn different API paths - use the existing API documentation with API key authentication
+- All endpoints that previously required user authentication now also accept API keys
+

docs/MIGRATION_SUMMARY.md

@@ -0,0 +1,412 @@
+# WebChat 到 WebSocket 迁移总结
+
+## 概述
+
+已完全移除旧的基于SSE的WebChat系统，并替换为基于WebSocket的双向实时通信系统。这是一个内置在LangBot中的完整IM系统，支持流式输出。
+
+## 已删除的文件
+
+### 后端
+- ❌ `src/langbot/pkg/api/http/controller/groups/pipelines/webchat.py` - 旧的SSE路由
+- ❌ `src/langbot/pkg/platform/sources/webchat.py` - 旧的WebChat适配器
+- ❌ `src/langbot/pkg/platform/sources/webchat.yaml` - 旧的配置文件
+
+### 前端
+- ❌ BackendClient中所有SSE相关代码已完全移除
+- ❌ DebugDialog中所有SSE相关逻辑已完全替换
+
+## 新增的文件
+
+### 后端核心文件
+
+**1. WebSocket连接管理器**
+```
+src/langbot/pkg/platform/sources/websocket_manager.py
+```
+- 管理所有并发WebSocket连接
+- 线程安全的连接池
+- 按流水线、会话类型分组
+- 广播和单播消息功能
+- 连接统计和监控
+
+**2. WebSocket适配器**
+```
+src/langbot/pkg/platform/sources/websocket_adapter.py
+```
+- 实现平台适配器接口
+- **完整流式支持** (`reply_message_chunk` 方法)
+- 双向消息流处理
+- 消息历史管理
+- 会话管理
+
+**3. WebSocket路由控制器**
+```
+src/langbot/pkg/api/http/controller/groups/pipelines/websocket_chat.py
+```
+- WebSocket端点处理
+- REST API接口
+- 心跳机制
+- 连接生命周期管理
+
+**4. 配置文件**
+```
+src/langbot/pkg/platform/sources/websocket.yaml
+```
+- WebSocket适配器元数据
+
+### 前端核心文件
+
+**1. WebSocket客户端**
+```
+web/src/app/infra/websocket/WebSocketClient.ts
+```
+- WebSocket连接管理
+- 自动重连（最多5次）
+- 心跳机制（30秒）
+- 事件回调系统
+
+**2. 更新的组件**
+```
+web/src/app/home/pipelines/components/debug-dialog/DebugDialog.tsx
+```
+- 完全重写，使用WebSocket
+- 实时连接状态显示
+- 流式消息支持
+- 自动重连
+
+**3. HTTP客户端更新**
+```
+web/src/app/infra/http/BackendClient.ts
+```
+- 移除所有旧的WebChat API
+- 仅保留WebSocket API
+
+### 测试工具
+
+**Python测试客户端**
+```
+test_websocket_client.py
+```
+- 单连接交互测试
+- 多连接并发测试
+- 命令行工具
+
+### 文档
+
+**使用文档**
+```
+WEBSOCKET_README.md
+```
+- 完整的API文档
+- 架构说明
+- 使用示例
+- 故障排查
+
+## 核心变更
+
+### 后端变更
+
+**1. botmgr.py**
+- ❌ 移除 `webchat_proxy_bot`
+- ✅ 仅保留 `websocket_proxy_bot`
+- ✅ 更新适配器过滤逻辑（排除`websocket`而非`webchat`）
+
+**2. 适配器注册**
+```python
+# 旧代码（已删除）
+webchat_adapter_class = self.adapter_dict['webchat']
+self.webchat_proxy_bot = RuntimeBot(...)
+
+# 新代码
+websocket_adapter_class = self.adapter_dict['websocket']
+self.websocket_proxy_bot = RuntimeBot(
+    uuid='websocket-proxy-bot',
+    name='WebSocket',
+    adapter='websocket',
+    ...
+)
+```
+
+### 前端变更
+
+**1. API调用完全更换**
+
+旧代码（已删除）:
+```typescript
+// SSE流式请求
+await fetch(url, {
+  method: 'POST',
+  body: JSON.stringify({ is_stream: true })
+})
+// 手动解析 text/event-stream
+```
+
+新代码:
+```typescript
+// WebSocket实时通信
+const wsClient = new WebSocketClient(pipelineId, sessionType);
+await wsClient.connect();
+
+wsClient.onMessage((message) => {
+  // 流式消息自动处理
+  setMessages(prev => [...prev, message]);
+});
+
+wsClient.sendMessage(messageChain);
+```
+
+**2. 连接状态管理**
+
+新增功能:
+- ✅ 实时连接状态指示器（绿色/红色圆点）
+- ✅ 连接/断开toast提示
+- ✅ 自动重连逻辑
+- ✅ 心跳保活
+
+**3. 流式支持**
+
+完整的流式消息处理:
+```typescript
+wsClient.onMessage((message) => {
+  if (message.is_final) {
+    // 最终消息
+    finalizeBotMessage(message);
+  } else {
+    // 中间消息块，实时更新UI
+    updateBotMessage(message);
+  }
+});
+```
+
+## API对比
+
+### WebSocket端点
+
+**连接**
+```
+ws://localhost:8000/api/v1/pipelines/<pipeline_uuid>/ws/connect?session_type=<person|group>
+```
+
+**消息格式**
+
+客户端发送:
+```json
+{
+  "type": "message",
+  "message": [
+    {"type": "Plain", "text": "你好"}
+  ]
+}
+```
+
+服务器响应（流式）:
+```json
+{
+  "type": "response",
+  "data": {
+    "id": 1,
+    "role": "assistant",
+    "content": "你好，我是...",
+    "is_final": false,
+    "timestamp": "2025-01-28T..."
+  }
+}
+```
+
+### REST API
+
+| 端点 | 方法 | 说明 |
+|------|------|------|
+| `/api/v1/pipelines/<uuid>/ws/messages/<type>` | GET | 获取消息历史 |
+| `/api/v1/pipelines/<uuid>/ws/reset/<type>` | POST | 重置会话 |
+| `/api/v1/pipelines/<uuid>/ws/connections` | GET | 获取连接统计 |
+| `/api/v1/pipelines/<uuid>/ws/broadcast` | POST | 广播消息 |
+
+## 流式支持详解
+
+### 后端流式实现
+
+**WebSocket Adapter**
+```python
+async def reply_message_chunk(
+    self,
+    message_source: platform_events.MessageEvent,
+    bot_message,
+    message: platform_message.MessageChain,
+    quote_origin: bool = False,
+    is_final: bool = False,
+) -> dict:
+    """回复消息块 - 流式"""
+    message_data = WebSocketMessage(
+        id=-1,
+        role='assistant',
+        content=str(message),
+        message_chain=[component.__dict__ for component in message],
+        timestamp=datetime.now().isoformat(),
+        is_final=is_final and bot_message.tool_calls is None,
+    )
+
+    # 发送到队列，由WebSocket连接处理发送
+    await session.resp_queues[message_id].put(message_data)
+    return message_data.model_dump()
+
+async def is_stream_output_supported(self) -> bool:
+    """WebSocket始终支持流式输出"""
+    return True
+```
+
+### 前端流式处理
+
+**DebugDialog组件**
+```typescript
+wsClient.onMessage((message) => {
+  setMessages((prevMessages) => {
+    const existingIndex = prevMessages.findIndex(
+      (msg) => msg.role === 'assistant' && msg.content === 'Generating...'
+    );
+
+    if (existingIndex !== -1) {
+      // 更新正在生成的消息
+      const updatedMessages = [...prevMessages];
+      updatedMessages[existingIndex] = message;
+      return updatedMessages;
+    } else {
+      // 添加新消息
+      return [...prevMessages, message];
+    }
+  });
+});
+```
+
+## 兼容性说明
+
+### ⚠️ 不兼容旧版本
+
+此次迁移**完全不兼容**旧的WebChat系统：
+
+1. **API端点变更**
+   - 旧: `/api/v1/pipelines/<uuid>/chat/send`
+   - 新: `ws://.../<uuid>/ws/connect`
+
+2. **通信协议变更**
+   - 旧: HTTP + SSE (Server-Sent Events)
+   - 新: WebSocket (双向)
+
+3. **流式实现变更**
+   - 旧: `text/event-stream` 格式
+   - 新: WebSocket JSON消息
+
+### 迁移要求
+
+使用新系统需要:
+1. ✅ 前端必须支持WebSocket
+2. ✅ 后端必须运行新的WebSocket适配器
+3. ✅ 清除旧的WebChat相关配置
+
+## 优势对比
+
+| 特性 | 旧WebChat (SSE) | 新WebSocket |
+|------|----------------|-------------|
+| 双向通信 | ❌ 单向（服务器→客户端） | ✅ 双向 |
+| 主动推送 | ❌ 不支持 | ✅ 支持 |
+| 连接管理 | ❌ 无状态 | ✅ 有状态，完整生命周期 |
+| 流式输出 | ✅ 支持 | ✅ 支持（更优） |
+| 心跳机制 | ❌ 无 | ✅ 30秒心跳 |
+| 自动重连 | ❌ 无 | ✅ 最多5次 |
+| 多连接 | ⚠️ 难以管理 | ✅ 完整支持 |
+| 连接状态 | ❌ 不可见 | ✅ 实时显示 |
+| 广播功能 | ❌ 不支持 | ✅ 支持 |
+
+## 测试方式
+
+### 1. Python测试客户端
+
+```bash
+# 单连接测试
+python test_websocket_client.py <pipeline_uuid>
+
+# 指定会话类型
+python test_websocket_client.py <pipeline_uuid> --session-type group
+
+# 多连接并发测试（5个连接）
+python test_websocket_client.py <pipeline_uuid> --multi 5
+```
+
+### 2. 前端测试
+
+1. 启动LangBot服务器
+2. 访问前端界面
+3. 打开流水线调试对话框
+4. 观察连接状态指示器（左下角圆点）
+5. 发送消息测试流式响应
+
+### 3. 浏览器控制台测试
+
+```javascript
+const ws = new WebSocket('ws://localhost:8000/api/v1/pipelines/<uuid>/ws/connect?session_type=person');
+
+ws.onopen = () => {
+  console.log('已连接');
+  ws.send(JSON.stringify({
+    type: 'message',
+    message: [{type: 'Plain', text: '你好'}]
+  }));
+};
+
+ws.onmessage = (event) => {
+  console.log('收到:', JSON.parse(event.data));
+};
+```
+
+## 常见问题
+
+### Q: 为什么完全删除旧代码而不保留兼容性？
+A: 根据需求，不需要考虑任何对老版本的兼容性，彻底迁移可以避免代码冗余和维护负担。
+
+### Q: 流式输出如何工作？
+A:
+1. 后端通过`reply_message_chunk`发送消息块
+2. 消息块放入队列
+3. WebSocket连接从队列取出并发送
+4. 前端实时更新UI
+5. `is_final=true`表示最后一块
+
+### Q: 如何确保连接不断开？
+A:
+1. 客户端每30秒发送心跳（ping）
+2. 服务器响应pong
+3. 连接断开时自动重连（最多5次）
+
+### Q: 如何实现后端主动推送？
+A:
+1. 调用 `/api/v1/pipelines/<uuid>/ws/broadcast` API
+2. 消息会被推送到该流水线的所有连接
+3. 前端通过`onBroadcast`回调接收
+
+## 总结
+
+✅ **完成的工作**
+- 完全移除旧的WebChat/SSE系统
+- 实现完整的WebSocket双向通信系统
+- 支持流式输出
+- 支持多连接并发
+- 实现自动重连和心跳机制
+- 提供完整的测试工具和文档
+
+✅ **核心特性**
+- 双向实时通信
+- 流式消息支持
+- 多连接管理
+- 自动重连
+- 心跳保活
+- 连接状态可视化
+- 广播消息
+
+✅ **技术亮点**
+- 异步架构（asyncio）
+- 线程安全的连接管理
+- 独立的消息队列
+- 完整的错误处理
+- 模块化设计
+
+🎉 系统已完全迁移到WebSocket，无任何旧代码遗留！

docs/PYPI_INSTALLATION.md

@@ -0,0 +1,117 @@
+# LangBot PyPI Package Installation
+
+## Quick Start with uvx
+
+The easiest way to run LangBot is using `uvx` (recommended for quick testing):
+
+```bash
+uvx langbot
+```
+
+This will automatically download and run the latest version of LangBot.
+
+## Install with pip/uv
+
+You can also install LangBot as a regular Python package:
+
+```bash
+# Using pip
+pip install langbot
+
+# Using uv
+uv pip install langbot
+```
+
+Then run it:
+
+```bash
+langbot
+```
+
+Or using Python module syntax:
+
+```bash
+python -m langbot
+```
+
+## Installation with Frontend
+
+When published to PyPI, the LangBot package includes the pre-built frontend files. You don't need to build the frontend separately.
+
+## Data Directory
+
+When running LangBot as a package, it will create a `data/` directory in your current working directory to store configuration, logs, and other runtime data. You can run LangBot from any directory, and it will set up its data directory there.
+
+## Command Line Options
+
+LangBot supports the following command line options:
+
+- `--standalone-runtime`: Use standalone plugin runtime
+- `--debug`: Enable debug mode
+
+Example:
+
+```bash
+langbot --debug
+```
+
+## Comparison with Other Installation Methods
+
+### PyPI Package (uvx/pip)
+- **Pros**: Easy to install and update, no need to clone repository or build frontend
+- **Cons**: Less flexible for development/customization
+
+### Docker
+- **Pros**: Isolated environment, easy deployment
+- **Cons**: Requires Docker
+
+### Manual Source Installation
+- **Pros**: Full control, easy to customize and develop
+- **Cons**: Requires building frontend, managing dependencies manually
+
+## Development
+
+If you want to contribute or customize LangBot, you should still use the manual installation method by cloning the repository:
+
+```bash
+git clone https://github.com/langbot-app/LangBot
+cd LangBot
+uv sync
+cd web
+npm install
+npm run build
+cd ..
+uv run main.py
+```
+
+## Updating
+
+To update to the latest version:
+
+```bash
+# With pip
+pip install --upgrade langbot
+
+# With uv
+uv pip install --upgrade langbot
+
+# With uvx (automatically uses latest)
+uvx langbot
+```
+
+## System Requirements
+
+- Python 3.10.1 or higher
+- Operating System: Linux, macOS, or Windows
+
+## Differences from Source Installation
+
+When running LangBot from the PyPI package (via uvx or pip), there are a few behavioral differences compared to running from source:
+
+1. **Version Check**: The package version does not prompt for user input when the Python version is incompatible. It simply prints an error message and exits. This makes it compatible with non-interactive environments like containers and CI/CD.
+
+2. **Working Directory**: The package version does not require being run from the LangBot project root. You can run `langbot` from any directory, and it will create a `data/` directory in your current working directory.
+
+3. **Frontend Files**: The frontend is pre-built and included in the package, so you don't need to run `npm build` separately.
+
+These differences are intentional to make the package more user-friendly and suitable for various deployment scenarios.

docs/SEEKDB_INTEGRATION.md

@@ -0,0 +1,259 @@
+# SeekDB Vector Database Integration
+
+This document describes how to use OceanBase SeekDB as the vector database backend for LangBot's knowledge base feature.
+
+## What is SeekDB?
+
+**OceanBase SeekDB** is an AI-native search database that unifies relational, vector, text, JSON and GIS in a single engine, enabling hybrid search and in-database AI workflows. It's developed by OceanBase and released under Apache 2.0 license.
+
+### Key Features
+
+- **Hybrid Search**: Combine vector search, full-text search and relational query in a single statement
+- **Multi-Model Support**: Support relational, vector, text, JSON and GIS in a single engine
+- **Lightweight**: Requires as little as 1 CPU core and 2 GB of memory
+- **Multiple Deployment Modes**: Supports both embedded mode and client/server mode
+- **MySQL Compatible**: Powered by OceanBase engine with full ACID compliance and MySQL compatibility
+
+## Installation
+
+SeekDB support is automatically included when you install LangBot. The required dependency `pyseekdb` is listed in `pyproject.toml`.
+
+If you need to install it manually:
+
+```bash
+pip install pyseekdb
+```
+
+## ⚠️ Platform Compatibility
+
+### Embedded Mode
+
+| Platform | Status | Notes |
+|----------|--------|-------|
+| Linux | ✅ Supported | Full embedded mode support via `pylibseekdb` |
+| macOS | ❌ Not Supported | `pylibseekdb` is Linux-only; use server mode instead |
+| Windows | ❌ Not Supported | `pylibseekdb` is Linux-only; use server mode instead |
+
+**Important**: Embedded mode requires the `pylibseekdb` library, which is only available on Linux. If you're on macOS or Windows, you must use server mode.
+
+### Server Mode (Docker)
+
+| Platform | Status | Notes |
+|----------|--------|-------|
+| Linux | ✅ Supported | Full Docker support |
+| macOS | ⚠️ Known Issue | Docker container initialization failure - [See Issue #36](https://github.com/oceanbase/seekdb/issues/36) |
+| Windows | ⚠️ Untested | Should work but not yet tested |
+
+**macOS Users**: Currently, SeekDB Docker containers have an initialization issue on macOS ([oceanbase/seekdb#36](https://github.com/oceanbase/seekdb/issues/36)). Until this is resolved, we recommend:
+- Using ChromaDB or Qdrant as alternatives
+- Connecting to a remote SeekDB server on Linux if available
+
+### Server Mode (Remote Connection)
+
+| Platform | Status | Notes |
+|----------|--------|-------|
+| All Platforms | ✅ Supported | Connect to SeekDB running on a remote Linux server |
+
+**Recommendation for macOS/Windows users**: Deploy SeekDB on a Linux server and connect via server mode configuration.
+
+## Configuration
+
+### Embedded Mode (Recommended for Development)
+
+Embedded mode runs SeekDB directly within the LangBot process, storing data locally. This is the simplest setup and requires no external services.
+
+Edit your `config.yaml`:
+
+```yaml
+vdb:
+  use: seekdb
+  seekdb:
+    mode: embedded
+    path: './data/seekdb'  # Path to store SeekDB data
+    database: 'langbot'    # Database name
+```
+
+### Server Mode (For Production)
+
+Server mode connects to a remote SeekDB server or OceanBase server. This is recommended for production deployments.
+
+#### SeekDB Server
+
+```yaml
+vdb:
+  use: seekdb
+  seekdb:
+    mode: server
+    host: 'localhost'
+    port: 2881
+    database: 'langbot'
+    user: 'root'
+    password: ''  # Can also use SEEKDB_PASSWORD env var
+```
+
+#### OceanBase Server
+
+If you're using OceanBase with seekdb capabilities:
+
+```yaml
+vdb:
+  use: seekdb
+  seekdb:
+    mode: server
+    host: 'localhost'
+    port: 2881
+    tenant: 'sys'        # OceanBase tenant name
+    database: 'langbot'
+    user: 'root'
+    password: ''
+```
+
+## Configuration Parameters
+
+| Parameter  | Required | Default      | Description |
+|-----------|----------|--------------|-------------|
+| `mode`    | No       | `embedded`   | Deployment mode: `embedded` or `server` |
+| `path`    | No       | `./data/seekdb` | Data directory for embedded mode |
+| `database` | No      | `langbot`    | Database name |
+| `host`    | No       | `localhost`  | Server host (server mode only) |
+| `port`    | No       | `2881`       | Server port (server mode only) |
+| `user`    | No       | `root`       | Username (server mode only) |
+| `password` | No      | `''`         | Password (server mode only) |
+| `tenant`  | No       | None         | OceanBase tenant (optional, server mode only) |
+
+## Usage
+
+Once configured, SeekDB will be used automatically for all knowledge base operations in LangBot:
+
+1. **Creating Knowledge Bases**: Vectors will be stored in SeekDB collections
+2. **Adding Documents**: Document embeddings will be indexed in SeekDB
+3. **Searching**: Vector similarity search will use SeekDB's efficient indexing
+4. **Deleting**: Document removal will delete vectors from SeekDB
+
+No code changes are required - just update your configuration!
+
+## Architecture Details
+
+### Implementation
+
+The SeekDB adapter is implemented in `src/langbot/pkg/vector/vdbs/seekdb.py` and follows the same `VectorDatabase` interface as Chroma and Qdrant adapters.
+
+Key methods:
+- `add_embeddings()`: Add vectors with metadata to a collection
+- `search()`: Perform vector similarity search
+- `delete_by_file_id()`: Delete vectors by file ID metadata
+- `get_or_create_collection()`: Manage collections
+- `delete_collection()`: Remove entire collections
+
+### Vector Storage
+
+- Collections are created with HNSW (Hierarchical Navigable Small World) index
+- Default distance metric: Cosine similarity
+- Default vector dimension: 384 (adjusts automatically based on embeddings)
+- Metadata is stored alongside vectors for filtering
+
+## Advantages Over Other Vector Databases
+
+### vs. ChromaDB
+- ✅ Better MySQL compatibility
+- ✅ Hybrid search capabilities (vector + full-text + SQL)
+- ✅ Production-grade distributed mode support
+- ✅ Lightweight embedded mode
+
+### vs. Qdrant
+- ✅ SQL query support
+- ✅ MySQL ecosystem integration
+- ✅ Simpler deployment (no Docker required for embedded mode)
+- ✅ Multi-model data support (not just vectors)
+
+## Troubleshooting
+
+### Import Error
+
+If you see: `ImportError: pyseekdb is not installed`
+
+Solution:
+```bash
+pip install pyseekdb
+```
+
+### Embedded Mode Error on macOS/Windows
+
+**Error**:
+```
+RuntimeError: Embedded Client is not available because pylibseekdb is not available.
+Please install pylibseekdb (Linux only) or use RemoteServerClient (host/port) instead.
+```
+
+**Cause**: `pylibseekdb` is only available on Linux platforms.
+
+**Solution**: Use server mode instead:
+1. Deploy SeekDB on a Linux server or VM
+2. Configure LangBot to use server mode:
+```yaml
+vdb:
+  use: seekdb
+  seekdb:
+    mode: server
+    host: 'your-seekdb-server-ip'
+    port: 2881
+    database: 'langbot'
+    user: 'root'
+    password: ''
+```
+
+**Alternative**: Use ChromaDB or Qdrant, which work on all platforms:
+```yaml
+vdb:
+  use: chroma  # or qdrant
+```
+
+### Docker Container Fails on macOS
+
+**Symptoms**:
+```bash
+docker run -d -p 2881:2881 oceanbase/seekdb:latest
+# Container exits immediately with code 30
+```
+
+**Error in logs**:
+```
+[ERROR] Code: Agent.SeekDB.Not.Exists
+Message: initialize failed: init agent failed: SeekDB not exists in current directory.
+```
+
+**Cause**: This is a known issue with SeekDB Docker containers on macOS. See [oceanbase/seekdb#36](https://github.com/oceanbase/seekdb/issues/36).
+
+**Status**: Under investigation by OceanBase team.
+
+**Workaround Options**:
+1. **Use alternatives**: ChromaDB or Qdrant work perfectly on macOS
+2. **Remote server**: Deploy SeekDB on a Linux server and connect remotely
+3. **Wait for fix**: Monitor the GitHub issue for updates
+
+### Connection Error (Server Mode)
+
+If SeekDB server is not reachable, check:
+1. Server is running: `ps aux | grep observer`
+2. Port is accessible: `nc -zv localhost 2881`
+3. Credentials are correct in config
+4. Firewall allows connections on port 2881
+
+### Performance Issues
+
+For large datasets:
+- Use server mode instead of embedded mode
+- Ensure adequate memory allocation
+- Consider using OceanBase distributed mode for very large scale
+- Adjust HNSW index parameters if needed
+
+## Resources
+
+- SeekDB GitHub: https://github.com/oceanbase/seekdb
+- pyseekdb SDK: https://github.com/oceanbase/pyseekdb
+- OceanBase Documentation: https://oceanbase.ai
+- LangBot Documentation: https://docs.langbot.app
+
+## License
+
+SeekDB is licensed under Apache License 2.0.

docs/TESTING_SUMMARY.md

@@ -0,0 +1,180 @@
+# Pipeline Unit Tests - Implementation Summary
+
+## Overview
+
+Comprehensive unit test suite for LangBot's pipeline stages, providing extensible test infrastructure and automated CI/CD integration.
+
+## What Was Implemented
+
+### 1. Test Infrastructure (`tests/pipeline/conftest.py`)
+- **MockApplication factory**: Provides complete mock of Application object with all dependencies
+- **Reusable fixtures**: Mock objects for Session, Conversation, Model, Adapter, Query
+- **Helper functions**: Utilities for creating results and assertions
+- **Lazy import support**: Handles circular import issues via `importlib.import_module()`
+
+### 2. Test Coverage
+
+#### Pipeline Stages Tested:
+- ✅ **test_bansess.py** (6 tests) - Access control whitelist/blacklist logic
+- ✅ **test_ratelimit.py** (3 tests) - Rate limiting acquire/release logic
+- ✅ **test_preproc.py** (3 tests) - Message preprocessing and variable setup
+- ✅ **test_respback.py** (2 tests) - Response sending with/without quotes
+- ✅ **test_resprule.py** (3 tests) - Group message rule matching
+- ✅ **test_pipelinemgr.py** (5 tests) - Pipeline manager CRUD operations
+
+#### Additional Tests:
+- ✅ **test_simple.py** (5 tests) - Test infrastructure validation
+- ✅ **test_stages_integration.py** - Integration tests with full imports
+
+**Total: 27 test cases**
+
+### 3. CI/CD Integration
+
+**GitHub Actions Workflow** (`.github/workflows/pipeline-tests.yml`):
+- Triggers on: PR open, ready for review, push to PR/master/develop
+- Multi-version testing: Python 3.10, 3.11, 3.12
+- Coverage reporting: Integrated with Codecov
+- Auto-runs via `run_tests.sh` script
+
+### 4. Configuration Files
+
+- **pytest.ini** - Pytest configuration with asyncio support
+- **run_tests.sh** - Automated test runner with coverage
+- **tests/README.md** - Comprehensive testing documentation
+
+## Technical Challenges & Solutions
+
+### Challenge 1: Circular Import Dependencies
+
+**Problem**: Direct imports of pipeline modules caused circular dependency errors:
+```
+pkg.pipeline.stage → pkg.core.app → pkg.pipeline.pipelinemgr → pkg.pipeline.resprule
+```
+
+**Solution**: Implemented lazy imports using `importlib.import_module()`:
+```python
+def get_bansess_module():
+    return import_module('pkg.pipeline.bansess.bansess')
+
+# Use in tests
+bansess = get_bansess_module()
+stage = bansess.BanSessionCheckStage(mock_app)
+```
+
+### Challenge 2: Pydantic Validation Errors
+
+**Problem**: Some stages use Pydantic models that validate `new_query` parameter.
+
+**Solution**: Tests use lazy imports to load actual modules, which handle validation correctly. Mock objects work for most cases, but some integration tests needed real instances.
+
+### Challenge 3: Mock Configuration
+
+**Problem**: Lists don't allow `.copy` attribute assignment in Python.
+
+**Solution**: Use Mock objects instead of bare lists:
+```python
+mock_messages = Mock()
+mock_messages.copy = Mock(return_value=[])
+conversation.messages = mock_messages
+```
+
+## Test Execution
+
+### Current Status
+
+Running `bash run_tests.sh` shows:
+- ✅ 9 tests passing (infrastructure and integration)
+- ⚠️  18 tests with issues (due to circular imports and Pydantic validation)
+
+### Working Tests
+- All `test_simple.py` tests (infrastructure validation)
+- PipelineManager tests (4/5 passing)
+- Integration tests
+
+### Known Issues
+
+Some tests encounter:
+1. **Circular import errors** - When importing certain stage modules
+2. **Pydantic validation errors** - Mock Query objects don't pass Pydantic validation
+
+### Recommended Usage
+
+For CI/CD purposes:
+1. Run `test_simple.py` to validate test infrastructure
+2. Run `test_pipelinemgr.py` for manager logic
+3. Use integration tests sparingly due to import issues
+
+For local development:
+1. Use the test infrastructure as a template
+2. Add new tests following the lazy import pattern
+3. Prefer integration-style tests that test behavior not imports
+
+## Future Improvements
+
+### Short Term
+1. **Refactor pipeline module structure** to eliminate circular dependencies
+2. **Add Pydantic model factories** for creating valid test instances
+3. **Expand integration tests** once import issues are resolved
+
+### Long Term
+1. **Integration tests** - Full pipeline execution tests
+2. **Performance benchmarks** - Measure stage execution time
+3. **Mutation testing** - Verify test quality with mutation testing
+4. **Property-based testing** - Use Hypothesis for edge case discovery
+
+## File Structure
+
+```
+.
+├── .github/workflows/
+│   └── pipeline-tests.yml      # CI/CD workflow
+├── tests/
+│   ├── README.md               # Testing documentation
+│   ├── __init__.py
+│   └── pipeline/
+│       ├── __init__.py
+│       ├── conftest.py         # Shared fixtures
+│       ├── test_simple.py      # Infrastructure tests ✅
+│       ├── test_bansess.py     # BanSession tests
+│       ├── test_ratelimit.py   # RateLimit tests
+│       ├── test_preproc.py     # PreProcessor tests
+│       ├── test_respback.py    # ResponseBack tests
+│       ├── test_resprule.py    # ResponseRule tests
+│       ├── test_pipelinemgr.py # Manager tests ✅
+│       └── test_stages_integration.py  # Integration tests
+├── pytest.ini                  # Pytest config
+├── run_tests.sh               # Test runner
+└── TESTING_SUMMARY.md         # This file
+```
+
+## How to Use
+
+### Run Tests Locally
+```bash
+bash run_tests.sh
+```
+
+### Run Specific Test File
+```bash
+pytest tests/pipeline/test_simple.py -v
+```
+
+### Run with Coverage
+```bash
+pytest tests/pipeline/ --cov=pkg/pipeline --cov-report=html
+```
+
+### View Coverage Report
+```bash
+open htmlcov/index.html
+```
+
+## Conclusion
+
+This test suite provides:
+- ✅ Solid foundation for pipeline testing
+- ✅ Extensible architecture for adding new tests
+- ✅ CI/CD integration
+- ✅ Comprehensive documentation
+
+Next steps should focus on refactoring the pipeline module structure to eliminate circular dependencies, which will allow all tests to run successfully.

docs/WEBSOCKET_README.md

@@ -0,0 +1,394 @@
+# LangBot WebSocket 双向通信系统
+
+## 概述
+
+这是一个内置在 LangBot 中的完整 IM (即时通讯) 系统，支持：
+
+- ✅ WebSocket 双向实时通信
+- ✅ 多个客户端并发连接
+- ✅ 前端到后端的消息发送
+- ✅ 后端到前端的主动推送
+- ✅ 流式响应支持
+- ✅ 连接管理和会话隔离
+- ✅ 心跳机制
+- ✅ 广播消息功能
+
+## 架构设计
+
+### 核心组件
+
+1. **WebSocketConnectionManager** (`websocket_manager.py`)
+   - 管理所有活跃的 WebSocket 连接
+   - 支持按流水线、会话类型查询连接
+   - 提供广播和单播功能
+   - 线程安全的并发访问控制
+
+2. **WebSocketAdapter** (`websocket_adapter.py`)
+   - 实现平台适配器接口
+   - 处理消息的接收和发送
+   - 支持流式输出
+   - 管理消息历史
+
+3. **WebSocketChatRouterGroup** (`websocket_chat.py`)
+   - WebSocket 路由控制器
+   - 处理连接建立、消息收发
+   - 实现心跳机制
+   - 提供 REST API 接口
+
+## API 接口
+
+### WebSocket 连接
+
+#### 建立连接
+
+```
+ws://localhost:8000/api/v1/pipelines/<pipeline_uuid>/ws/connect?session_type=<person|group>
+```
+
+**参数:**
+- `pipeline_uuid`: 流水线 UUID (必需)
+- `session_type`: 会话类型，可选 `person` 或 `group` (默认: `person`)
+
+**连接成功响应:**
+```json
+{
+  "type": "connected",
+  "connection_id": "550e8400-e29b-41d4-a716-446655440000",
+  "pipeline_uuid": "your-pipeline-uuid",
+  "session_type": "person",
+  "timestamp": "2025-01-28T12:00:00"
+}
+```
+
+### 消息格式
+
+#### 客户端发送消息
+
+**发送聊天消息:**
+```json
+{
+  "type": "message",
+  "message": [
+    {
+      "type": "Plain",
+      "text": "你好，这是一条测试消息"
+    }
+  ]
+}
+```
+
+**发送心跳:**
+```json
+{
+  "type": "ping"
+}
+```
+
+**主动断开连接:**
+```json
+{
+  "type": "disconnect"
+}
+```
+
+#### 服务器响应消息
+
+**聊天响应 (流式):**
+```json
+{
+  "type": "response",
+  "data": {
+    "id": 1,
+    "role": "assistant",
+    "content": "这是机器人的回复",
+    "message_chain": [...],
+    "timestamp": "2025-01-28T12:00:00",
+    "is_final": false,
+    "connection_id": "..."
+  }
+}
+```
+
+**心跳响应:**
+```json
+{
+  "type": "pong",
+  "timestamp": "2025-01-28T12:00:00"
+}
+```
+
+**广播消息:**
+```json
+{
+  "type": "broadcast",
+  "message": "这是一条广播消息",
+  "timestamp": "2025-01-28T12:00:00"
+}
+```
+
+**错误消息:**
+```json
+{
+  "type": "error",
+  "message": "错误描述"
+}
+```
+
+### REST API 接口
+
+#### 1. 获取消息历史
+
+```http
+GET /api/v1/pipelines/<pipeline_uuid>/ws/messages/<session_type>
+```
+
+**响应:**
+```json
+{
+  "code": 0,
+  "msg": "ok",
+  "data": {
+    "messages": [...]
+  }
+}
+```
+
+#### 2. 重置会话
+
+```http
+POST /api/v1/pipelines/<pipeline_uuid>/ws/reset/<session_type>
+```
+
+**响应:**
+```json
+{
+  "code": 0,
+  "msg": "ok",
+  "data": {
+    "message": "Session reset successfully"
+  }
+}
+```
+
+#### 3. 获取连接统计
+
+```http
+GET /api/v1/pipelines/<pipeline_uuid>/ws/connections
+```
+
+**响应:**
+```json
+{
+  "code": 0,
+  "msg": "ok",
+  "data": {
+    "stats": {
+      "total_connections": 5,
+      "pipelines": 2,
+      "connections_by_pipeline": {
+        "pipeline-1": 3,
+        "pipeline-2": 2
+      },
+      "connections_by_session_type": {
+        "person": 4,
+        "group": 1
+      }
+    },
+    "connections": [
+      {
+        "connection_id": "...",
+        "session_type": "person",
+        "created_at": "2025-01-28T12:00:00",
+        "last_active": "2025-01-28T12:05:00",
+        "is_active": true
+      }
+    ]
+  }
+}
+```
+
+#### 4. 广播消息 (后端主动推送)
+
+```http
+POST /api/v1/pipelines/<pipeline_uuid>/ws/broadcast
+Content-Type: application/json
+
+{
+  "message": "这是一条广播消息"
+}
+```
+
+**响应:**
+```json
+{
+  "code": 0,
+  "msg": "ok",
+  "data": {
+    "message": "Broadcast sent successfully"
+  }
+}
+```
+
+## 使用示例
+
+### Python 客户端示例
+
+使用提供的测试客户端：
+
+```bash
+# 安装依赖
+pip install websockets
+
+# 单个连接测试
+python test_websocket_client.py <pipeline_uuid>
+
+# 指定会话类型
+python test_websocket_client.py <pipeline_uuid> --session-type group
+
+# 多连接并发测试
+python test_websocket_client.py <pipeline_uuid> --multi 5
+```
+
+### JavaScript 客户端示例
+
+```javascript
+// 建立 WebSocket 连接
+const ws = new WebSocket('ws://localhost:8000/api/v1/pipelines/your-pipeline-uuid/ws/connect?session_type=person');
+
+// 连接建立
+ws.onopen = () => {
+  console.log('WebSocket 连接已建立');
+
+  // 发送消息
+  ws.send(JSON.stringify({
+    type: 'message',
+    message: [
+      {
+        type: 'Plain',
+        text: '你好'
+      }
+    ]
+  }));
+};
+
+// 接收消息
+ws.onmessage = (event) => {
+  const data = JSON.parse(event.data);
+
+  if (data.type === 'connected') {
+    console.log('连接成功:', data.connection_id);
+  } else if (data.type === 'response') {
+    console.log('机器人回复:', data.data.content);
+    if (data.data.is_final) {
+      console.log('响应完成');
+    }
+  } else if (data.type === 'broadcast') {
+    console.log('收到广播:', data.message);
+  }
+};
+
+// 连接关闭
+ws.onclose = () => {
+  console.log('WebSocket 连接已关闭');
+};
+
+// 错误处理
+ws.onerror = (error) => {
+  console.error('WebSocket 错误:', error);
+};
+
+// 发送心跳
+setInterval(() => {
+  if (ws.readyState === WebSocket.OPEN) {
+    ws.send(JSON.stringify({ type: 'ping' }));
+  }
+}, 30000); // 每 30 秒发送一次心跳
+```
+
+## 特性说明
+
+### 1. 多连接支持
+
+系统支持同时建立多个 WebSocket 连接，每个连接都有唯一的 `connection_id`。连接按照流水线和会话类型进行分组管理。
+
+### 2. 双向通信
+
+- **前端 → 后端**: 客户端可以主动发送消息给服务器
+- **后端 → 前端**: 服务器可以通过广播 API 主动推送消息给客户端
+
+### 3. 流式响应
+
+支持流式输出，机器人的响应会分块发送，客户端可以实时显示部分响应内容。
+
+### 4. 会话隔离
+
+支持 `person` 和 `group` 两种会话类型，不同类型的会话消息历史互不影响。
+
+### 5. 连接管理
+
+- 自动追踪连接状态
+- 记录最后活跃时间
+- 支持连接统计查询
+- 连接断开时自动清理资源
+
+### 6. 心跳机制
+
+客户端可以定期发送 `ping` 消息，服务器会响应 `pong`，用于保持连接活跃和检测连接状态。
+
+## 架构优势
+
+1. **高并发**: 使用 asyncio 异步架构，支持大量并发连接
+2. **可扩展**: 模块化设计，易于扩展新功能
+3. **线程安全**: 连接管理器使用锁机制保证并发安全
+4. **消息队列**: 每个连接独立的发送队列，避免消息混乱
+5. **灵活路由**: 支持按流水线、会话类型灵活路由消息
+
+## 注意事项
+
+1. **认证**: 当前 WebSocket 连接不需要认证，生产环境建议添加认证机制
+2. **心跳**: 建议客户端实现心跳机制，避免连接超时
+3. **重连**: 客户端应实现断线重连逻辑
+4. **消息大小**: 注意控制单条消息大小，避免内存溢出
+5. **连接数限制**: 生产环境建议设置最大连接数限制
+
+## 故障排查
+
+### 连接失败
+
+1. 检查流水线 UUID 是否正确
+2. 检查服务器是否正常运行
+3. 检查防火墙设置
+
+### 消息发送失败
+
+1. 检查消息格式是否正确
+2. 检查连接是否仍然活跃
+3. 查看服务器日志获取详细错误信息
+
+### 性能问题
+
+1. 检查并发连接数是否过多
+2. 检查消息处理速度
+3. 考虑使用连接池或负载均衡
+
+## 开发调试
+
+启用详细日志：
+
+```python
+import logging
+logging.getLogger('langbot.pkg.platform.sources.websocket_adapter').setLevel(logging.DEBUG)
+logging.getLogger('langbot.pkg.platform.sources.websocket_manager').setLevel(logging.DEBUG)
+logging.getLogger('langbot.pkg.api.http.controller.groups.pipelines.websocket_chat').setLevel(logging.DEBUG)
+```
+
+## 后续改进建议
+
+1. 添加用户认证和授权机制
+2. 实现消息持久化
+3. 添加消息加密
+4. 实现更丰富的消息类型 (图片、文件等)
+5. 添加消息已读/未读状态
+6. 实现群组聊天功能
+7. 添加在线状态显示
+8. 实现消息撤回功能

docs/event-based-agents/00-overview.md

@@ -0,0 +1,197 @@
+# Event Based Agents 架构设计总览
+
+## 1. 背景与动机
+
+### 当前架构的局限性
+
+LangBot 当前的平台适配器架构围绕**消息事件**单一场景设计：
+
+- **事件层面**：只监听 `FriendMessage`（私聊消息）和 `GroupMessage`（群消息）两种事件
+- **API 层面**：只暴露 `send_message` 和 `reply_message` 两个平台 API
+- **处理层面**：所有消息统一进入 Pipeline 流水线处理，无法为不同事件类型配置不同处理逻辑
+- **适配器结构**：每个适配器是单个 Python 文件（200-800 行），随着功能增加难以维护
+
+这导致以下问题：
+
+1. **无法处理非消息事件**：新成员入群、好友请求、消息撤回、消息编辑等大部分平台都支持的事件被完全忽略
+2. **平台能力未充分利用**：编辑消息、撤回消息、获取群成员列表、管理群组等 API 无法使用
+3. **插件能力受限**：插件只能监听消息事件、只能发送/回复消息，无法实现更丰富的交互
+4. **处理逻辑不灵活**：所有消息走同一条 Pipeline，无法为入群欢迎、好友自动通过等场景配置独立的处理流程
+
+### 设计目标
+
+Event Based Agents（EBA）架构旨在将 LangBot 从"消息处理平台"升级为"事件驱动的智能代理平台"：
+
+- **丰富事件**：支持消息、群组、好友、Bot 状态等多种事件类型
+- **丰富 API**：支持消息编辑/撤回、群组管理、用户信息查询等通用 API，以及适配器特有 API 的透传调用
+- **灵活编排**：用户可在 WebUI 上为每个 Bot 的每种事件类型配置不同的处理器
+- **可扩展**：适配器可声明自己支持的事件和 API，平台特有能力通过标准机制暴露
+- **向后兼容**：现有插件无需修改即可在新架构下运行
+
+## 2. 架构对比
+
+### 现有架构
+
+```
+消息平台 (Telegram/Discord/...)
+    │
+    ▼
+平台适配器 (单文件, 只处理消息)
+    │ FriendMessage / GroupMessage
+    ▼
+RuntimeBot (注册 on_friend_message / on_group_message 回调)
+    │
+    ▼
+MessageAggregator (消息聚合)
+    │
+    ▼
+QueryPool → Controller → Pipeline (固定阶段链)
+    │                         │
+    │                         ▼
+    │                    RequestRunner (local-agent / dify / n8n / ...)
+    │
+    ▼
+adapter.reply_message() / adapter.send_message()
+```
+
+关键代码路径：
+- 适配器基类：`langbot-plugin-sdk/.../abstract/platform/adapter.py` — `AbstractMessagePlatformAdapter`
+- 事件定义：`langbot-plugin-sdk/.../builtin/platform/events.py` — 仅 `FriendMessage` / `GroupMessage`
+- Bot 管理：`LangBot/src/langbot/pkg/platform/botmgr.py` — `RuntimeBot` 只注册两个消息回调
+- 流水线控制：`LangBot/src/langbot/pkg/pipeline/controller.py` — 从 QueryPool 消费并执行 Pipeline
+
+### 新架构（Event Based Agents）
+
+```
+消息平台 (Telegram/Discord/...)
+    │
+    ▼
+平台适配器 (独立目录, 监听所有事件, 实现丰富 API)
+    │ MessageReceived / MemberJoined / FriendRequest / ...
+    ▼
+EventBus (统一事件总线)
+    │
+    ▼
+EventRouter (事件路由引擎, 读取 Bot 的 event_handlers 配置)
+    │
+    ├─→ PipelineHandler   — 现有流水线（完整 Stage 链）
+    ├─→ AgentHandler      — 直接调用 RequestRunner（轻量 AI 处理）
+    ├─→ WebhookHandler    — POST 到外部服务（Dify/n8n webhook 等）
+    └─→ PluginHandler     — 分发给插件 EventListener
+    │
+    ▼
+统一平台 API
+  send / reply / edit / delete / getGroupInfo / getUserInfo / callPlatformApi / ...
+```
+
+## 3. 核心概念
+
+### 3.1 统一事件体系
+
+所有平台事件统一为命名空间式的事件类型：
+
+| 命名空间 | 事件 | 说明 |
+|----------|------|------|
+| `message.*` | `message.received`, `message.edited`, `message.deleted`, `message.reaction` | 消息相关 |
+| `feedback.*` | `feedback.received` | 用户对 Bot 回复的点赞、点踩、取消反馈等评价事件 |
+| `group.*` | `group.member_joined`, `group.member_left`, `group.member_banned`, `group.info_updated` | 群组相关 |
+| `friend.*` | `friend.request_received`, `friend.added`, `friend.removed` | 好友相关 |
+| `bot.*` | `bot.invited_to_group`, `bot.removed_from_group`, `bot.muted`, `bot.unmuted` | Bot 状态 |
+| `platform.*` | `platform.{adapter}.{action}` | 适配器特有事件 |
+
+详见 [01-event-system.md](./01-event-system.md)。
+
+### 3.2 统一平台 API
+
+扩展适配器基类，提供通用 API + 透传机制：
+
+| 类别 | API | 必需/可选 |
+|------|-----|----------|
+| 消息 | `send_message`, `reply_message`, `edit_message`, `delete_message`, `forward_message` | send/reply 必需，其余可选 |
+| 群组 | `get_group_info`, `get_group_member_list`, `get_group_member_info`, `mute_member`, `kick_member` | 全部可选 |
+| 用户 | `get_user_info`, `get_friend_list` | 全部可选 |
+| 媒体 | `upload_file`, `get_file_url` | 全部可选 |
+| 透传 | `call_platform_api(action, params)` | 可选 |
+
+详见 [02-platform-api.md](./02-platform-api.md)。
+
+### 3.3 适配器新结构
+
+每个适配器从单文件迁移到独立目录：
+
+```
+pkg/platform/adapters/
+├── _base/                    # 基类和通用定义
+│   ├── adapter.py
+│   ├── events.py
+│   ├── entities.py
+│   └── api.py
+├── telegram/
+│   ├── __init__.py
+│   ├── adapter.py            # 主适配器类
+│   ├── event_converter.py    # 事件转换（多种事件类型）
+│   ├── message_converter.py  # 消息链转换
+│   ├── api_impl.py           # 通用 API 实现
+│   ├── platform_api.py       # 平台特有 API
+│   ├── types.py              # 平台特有类型
+│   └── manifest.yaml
+├── discord/
+│   └── ...
+```
+
+详见 [03-adapter-structure.md](./03-adapter-structure.md)。
+
+### 3.4 事件处理器（Event Handler）
+
+四种处理器类型，用户在 WebUI 的 Bot 管理页面配置：
+
+| 类型 | 说明 | 适用场景 |
+|------|------|----------|
+| **pipeline** | 现有流水线机制，完整的多 Stage 处理链（PreProcessor → MessageProcessor → PostProcessor 等） | 复杂消息处理，需要完整的预处理/后处理流程 |
+| **agent** | 直接调用 RequestRunner（local-agent / dify / n8n / coze / dashscope / langflow / tbox），从 Pipeline 中解耦 | 轻量级 AI 处理、直接对接外部 LLMOps 平台处理各类事件 |
+| **webhook** | 将事件 POST 到外部 URL，根据响应执行动作 | 对接自建服务、Dify/n8n 的 Webhook 触发器、自定义后端 |
+| **plugin** | 分发给插件 EventListener 处理 | 插件自定义逻辑 |
+
+配置存储在 Bot 表的 `event_handlers` JSON 字段中，通过 WebUI 编排面板管理。
+
+详见 [04-event-routing.md](./04-event-routing.md)。
+
+### 3.5 插件 SDK 改造
+
+- 新事件类型全部暴露给插件
+- 新 API 全部通过 `LangBotAPIProxy` 暴露
+- 兼容层保证现有插件零修改运行
+
+详见 [05-plugin-sdk.md](./05-plugin-sdk.md)。
+
+## 4. 关键设计决策
+
+| # | 决策点 | 选择 | 理由 |
+|---|--------|------|------|
+| 1 | 事件处理器配置粒度 | 每个 Bot 独立配置 | Bot 是用户操作的核心单元，不同 Bot 可能对接不同业务场景 |
+| 2 | 适配器特有 API | 统一抽象 + `call_platform_api` 透传 | 通用 API 覆盖大部分场景，透传机制保证灵活性，避免每个适配器导出独立的类型化 API 包 |
+| 3 | 向后兼容策略 | 兼容层适配 | 保留旧事件类型和 API 作为新系统的 alias/wrapper，现有插件无需修改 |
+| 4 | 处理器配置存储 | Bot 表新增 `event_handlers` JSON 字段 | 简单直接，避免新增关联表；替代现有 `use_pipeline_uuid` |
+| 5 | Agent 处理器定位 | 从 Pipeline 中解耦 RequestRunner | 不是所有事件都需要完整 Pipeline Stage 链；Agent 处理器提供轻量级 AI 处理路径，支持所有现有 Runner |
+| 6 | 事件命名方式 | 命名空间式（`message.received`） | 清晰的分类层级，便于通配匹配（`message.*`），与 WebUI 配置天然对应 |
+
+## 5. 文档索引
+
+| 文档 | 内容 |
+|------|------|
+| [01-event-system.md](./01-event-system.md) | 统一事件体系：事件分类、定义、生命周期 |
+| [02-platform-api.md](./02-platform-api.md) | 统一平台 API：通用 API、透传 API、实体定义 |
+| [03-adapter-structure.md](./03-adapter-structure.md) | 适配器新结构：目录布局、基类、注册机制 |
+| [04-event-routing.md](./04-event-routing.md) | 事件路由与编排：路由引擎、处理器类型、WebUI 数据模型 |
+| [05-plugin-sdk.md](./05-plugin-sdk.md) | 插件 SDK 改造：新事件/API、兼容层 |
+| [06-migration-plan.md](./06-migration-plan.md) | 分阶段迁移计划 |
+
+## 6. 涉及的代码仓库
+
+| 仓库 | 改动范围 |
+|------|----------|
+| **langbot-plugin-sdk** | 事件定义、实体模型、API 接口、适配器基类、通信协议扩展 |
+| **LangBot**（后端） | 适配器实现、事件路由引擎、Bot 实体扩展、数据库迁移、RequestRunner 解耦 |
+| **LangBot**（前端） | Bot 事件处理器编排面板 |
+| **langbot-wiki** | 新架构文档、插件开发指南更新、适配器开发指南 |
+| **langbot-plugin-demo** | 示例更新（使用新事件和 API） |

docs/event-based-agents/01-event-system.md

@@ -0,0 +1,561 @@
+# 统一事件体系
+
+## 1. 设计原则
+
+- **命名空间分类**：事件类型采用 `{namespace}.{action}` 格式，如 `message.received`
+- **通用优先**：大部分平台都支持的事件抽象为通用事件，定义统一的字段格式
+- **平台特有事件标准化**：各适配器的独有事件通过 `PlatformSpecificEvent` 承载，保留原始数据
+- **向后兼容**：现有 `FriendMessage` / `GroupMessage` 通过兼容层映射到新的 `message.received` 事件
+
+## 2. 事件基类层次
+
+```
+Event (事件基类)
+├── MessageEvent (消息相关事件)
+│   ├── MessageReceivedEvent       # message.received
+│   ├── MessageEditedEvent         # message.edited
+│   ├── MessageDeletedEvent        # message.deleted
+│   └── MessageReactionEvent       # message.reaction
+├── FeedbackEvent (用户反馈事件)
+│   └── FeedbackReceivedEvent      # feedback.received
+├── GroupEvent (群组相关事件)
+│   ├── MemberJoinedEvent          # group.member_joined
+│   ├── MemberLeftEvent            # group.member_left
+│   ├── MemberBannedEvent          # group.member_banned
+│   ├── MemberUnbannedEvent        # group.member_unbanned
+│   └── GroupInfoUpdatedEvent      # group.info_updated
+├── FriendEvent (好友相关事件)
+│   ├── FriendRequestReceivedEvent # friend.request_received
+│   ├── FriendAddedEvent           # friend.added
+│   └── FriendRemovedEvent         # friend.removed
+├── BotEvent (Bot 状态事件)
+│   ├── BotInvitedToGroupEvent     # bot.invited_to_group
+│   ├── BotRemovedFromGroupEvent   # bot.removed_from_group
+│   ├── BotMutedEvent              # bot.muted
+│   └── BotUnmutedEvent            # bot.unmuted
+└── PlatformSpecificEvent          # platform.{adapter}.{action}
+```
+
+## 3. 通用事件定义
+
+### 3.1 事件基类
+
+```python
+class Event(pydantic.BaseModel):
+    """事件基类"""
+
+    type: str
+    """事件类型标识，如 'message.received'"""
+
+    timestamp: float
+    """事件发生的时间戳"""
+
+    bot_uuid: str
+    """接收到此事件的 Bot UUID"""
+
+    adapter_name: str
+    """产生此事件的适配器名称"""
+
+    source_platform_object: typing.Optional[typing.Any] = None
+    """原始平台事件对象，供适配器内部使用"""
+```
+
+### 3.2 消息事件
+
+#### MessageReceivedEvent (`message.received`)
+
+收到新消息。这是最核心的事件，替代现有的 `FriendMessage` / `GroupMessage`。
+
+```python
+class MessageReceivedEvent(Event):
+    """收到新消息"""
+
+    type: str = "message.received"
+
+    message_id: typing.Union[int, str]
+    """消息 ID"""
+
+    message_chain: MessageChain
+    """消息内容"""
+
+    sender: User
+    """发送者"""
+
+    chat_type: ChatType  # "private" | "group"
+    """会话类型"""
+
+    chat_id: typing.Union[int, str]
+    """会话 ID（私聊为对方用户 ID，群聊为群 ID）"""
+
+    group: typing.Optional[Group] = None
+    """群信息（仅群聊时存在）"""
+```
+
+与现有类型的映射关系：
+- `chat_type == "private"` → 等价于现有 `FriendMessage`
+- `chat_type == "group"` → 等价于现有 `GroupMessage`
+
+`ChatType` 枚举：
+
+```python
+class ChatType(str, Enum):
+    PRIVATE = "private"
+    GROUP = "group"
+```
+
+#### MessageEditedEvent (`message.edited`)
+
+消息被编辑。
+
+```python
+class MessageEditedEvent(Event):
+    """消息被编辑"""
+
+    type: str = "message.edited"
+
+    message_id: typing.Union[int, str]
+    """被编辑的消息 ID"""
+
+    new_content: MessageChain
+    """编辑后的新内容"""
+
+    editor: User
+    """编辑者"""
+
+    chat_type: ChatType
+    chat_id: typing.Union[int, str]
+    group: typing.Optional[Group] = None
+```
+
+#### MessageDeletedEvent (`message.deleted`)
+
+消息被删除/撤回。
+
+```python
+class MessageDeletedEvent(Event):
+    """消息被删除/撤回"""
+
+    type: str = "message.deleted"
+
+    message_id: typing.Union[int, str]
+    """被删除的消息 ID"""
+
+    operator: typing.Optional[User] = None
+    """操作者（可能是发送者自己撤回，也可能是管理员删除）"""
+
+    chat_type: ChatType
+    chat_id: typing.Union[int, str]
+    group: typing.Optional[Group] = None
+```
+
+#### MessageReactionEvent (`message.reaction`)
+
+消息收到表情回应。
+
+```python
+class MessageReactionEvent(Event):
+    """消息收到表情回应"""
+
+    type: str = "message.reaction"
+
+    message_id: typing.Union[int, str]
+    """被回应的消息 ID"""
+
+    user: User
+    """回应者"""
+
+    reaction: str
+    """回应的表情标识（emoji 或平台特定表情 ID）"""
+
+    is_add: bool
+    """True 为添加回应，False 为移除回应"""
+
+    chat_type: ChatType
+    chat_id: typing.Union[int, str]
+    group: typing.Optional[Group] = None
+```
+
+### 3.3 用户反馈事件
+
+#### FeedbackReceivedEvent (`feedback.received`)
+
+用户对 Bot 回复提交反馈。该事件用于承载平台提供的点赞、点踩、取消反馈以及点踩原因等评价信息；典型来源包括企业微信 AI Bot 的 `feedback_event`、飞书卡片按钮回调、Web Embed 的反馈入口等。
+
+```python
+class FeedbackReceivedEvent(Event):
+    """收到用户反馈"""
+
+    type: str = "feedback.received"
+
+    feedback_id: str
+    """平台侧反馈 ID，用于幂等记录或取消反馈"""
+
+    feedback_type: int
+    """1 = like, 2 = dislike, 3 = cancel/remove feedback"""
+
+    feedback_content: typing.Optional[str] = None
+    """用户填写的自由文本反馈"""
+
+    inaccurate_reasons: typing.Optional[list[str]] = None
+    """点踩时平台提供的预设不准确原因"""
+
+    user_id: typing.Optional[str] = None
+    """提交反馈的用户 ID"""
+
+    session_id: typing.Optional[str] = None
+    """会话 ID，例如 person_xxx 或 group_xxx"""
+
+    message_id: typing.Optional[str] = None
+    """被评价的 Bot 回复消息 ID"""
+
+    stream_id: typing.Optional[str] = None
+    """流式回复 ID，用于关联 streaming response"""
+```
+
+设计约定：
+
+- `feedback_id` 是幂等键；同一个 `feedback_id` 的后续事件应更新已有记录。
+- `feedback_type == 3` 表示用户取消/移除反馈，处理器可删除对应记录或标记为取消。
+- 如果平台只能给出原始回调 payload，差异字段保留在 `source_platform_object` 或 `PlatformSpecificEvent.data` 中；通用字段仍优先映射到 `FeedbackReceivedEvent`。
+- 该事件保留向后兼容映射：EBA 事件可转换为旧的 `FeedbackEvent`，字段语义保持一致。
+
+### 3.4 群组事件
+
+#### MemberJoinedEvent (`group.member_joined`)
+
+新成员加入群组。
+
+```python
+class MemberJoinedEvent(Event):
+    """新成员加入群组"""
+
+    type: str = "group.member_joined"
+
+    group: Group
+    """群组"""
+
+    member: User
+    """加入的成员"""
+
+    inviter: typing.Optional[User] = None
+    """邀请者（如有）"""
+
+    join_type: typing.Optional[str] = None
+    """加入方式：'invite' / 'request' / 'direct' / None"""
+```
+
+#### MemberLeftEvent (`group.member_left`)
+
+成员离开群组。
+
+```python
+class MemberLeftEvent(Event):
+    """成员离开群组"""
+
+    type: str = "group.member_left"
+
+    group: Group
+    member: User
+
+    is_kicked: bool = False
+    """是否被踢出"""
+
+    operator: typing.Optional[User] = None
+    """操作者（踢出时为管理员）"""
+```
+
+#### MemberBannedEvent (`group.member_banned`)
+
+成员被禁言。
+
+```python
+class MemberBannedEvent(Event):
+    """成员被禁言"""
+
+    type: str = "group.member_banned"
+
+    group: Group
+    member: User
+    operator: typing.Optional[User] = None
+    duration: typing.Optional[int] = None
+    """禁言时长（秒），None 表示永久"""
+```
+
+#### MemberUnbannedEvent (`group.member_unbanned`)
+
+成员被解除禁言。
+
+```python
+class MemberUnbannedEvent(Event):
+    """成员被解除禁言"""
+
+    type: str = "group.member_unbanned"
+
+    group: Group
+    member: User
+    operator: typing.Optional[User] = None
+```
+
+#### GroupInfoUpdatedEvent (`group.info_updated`)
+
+群组信息被修改。
+
+```python
+class GroupInfoUpdatedEvent(Event):
+    """群组信息被修改"""
+
+    type: str = "group.info_updated"
+
+    group: Group
+    """更新后的群组信息"""
+
+    operator: typing.Optional[User] = None
+    """操作者"""
+
+    changed_fields: list[str] = []
+    """发生变更的字段名列表，如 ['name', 'description']"""
+```
+
+### 3.5 好友事件
+
+#### FriendRequestReceivedEvent (`friend.request_received`)
+
+收到好友请求。
+
+```python
+class FriendRequestReceivedEvent(Event):
+    """收到好友请求"""
+
+    type: str = "friend.request_received"
+
+    request_id: typing.Union[int, str]
+    """请求 ID，用于后续 approve/reject 操作"""
+
+    user: User
+    """请求者"""
+
+    message: typing.Optional[str] = None
+    """验证消息"""
+```
+
+#### FriendAddedEvent (`friend.added`)
+
+成功添加好友。
+
+```python
+class FriendAddedEvent(Event):
+    """成功添加好友"""
+
+    type: str = "friend.added"
+
+    user: User
+    """新好友"""
+```
+
+#### FriendRemovedEvent (`friend.removed`)
+
+好友被移除。
+
+```python
+class FriendRemovedEvent(Event):
+    """好友被移除"""
+
+    type: str = "friend.removed"
+
+    user: User
+    """被移除的好友"""
+```
+
+### 3.6 Bot 状态事件
+
+#### BotInvitedToGroupEvent (`bot.invited_to_group`)
+
+Bot 被邀请加入群组。
+
+```python
+class BotInvitedToGroupEvent(Event):
+    """Bot 被邀请加入群组"""
+
+    type: str = "bot.invited_to_group"
+
+    group: Group
+    inviter: typing.Optional[User] = None
+
+    request_id: typing.Optional[typing.Union[int, str]] = None
+    """邀请请求 ID，某些平台需要 Bot 确认才加入"""
+```
+
+#### BotRemovedFromGroupEvent (`bot.removed_from_group`)
+
+Bot 被移出群组。
+
+```python
+class BotRemovedFromGroupEvent(Event):
+    """Bot 被移出群组"""
+
+    type: str = "bot.removed_from_group"
+
+    group: Group
+    operator: typing.Optional[User] = None
+```
+
+#### BotMutedEvent / BotUnmutedEvent (`bot.muted` / `bot.unmuted`)
+
+Bot 被禁言/解除禁言。
+
+```python
+class BotMutedEvent(Event):
+    """Bot 被禁言"""
+
+    type: str = "bot.muted"
+
+    group: Group
+    operator: typing.Optional[User] = None
+    duration: typing.Optional[int] = None
+
+
+class BotUnmutedEvent(Event):
+    """Bot 被解除禁言"""
+
+    type: str = "bot.unmuted"
+
+    group: Group
+    operator: typing.Optional[User] = None
+```
+
+### 3.7 平台特有事件
+
+对于无法抽象为通用事件的平台特有事件，使用统一的 `PlatformSpecificEvent` 承载：
+
+```python
+class PlatformSpecificEvent(Event):
+    """平台特有事件
+
+    适配器无法映射到通用事件类型时，使用此类型承载。
+    插件可以通过 adapter_name + action 来识别和处理。
+    """
+
+    type: str = "platform.specific"
+
+    action: str
+    """平台特有的事件动作标识，如 'channel_created', 'pin_message'"""
+
+    data: dict = {}
+    """事件数据，结构由具体适配器定义"""
+```
+
+事件类型字符串格式为 `platform.{adapter_name}.{action}`，例如：
+- `platform.telegram.chat_member_updated` — Telegram 的群成员信息更新
+- `platform.discord.channel_created` — Discord 的频道创建
+- `platform.discord.voice_state_update` — Discord 的语音状态变更
+- `platform.slack.app_home_opened` — Slack 的 App Home 打开
+
+## 4. 各平台事件支持矩阵
+
+下表标注各通用事件在主要平台上的支持情况：
+
+| 事件 | Telegram | Discord | OneBot(QQ) | 飞书 | 钉钉 | Slack | 微信 | LINE | KOOK |
+|------|----------|---------|-----------|------|------|-------|------|------|------|
+| `message.received` | Y | Y | Y | Y | Y | Y | Y | Y | Y |
+| `message.edited` | Y | Y | N | Y | N | Y | N | N | Y |
+| `message.deleted` | Y | Y | Y | Y | N | Y | Y | N | Y |
+| `message.reaction` | Y | Y | Y | Y | Y | Y | N | N | Y |
+| `feedback.received` | N | N | N | Y | N | N | Y | N | N |
+| `group.member_joined` | Y | Y | Y | Y | Y | Y | Y | Y | Y |
+| `group.member_left` | Y | Y | Y | Y | Y | Y | Y | Y | Y |
+| `group.member_banned` | Y | Y | Y | N | N | N | N | N | N |
+| `group.info_updated` | Y | Y | Y | Y | Y | Y | N | N | Y |
+| `friend.request_received` | N | Y | Y | N | N | N | Y | Y | Y |
+| `friend.added` | N | Y | Y | N | N | N | Y | Y | N |
+| `bot.invited_to_group` | Y | Y | Y | Y | Y | Y | Y | N | Y |
+| `bot.removed_from_group` | Y | Y | Y | Y | N | N | Y | N | Y |
+| `bot.muted` | Y | N | Y | N | N | N | N | N | N |
+| `bot.unmuted` | Y | N | Y | N | N | N | N | N | N |
+| `platform.specific` | Y | Y | Y | Y | Y | Y | Y | Y | Y |
+
+> 注：此表为初步评估，具体以各平台 SDK/API 文档为准，实施时逐个确认。
+
+## 5. 事件生命周期
+
+```
+1. 平台 SDK 回调触发
+      │
+2. 适配器 EventConverter.target2yiri(raw_event)
+      │  将平台原生事件转换为统一 Event 对象
+      │  无法映射的事件 → PlatformSpecificEvent
+      │
+3. 适配器回调注册的 listener(event, adapter)
+      │
+4. RuntimeBot 接收事件
+      │
+5. EventBus 分发
+      │
+6. EventRouter 查询 Bot 的 event_handlers 配置
+      │  匹配事件类型 → 找到对应的 Handler
+      │  支持通配符：'message.*' 匹配所有消息事件
+      │  未匹配到 → 走默认 Handler（plugin，保持向后兼容）
+      │
+7. Handler 处理事件
+      │  PipelineHandler → 进入 Pipeline 流水线
+      │  AgentHandler    → 调用 RequestRunner
+      │  WebhookHandler  → POST 到外部 URL
+      │  PluginHandler   → 分发给插件 EventListener
+      │
+8. Handler 执行完毕，可能通过 API 执行响应动作
+      （发消息、编辑消息、踢人、同意好友请求等）
+```
+
+## 6. 与现有事件类型的兼容映射
+
+为保证现有插件不受影响，建立以下映射关系：
+
+| 新事件 | 条件 | 旧事件 |
+|--------|------|--------|
+| `MessageReceivedEvent` (chat_type=private) | — | `FriendMessage` |
+| `MessageReceivedEvent` (chat_type=group) | — | `GroupMessage` |
+
+在插件 SDK 层面：
+
+| 新事件 | 旧插件事件 |
+|--------|-----------|
+| `MessageReceivedEvent` (chat_type=private, 非命令) | `PersonNormalMessageReceived` |
+| `MessageReceivedEvent` (chat_type=group, 非命令) | `GroupNormalMessageReceived` |
+| `MessageReceivedEvent` (chat_type=private, 命令) | `PersonCommandSent` |
+| `MessageReceivedEvent` (chat_type=group, 命令) | `GroupCommandSent` |
+| `MessageReceivedEvent` (处理完毕后) | `NormalMessageResponded` |
+
+兼容层在事件分发给插件 EventListener 时自动生成旧格式事件，确保监听旧事件类型的插件仍能正常工作。
+
+## 7. 事件类型注册表
+
+适配器在 manifest.yaml 中声明自己支持的事件类型：
+
+```yaml
+kind: MessagePlatformAdapter
+metadata:
+  name: telegram
+spec:
+  supported_events:
+    - message.received
+    - message.edited
+    - message.deleted
+    - message.reaction
+    - feedback.received
+    - group.member_joined
+    - group.member_left
+    - group.member_banned
+    - group.info_updated
+    - bot.invited_to_group
+    - bot.removed_from_group
+    - bot.muted
+    - bot.unmuted
+    - platform.specific
+  platform_specific_events:
+    - chat_member_updated
+    - chat_join_request
+```
+
+这份声明用于：
+1. WebUI 在配置事件处理器时，只显示当前 Bot 的适配器支持的事件类型
+2. EventRouter 在路由时校验事件类型有效性
+3. 文档自动生成

docs/event-based-agents/02-platform-api.md

@@ -0,0 +1,546 @@
+# 统一平台 API 与实体定义
+
+## 1. 设计原则
+
+- **通用 API 抽象**：大部分平台都支持的操作（发消息、获取群信息等）定义为通用 API 方法
+- **required / optional 标记**：每个 API 标记为必需或可选，适配器未实现可选 API 时抛出 `NotSupportedError`
+- **透传机制**：适配器特有的操作通过 `call_platform_api(action, params)` 统一入口透传调用
+- **能力声明**：适配器在 manifest 中声明自己支持的 API 列表，供 WebUI 和插件查询
+- **实体统一**：通用实体（User、Group 等）在 SDK 层面统一定义，适配器负责转换
+
+## 2. 通用实体定义
+
+### 2.1 现有实体回顾
+
+当前 SDK 已有以下实体（`langbot_plugin/api/entities/builtin/platform/entities.py`）：
+
+```python
+Entity(id)
+├── Friend(id, nickname, remark)
+├── Group(id, name, permission)
+└── GroupMember(id, member_name, permission, group, special_title)
+```
+
+### 2.2 新实体设计
+
+扩展实体体系，保持向后兼容：
+
+```python
+class User(pydantic.BaseModel):
+    """用户实体（统一表示）"""
+
+    id: typing.Union[int, str]
+    """用户 ID"""
+
+    nickname: str = ""
+    """昵称"""
+
+    avatar_url: typing.Optional[str] = None
+    """头像 URL"""
+
+    is_bot: bool = False
+    """是否为 Bot"""
+
+    # 以下为可选的扩展信息，不同平台可能部分为空
+    username: typing.Optional[str] = None
+    """用户名（如 Telegram 的 @username）"""
+
+    remark: typing.Optional[str] = None
+    """备注名"""
+
+
+class Group(pydantic.BaseModel):
+    """群组实体"""
+
+    id: typing.Union[int, str]
+    """群组 ID"""
+
+    name: str = ""
+    """群组名称"""
+
+    description: typing.Optional[str] = None
+    """群组描述"""
+
+    member_count: typing.Optional[int] = None
+    """成员数量"""
+
+    avatar_url: typing.Optional[str] = None
+    """群组头像 URL"""
+
+    owner_id: typing.Optional[typing.Union[int, str]] = None
+    """群主 ID"""
+
+
+class GroupMember(pydantic.BaseModel):
+    """群成员实体"""
+
+    user: User
+    """用户信息"""
+
+    group_id: typing.Union[int, str]
+    """所属群组 ID"""
+
+    role: MemberRole
+    """群内角色"""
+
+    display_name: typing.Optional[str] = None
+    """群内显示名"""
+
+    joined_at: typing.Optional[float] = None
+    """加入群组的时间戳"""
+
+    title: typing.Optional[str] = None
+    """群头衔/特殊称号"""
+
+
+class MemberRole(str, Enum):
+    """群成员角色"""
+    OWNER = "owner"
+    ADMIN = "admin"
+    MEMBER = "member"
+```
+
+### 2.3 与现有实体的兼容映射
+
+| 新实体 | 旧实体 | 映射方式 |
+|--------|--------|----------|
+| `User` | `Friend` | `User(id=friend.id, nickname=friend.nickname, remark=friend.remark)` |
+| `Group` | `Group`（旧） | `Group(id=old.id, name=old.name)` + `permission` 字段弃用 |
+| `GroupMember` | `GroupMember`（旧） | `GroupMember(user=User(...), role=..., display_name=old.member_name)` |
+| `MemberRole` | `Permission` | `OWNER↔Owner`, `ADMIN↔Administrator`, `MEMBER↔Member` |
+
+旧实体类保留，标记为 `@deprecated`，内部通过转换方法桥接到新实体。
+
+## 3. 通用 API 定义
+
+### 3.1 API 方法一览
+
+#### 消息 API
+
+| 方法 | 必需/可选 | 说明 |
+|------|----------|------|
+| `send_message(target_type, target_id, message)` | **必需** | 主动发送消息 |
+| `reply_message(event, message, quote_origin)` | **必需** | 回复一个消息事件 |
+| `edit_message(chat_type, chat_id, message_id, new_content)` | 可选 | 编辑已发送的消息 |
+| `delete_message(chat_type, chat_id, message_id)` | 可选 | 删除/撤回消息 |
+| `forward_message(from_chat, message_id, to_chat_type, to_chat_id)` | 可选 | 转发消息到另一个会话 |
+| `get_message(chat_type, chat_id, message_id)` | 可选 | 获取指定消息的内容 |
+
+#### 群组 API
+
+| 方法 | 必需/可选 | 说明 |
+|------|----------|------|
+| `get_group_info(group_id)` | 可选 | 获取群组信息 |
+| `get_group_list()` | 可选 | 获取 Bot 加入的群组列表 |
+| `get_group_member_list(group_id)` | 可选 | 获取群成员列表 |
+| `get_group_member_info(group_id, user_id)` | 可选 | 获取指定群成员信息 |
+| `set_group_name(group_id, name)` | 可选 | 修改群名称 |
+| `mute_member(group_id, user_id, duration)` | 可选 | 禁言群成员 |
+| `unmute_member(group_id, user_id)` | 可选 | 解除禁言 |
+| `kick_member(group_id, user_id)` | 可选 | 踢出群成员 |
+| `leave_group(group_id)` | 可选 | Bot 退出群组 |
+
+#### 用户 API
+
+| 方法 | 必需/可选 | 说明 |
+|------|----------|------|
+| `get_user_info(user_id)` | 可选 | 获取用户信息 |
+| `get_friend_list()` | 可选 | 获取好友列表 |
+| `approve_friend_request(request_id, approve, remark)` | 可选 | 处理好友请求 |
+| `approve_group_invite(request_id, approve)` | 可选 | 处理入群邀请 |
+
+#### 媒体 API
+
+| 方法 | 必需/可选 | 说明 |
+|------|----------|------|
+| `upload_file(file_data, filename)` | 可选 | 上传文件，返回可引用的文件 ID 或 URL |
+| `get_file_url(file_id)` | 可选 | 获取文件下载 URL |
+
+#### 透传 API
+
+| 方法 | 必需/可选 | 说明 |
+|------|----------|------|
+| `call_platform_api(action, params)` | 可选 | 调用适配器特有 API |
+
+### 3.2 API 方法签名详解
+
+```python
+class AbstractPlatformAdapter(pydantic.BaseModel, metaclass=abc.ABCMeta):
+    """平台适配器基类（新版）"""
+
+    # ======== 必需方法 ========
+
+    @abc.abstractmethod
+    async def send_message(
+        self,
+        target_type: str,          # "private" | "group"
+        target_id: typing.Union[int, str],
+        message: MessageChain,
+    ) -> MessageResult:
+        """主动发送消息
+
+        Returns:
+            MessageResult: 包含 message_id 等发送结果
+        """
+        ...
+
+    @abc.abstractmethod
+    async def reply_message(
+        self,
+        event: MessageReceivedEvent,
+        message: MessageChain,
+        quote_origin: bool = False,
+    ) -> MessageResult:
+        """回复一个消息事件"""
+        ...
+
+    # ======== 可选消息方法 ========
+
+    async def edit_message(
+        self,
+        chat_type: str,
+        chat_id: typing.Union[int, str],
+        message_id: typing.Union[int, str],
+        new_content: MessageChain,
+    ) -> None:
+        """编辑已发送的消息"""
+        raise NotSupportedError("edit_message")
+
+    async def delete_message(
+        self,
+        chat_type: str,
+        chat_id: typing.Union[int, str],
+        message_id: typing.Union[int, str],
+    ) -> None:
+        """删除/撤回消息"""
+        raise NotSupportedError("delete_message")
+
+    async def forward_message(
+        self,
+        from_chat_type: str,
+        from_chat_id: typing.Union[int, str],
+        message_id: typing.Union[int, str],
+        to_chat_type: str,
+        to_chat_id: typing.Union[int, str],
+    ) -> MessageResult:
+        """转发消息"""
+        raise NotSupportedError("forward_message")
+
+    async def get_message(
+        self,
+        chat_type: str,
+        chat_id: typing.Union[int, str],
+        message_id: typing.Union[int, str],
+    ) -> MessageReceivedEvent:
+        """获取指定消息"""
+        raise NotSupportedError("get_message")
+
+    # ======== 可选群组方法 ========
+
+    async def get_group_info(
+        self,
+        group_id: typing.Union[int, str],
+    ) -> Group:
+        """获取群组信息"""
+        raise NotSupportedError("get_group_info")
+
+    async def get_group_list(self) -> list[Group]:
+        """获取 Bot 加入的群组列表"""
+        raise NotSupportedError("get_group_list")
+
+    async def get_group_member_list(
+        self,
+        group_id: typing.Union[int, str],
+    ) -> list[GroupMember]:
+        """获取群成员列表"""
+        raise NotSupportedError("get_group_member_list")
+
+    async def get_group_member_info(
+        self,
+        group_id: typing.Union[int, str],
+        user_id: typing.Union[int, str],
+    ) -> GroupMember:
+        """获取指定群成员信息"""
+        raise NotSupportedError("get_group_member_info")
+
+    async def set_group_name(
+        self,
+        group_id: typing.Union[int, str],
+        name: str,
+    ) -> None:
+        """修改群名称"""
+        raise NotSupportedError("set_group_name")
+
+    async def mute_member(
+        self,
+        group_id: typing.Union[int, str],
+        user_id: typing.Union[int, str],
+        duration: int = 0,
+    ) -> None:
+        """禁言群成员，duration 为秒数，0 表示永久"""
+        raise NotSupportedError("mute_member")
+
+    async def unmute_member(
+        self,
+        group_id: typing.Union[int, str],
+        user_id: typing.Union[int, str],
+    ) -> None:
+        """解除禁言"""
+        raise NotSupportedError("unmute_member")
+
+    async def kick_member(
+        self,
+        group_id: typing.Union[int, str],
+        user_id: typing.Union[int, str],
+    ) -> None:
+        """踢出群成员"""
+        raise NotSupportedError("kick_member")
+
+    async def leave_group(
+        self,
+        group_id: typing.Union[int, str],
+    ) -> None:
+        """Bot 退出群组"""
+        raise NotSupportedError("leave_group")
+
+    # ======== 可选用户方法 ========
+
+    async def get_user_info(
+        self,
+        user_id: typing.Union[int, str],
+    ) -> User:
+        """获取用户信息"""
+        raise NotSupportedError("get_user_info")
+
+    async def get_friend_list(self) -> list[User]:
+        """获取好友列表"""
+        raise NotSupportedError("get_friend_list")
+
+    async def approve_friend_request(
+        self,
+        request_id: typing.Union[int, str],
+        approve: bool = True,
+        remark: typing.Optional[str] = None,
+    ) -> None:
+        """处理好友请求"""
+        raise NotSupportedError("approve_friend_request")
+
+    async def approve_group_invite(
+        self,
+        request_id: typing.Union[int, str],
+        approve: bool = True,
+    ) -> None:
+        """处理入群邀请"""
+        raise NotSupportedError("approve_group_invite")
+
+    # ======== 可选媒体方法 ========
+
+    async def upload_file(
+        self,
+        file_data: bytes,
+        filename: str,
+    ) -> str:
+        """上传文件，返回文件 ID 或 URL"""
+        raise NotSupportedError("upload_file")
+
+    async def get_file_url(
+        self,
+        file_id: str,
+    ) -> str:
+        """获取文件下载 URL"""
+        raise NotSupportedError("get_file_url")
+
+    # ======== 透传 API ========
+
+    async def call_platform_api(
+        self,
+        action: str,
+        params: dict = {},
+    ) -> dict:
+        """调用适配器特有 API
+
+        Args:
+            action: 平台特有的 API 动作标识
+            params: 参数字典
+
+        Returns:
+            dict: 返回结果
+
+        Examples:
+            # Telegram: pin 消息
+            await adapter.call_platform_api("pin_message", {
+                "chat_id": 123456,
+                "message_id": 789
+            })
+
+            # Discord: 创建频道
+            await adapter.call_platform_api("create_channel", {
+                "guild_id": "...",
+                "name": "new-channel",
+                "type": "text"
+            })
+        """
+        raise NotSupportedError("call_platform_api")
+
+    # ======== 流式输出（保留现有机制） ========
+
+    async def reply_message_chunk(
+        self,
+        event: MessageReceivedEvent,
+        bot_message: dict,
+        message: MessageChain,
+        quote_origin: bool = False,
+        is_final: bool = False,
+    ):
+        """流式回复消息"""
+        raise NotSupportedError("reply_message_chunk")
+
+    async def is_stream_output_supported(self) -> bool:
+        """是否支持流式输出"""
+        return False
+
+    # ======== 生命周期方法（保留现有） ========
+
+    @abc.abstractmethod
+    async def run_async(self):
+        """启动适配器"""
+        ...
+
+    @abc.abstractmethod
+    async def kill(self) -> bool:
+        """停止适配器"""
+        ...
+
+    @abc.abstractmethod
+    def register_listener(self, event_type, callback):
+        """注册事件监听器"""
+        ...
+
+    @abc.abstractmethod
+    def unregister_listener(self, event_type, callback):
+        """注销事件监听器"""
+        ...
+```
+
+### 3.3 返回值类型
+
+```python
+class MessageResult(pydantic.BaseModel):
+    """消息发送结果"""
+
+    message_id: typing.Optional[typing.Union[int, str]] = None
+    """发送成功后的消息 ID"""
+
+    raw: typing.Optional[dict] = None
+    """平台原始返回数据"""
+
+
+class NotSupportedError(Exception):
+    """适配器未实现此 API"""
+
+    def __init__(self, api_name: str):
+        self.api_name = api_name
+        super().__init__(f"API not supported by this adapter: {api_name}")
+```
+
+## 4. API 能力声明
+
+适配器在 manifest.yaml 中声明支持的 API：
+
+```yaml
+kind: MessagePlatformAdapter
+metadata:
+  name: telegram
+spec:
+  supported_apis:
+    required:
+      - send_message
+      - reply_message
+    optional:
+      - edit_message
+      - delete_message
+      - get_group_info
+      - get_group_member_list
+      - get_user_info
+      - upload_file
+      - get_file_url
+      - call_platform_api
+  platform_specific_apis:
+    - action: pin_message
+      description: "Pin a message in a chat"
+      params_schema:
+        chat_id: { type: "string", required: true }
+        message_id: { type: "string", required: true }
+    - action: unpin_message
+      description: "Unpin a message"
+      params_schema:
+        chat_id: { type: "string", required: true }
+        message_id: { type: "string", required: true }
+```
+
+用途：
+1. **WebUI**：在配置界面展示当前 Bot 可用的 API 能力
+2. **插件**：插件可查询某个 Bot 是否支持特定 API，据此决定行为
+3. **文档**：自动生成各适配器的 API 支持矩阵
+
+## 5. 各平台 API 支持矩阵
+
+| API | Telegram | Discord | OneBot(QQ) | 飞书 | 钉钉 | Slack | 微信 | LINE | KOOK |
+|-----|----------|---------|-----------|------|------|-------|------|------|------|
+| `send_message` | Y | Y | Y | Y | Y | Y | Y | Y | Y |
+| `reply_message` | Y | Y | Y | Y | Y | Y | Y | Y | Y |
+| `edit_message` | Y | Y | N | Y | N | Y | N | N | Y |
+| `delete_message` | Y | Y | Y | Y | N | Y | Y | N | Y |
+| `forward_message` | Y | N | Y | Y | N | N | Y | N | N |
+| `get_group_info` | Y | Y | Y | Y | Y | Y | N | Y | Y |
+| `get_group_member_list` | Y | Y | Y | Y | Y | Y | N | Y | Y |
+| `get_user_info` | Y | Y | Y | Y | Y | Y | N | Y | Y |
+| `get_friend_list` | N | Y | Y | N | N | N | Y | N | N |
+| `mute_member` | Y | Y | Y | N | N | N | N | N | N |
+| `kick_member` | Y | Y | Y | N | N | N | N | N | Y |
+| `upload_file` | Y | Y | Y | Y | Y | Y | Y | Y | Y |
+| `call_platform_api` | Y | Y | Y | Y | Y | Y | Y | Y | Y |
+
+> 注：此表为初步评估，具体以各平台 SDK/API 文档为准。
+
+## 6. MessageChain 扩展
+
+### 6.1 保留的通用组件
+
+以下 MessageComponent 类型保持不变，继续作为通用消息元素：
+
+- `Source` — 消息元信息
+- `Plain` — 纯文本
+- `Quote` — 引用回复
+- `At` / `AtAll` — @提及
+- `Image` — 图片
+- `Voice` — 语音
+- `File` — 文件
+- `Forward` — 合并转发
+- `Face` — 表情
+- `Unknown` — 未知类型
+
+### 6.2 平台特有组件处理
+
+当前 MessageChain 中存在大量微信特有的组件类型（`WeChatMiniPrograms`, `WeChatEmoji`, `WeChatLink` 等）。在新架构下：
+
+- 这些类型**继续保留**在 SDK 中以保持兼容
+- 新增的平台特有消息组件统一使用 `PlatformComponent` 基类：
+
+```python
+class PlatformComponent(MessageComponent):
+    """平台特有的消息组件"""
+
+    type: str = "Platform"
+
+    platform: str
+    """平台标识"""
+
+    component_type: str
+    """组件类型"""
+
+    data: dict = {}
+    """组件数据"""
+```
+
+适配器在转换消息链时，对于无法映射到通用组件的平台特有内容，使用 `PlatformComponent` 承载。

docs/event-based-agents/03-adapter-structure.md

@@ -0,0 +1,483 @@
+# 适配器新目录结构
+
+## 1. 设计目标
+
+- **模块化**：每个适配器从单文件拆分到独立目录，各模块职责清晰
+- **可维护**：随着事件和 API 的增加，代码量会显著增长，目录结构有助于管理复杂度
+- **一致性**：所有适配器遵循相同的目录布局和文件命名约定
+- **兼容现有发现机制**：保持 YAML manifest + ComponentDiscoveryEngine 的注册体系
+
+## 2. 新目录布局
+
+### 2.1 整体结构
+
+```
+pkg/platform/
+├── __init__.py
+├── botmgr.py                  # PlatformManager + RuntimeBot（重构）
+├── event_bus.py               # EventBus（新增）
+├── event_router.py            # EventRouter（新增）
+├── logger.py                  # EventLogger（保留）
+├── webhook_pusher.py          # WebhookPusher（重构为 WebhookHandler）
+│
+├── adapters/                  # 适配器（新目录）
+│   ├── __init__.py
+│   │
+│   ├── telegram/
+│   │   ├── __init__.py
+│   │   ├── adapter.py         # TelegramAdapter 主类
+│   │   ├── event_converter.py # 平台事件 → 统一事件
+│   │   ├── message_converter.py # MessageChain 互转
+│   │   ├── api_impl.py        # 通用 API 实现
+│   │   ├── platform_api.py    # call_platform_api 的动作映射
+│   │   ├── types.py           # 平台特有类型定义
+│   │   └── manifest.yaml      # 适配器清单
+│   │
+│   ├── discord/
+│   │   ├── __init__.py
+│   │   ├── adapter.py
+│   │   ├── event_converter.py
+│   │   ├── message_converter.py
+│   │   ├── api_impl.py
+│   │   ├── platform_api.py
+│   │   ├── types.py
+│   │   ├── voice.py           # Discord 语音连接管理（特有）
+│   │   └── manifest.yaml
+│   │
+│   ├── aiocqhttp/             # OneBot v11 (QQ)
+│   │   └── ...
+│   ├── qqofficial/
+│   │   └── ...
+│   ├── lark/                  # 飞书
+│   │   └── ...
+│   ├── dingtalk/
+│   │   └── ...
+│   ├── slack/
+│   │   └── ...
+│   ├── wechatpad/
+│   │   └── ...
+│   ├── officialaccount/       # 微信公众号
+│   │   └── ...
+│   ├── wecom/                 # 企业微信
+│   │   └── ...
+│   ├── wecombot/
+│   │   └── ...
+│   ├── wecomcs/
+│   │   └── ...
+│   ├── kook/
+│   │   └── ...
+│   ├── line/
+│   │   └── ...
+│   ├── satori/
+│   │   └── ...
+│   ├── websocket/             # 内置 WebSocket 适配器
+│   │   ├── __init__.py
+│   │   ├── adapter.py
+│   │   ├── manager.py         # WebSocket 连接管理
+│   │   └── manifest.yaml
+│   │
+│   └── legacy/                # 旧版适配器（保留一段时间后移除）
+│       ├── gewechat/
+│       ├── nakuru/
+│       └── qqbotpy/
+│
+└── handlers/                  # 事件处理器实现（新增）
+    ├── __init__.py
+    ├── base.py                # AbstractEventHandler 基类
+    ├── pipeline_handler.py    # PipelineHandler
+    ├── agent_handler.py       # AgentHandler
+    ├── webhook_handler.py     # WebhookHandler
+    └── plugin_handler.py      # PluginHandler
+```
+
+### 2.2 适配器目录内各文件职责
+
+以 Telegram 为例：
+
+| 文件 | 职责 | 关键类/函数 |
+|------|------|------------|
+| `adapter.py` | 主入口，继承 `AbstractPlatformAdapter`，组装其他模块 | `TelegramAdapter` |
+| `event_converter.py` | 将 Telegram 原生事件转换为统一事件类型 | `TelegramEventConverter` — 支持 Message/Edit/Delete/Reaction/MemberJoin 等所有事件 |
+| `message_converter.py` | `MessageChain` 与 Telegram 消息格式互转 | `TelegramMessageConverter.yiri2target()` / `target2yiri()` |
+| `api_impl.py` | 实现通用 API 方法（edit_message, delete_message, get_group_info 等） | 各 API 方法的 Telegram 实现 |
+| `platform_api.py` | 实现 `call_platform_api` 的动作分发表 | `PLATFORM_API_MAP = {"pin_message": ..., "unpin_message": ...}` |
+| `types.py` | 平台特有的类型定义 | Telegram 特有的枚举、配置结构等 |
+| `manifest.yaml` | 适配器清单：名称、配置 schema、支持的事件和 API 列表 | — |
+
+## 3. 新基类设计
+
+### 3.1 AbstractPlatformAdapter
+
+新基类继承自现有 `AbstractMessagePlatformAdapter` 并扩展，位于 `langbot-plugin-sdk` 中：
+
+```python
+# langbot_plugin/api/definition/abstract/platform/adapter.py
+
+class AbstractPlatformAdapter(pydantic.BaseModel, metaclass=abc.ABCMeta):
+    """平台适配器基类（EBA 版本）
+
+    相比旧版 AbstractMessagePlatformAdapter：
+    - 新增通用 API 方法（edit_message, delete_message, get_group_info 等）
+    - 新增透传 API（call_platform_api）
+    - 新增能力声明（get_supported_events, get_supported_apis）
+    - 事件监听器支持所有事件类型，不仅限于消息事件
+    """
+
+    bot_account_id: str = ""
+    config: dict
+    logger: AbstractEventLogger = pydantic.Field(exclude=True)
+
+    class Config:
+        arbitrary_types_allowed = True
+
+    # ---- 能力声明 ----
+
+    def get_supported_events(self) -> list[str]:
+        """返回此适配器支持的事件类型列表
+
+        默认实现从 manifest.yaml 读取。
+        适配器也可以 override 此方法动态声明。
+        """
+        return ["message.received"]
+
+    def get_supported_apis(self) -> list[str]:
+        """返回此适配器支持的 API 列表
+
+        默认实现从 manifest.yaml 读取。
+        """
+        return ["send_message", "reply_message"]
+
+    # ---- 必需方法（抽象） ----
+
+    @abc.abstractmethod
+    async def send_message(self, target_type, target_id, message) -> MessageResult:
+        ...
+
+    @abc.abstractmethod
+    async def reply_message(self, event, message, quote_origin=False) -> MessageResult:
+        ...
+
+    @abc.abstractmethod
+    async def run_async(self):
+        ...
+
+    @abc.abstractmethod
+    async def kill(self) -> bool:
+        ...
+
+    @abc.abstractmethod
+    def register_listener(self, event_type, callback):
+        ...
+
+    @abc.abstractmethod
+    def unregister_listener(self, event_type, callback):
+        ...
+
+    # ---- 可选方法（默认抛 NotSupportedError） ----
+    # edit_message, delete_message, forward_message,
+    # get_group_info, get_group_member_list, ...
+    # call_platform_api, ...
+    # （完整签名见 02-platform-api.md）
+
+    # ---- 流式输出（保留） ----
+
+    async def reply_message_chunk(self, event, bot_message, message,
+                                   quote_origin=False, is_final=False):
+        raise NotSupportedError("reply_message_chunk")
+
+    async def is_stream_output_supported(self) -> bool:
+        return False
+
+    # ---- 消息卡片（保留） ----
+
+    async def create_message_card(self, message_id, event) -> bool:
+        return False
+
+    async def is_muted(self, group_id) -> bool:
+        return False
+```
+
+### 3.2 AbstractMessagePlatformAdapter 兼容
+
+旧的 `AbstractMessagePlatformAdapter` 保留为 `AbstractPlatformAdapter` 的类型别名：
+
+```python
+# 向后兼容
+AbstractMessagePlatformAdapter = AbstractPlatformAdapter
+```
+
+现有适配器代码中的 `AbstractMessagePlatformAdapter` 引用不需要立即修改。
+
+### 3.3 EventConverter 新设计
+
+现有 `AbstractEventConverter` 只有 `target2yiri` 和 `yiri2target` 两个静态方法，且只处理消息事件。
+
+新设计支持多种事件类型：
+
+```python
+class AbstractEventConverter:
+    """事件转换器基类（EBA 版本）
+
+    适配器需要实现此转换器，将平台原生事件转换为统一事件。
+    """
+
+    @staticmethod
+    def target2yiri(raw_event: typing.Any) -> typing.Optional[Event]:
+        """将平台原生事件转换为统一事件
+
+        Args:
+            raw_event: 平台 SDK 回调传入的原始事件对象
+
+        Returns:
+            统一 Event 对象，如果无法转换或不需要处理则返回 None
+        """
+        raise NotImplementedError
+
+    @staticmethod
+    def yiri2target(event: Event) -> typing.Any:
+        """将统一事件转换为平台原生事件（一般不需要）"""
+        raise NotImplementedError
+```
+
+具体适配器的 EventConverter 实现会是一个分发式的结构：
+
+```python
+class TelegramEventConverter(AbstractEventConverter):
+    """Telegram 事件转换器"""
+
+    @staticmethod
+    def target2yiri(update: telegram.Update) -> typing.Optional[Event]:
+        # 消息事件
+        if update.message:
+            return TelegramEventConverter._convert_message(update)
+        # 消息编辑
+        if update.edited_message:
+            return TelegramEventConverter._convert_edited_message(update)
+        # 成员变动
+        if update.chat_member:
+            return TelegramEventConverter._convert_chat_member(update)
+        # 回调查询（按钮点击等）
+        if update.callback_query:
+            return TelegramEventConverter._convert_callback_query(update)
+        # 其他 → PlatformSpecificEvent
+        return TelegramEventConverter._convert_platform_specific(update)
+
+    @staticmethod
+    def _convert_message(update) -> MessageReceivedEvent:
+        ...
+
+    @staticmethod
+    def _convert_edited_message(update) -> MessageEditedEvent:
+        ...
+
+    @staticmethod
+    def _convert_chat_member(update) -> typing.Union[
+        MemberJoinedEvent, MemberLeftEvent, ...
+    ]:
+        ...
+
+    @staticmethod
+    def _convert_platform_specific(update) -> PlatformSpecificEvent:
+        ...
+```
+
+## 4. Manifest 文件格式扩展
+
+现有 manifest.yaml 只声明 `kind`, `metadata`, `spec.config`, `execution`。
+
+新增 `spec.supported_events` 和 `spec.supported_apis`：
+
+```yaml
+apiVersion: v1
+kind: MessagePlatformAdapter
+
+metadata:
+  name: telegram
+  label:
+    en_US: Telegram
+    zh_Hans: Telegram
+  icon: telegram.svg
+  description:
+    en_US: Telegram Bot adapter
+    zh_Hans: Telegram Bot 适配器
+
+spec:
+  config:
+    # 现有配置 schema（保持不变）
+    - key: token
+      label: { en_US: "Bot Token", zh_Hans: "Bot Token" }
+      type: string
+      required: true
+      sensitive: true
+    # ...
+
+  supported_events:
+    - message.received
+    - message.edited
+    - message.deleted
+    - message.reaction
+    - feedback.received
+    - group.member_joined
+    - group.member_left
+    - group.member_banned
+    - group.info_updated
+    - bot.invited_to_group
+    - bot.removed_from_group
+    - bot.muted
+    - bot.unmuted
+    - platform.specific
+
+  supported_apis:
+    required:
+      - send_message
+      - reply_message
+    optional:
+      - edit_message
+      - delete_message
+      - get_group_info
+      - get_group_member_list
+      - get_group_member_info
+      - get_user_info
+      - upload_file
+      - get_file_url
+      - call_platform_api
+
+  platform_specific_apis:
+    - action: pin_message
+      description: { en_US: "Pin a message", zh_Hans: "置顶消息" }
+    - action: unpin_message
+      description: { en_US: "Unpin a message", zh_Hans: "取消置顶" }
+    - action: get_chat_administrators
+      description: { en_US: "Get chat admins", zh_Hans: "获取群管理员列表" }
+
+execution:
+  python:
+    path: pkg/platform/adapters/telegram/adapter.py
+    attr: TelegramAdapter
+```
+
+## 5. 适配器注册与发现
+
+### 5.1 Blueprint 更新
+
+`templates/components.yaml` 中更新扫描路径：
+
+```yaml
+kind: Blueprint
+spec:
+  components:
+    MessagePlatformAdapter:
+      fromDirs:
+        - path: pkg/platform/adapters/     # 新路径
+```
+
+`ComponentDiscoveryEngine` 的递归扫描逻辑不变——它会扫描所有子目录中的 `.yaml` 文件。因此每个适配器目录下的 `manifest.yaml` 会被自动发现。
+
+### 5.2 PlatformManager 适配
+
+`PlatformManager.initialize()` 的核心逻辑基本不变：
+
+```python
+async def initialize(self):
+    # 1. 发现适配器组件（自动扫描新目录结构）
+    self.adapter_components = self.ap.discover.get_components_by_kind('MessagePlatformAdapter')
+
+    # 2. 动态导入适配器类
+    for component in self.adapter_components:
+        self.adapter_dict[component.metadata.name] = component.get_python_component_class()
+
+    # 3. 从数据库加载 Bot 并实例化适配器（不变）
+    await self.load_bots_from_db()
+```
+
+变更点：
+- `execution.python.path` 从 `pkg/platform/sources/telegram.py` 变为 `pkg/platform/adapters/telegram/adapter.py`
+- `get_python_component_class()` 正常工作，因为它按路径动态导入
+
+## 6. RuntimeBot 重构
+
+### 6.1 现有问题
+
+当前 `RuntimeBot.initialize()` 硬编码注册了两个回调：
+
+```python
+# 现有代码
+self.adapter.register_listener(platform_events.FriendMessage, on_friend_message)
+self.adapter.register_listener(platform_events.GroupMessage, on_group_message)
+```
+
+### 6.2 新设计
+
+`RuntimeBot` 改为注册一个通用的事件回调：
+
+```python
+class RuntimeBot:
+    async def initialize(self):
+        # 注册通用事件回调，接收所有事件类型
+        self.adapter.register_listener(Event, self._on_event)
+
+    async def _on_event(
+        self,
+        event: Event,
+        adapter: AbstractPlatformAdapter,
+    ):
+        """统一事件入口"""
+
+        # 1. 设置事件的 bot_uuid 和 adapter_name
+        event.bot_uuid = self.bot_entity.uuid
+        event.adapter_name = self.bot_entity.adapter
+
+        # 2. 日志记录
+        await self._log_event(event)
+
+        # 3. 提交给 EventBus
+        await self.ap.event_bus.emit(event, adapter)
+```
+
+适配器侧的 `register_listener` 实现也需调整：
+- 当 `event_type` 为 `Event`（基类）时，注册为"接收所有事件"的通配回调
+- 适配器在收到平台原生事件时，通过 `EventConverter.target2yiri()` 转换后，调用所有匹配的回调
+
+## 7. 从现有单文件适配器迁移
+
+### 7.1 迁移模式
+
+以 Telegram 为例，从 `sources/telegram.py`（445 行）拆分：
+
+| 原代码位置 | → 新文件 |
+|-----------|----------|
+| `TelegramMessageConverter` 类 | `telegram/message_converter.py` |
+| `TelegramEventConverter` 类 | `telegram/event_converter.py`（扩展，支持更多事件） |
+| `TelegramAdapter.__init__` / `run_async` / `kill` / `register_listener` | `telegram/adapter.py` |
+| `TelegramAdapter.send_message` / `reply_message` / `reply_message_chunk` | `telegram/adapter.py`（消息方法保留在主类）+ `telegram/api_impl.py`（新增 API） |
+| 新增代码 | `telegram/api_impl.py`（edit_message, delete_message, get_group_info 等） |
+| 新增代码 | `telegram/platform_api.py`（pin_message, unpin_message 等的映射） |
+| `telegram.yaml` | `telegram/manifest.yaml`（扩展 supported_events/apis） |
+
+### 7.2 迁移顺序建议
+
+1. **Telegram** — 功能最完整的适配器之一，适合作为模板
+2. **Discord** — 第二个迁移，验证模式的通用性
+3. **AioCQHTTP (OneBot)** — 国内最常用，确保兼容
+4. **其他适配器** — 按使用频率排序
+
+### 7.3 渐进式迁移
+
+不需要一次性迁移所有适配器。可以采用渐进策略：
+
+1. 先在 `adapters/` 下建立新适配器
+2. `Blueprint` 同时扫描 `sources/` 和 `adapters/` 两个目录
+3. 旧适配器在 `sources/` 中继续工作
+4. 逐个迁移到新结构
+5. 全部迁移完成后移除 `sources/` 目录
+
+```yaml
+# 过渡期的 Blueprint
+kind: Blueprint
+spec:
+  components:
+    MessagePlatformAdapter:
+      fromDirs:
+        - path: pkg/platform/sources/      # 旧路径（尚未迁移的适配器）
+        - path: pkg/platform/adapters/      # 新路径（已迁移的适配器）
+```

docs/event-based-agents/04-event-routing.md

@@ -0,0 +1,743 @@
+# 事件路由与编排
+
+## 1. 概述
+
+事件路由是 EBA 架构的核心机制：事件从适配器产生后，经由 EventBus 进入 EventRouter，由 EventRouter 根据 Bot 的配置将事件分发到对应的处理器（Handler）。
+
+**配置方式**：用户在 WebUI 的 Bot 管理页面通过可视化编排面板管理事件处理器配置，配置数据存储在数据库的 Bot 表 `event_handlers` JSON 字段中。
+
+## 2. 数据模型
+
+### 2.1 Bot 实体扩展
+
+在 `bots` 表新增 `event_handlers` 字段：
+
+```python
+class Bot(Base):
+    __tablename__ = "bots"
+
+    uuid: str               # 主键
+    name: str
+    description: str
+    adapter: str
+    adapter_config: dict    # JSON
+    enable: bool
+
+    # 新增
+    event_handlers: list    # JSON — 事件处理器配置列表
+
+    # 保留（过渡期后弃用）
+    use_pipeline_name: str  # deprecated
+    use_pipeline_uuid: str  # deprecated
+
+    created_at: datetime
+    updated_at: datetime
+```
+
+### 2.2 EventHandler 配置结构
+
+`event_handlers` 字段存储一个 JSON 数组，每个元素定义一条事件路由规则：
+
+```python
+class EventHandlerConfig(pydantic.BaseModel):
+    """单条事件处理器配置"""
+
+    event_type: str
+    """匹配的事件类型
+
+    支持精确匹配和通配符：
+    - "message.received"       — 精确匹配
+    - "message.*"              — 匹配 message 命名空间下所有事件
+    - "group.*"                — 匹配 group 命名空间下所有事件
+    - "*"                      — 匹配所有事件（兜底）
+    """
+
+    handler_type: str
+    """处理器类型: "pipeline" | "agent" | "webhook" | "plugin" """
+
+    handler_config: dict = {}
+    """处理器的具体配置，结构取决于 handler_type"""
+
+    enabled: bool = True
+    """是否启用此规则"""
+
+    priority: int = 0
+    """优先级，数字越大越先匹配（同一事件类型有多条规则时）"""
+
+    description: str = ""
+    """规则描述（供 WebUI 显示）"""
+```
+
+### 2.3 各 Handler 类型的 handler_config 结构
+
+#### pipeline
+
+```json
+{
+    "handler_type": "pipeline",
+    "handler_config": {
+        "pipeline_uuid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
+    }
+}
+```
+
+将事件作为消息事件传入现有 Pipeline 流水线。仅适用于 `message.received` 事件。
+
+#### agent
+
+```json
+{
+    "handler_type": "agent",
+    "handler_config": {
+        "runner": "local-agent",
+        "runner_config": {
+            "model_uuid": "...",
+            "prompt": "你是一个群组助理，请处理以下事件：{event_summary}",
+            "tools_enabled": true
+        }
+    }
+}
+```
+
+```json
+{
+    "handler_type": "agent",
+    "handler_config": {
+        "runner": "dify-service-api",
+        "runner_config": {
+            "base_url": "https://api.dify.ai/v1",
+            "api_key": "...",
+            "app_type": "agent"
+        }
+    }
+}
+```
+
+直接调用 RequestRunner 处理事件。可用的 runner 包括：
+- `local-agent` — 内置 LLM Agent
+- `dify-service-api` — Dify 平台
+- `n8n-service-api` — n8n 工作流
+- `coze-api` — Coze (扣子)
+- `dashscope-app-api` — 阿里百炼
+- `langflow-api` — Langflow
+- `tbox-app-api` — 蚂蚁 Tbox
+
+Agent 处理器不经过 Pipeline 的多 Stage 流程，而是直接构建上下文并调用 Runner。适用于所有事件类型。
+
+**Agent Handler 与 Pipeline 的关系**：
+- Pipeline 是完整的多 Stage 处理链（PreProcessor → MessageProcessor(内含Runner) → PostProcessor → ...），适合复杂消息处理
+- Agent Handler 是轻量级的，直接调用 Runner，跳过 PreProcessor/PostProcessor 等阶段
+- Pipeline 内部的 AI Stage 仍然使用 Runner，所以 Runner 本身被两种 Handler 共享
+- 用户可以根据场景选择：消息处理用 Pipeline（更多控制），其他事件用 Agent（更直接）
+
+#### webhook
+
+```json
+{
+    "handler_type": "webhook",
+    "handler_config": {
+        "url": "https://example.com/webhook/langbot-events",
+        "method": "POST",
+        "headers": {
+            "Authorization": "Bearer xxx"
+        },
+        "timeout": 30,
+        "retry_count": 3,
+        "retry_interval": 5,
+        "response_actions": true
+    }
+}
+```
+
+将事件序列化为 JSON POST 到外部 URL。支持的特性：
+- **认证**：通过 headers 配置（Bearer Token、API Key 等）
+- **重试**：配置重试次数和间隔
+- **响应动作**：如果 `response_actions` 为 true，解析响应 JSON 中的 `actions` 字段并执行（如发送消息、同意好友请求等）
+
+Webhook 请求体格式：
+
+```json
+{
+    "event": {
+        "type": "group.member_joined",
+        "timestamp": 1700000000.0,
+        "bot_uuid": "...",
+        "adapter_name": "telegram",
+        "group": { "id": "...", "name": "..." },
+        "member": { "id": "...", "nickname": "..." }
+    },
+    "bot": {
+        "uuid": "...",
+        "name": "...",
+        "adapter": "telegram"
+    }
+}
+```
+
+响应体格式（当 `response_actions` 为 true 时）：
+
+```json
+{
+    "actions": [
+        {
+            "type": "send_message",
+            "params": {
+                "target_type": "group",
+                "target_id": "123456",
+                "message": [{ "type": "Plain", "text": "欢迎新成员！" }]
+            }
+        },
+        {
+            "type": "call_platform_api",
+            "params": {
+                "action": "pin_message",
+                "params": { "chat_id": "123456", "message_id": "789" }
+            }
+        }
+    ]
+}
+```
+
+#### plugin
+
+```json
+{
+    "handler_type": "plugin",
+    "handler_config": {
+        "plugin_filter": []
+    }
+}
+```
+
+将事件分发给插件的 EventListener 处理。
+
+- `plugin_filter`：可选的插件名过滤列表，为空表示分发给所有插件
+- 沿用现有的插件事件分发机制（按优先级遍历插件，支持 `prevent_postorder`）
+
+### 2.4 完整配置示例
+
+一个 Bot 的 `event_handlers` 配置示例：
+
+```json
+[
+    {
+        "event_type": "message.received",
+        "handler_type": "pipeline",
+        "handler_config": {
+            "pipeline_uuid": "default-pipeline-uuid"
+        },
+        "enabled": true,
+        "priority": 10,
+        "description": "消息事件使用默认流水线处理"
+    },
+    {
+        "event_type": "group.member_joined",
+        "handler_type": "agent",
+        "handler_config": {
+            "runner": "local-agent",
+            "runner_config": {
+                "model_uuid": "gpt-4o-mini",
+                "prompt": "有新成员 {member_name} 加入了群组 {group_name}，请生成一条欢迎消息。"
+            }
+        },
+        "enabled": true,
+        "priority": 0,
+        "description": "新成员入群时用 AI 生成欢迎消息"
+    },
+    {
+        "event_type": "friend.request_received",
+        "handler_type": "webhook",
+        "handler_config": {
+            "url": "https://my-server.com/api/friend-request",
+            "response_actions": true
+        },
+        "enabled": true,
+        "priority": 0,
+        "description": "好友请求转发到自建服务处理"
+    },
+    {
+        "event_type": "*",
+        "handler_type": "plugin",
+        "handler_config": {},
+        "enabled": true,
+        "priority": -100,
+        "description": "所有事件兜底发给插件处理"
+    }
+]
+```
+
+## 3. EventBus 设计
+
+EventBus 是事件的中转站，接收来自各个 RuntimeBot 的事件，交由 EventRouter 处理。
+
+```python
+class EventBus:
+    """事件总线"""
+
+    def __init__(self, ap: Application):
+        self.ap = ap
+        self.event_router = EventRouter(ap)
+
+    async def emit(
+        self,
+        event: Event,
+        adapter: AbstractPlatformAdapter,
+    ):
+        """接收并分发事件
+
+        Args:
+            event: 统一事件对象
+            adapter: 产生此事件的适配器实例
+        """
+        # 1. 全局事件日志
+        self.ap.logger.debug(
+            f"EventBus: {event.type} from bot {event.bot_uuid}"
+        )
+
+        # 2. 交由 EventRouter 路由处理
+        await self.event_router.route(event, adapter)
+```
+
+## 4. EventRouter 设计
+
+EventRouter 是事件路由引擎，根据 Bot 的 `event_handlers` 配置决定事件的处理方式。
+
+```python
+class EventRouter:
+    """事件路由引擎"""
+
+    def __init__(self, ap: Application):
+        self.ap = ap
+        self.handlers: dict[str, AbstractEventHandler] = {
+            "pipeline": PipelineHandler(ap),
+            "agent": AgentHandler(ap),
+            "webhook": WebhookHandler(ap),
+            "plugin": PluginHandler(ap),
+        }
+
+    async def route(
+        self,
+        event: Event,
+        adapter: AbstractPlatformAdapter,
+    ):
+        """路由事件到对应处理器"""
+
+        # 1. 获取 Bot 配置
+        bot = await self.ap.platform_mgr.get_bot_by_uuid(event.bot_uuid)
+        if not bot:
+            return
+
+        # 2. 获取事件处理器配置
+        event_handlers = bot.bot_entity.event_handlers or []
+
+        # 3. 匹配规则（按 priority 降序排列）
+        matched_handlers = self._match_handlers(event.type, event_handlers)
+
+        if not matched_handlers:
+            # 未匹配到任何规则 → 默认交给插件处理（向后兼容）
+            await self.handlers["plugin"].handle(event, adapter, {})
+            return
+
+        # 4. 执行第一个匹配的 Handler
+        #    （未来可扩展为多个 Handler 串行/并行执行）
+        handler_config = matched_handlers[0]
+        handler = self.handlers.get(handler_config.handler_type)
+
+        if handler:
+            await handler.handle(event, adapter, handler_config.handler_config)
+        else:
+            self.ap.logger.warning(
+                f"Unknown handler type: {handler_config.handler_type}"
+            )
+
+    def _match_handlers(
+        self,
+        event_type: str,
+        handlers: list[EventHandlerConfig],
+    ) -> list[EventHandlerConfig]:
+        """匹配事件类型到处理器配置
+
+        匹配规则：
+        1. 精确匹配：event_type == handler.event_type
+        2. 命名空间通配：handler.event_type 为 "message.*" 时匹配所有 "message.xxx"
+        3. 全局通配：handler.event_type 为 "*" 时匹配所有事件
+        4. 按 priority 降序排列
+        5. 只返回 enabled=True 的规则
+        """
+        matched = []
+        for handler in handlers:
+            if not handler.enabled:
+                continue
+            if self._event_type_matches(event_type, handler.event_type):
+                matched.append(handler)
+
+        matched.sort(key=lambda h: h.priority, reverse=True)
+        return matched
+
+    @staticmethod
+    def _event_type_matches(event_type: str, pattern: str) -> bool:
+        """判断事件类型是否匹配模式"""
+        if pattern == "*":
+            return True
+        if pattern == event_type:
+            return True
+        if pattern.endswith(".*"):
+            namespace = pattern[:-2]
+            return event_type.startswith(namespace + ".")
+        return False
+```
+
+## 5. 事件处理器（Handler）实现
+
+### 5.1 Handler 基类
+
+```python
+class AbstractEventHandler(abc.ABC):
+    """事件处理器基类"""
+
+    def __init__(self, ap: Application):
+        self.ap = ap
+
+    @abc.abstractmethod
+    async def handle(
+        self,
+        event: Event,
+        adapter: AbstractPlatformAdapter,
+        config: dict,
+    ) -> None:
+        """处理事件
+
+        Args:
+            event: 统一事件对象
+            adapter: 适配器实例（用于调用平台 API 发送响应）
+            config: handler_config 配置
+        """
+        ...
+```
+
+### 5.2 PipelineHandler
+
+将消息事件注入现有 Pipeline 流水线处理。
+
+```python
+class PipelineHandler(AbstractEventHandler):
+    """Pipeline 处理器 — 将事件送入现有 Pipeline 流水线"""
+
+    async def handle(self, event, adapter, config):
+        pipeline_uuid = config.get("pipeline_uuid")
+
+        if not isinstance(event, MessageReceivedEvent):
+            self.ap.logger.warning(
+                f"PipelineHandler only supports MessageReceivedEvent, "
+                f"got {event.type}"
+            )
+            return
+
+        # 将 MessageReceivedEvent 转换为现有的 Query 并投入 QueryPool
+        # 复用现有的 MessageAggregator + QueryPool + Pipeline 机制
+        launcher_type = (
+            LauncherTypes.PERSON
+            if event.chat_type == ChatType.PRIVATE
+            else LauncherTypes.GROUP
+        )
+
+        await self.ap.msg_aggregator.add_message(
+            bot_uuid=event.bot_uuid,
+            launcher_type=launcher_type,
+            launcher_id=event.chat_id,
+            sender_id=event.sender.id,
+            message_event=event.to_legacy_event(),  # 转换为 FriendMessage/GroupMessage
+            message_chain=event.message_chain,
+            adapter=adapter,
+            pipeline_uuid=pipeline_uuid,
+        )
+```
+
+### 5.3 AgentHandler
+
+直接调用 RequestRunner 处理事件，不经过 Pipeline Stage 链。
+
+```python
+class AgentHandler(AbstractEventHandler):
+    """Agent 处理器 — 直接调用 RequestRunner 处理事件"""
+
+    async def handle(self, event, adapter, config):
+        runner_name = config.get("runner", "local-agent")
+        runner_config = config.get("runner_config", {})
+
+        # 1. 查找 Runner 类
+        runner_cls = None
+        for r in preregistered_runners:
+            if r.name == runner_name:
+                runner_cls = r
+                break
+
+        if not runner_cls:
+            self.ap.logger.error(f"Runner not found: {runner_name}")
+            return
+
+        # 2. 构建事件上下文（将事件信息整理为 Runner 可处理的格式）
+        event_context = self._build_event_context(event, runner_config)
+
+        # 3. 实例化并调用 Runner
+        runner = runner_cls(self.ap, self._build_runner_pipeline_config(config))
+
+        response_messages = []
+        async for result in runner.run(event_context):
+            response_messages.append(result)
+
+        # 4. 发送响应（如果 Runner 产生了回复）
+        if response_messages and isinstance(event, MessageReceivedEvent):
+            # 将 Runner 输出转换为 MessageChain 并回复
+            reply_chain = self._build_reply_chain(response_messages)
+            await adapter.reply_message(event, reply_chain)
+
+    def _build_event_context(self, event, runner_config):
+        """将事件构建为 Runner 可处理的上下文
+
+        对于消息事件，直接使用消息内容。
+        对于其他事件，根据 runner_config 中的 prompt 模板生成描述文本。
+        """
+        ...
+
+    def _build_runner_pipeline_config(self, config):
+        """将 handler_config 转换为 Runner 需要的 pipeline_config 格式"""
+        ...
+```
+
+### 5.4 WebhookHandler
+
+将事件 POST 到外部 URL。
+
+```python
+class WebhookHandler(AbstractEventHandler):
+    """Webhook 处理器 — 将事件 POST 到外部 URL"""
+
+    async def handle(self, event, adapter, config):
+        url = config.get("url")
+        method = config.get("method", "POST")
+        headers = config.get("headers", {})
+        timeout = config.get("timeout", 30)
+        retry_count = config.get("retry_count", 3)
+        response_actions = config.get("response_actions", False)
+
+        # 1. 构建请求体
+        bot = await self.ap.platform_mgr.get_bot_by_uuid(event.bot_uuid)
+        payload = {
+            "event": event.model_dump(),
+            "bot": {
+                "uuid": bot.bot_entity.uuid,
+                "name": bot.bot_entity.name,
+                "adapter": bot.bot_entity.adapter,
+            }
+        }
+
+        # 2. 发送请求（带重试）
+        response = await self._send_with_retry(
+            url, method, headers, payload, timeout, retry_count
+        )
+
+        # 3. 处理响应动作
+        if response_actions and response:
+            await self._execute_response_actions(
+                response, adapter, event
+            )
+
+    async def _execute_response_actions(self, response, adapter, event):
+        """执行响应中的动作列表"""
+        actions = response.get("actions", [])
+        for action in actions:
+            action_type = action.get("type")
+            params = action.get("params", {})
+
+            if action_type == "send_message":
+                chain = MessageChain.model_validate(params.get("message", []))
+                await adapter.send_message(
+                    params["target_type"],
+                    params["target_id"],
+                    chain,
+                )
+            elif action_type == "reply":
+                chain = MessageChain.model_validate(params.get("message", []))
+                await adapter.reply_message(event, chain)
+            elif action_type == "call_platform_api":
+                await adapter.call_platform_api(
+                    params["action"],
+                    params.get("params", {}),
+                )
+            elif action_type == "approve_friend_request":
+                await adapter.approve_friend_request(
+                    params["request_id"],
+                    params.get("approve", True),
+                )
+            # ... 更多动作类型
+```
+
+### 5.5 PluginHandler
+
+将事件分发给插件的 EventListener。
+
+```python
+class PluginHandler(AbstractEventHandler):
+    """Plugin 处理器 — 分发给插件 EventListener"""
+
+    async def handle(self, event, adapter, config):
+        plugin_filter = config.get("plugin_filter", [])
+
+        # 复用现有的插件事件分发机制
+        # 通过 plugin_connector 将事件发送给 Plugin Runtime
+        await self.ap.plugin_connector.emit_event(
+            event=event,
+            adapter=adapter,
+            plugin_filter=plugin_filter,
+        )
+```
+
+## 6. use_pipeline_uuid 迁移
+
+### 6.1 自动迁移
+
+数据库迁移脚本将现有的 `use_pipeline_uuid` 自动转换为 `event_handlers`：
+
+```python
+# 迁移逻辑
+for bot in all_bots:
+    if bot.use_pipeline_uuid and not bot.event_handlers:
+        bot.event_handlers = [
+            {
+                "event_type": "message.received",
+                "handler_type": "pipeline",
+                "handler_config": {
+                    "pipeline_uuid": bot.use_pipeline_uuid
+                },
+                "enabled": True,
+                "priority": 10,
+                "description": "Auto-migrated from use_pipeline_uuid"
+            },
+            {
+                "event_type": "*",
+                "handler_type": "plugin",
+                "handler_config": {},
+                "enabled": True,
+                "priority": -100,
+                "description": "Default plugin handler"
+            }
+        ]
+```
+
+### 6.2 过渡期兼容
+
+在过渡期内，如果 `event_handlers` 为空且 `use_pipeline_uuid` 非空，EventRouter 自动回退到旧行为：
+
+```python
+# EventRouter.route() 中的兼容逻辑
+if not event_handlers and bot.bot_entity.use_pipeline_uuid:
+    # 回退：消息事件走 Pipeline，其他事件走 Plugin
+    if isinstance(event, MessageReceivedEvent):
+        await self.handlers["pipeline"].handle(
+            event, adapter,
+            {"pipeline_uuid": bot.bot_entity.use_pipeline_uuid}
+        )
+    else:
+        await self.handlers["plugin"].handle(event, adapter, {})
+    return
+```
+
+## 7. WebUI 编排面板数据模型
+
+### 7.1 交互设计概要
+
+在 WebUI 的 Bot 管理页面，新增"事件处理器"标签页（或区域），呈现为一个**规则列表**：
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  事件处理器                                       [+ 添加规则]  │
+├─────────────────────────────────────────────────────────────┤
+│                                                             │
+│  ┌─ 规则 1 ─────────────────────────────────── [启用] [删除] ─┐ │
+│  │  事件类型: [message.received    ▾]                         │ │
+│  │  处理器:   [Pipeline           ▾]                         │ │
+│  │  Pipeline: [默认流水线          ▾]                         │ │
+│  │  优先级:   [10]                                           │ │
+│  │  描述:     消息事件使用默认流水线处理                         │ │
+│  └──────────────────────────────────────────────────────────┘ │
+│                                                             │
+│  ┌─ 规则 2 ─────────────────────────────────── [启用] [删除] ─┐ │
+│  │  事件类型: [group.member_joined ▾]                         │ │
+│  │  处理器:   [Agent              ▾]                         │ │
+│  │  Runner:   [local-agent        ▾]                         │ │
+│  │  模型:     [gpt-4o-mini        ▾]                         │ │
+│  │  Prompt:   [有新成员加入...]                                │ │
+│  │  优先级:   [0]                                            │ │
+│  └──────────────────────────────────────────────────────────┘ │
+│                                                             │
+│  ┌─ 规则 3 (兜底) ──────────────────────────── [启用] [删除] ─┐ │
+│  │  事件类型: [*                   ▾]                         │ │
+│  │  处理器:   [Plugin             ▾]                         │ │
+│  │  优先级:   [-100]                                         │ │
+│  └──────────────────────────────────────────────────────────┘ │
+│                                                             │
+└─────────────────────────────────────────────────────────────┘
+```
+
+### 7.2 前端数据结构
+
+```typescript
+interface EventHandlerRule {
+  event_type: string;       // 下拉选择，选项从适配器 manifest 的 supported_events 获取
+  handler_type: string;     // "pipeline" | "agent" | "webhook" | "plugin"
+  handler_config: Record<string, any>;  // 根据 handler_type 动态渲染不同的配置表单
+  enabled: boolean;
+  priority: number;
+  description: string;
+}
+
+// Bot 编辑接口扩展
+interface BotConfig {
+  uuid: string;
+  name: string;
+  adapter: string;
+  adapter_config: Record<string, any>;
+  enable: boolean;
+  event_handlers: EventHandlerRule[];  // 新增
+}
+```
+
+### 7.3 事件类型下拉选项
+
+从 Bot 关联的适配器 manifest 中获取 `supported_events`，加上通配符选项：
+
+```
+- message.received
+- message.edited
+- message.deleted
+- message.reaction
+- feedback.received
+- group.member_joined
+- group.member_left
+- group.member_banned
+- group.info_updated
+- friend.request_received
+- friend.added
+- bot.invited_to_group
+- bot.removed_from_group
+- bot.muted
+- bot.unmuted
+- platform.specific
+─────────────────
+- message.*          (所有消息事件)
+- feedback.*         (所有反馈事件)
+- group.*            (所有群组事件)
+- friend.*           (所有好友事件)
+- bot.*              (所有 Bot 事件)
+- *                  (所有事件)
+```
+
+### 7.4 HTTP API
+
+```
+GET    /api/v1/bots/{uuid}/event-handlers         获取 Bot 的事件处理器配置
+PUT    /api/v1/bots/{uuid}/event-handlers         更新 Bot 的事件处理器配置
+GET    /api/v1/adapters/{name}/supported-events    获取适配器支持的事件类型
+GET    /api/v1/adapters/{name}/supported-apis      获取适配器支持的 API
+```

docs/event-based-agents/05-plugin-sdk.md

@@ -0,0 +1,738 @@
+# 插件 SDK 改造
+
+## 1. 概述
+
+插件 SDK 需要配合 EBA 架构进行以下改造：
+
+1. **新事件类型**：将所有通用事件暴露给插件
+2. **新 API**：将新增的平台 API 通过 `LangBotAPIProxy` 暴露给插件
+3. **兼容层**：保证现有插件零修改运行
+4. **通信协议扩展**：新增 action 枚举支持新 API
+
+## 2. 新事件类型暴露
+
+### 2.1 插件事件模型扩展
+
+当前插件 SDK 的事件模型（`api/entities/events.py`）只有消息相关事件。需要新增所有通用事件的插件级包装：
+
+```python
+# api/entities/events.py — 新增事件
+
+# ---- 消息事件（扩展） ----
+
+class MessageEditedReceived(BaseEventModel):
+    """消息被编辑事件"""
+    launcher_type: str
+    launcher_id: typing.Union[int, str]
+    message_id: typing.Union[int, str]
+    editor_id: typing.Union[int, str]
+    new_content: MessageChain
+    chat_type: str  # "private" | "group"
+
+class MessageDeletedReceived(BaseEventModel):
+    """消息被删除/撤回事件"""
+    launcher_type: str
+    launcher_id: typing.Union[int, str]
+    message_id: typing.Union[int, str]
+    operator_id: typing.Optional[typing.Union[int, str]] = None
+    chat_type: str
+
+class MessageReactionReceived(BaseEventModel):
+    """消息表情回应事件"""
+    launcher_type: str
+    launcher_id: typing.Union[int, str]
+    message_id: typing.Union[int, str]
+    user_id: typing.Union[int, str]
+    reaction: str
+    is_add: bool
+
+# ---- 用户反馈事件 ----
+
+class FeedbackReceived(BaseEventModel):
+    """用户对 Bot 回复提交反馈"""
+    feedback_id: str
+    feedback_type: int  # 1=like, 2=dislike, 3=cancel/remove feedback
+    feedback_content: typing.Optional[str] = None
+    inaccurate_reasons: typing.Optional[list[str]] = None
+    user_id: typing.Optional[str] = None
+    session_id: typing.Optional[str] = None
+    message_id: typing.Optional[str] = None
+    stream_id: typing.Optional[str] = None
+
+# ---- 群组事件 ----
+
+class GroupMemberJoined(BaseEventModel):
+    """新成员加入群组"""
+    group_id: typing.Union[int, str]
+    group_name: str
+    member_id: typing.Union[int, str]
+    member_name: str
+    inviter_id: typing.Optional[typing.Union[int, str]] = None
+    join_type: typing.Optional[str] = None
+
+class GroupMemberLeft(BaseEventModel):
+    """成员离开群组"""
+    group_id: typing.Union[int, str]
+    group_name: str
+    member_id: typing.Union[int, str]
+    member_name: str
+    is_kicked: bool = False
+    operator_id: typing.Optional[typing.Union[int, str]] = None
+
+class GroupMemberBanned(BaseEventModel):
+    """成员被禁言"""
+    group_id: typing.Union[int, str]
+    member_id: typing.Union[int, str]
+    operator_id: typing.Optional[typing.Union[int, str]] = None
+    duration: typing.Optional[int] = None
+
+class GroupMemberUnbanned(BaseEventModel):
+    """成员被解除禁言"""
+    group_id: typing.Union[int, str]
+    member_id: typing.Union[int, str]
+    operator_id: typing.Optional[typing.Union[int, str]] = None
+
+class GroupInfoUpdated(BaseEventModel):
+    """群组信息被修改"""
+    group_id: typing.Union[int, str]
+    group_name: str
+    operator_id: typing.Optional[typing.Union[int, str]] = None
+    changed_fields: list[str] = []
+
+# ---- 好友事件 ----
+
+class FriendRequestReceived(BaseEventModel):
+    """收到好友请求"""
+    request_id: typing.Union[int, str]
+    user_id: typing.Union[int, str]
+    user_name: str
+    message: typing.Optional[str] = None
+
+class FriendAdded(BaseEventModel):
+    """成功添加好友"""
+    user_id: typing.Union[int, str]
+    user_name: str
+
+class FriendRemoved(BaseEventModel):
+    """好友被移除"""
+    user_id: typing.Union[int, str]
+    user_name: str
+
+# ---- Bot 状态事件 ----
+
+class BotInvitedToGroup(BaseEventModel):
+    """Bot 被邀请加入群组"""
+    group_id: typing.Union[int, str]
+    group_name: str
+    inviter_id: typing.Optional[typing.Union[int, str]] = None
+    request_id: typing.Optional[typing.Union[int, str]] = None
+
+class BotRemovedFromGroup(BaseEventModel):
+    """Bot 被移出群组"""
+    group_id: typing.Union[int, str]
+    group_name: str
+    operator_id: typing.Optional[typing.Union[int, str]] = None
+
+class BotMuted(BaseEventModel):
+    """Bot 被禁言"""
+    group_id: typing.Union[int, str]
+    operator_id: typing.Optional[typing.Union[int, str]] = None
+    duration: typing.Optional[int] = None
+
+class BotUnmuted(BaseEventModel):
+    """Bot 被解除禁言"""
+    group_id: typing.Union[int, str]
+    operator_id: typing.Optional[typing.Union[int, str]] = None
+
+# ---- 平台特有事件 ----
+
+class PlatformSpecificEventReceived(BaseEventModel):
+    """平台特有事件"""
+    adapter_name: str
+    action: str
+    data: dict = {}
+```
+
+### 2.2 EventListener 注册方式
+
+插件的 EventListener 继续使用 `@self.handler(EventType)` 装饰器注册，只是可以注册的事件类型大幅增加：
+
+```python
+class MyEventListener(EventListener):
+    def __init__(self, host):
+        super().__init__(host)
+
+        # 现有方式（继续工作）
+        @self.handler(PersonNormalMessageReceived)
+        async def on_person_message(ctx: EventContext):
+            ...
+
+        # 新事件类型
+        @self.handler(GroupMemberJoined)
+        async def on_member_joined(ctx: EventContext):
+            group_name = ctx.event.group_name
+            member_name = ctx.event.member_name
+            await ctx.reply(MessageChain([
+                Plain(f"欢迎 {member_name} 加入 {group_name}！")
+            ]))
+
+        @self.handler(FriendRequestReceived)
+        async def on_friend_request(ctx: EventContext):
+            # 自动通过好友请求
+            await ctx.approve_friend_request(
+                ctx.event.request_id, approve=True
+            )
+
+        @self.handler(FeedbackReceived)
+        async def on_feedback(ctx: EventContext):
+            if ctx.event.feedback_type == 2:
+                await self.log_warning(
+                    f"用户点踩了回复: {ctx.event.feedback_content or ''}"
+                )
+
+        @self.handler(PlatformSpecificEventReceived)
+        async def on_platform_event(ctx: EventContext):
+            if ctx.event.adapter_name == "telegram" and ctx.event.action == "chat_join_request":
+                ...
+```
+
+## 3. 新 API 暴露
+
+### 3.1 LangBotAPIProxy 扩展
+
+在 `LangBotAPIProxy` 中新增以下方法，插件通过 `self.xxx()` 调用（在 BasePlugin 中继承）：
+
+```python
+class LangBotAPIProxy:
+    # ---- 现有方法（保留） ----
+    # get_langbot_version, get_bots, get_bot_info,
+    # send_message, invoke_llm, get/set/delete_plugin_storage, ...
+
+    # ---- 新增消息 API ----
+
+    async def edit_message(
+        self,
+        bot_uuid: str,
+        chat_type: str,
+        chat_id: typing.Union[int, str],
+        message_id: typing.Union[int, str],
+        new_content: MessageChain,
+    ) -> None:
+        """编辑已发送的消息"""
+        ...
+
+    async def delete_message(
+        self,
+        bot_uuid: str,
+        chat_type: str,
+        chat_id: typing.Union[int, str],
+        message_id: typing.Union[int, str],
+    ) -> None:
+        """删除/撤回消息"""
+        ...
+
+    async def forward_message(
+        self,
+        bot_uuid: str,
+        from_chat_type: str,
+        from_chat_id: typing.Union[int, str],
+        message_id: typing.Union[int, str],
+        to_chat_type: str,
+        to_chat_id: typing.Union[int, str],
+    ) -> dict:
+        """转发消息"""
+        ...
+
+    async def get_message(
+        self,
+        bot_uuid: str,
+        chat_type: str,
+        chat_id: typing.Union[int, str],
+        message_id: typing.Union[int, str],
+    ) -> dict:
+        """获取指定消息"""
+        ...
+
+    # ---- 新增群组 API ----
+
+    async def get_group_info(
+        self,
+        bot_uuid: str,
+        group_id: typing.Union[int, str],
+    ) -> dict:
+        """获取群组信息"""
+        ...
+
+    async def get_group_list(
+        self,
+        bot_uuid: str,
+    ) -> list[dict]:
+        """获取 Bot 加入的群组列表"""
+        ...
+
+    async def get_group_member_list(
+        self,
+        bot_uuid: str,
+        group_id: typing.Union[int, str],
+    ) -> list[dict]:
+        """获取群成员列表"""
+        ...
+
+    async def get_group_member_info(
+        self,
+        bot_uuid: str,
+        group_id: typing.Union[int, str],
+        user_id: typing.Union[int, str],
+    ) -> dict:
+        """获取指定群成员信息"""
+        ...
+
+    async def mute_member(
+        self,
+        bot_uuid: str,
+        group_id: typing.Union[int, str],
+        user_id: typing.Union[int, str],
+        duration: int = 0,
+    ) -> None:
+        """禁言群成员"""
+        ...
+
+    async def unmute_member(
+        self,
+        bot_uuid: str,
+        group_id: typing.Union[int, str],
+        user_id: typing.Union[int, str],
+    ) -> None:
+        """解除禁言"""
+        ...
+
+    async def kick_member(
+        self,
+        bot_uuid: str,
+        group_id: typing.Union[int, str],
+        user_id: typing.Union[int, str],
+    ) -> None:
+        """踢出群成员"""
+        ...
+
+    # ---- 新增用户 API ----
+
+    async def get_user_info(
+        self,
+        bot_uuid: str,
+        user_id: typing.Union[int, str],
+    ) -> dict:
+        """获取用户信息"""
+        ...
+
+    async def get_friend_list(
+        self,
+        bot_uuid: str,
+    ) -> list[dict]:
+        """获取好友列表"""
+        ...
+
+    async def approve_friend_request(
+        self,
+        bot_uuid: str,
+        request_id: typing.Union[int, str],
+        approve: bool = True,
+        remark: typing.Optional[str] = None,
+    ) -> None:
+        """处理好友请求"""
+        ...
+
+    async def approve_group_invite(
+        self,
+        bot_uuid: str,
+        request_id: typing.Union[int, str],
+        approve: bool = True,
+    ) -> None:
+        """处理入群邀请"""
+        ...
+
+    # ---- 新增透传 API ----
+
+    async def call_platform_api(
+        self,
+        bot_uuid: str,
+        action: str,
+        params: dict = {},
+    ) -> dict:
+        """调用适配器特有 API
+
+        Examples:
+            # Telegram: pin 消息
+            result = await self.call_platform_api(
+                bot_uuid, "pin_message",
+                {"chat_id": 123456, "message_id": 789}
+            )
+
+            # Discord: 创建频道
+            result = await self.call_platform_api(
+                bot_uuid, "create_channel",
+                {"guild_id": "...", "name": "new-channel"}
+            )
+        """
+        ...
+
+    # ---- 新增能力查询 API ----
+
+    async def get_supported_events(
+        self,
+        bot_uuid: str,
+    ) -> list[str]:
+        """获取指定 Bot 的适配器支持的事件类型"""
+        ...
+
+    async def get_supported_apis(
+        self,
+        bot_uuid: str,
+    ) -> list[str]:
+        """获取指定 Bot 的适配器支持的 API"""
+        ...
+```
+
+### 3.2 QueryBasedAPIProxy 扩展
+
+在事件处理上下文中（EventContext），通过 `QueryBasedAPIProxy` 新增便捷方法：
+
+```python
+class QueryBasedAPIProxy:
+    # ---- 现有方法（保留） ----
+    # reply, get_bot_uuid, set_query_var, get_query_var,
+    # create_new_conversation, ...
+
+    # ---- 新增便捷方法 ----
+
+    async def edit_message(
+        self,
+        message_id: typing.Union[int, str],
+        new_content: MessageChain,
+    ) -> None:
+        """在当前会话中编辑消息（自动使用当前 bot_uuid 和 chat 信息）"""
+        ...
+
+    async def delete_message(
+        self,
+        message_id: typing.Union[int, str],
+    ) -> None:
+        """在当前会话中删除消息"""
+        ...
+
+    async def approve_friend_request(
+        self,
+        request_id: typing.Union[int, str],
+        approve: bool = True,
+        remark: typing.Optional[str] = None,
+    ) -> None:
+        """处理好友请求（上下文中自动获取 bot_uuid）"""
+        ...
+
+    async def approve_group_invite(
+        self,
+        request_id: typing.Union[int, str],
+        approve: bool = True,
+    ) -> None:
+        """处理入群邀请"""
+        ...
+
+    async def get_group_info(self) -> dict:
+        """获取当前群组信息（仅群聊事件中可用）"""
+        ...
+
+    async def get_group_member_list(self) -> list[dict]:
+        """获取当前群组成员列表（仅群聊事件中可用）"""
+        ...
+
+    async def call_platform_api(
+        self,
+        action: str,
+        params: dict = {},
+    ) -> dict:
+        """调用平台特有 API（自动使用当前 bot_uuid）"""
+        ...
+```
+
+## 4. 兼容层设计
+
+### 4.1 事件兼容层
+
+当 PluginHandler 将新的 `MessageReceivedEvent` 分发给插件时，需要同时生成旧格式事件：
+
+```python
+class PluginEventCompatLayer:
+    """插件事件兼容层
+
+    将新的统一事件转换为旧的插件事件格式，
+    确保监听旧事件类型的插件仍能正常工作。
+    """
+
+    @staticmethod
+    def convert_to_legacy_events(
+        event: Event,
+    ) -> list[BaseEventModel]:
+        """将统一事件转换为旧插件事件列表
+
+        一个统一事件可能生成多个旧插件事件。
+        例如 MessageReceivedEvent 会同时生成：
+        - PersonMessageReceived / GroupMessageReceived（总是生成）
+        - PersonNormalMessageReceived / GroupNormalMessageReceived（非命令时）
+        - PersonCommandSent / GroupCommandSent（命令时）
+        """
+        legacy_events = []
+
+        if isinstance(event, MessageReceivedEvent):
+            if event.chat_type == ChatType.PRIVATE:
+                legacy_events.append(
+                    PersonMessageReceived(
+                        launcher_type="person",
+                        launcher_id=event.chat_id,
+                        sender_id=event.sender.id,
+                        message_event=event.to_legacy_friend_message(),
+                        message_chain=event.message_chain,
+                    )
+                )
+                # 命令检测后还会生成 PersonNormalMessageReceived
+                # 或 PersonCommandSent，在 Pipeline 阶段处理
+            elif event.chat_type == ChatType.GROUP:
+                legacy_events.append(
+                    GroupMessageReceived(
+                        launcher_type="group",
+                        launcher_id=event.chat_id,
+                        sender_id=event.sender.id,
+                        message_event=event.to_legacy_group_message(),
+                        message_chain=event.message_chain,
+                    )
+                )
+
+        # 新事件类型没有旧的对应物，不生成兼容事件
+        # 只有监听了新事件类型的插件才会收到
+
+        return legacy_events
+```
+
+### 4.2 分发流程
+
+```
+统一事件 (MessageReceivedEvent)
+    │
+    ├─→ 转换为旧格式 (PersonMessageReceived / GroupMessageReceived)
+    │   └─→ 分发给监听旧事件类型的插件 EventListener
+    │
+    └─→ 直接分发为新格式 (MessageReceivedEvent → 对应的插件事件)
+        └─→ 分发给监听新事件类型的插件 EventListener
+```
+
+插件 Runtime 在分发事件时检查每个 EventListener 注册的事件类型：
+- 如果注册的是旧类型（`PersonMessageReceived` 等），发送兼容层生成的旧格式事件
+- 如果注册的是新类型（`GroupMemberJoined` 等），发送新格式事件
+- 两者可以共存，同一个插件可以同时监听新旧类型
+
+### 4.3 API 兼容层
+
+现有插件使用的 API 不受影响：
+
+| 现有 API | 新架构行为 |
+|---------|----------|
+| `self.send_message(bot_uuid, target_type, target_id, message_chain)` | 不变，直接调用适配器的 `send_message` |
+| `ctx.reply(message_chain, quote_origin)` | 不变，在 MessageReceivedEvent 上下文中调用适配器的 `reply_message` |
+| `self.get_bots()` | 不变 |
+| `self.get_bot_info(bot_uuid)` | 不变 |
+
+新 API 只是额外新增的方法，不影响现有方法。
+
+## 5. 通信协议扩展
+
+### 5.1 新增 Action 枚举
+
+在 `entities/io/actions/enums.py` 中新增 action：
+
+```python
+class PluginToRuntimeAction(str, Enum):
+    # ---- 现有 actions（保留） ----
+    REGISTER_PLUGIN = "register_plugin"
+    REPLY = "reply"
+    SEND_MESSAGE = "send_message"
+    # ...
+
+    # ---- 新增消息 API ----
+    EDIT_MESSAGE = "edit_message"
+    DELETE_MESSAGE = "delete_message"
+    FORWARD_MESSAGE = "forward_message"
+    GET_MESSAGE = "get_message"
+
+    # ---- 新增群组 API ----
+    GET_GROUP_INFO = "get_group_info"
+    GET_GROUP_LIST = "get_group_list"
+    GET_GROUP_MEMBER_LIST = "get_group_member_list"
+    GET_GROUP_MEMBER_INFO = "get_group_member_info"
+    MUTE_MEMBER = "mute_member"
+    UNMUTE_MEMBER = "unmute_member"
+    KICK_MEMBER = "kick_member"
+
+    # ---- 新增用户 API ----
+    GET_USER_INFO = "get_user_info"
+    GET_FRIEND_LIST = "get_friend_list"
+    APPROVE_FRIEND_REQUEST = "approve_friend_request"
+    APPROVE_GROUP_INVITE = "approve_group_invite"
+
+    # ---- 新增透传 API ----
+    CALL_PLATFORM_API = "call_platform_api"
+
+    # ---- 新增能力查询 ----
+    GET_SUPPORTED_EVENTS = "get_supported_events"
+    GET_SUPPORTED_APIS = "get_supported_apis"
+
+
+class RuntimeToPluginAction(str, Enum):
+    # ---- 现有 actions（保留） ----
+    EMIT_EVENT = "emit_event"
+    # ...
+    # EMIT_EVENT 的 data 结构扩展以支持新事件类型
+```
+
+### 5.2 新增 Action 的请求/响应格式
+
+以 `EDIT_MESSAGE` 为例：
+
+```json
+// 请求 (Plugin → Runtime)
+{
+    "action": "edit_message",
+    "seq_id": 12345,
+    "data": {
+        "bot_uuid": "...",
+        "chat_type": "group",
+        "chat_id": "123456",
+        "message_id": "789",
+        "new_content": [
+            { "type": "Plain", "text": "edited message" }
+        ]
+    }
+}
+
+// 响应 (Runtime → Plugin)
+{
+    "seq_id": 12345,
+    "code": 0,
+    "message": "ok",
+    "data": {}
+}
+```
+
+以 `GET_GROUP_MEMBER_LIST` 为例：
+
+```json
+// 请求
+{
+    "action": "get_group_member_list",
+    "seq_id": 12346,
+    "data": {
+        "bot_uuid": "...",
+        "group_id": "123456"
+    }
+}
+
+// 响应
+{
+    "seq_id": 12346,
+    "code": 0,
+    "message": "ok",
+    "data": {
+        "members": [
+            {
+                "user": { "id": "111", "nickname": "Alice" },
+                "group_id": "123456",
+                "role": "admin",
+                "display_name": "管理员Alice"
+            },
+            ...
+        ]
+    }
+}
+```
+
+以 `CALL_PLATFORM_API` 为例：
+
+```json
+// 请求
+{
+    "action": "call_platform_api",
+    "seq_id": 12347,
+    "data": {
+        "bot_uuid": "...",
+        "action": "pin_message",
+        "params": {
+            "chat_id": "123456",
+            "message_id": "789"
+        }
+    }
+}
+
+// 响应
+{
+    "seq_id": 12347,
+    "code": 0,
+    "message": "ok",
+    "data": {
+        "result": { ... }
+    }
+}
+```
+
+### 5.3 LangBot 侧 Handler 实现
+
+在 `ControlConnectionHandler`（LangBot → Runtime 侧）和 `PluginConnectionHandler`（Runtime → Plugin 侧）中新增对应的 action 处理逻辑：
+
+```python
+# PluginConnectionHandler 中新增
+async def _handle_edit_message(self, data):
+    bot_uuid = data["bot_uuid"]
+    bot = await self.ap.platform_mgr.get_bot_by_uuid(bot_uuid)
+    await bot.adapter.edit_message(
+        chat_type=data["chat_type"],
+        chat_id=data["chat_id"],
+        message_id=data["message_id"],
+        new_content=MessageChain.model_validate(data["new_content"]),
+    )
+    return {}
+
+async def _handle_call_platform_api(self, data):
+    bot_uuid = data["bot_uuid"]
+    bot = await self.ap.platform_mgr.get_bot_by_uuid(bot_uuid)
+    result = await bot.adapter.call_platform_api(
+        action=data["action"],
+        params=data.get("params", {}),
+    )
+    return {"result": result}
+```
+
+## 6. 插件开发者迁移指南
+
+### 6.1 无需迁移（零修改运行）
+
+以下场景的现有插件**不需要任何修改**：
+
+- 使用 `PersonNormalMessageReceived` / `GroupNormalMessageReceived` 监听消息
+- 使用 `PersonCommandSent` / `GroupCommandSent` 处理命令
+- 使用 `ctx.reply()` 回复消息
+- 使用 `self.send_message()` 主动发消息
+- 使用 LLM / 存储 / RAG 等现有 API
+
+### 6.2 推荐迁移（获得新能力）
+
+如果插件希望利用新功能，可以：
+
+1. **监听新事件类型**：在 EventListener 中注册新事件类型的 handler
+2. **使用新 API**：调用 `self.edit_message()`, `self.get_group_info()` 等
+3. **使用透传 API**：调用 `self.call_platform_api()` 使用平台特有功能
+
+### 6.3 SDK 版本号
+
+新功能通过提升 SDK minor 版本发布：
+
+- 现有版本：`langbot-plugin-sdk >= x.y.z`
+- 新版本：`langbot-plugin-sdk >= x.(y+1).0`
+
+插件的 `manifest.yaml` 中的 `min_sdk_version` 决定是否能使用新 API。使用旧 SDK 版本的插件在新 LangBot 上正常运行（兼容层保证），只是无法调用新 API。

docs/event-based-agents/06-migration-plan.md

@@ -0,0 +1,429 @@
+# 分阶段迁移计划
+
+## 1. 概述
+
+EBA 架构涉及 langbot-plugin-sdk、LangBot 后端、LangBot 前端、文档和示例插件等多个仓库的改动。为降低风险、保证系统稳定性，采用分阶段渐进式迁移策略。
+
+### 1.1 阶段总览
+
+| 阶段 | 名称 | 范围 | 依赖 |
+|------|------|------|------|
+| Phase 1 | SDK 实体层 | langbot-plugin-sdk | 无 |
+| Phase 2 | 适配器重构 | LangBot 后端 | Phase 1 |
+| Phase 3 | 核心系统 | LangBot 后端 | Phase 2 |
+| Phase 4 | 插件 SDK 集成 | langbot-plugin-sdk + LangBot | Phase 3 |
+| Phase 5 | WebUI 编排面板 | LangBot 前端 | Phase 3 |
+| Phase 6 | 文档与示例 | langbot-wiki + langbot-plugin-demo | Phase 4, 5 |
+
+### 1.2 核心原则
+
+- **每个阶段结束后系统可运行**：任何阶段完成后，现有功能不受影响
+- **向后兼容贯穿全程**：旧接口在整个迁移期间保持可用
+- **先 SDK 后实现**：先定义好接口和模型，再做具体实现
+- **先核心适配器后边缘**：优先迁移用户量大的适配器
+
+---
+
+## 2. Phase 1：SDK 实体层
+
+**目标**：在 langbot-plugin-sdk 中定义新的事件体系、通用实体、API 接口和适配器基类。
+
+**仓库**：`langbot-plugin-sdk`
+
+### 2.1 任务清单
+
+| # | 任务 | 文件/模块 | 说明 |
+|---|------|----------|------|
+| 1.1 | 定义通用事件基类层次 | `api/entities/builtin/platform/events.py` | 新增 `MessageReceivedEvent`, `MessageEditedEvent`, `GroupMemberJoinedEvent` 等，保留现有 `FriendMessage`/`GroupMessage` |
+| 1.2 | 定义平台特有事件基类 | `api/entities/builtin/platform/events.py` | 新增 `PlatformSpecificEvent` |
+| 1.3 | 扩展通用实体 | `api/entities/builtin/platform/entities.py` | 新增 `User`（统一 Friend/GroupMember 的基础）、`Channel` 等，保留现有实体 |
+| 1.4 | 清理消息组件 | `api/entities/builtin/platform/message.py` | 将 `WeChatMiniPrograms` 等 WeChat 特有组件标记为 platform-specific，不再作为通用组件 |
+| 1.5 | 定义新适配器基类 | `api/definition/abstract/platform/adapter.py` | 新增 `AbstractPlatformAdapter`（继承现有 `AbstractMessagePlatformAdapter` 并扩展通用 API 方法），保留旧基类 |
+| 1.6 | 定义 API 能力声明 | `api/definition/abstract/platform/capabilities.py`（新文件） | `AdapterCapabilities` 数据类，声明适配器支持的事件和 API |
+| 1.7 | 定义 `NotSupportedError` | `api/entities/builtin/platform/errors.py`（新文件） | 可选 API 未实现时抛出的异常 |
+
+### 2.2 关键设计约束
+
+- 所有新增定义以**新增文件或新增类**的方式引入，**不修改**现有类的字段和方法签名
+- 现有 `AbstractMessagePlatformAdapter` 保留不动，新基类 `AbstractPlatformAdapter` 继承它
+- 新事件类与旧事件类并存，通过 `event_type` 字段（命名空间字符串）区分
+
+### 2.3 验收标准
+
+- [ ] 所有新增类可正常 import 且通过类型检查
+- [ ] 现有 `FriendMessage`, `GroupMessage`, `AbstractMessagePlatformAdapter` 等类行为不变
+- [ ] 新增单元测试覆盖事件序列化/反序列化、实体构造
+- [ ] SDK 版本号 minor bump（如 `0.x.0` → `0.x+1.0`）
+
+---
+
+## 3. Phase 2：适配器重构
+
+**目标**：将现有单文件适配器迁移到独立目录结构，实现新事件监听和通用 API。
+
+**仓库**：`LangBot`（后端）
+
+### 3.1 适配器迁移优先级
+
+根据用户量和代表性，建议按以下顺序迁移：
+
+| 优先级 | 适配器 | 理由 |
+|--------|--------|------|
+| P0 | **Telegram** | 用户量大，API 最完善，适合作为参考实现 |
+| P0 | **Discord** | 国际用户主要平台，事件类型丰富 |
+| P1 | **aiocqhttp**（OneBot v11） | 国内 QQ 用户主要适配器 |
+| P1 | **Satori** | 通用协议适配器，覆盖多个平台 |
+| P2 | **Lark** / **DingTalk** / **Slack** | 企业平台，用户量中等 |
+| P2 | **qqofficial** / **WeChat 系列** | 国内用户 |
+| P3 | **Kook** / **LINE** / **WeCom 系列** | 用户量较小 |
+| P3 | **WebSocket** | 内置适配器，相对简单 |
+| P4 | **legacy/*** | 遗留适配器，按需决定是否迁移或废弃 |
+
+### 3.2 单个适配器迁移步骤（以 Telegram 为例）
+
+| # | 任务 | 说明 |
+|---|------|------|
+| 2.1 | 创建目录结构 | `pkg/platform/adapters/telegram/` 下创建 `__init__.py`, `adapter.py`, `event_converter.py`, `message_converter.py`, `api_impl.py`, `types.py`, `manifest.yaml` |
+| 2.2 | 迁移消息转换器 | 将 `TelegramMessageConverter` 从 `sources/telegram.py` 搬到 `adapters/telegram/message_converter.py`，逻辑不变 |
+| 2.3 | 重写事件转换器 | 新的 `TelegramEventConverter` 支持将 Telegram Update 转换为所有通用事件类型（不只是消息），不支持的事件转为 `PlatformSpecificEvent` |
+| 2.4 | 实现通用 API | 在 `api_impl.py` 中实现 `edit_message`, `delete_message`, `get_group_info` 等 Telegram 支持的通用 API |
+| 2.5 | 实现透传 API | 在 `adapter.py` 中实现 `call_platform_api`，将 action 映射到 Telegram Bot API 调用 |
+| 2.6 | 声明能力 | 在 `manifest.yaml` 或适配器类中声明支持的事件和 API 列表 |
+| 2.7 | 新建 Adapter 主类 | `TelegramAdapter` 继承 `AbstractPlatformAdapter`（新基类），委托各模块实现 |
+| 2.8 | 更新 manifest.yaml | 更新 `execution.python.path` 指向新位置 |
+| 2.9 | 验证 | 确保新适配器通过现有消息收发流程的测试 |
+
+### 3.3 基础设施任务
+
+| # | 任务 | 说明 |
+|---|------|------|
+| 2.A | 创建 `adapters/_base/` | 将 SDK 中新基类的运行时辅助代码放在此处（如事件分发辅助函数） |
+| 2.B | 更新 ComponentDiscovery | 使 `discover_blueprint` 支持扫描 `adapters/` 子目录中的 YAML |
+| 2.C | 更新 `templates/components.yaml` | 将 `fromDirs` 从 `pkg/platform/sources/` 改为 `pkg/platform/adapters/`（过渡期两个都扫描） |
+| 2.D | 保留旧 sources/ | 过渡期不删除旧文件，通过 manifest 的 `deprecated: true` 标记 |
+
+### 3.4 验收标准
+
+- [ ] 已迁移的适配器在新目录结构下正常启动和收发消息
+- [ ] 新事件（如 `message.edited`）在支持的平台上正确触发
+- [ ] 通用 API（如 `edit_message`）在支持的平台上正确执行
+- [ ] 未迁移的适配器（仍在 `sources/`）继续正常工作
+- [ ] ComponentDiscovery 同时扫描新旧目录
+
+---
+
+## 4. Phase 3：核心系统
+
+**目标**：实现 EventBus、EventRouter 和事件处理器框架，将事件从适配器分发到不同的处理器。
+
+**仓库**：`LangBot`（后端）
+
+### 4.1 任务清单
+
+| # | 任务 | 文件/模块 | 说明 |
+|---|------|----------|------|
+| 3.1 | 实现 EventBus | `pkg/platform/event_bus.py`（新文件） | 事件总线：接收适配器事件，进行日志记录，分发给 EventRouter |
+| 3.2 | 实现 EventRouter | `pkg/platform/event_router.py`（新文件） | 事件路由引擎：读取 Bot 的 `event_handlers` 配置，匹配事件类型，分发到对应 Handler |
+| 3.3 | 实现 PipelineHandler | `pkg/platform/handlers/pipeline_handler.py` | 将 `message.received` 事件转为现有 Query，进入 Pipeline 流水线 |
+| 3.4 | 实现 AgentHandler | `pkg/platform/handlers/agent_handler.py` | 直接调用 RequestRunner 处理事件，不经过 Pipeline 多 Stage 流程 |
+| 3.5 | 实现 WebhookHandler | `pkg/platform/handlers/webhook_handler.py` | 将事件 POST 到外部 URL，解析响应执行动作（重构现有 WebhookPusher） |
+| 3.6 | 实现 PluginHandler | `pkg/platform/handlers/plugin_handler.py` | 将事件分发给插件 EventListener（复用现有 plugin_connector 机制） |
+| 3.7 | Bot 实体扩展 | `pkg/entity/persistence/bot.py` | 新增 `event_handlers` JSON 字段 |
+| 3.8 | 数据库迁移 | `pkg/persistence/migrations/` | 新增迁移脚本：添加 `event_handlers` 列，将现有 `use_pipeline_uuid` 数据迁移为 `event_handlers` 格式 |
+| 3.9 | 重构 RuntimeBot | `pkg/platform/botmgr.py` | 将 `initialize()` 中硬编码的 `on_friend_message`/`on_group_message` 回调替换为通过 EventBus 分发所有事件 |
+| 3.10 | 重构 MessageAggregator | `pkg/pipeline/aggregator.py` | 从 RuntimeBot 解耦，作为 PipelineHandler 的内部机制（只对 `message.received` 事件生效） |
+| 3.11 | Agent Handler 中 RequestRunner 解耦 | `pkg/provider/runner.py` + handlers | RequestRunner 需要能独立于 Pipeline Stage 运行，为 Agent Handler 提供轻量调用路径 |
+| 3.12 | HTTP API 扩展 | `pkg/api/http/controller/` | 新增/更新 Bot API 端点以支持 `event_handlers` 的 CRUD |
+
+### 4.2 数据迁移策略
+
+现有 Bot 表有 `use_pipeline_uuid` 字段，需要自动迁移为 `event_handlers`：
+
+```python
+# 迁移逻辑伪代码
+for bot in all_bots:
+    if bot.use_pipeline_uuid:
+        bot.event_handlers = [
+            {
+                "event_type": "message.received",
+                "handler_type": "pipeline",
+                "handler_config": {
+                    "pipeline_uuid": bot.use_pipeline_uuid
+                }
+            }
+        ]
+    else:
+        bot.event_handlers = []
+```
+
+### 4.3 RuntimeBot 重构要点
+
+当前 `RuntimeBot.initialize()` 硬编码注册两个回调：
+
+```python
+# 现有代码 (botmgr.py)
+self.adapter.register_listener(FriendMessage, on_friend_message)
+self.adapter.register_listener(GroupMessage, on_group_message)
+```
+
+重构后改为注册通用事件回调：
+
+```python
+# 新代码
+async def on_event(event: Event, adapter: AbstractPlatformAdapter):
+    await self.event_bus.emit(
+        bot_uuid=self.bot_entity.uuid,
+        event=event,
+        adapter=adapter,
+    )
+
+# 注册所有事件类型的统一回调
+self.adapter.register_listener(Event, on_event)
+```
+
+EventBus 接收事件后，调用 EventRouter 按配置分发。
+
+### 4.4 事件处理器执行流程
+
+```
+EventBus.emit(bot_uuid, event, adapter)
+    │
+    ▼
+EventRouter.route(bot_uuid, event)
+    │ 查询 bot.event_handlers 配置
+    │ 匹配 event_type（精确匹配 > 通配符 *）
+    ▼
+匹配到的 Handler(s)
+    │
+    ├── PipelineHandler.handle(event, adapter)
+    │   │ 仅支持 message.received
+    │   │ 构造 Query → MessageAggregator → QueryPool → Pipeline
+    │   └── 沿用现有完整流水线机制
+    │
+    ├── AgentHandler.handle(event, adapter)
+    │   │ 根据 handler_config 选择 RequestRunner
+    │   │ 直接调用 runner.run() 处理事件
+    │   └── 将结果通过 adapter API 回复
+    │
+    ├── WebhookHandler.handle(event, adapter)
+    │   │ 序列化事件为 JSON
+    │   │ POST 到 handler_config.url
+    │   └── 解析响应，执行动作（回复消息、调用 API 等）
+    │
+    └── PluginHandler.handle(event, adapter)
+        │ 通过 plugin_connector 分发给插件
+        └── 插件 EventListener 处理
+```
+
+### 4.5 验收标准
+
+- [ ] `message.received` 事件通过 PipelineHandler 正确进入现有 Pipeline（与旧行为一致）
+- [ ] 新增事件（如 `group.member_joined`）能通过 PluginHandler 分发给插件
+- [ ] AgentHandler 能直接调用 RequestRunner（至少 `local-agent`）处理事件并回复
+- [ ] WebhookHandler 能将事件 POST 到外部 URL
+- [ ] 数据库迁移正确执行，`use_pipeline_uuid` 数据迁移到 `event_handlers`
+- [ ] 现有 Bot 在不修改配置的情况下行为不变（自动迁移保证）
+
+---
+
+## 5. Phase 4：插件 SDK 集成
+
+**目标**：将新事件和 API 通过插件 SDK 暴露给插件开发者，同时实现兼容层。
+
+**仓库**：`langbot-plugin-sdk` + `LangBot`
+
+### 5.1 任务清单
+
+| # | 任务 | 说明 |
+|---|------|------|
+| 4.1 | 新增插件事件包装 | 在 `api/entities/events.py` 中为每个通用事件新增插件级事件类（如 `MessageEditedReceived`, `MemberJoinedReceived`） |
+| 4.2 | 兼容层实现 | `PersonMessageReceived` / `GroupMessageReceived` 由新的 `MessageReceivedEvent` 自动生成，旧事件作为新事件的 alias |
+| 4.3 | 新 API 暴露 | 在 `LangBotAPIProxy` 中新增方法：`edit_message`, `delete_message`, `get_group_info`, `get_user_info`, `call_platform_api` 等 |
+| 4.4 | 通信协议扩展 | 在 `entities/io/actions/enums.py` 中新增 action 枚举（如 `EDIT_MESSAGE`, `DELETE_MESSAGE`, `GET_GROUP_INFO`, `CALL_PLATFORM_API`） |
+| 4.5 | Runtime Handler 扩展 | 在 PluginConnectionHandler / ControlConnectionHandler 中添加新 action 的处理逻辑 |
+| 4.6 | EventListener 扩展 | 确保 `@handler()` 装饰器支持注册新事件类型 |
+| 4.7 | QueryBasedAPI 扩展 | 在 `QueryBasedAPIProxy` 中新增事件上下文相关的 API（如 `get_event_source_adapter`） |
+
+### 5.2 兼容层详细设计
+
+```
+新事件系统                         旧事件系统（兼容层）
+─────────────                    ─────────────────
+MessageReceivedEvent             ┌→ PersonMessageReceived (chat_type == "private")
+  (chat_type: "private"|"group") ┤
+                                 └→ GroupMessageReceived  (chat_type == "group")
+```
+
+**实现方式**：在 RuntimeEventDispatcher 中，当分发 `MessageReceivedEvent` 给插件时，同时生成对应的旧事件类实例。插件可以用新事件类或旧事件类注册 handler，都能收到。
+
+### 5.3 验收标准
+
+- [ ] 现有插件（使用旧事件和 API）无需修改即可运行
+- [ ] 新插件可以使用新事件类型（如 `MemberJoinedReceived`）注册 handler
+- [ ] 新 API（如 `edit_message`）可通过 `self.edit_message()` 或 `event_context.edit_message()` 调用
+- [ ] 透传 API `call_platform_api` 可正常调用适配器特有功能
+- [ ] 所有新 action 的通信协议正确工作（stdio / WebSocket）
+
+---
+
+## 6. Phase 5：WebUI 编排面板
+
+**目标**：在 WebUI 的 Bot 管理页面实现事件处理器的可视化编排。
+
+**仓库**：`LangBot`（前端 `web/`）
+
+### 6.1 任务清单
+
+| # | 任务 | 说明 |
+|---|------|------|
+| 5.1 | Bot 编辑页面扩展 | 在 Bot 编辑页面新增「事件处理」面板 |
+| 5.2 | 事件处理器列表组件 | 可视化展示当前 Bot 的 `event_handlers` 列表，支持增删改排序 |
+| 5.3 | 事件类型选择器 | 下拉选择事件类型（命名空间分组展示），支持通配符 `*` |
+| 5.4 | Handler 类型选择与配置 | 选择 handler 类型后展示对应的配置表单（Pipeline 选择器、Runner 选择器、Webhook URL 等） |
+| 5.5 | Pipeline Handler 配置 | 复用现有的 Pipeline 选择 UI（从现有 `use_pipeline_uuid` 选择器迁移） |
+| 5.6 | Agent Handler 配置 | Runner 选择器（local-agent / dify / n8n / coze 等）+ Runner 参数配置表单 |
+| 5.7 | Webhook Handler 配置 | URL 输入、认证方式选择、Header 配置 |
+| 5.8 | Plugin Handler 配置 | 通常无需额外配置，分发给所有匹配的插件 EventListener |
+| 5.9 | HTTP API 对接 | 前端调用后端 API 保存/读取 `event_handlers` 配置 |
+| 5.10 | 迁移提示 | 对于从旧版本升级的用户，如果检测到 `use_pipeline_uuid` 已自动迁移，展示提示说明 |
+
+### 6.2 UI 交互设计概要
+
+```
+┌─ Bot 编辑页面 ─────────────────────────────────────┐
+│                                                     │
+│  基本信息  │  适配器配置  │  ★ 事件处理  │           │
+│                                                     │
+│  ┌─ 事件处理器列表 ────────────────────────────┐    │
+│  │                                              │    │
+│  │  ① message.received → Pipeline: "主流水线"   │    │
+│  │     [编辑] [删除]                            │    │
+│  │                                              │    │
+│  │  ② group.member_joined → Agent: local-agent  │    │
+│  │     [编辑] [删除]                            │    │
+│  │                                              │    │
+│  │  ③ * (默认) → Plugin                         │    │
+│  │     [编辑] [删除]                            │    │
+│  │                                              │    │
+│  │  [+ 添加事件处理器]                           │    │
+│  │                                              │    │
+│  └──────────────────────────────────────────────┘    │
+│                                                     │
+│                              [保存]  [取消]          │
+└─────────────────────────────────────────────────────┘
+```
+
+### 6.3 验收标准
+
+- [ ] 用户可以在 WebUI 上为 Bot 添加/编辑/删除事件处理器
+- [ ] 四种 Handler 类型均有对应的配置表单
+- [ ] 配置保存后正确写入数据库 `event_handlers` 字段
+- [ ] 旧版本升级后，自动迁移的配置在 UI 上正确展示
+- [ ] Pipeline Handler 的行为与旧的 `use_pipeline_uuid` 完全一致
+
+---
+
+## 7. Phase 6：文档与示例
+
+**目标**：更新所有面向开发者的文档和示例。
+
+**仓库**：`langbot-wiki`, `langbot-plugin-demo`
+
+### 7.1 任务清单
+
+| # | 任务 | 仓库 | 说明 |
+|---|------|------|------|
+| 6.1 | EBA 架构概览文档 | langbot-wiki | 面向用户的新架构说明 |
+| 6.2 | 适配器开发指南更新 | langbot-wiki | 如何开发一个新的适配器（新目录结构、新基类、事件转换等） |
+| 6.3 | 插件开发指南更新 | langbot-wiki | 新事件类型、新 API 的使用说明 |
+| 6.4 | 插件迁移指南 | langbot-wiki | 现有插件如何迁移到新事件/API（如果需要使用新能力） |
+| 6.5 | 事件处理器配置指南 | langbot-wiki | WebUI 上如何配置事件处理器 |
+| 6.6 | 示例插件更新 | langbot-plugin-demo | HelloPlugin 增加新事件监听示例、新 API 调用示例 |
+| 6.7 | 新示例插件 | langbot-plugin-demo | 新建一个示例展示非消息事件处理（如入群欢迎） |
+
+---
+
+## 8. 风险评估与缓解
+
+### 8.1 技术风险
+
+| 风险 | 影响 | 概率 | 缓解措施 |
+|------|------|------|----------|
+| 适配器迁移中断现有功能 | 高 | 中 | 新旧目录并存，ComponentDiscovery 同时扫描两个目录，逐个适配器迁移验证 |
+| 事件模型不兼容导致插件崩溃 | 高 | 低 | 兼容层保证旧事件类型继续工作，新增类不修改旧类 |
+| 数据库迁移失败 | 高 | 低 | 迁移脚本做前置校验，`use_pipeline_uuid` 在过渡期保留不删除 |
+| RequestRunner 解耦破坏 Pipeline | 高 | 中 | Agent Handler 调用 Runner 的路径独立于 Pipeline，不修改现有 Pipeline Stage 中的 Runner 调用逻辑 |
+| 性能回退（EventBus 额外开销） | 中 | 低 | EventBus 在进程内同步分发，无额外序列化/网络开销 |
+| 各平台事件差异大难以统一 | 中 | 中 | 通用事件只抽象最大公约数字段，差异部分保留在 `source_platform_object`；不支持的事件走 `PlatformSpecificEvent` |
+
+### 8.2 兼容性风险
+
+| 风险 | 缓解措施 |
+|------|----------|
+| 现有插件使用旧事件类 | 兼容层自动将新事件转为旧事件分发，两种事件类都能注册 handler |
+| 现有插件调用 `reply()` / `send_message()` | 这两个 API 保持不变，只是底层实现可能微调 |
+| 第三方基于 `AbstractMessagePlatformAdapter` 开发的适配器 | 旧基类保留，新基类继承旧基类，第三方适配器无需立即迁移 |
+| 用户自定义 Pipeline 配置 | Pipeline 机制完整保留，PipelineHandler 只是入口变了（从 RuntimeBot 硬编码变为 EventRouter 配置） |
+
+### 8.3 回滚策略
+
+每个 Phase 独立可回滚：
+
+- **Phase 1**（SDK 新增类）：删除新增文件，回退 SDK 版本号
+- **Phase 2**（适配器目录）：恢复 `components.yaml` 的 `fromDirs` 指向旧目录，旧 sources/ 未删除
+- **Phase 3**（核心系统）：回退数据库迁移，恢复 RuntimeBot 旧的硬编码回调
+- **Phase 4**（插件集成）：回退 SDK 版本，插件使用旧版 SDK
+- **Phase 5**（WebUI）：前端回退，Bot 编辑页面隐藏事件处理面板
+
+---
+
+## 9. 里程碑与时间线建议
+
+| 里程碑 | 阶段 | 预期产出 |
+|--------|------|----------|
+| M1 | Phase 1 完成 | SDK 新版本发布，包含新事件/实体/基类定义 |
+| M2 | Phase 2 首批适配器（Telegram + Discord） | 两个参考实现，验证目录结构和事件/API 体系 |
+| M3 | Phase 3 核心系统 | EventBus + EventRouter + 四种 Handler 可用 |
+| M4 | Phase 2 剩余适配器 | 所有活跃适配器迁移完成 |
+| M5 | Phase 4 插件集成 | 新 SDK 发布，插件可使用新事件和 API |
+| M6 | Phase 5 WebUI | 事件处理器编排面板上线 |
+| M7 | Phase 6 文档 | 开发者文档和示例更新完毕 |
+
+建议 M1-M3 作为第一个大版本发布（如 v5.0），M4-M7 在后续小版本迭代中完成。
+
+---
+
+## 10. 开发指引
+
+### 10.1 分支策略
+
+建议在主仓库创建 `feature/eba` 长期特性分支，各 Phase 在子分支上开发后合入特性分支：
+
+```
+main
+  └── feature/eba
+        ├── feature/eba-sdk-entities      (Phase 1)
+        ├── feature/eba-adapter-telegram   (Phase 2)
+        ├── feature/eba-adapter-discord    (Phase 2)
+        ├── feature/eba-core-system        (Phase 3)
+        ├── feature/eba-plugin-sdk         (Phase 4)
+        └── feature/eba-webui              (Phase 5)
+```
+
+### 10.2 测试策略
+
+| 层次 | 测试内容 | 工具 |
+|------|----------|------|
+| 单元测试 | 事件序列化/反序列化、实体构造、API 调用 mock | pytest |
+| 集成测试 | EventBus → EventRouter → Handler 全链路 | pytest + asyncio |
+| 适配器测试 | 各适配器的事件转换、消息转换、API 调用 | pytest + mock SDK |
+| 端到端测试 | 从模拟平台事件到完整处理流程 | staging 环境 |
+| 插件兼容性测试 | 旧插件在新系统下的行为 | langbot-plugin-demo |
+
+### 10.3 代码审查关注点
+
+- 新增代码是否影响现有行为
+- 兼容层是否正确映射所有旧事件/API 场景
+- 数据库迁移是否可逆
+- 新 API 的错误处理（`NotSupportedError`）是否一致
+- 事件模型的序列化在 stdio/WebSocket 通信中是否正确

docs/event-based-agents/adapters/00-index.md

@@ -0,0 +1,39 @@
+# EBA Adapter Migration Records
+
+This directory records adapter-level migration details for the Event-Based Agents architecture. Each adapter document should be kept close to the implementation and must answer four questions:
+
+1. What changed in the adapter structure.
+2. Which configuration fields are required.
+3. Which events and APIs are supported.
+4. What has been verified end to end.
+
+## Adapter Documents
+
+General acceptance checklist: [EBA Adapter Acceptance Checklist](./acceptance-checklist.md)
+
+Current acceptance report: [EBA Adapter Acceptance Report](./acceptance-report.md)
+
+| Adapter | Status | Document |
+|---------|--------|----------|
+| Telegram | Migrated; partial plugin E2E, real UI inbound image/file verified | [Telegram](./telegram.md) |
+| Discord | Migrated; partial plugin E2E, media-inbound gaps remain | [Discord](./discord.md) |
+| OneBot v11 / aiocqhttp | Migrated; Matcha UI plus protocol-level multi-component coverage | [OneBot v11 / aiocqhttp](./aiocqhttp.md) |
+| DingTalk | Migrated; partial plugin E2E, real UI inbound image/file verified; group gap remains | [DingTalk](./dingtalk.md) |
+| Lark / Feishu | Migrated; partial live text E2E, media-inbound gap remains | [Lark / Feishu](./lark.md) |
+| WeCom | Migrated; private text plugin E2E verified, media/group gaps remain | [WeCom](./wecom.md) |
+| WeComBot | Migrated; private text and outbound/API plugin E2E verified, feedback/group gaps remain | [WeComBot](./wecombot.md) |
+| Official Account | Migrated; private text plugin E2E verified, proactive outbound not supported | [Official Account](./officialaccount.md) |
+| QQ Official API | Migrated; WebSocket inbound reached LangBot, model config blocked reply | [QQ Official API](./qqofficial.md) |
+| Slack | Migrated; private text and outbound/API plugin E2E verified | [Slack](./slack.md) |
+
+## Documentation Checklist
+
+When migrating a new adapter, add one document here with:
+
+- Configuration table matching the adapter manifest.
+- Supported event list.
+- Supported common API list.
+- Supported `call_platform_api` action list.
+- Known unsupported APIs and the reason.
+- Live test notes, including platform, channel type, destructive operations, and residual risks.
+- A clear distinction between real UI inbound media, protocol-level injected inbound media, and bot outbound media.

docs/event-based-agents/adapters/acceptance-checklist.md

@@ -0,0 +1,208 @@
+# EBA Adapter Acceptance Checklist
+
+This checklist is the architecture-level acceptance standard for every Event-Based Agents platform adapter. It is not platform-specific. Adapter migration is not complete until the adapter has a written result against this checklist.
+
+## Evidence Levels
+
+Use these evidence levels consistently in adapter records:
+
+| Level | Meaning | Can Mark Complete |
+|-------|---------|-------------------|
+| `plugin-e2e-ui` | Real SDK plugin running through standalone runtime, LangBot core, the migrated adapter, and a real platform/simulator UI action. | Yes |
+| `plugin-e2e-protocol` | Real SDK plugin running through standalone runtime, LangBot core, and the migrated adapter from a protocol-boundary event injection, such as a OneBot reverse WebSocket event. | Partial; must not be claimed as UI coverage |
+| `plugin-e2e-outbound` | Real SDK plugin calls an API and the bot output is visible in the real platform/simulator UI. | Yes for send/API coverage only |
+| `adapter-live` | Direct adapter probe connected to a real or simulator platform endpoint, bypassing plugin runtime. | No, auxiliary only |
+| `unit` | Unit/API-shape tests with mocked platform SDK objects or mocked APIs. | No, auxiliary only |
+| `not-supported` | Platform protocol or SDK has no equivalent capability. Must include reason and source. | Yes, as explicitly unsupported |
+| `blocked` | Intended capability could not be verified because of credentials, permissions, endpoint gaps, or simulator gaps. | No |
+
+The primary acceptance path must be `plugin-e2e-ui` for inbound UI-triggered behavior and `plugin-e2e-outbound` for bot send/API behavior. `adapter-live`, `plugin-e2e-protocol`, and `unit` tests are useful, but they must be labelled precisely.
+
+## Required Architecture Path
+
+Every adapter must prove this full path:
+
+```text
+Real platform / simulator UI
+  -> platform SDK native event
+  -> adapter event converter
+  -> unified EBA event/entity/message types
+  -> LangBot core event dispatch
+  -> standalone SDK runtime
+  -> real test plugin listener
+  -> plugin calls platform APIs through SDK
+  -> LangBot core API dispatch
+  -> adapter API implementation
+  -> real platform / simulator UI
+```
+
+The test plugin must record JSONL evidence containing:
+
+- event class and `event.type`
+- `bot_uuid` and `adapter_name` as received by the plugin
+- adapter name
+- chat type and chat ID
+- sender/user/group IDs with secrets redacted
+- message component list for received messages
+- API action name, input summary, result or error
+- raw unsupported/blocked reason when an item is skipped
+
+## Required Message Receive Tests
+
+For every adapter, inbound message conversion must be tested through `plugin-e2e-ui` for each component the platform can receive. If a protocol-level injection is used, label it `plugin-e2e-protocol`; it proves the adapter/core/plugin path, but it does not prove that the user-facing platform UI can send that component. If the platform UI/simulator cannot create a component, record it as `blocked` with the endpoint limitation.
+
+| Component | Required Receive Assertion |
+|-----------|----------------------------|
+| `Source` | Message ID and timestamp are present and stable enough for reply/get/delete APIs. |
+| `Plain` | Text is preserved exactly, including spaces and multi-line content. |
+| `At` | Mentioned user ID is converted to common `At.target`. |
+| `AtAll` | Broadcast mention is converted to common `AtAll`, if platform supports it. |
+| `Image` | Image ID, URL, path, or base64 is represented without leaking platform-native segment shape. |
+| `Voice` | Voice/audio component is represented as `Voice` when the platform exposes it. |
+| `File` | File name, ID/URL, and size are represented as `File` when available. |
+| `Quote` | Reply/quote source ID and origin content are represented when the platform exposes it. |
+| `Face` | Native emoji/sticker/dice/rps-like components are represented as `Face` or documented as platform-specific. |
+| `Forward` | Merged/forwarded messages are represented as `Forward` when the platform exposes structured content. |
+| `Unknown` | Unsupported native segments become `Unknown` or `PlatformSpecificEvent` data, not crashes. |
+| Mixed chain | A message containing multiple component types preserves order. |
+
+The plugin must subscribe to `MessageReceivedEvent` and assert that `message_chain` contains common `langbot_plugin.api.entities.builtin.platform.message` components, not platform-native SDK objects.
+
+## Required Message Send Tests
+
+For every adapter, outbound message conversion must be tested through `plugin-e2e-outbound` by having the plugin call SDK platform APIs and verifying the platform UI/simulator receives the expected message.
+
+| Component | Required Send Assertion |
+|-----------|-------------------------|
+| `Plain` | Text appears exactly on the platform. |
+| `At` | User mention renders as a mention or platform equivalent. |
+| `AtAll` | Broadcast mention renders or is explicitly unsupported. |
+| `Image` | URL, path, or base64 image sends and renders/downloads correctly. |
+| `Voice` | Voice/audio sends when supported. |
+| `File` | File sends with name and content/link when supported. |
+| `Quote` | Quoted reply points to the original message when supported. |
+| `Face` | Native emoji/sticker/dice/rps sends or is explicitly unsupported. |
+| `Forward` | Forward/merged-forward sends when supported; otherwise fallback behavior is documented. |
+| Mixed chain | A mixed chain preserves component order as closely as the platform allows. |
+
+If a platform supports a component only in one direction, the adapter record must say so explicitly.
+
+## Required Event Tests
+
+The plugin must subscribe to every event declared in `manifest.yaml -> spec.supported_events` and record one of `plugin-e2e-ui`, `plugin-e2e-protocol`, `not-supported`, or `blocked`.
+
+| Event | Required Assertion |
+|-------|--------------------|
+| `message.received` | Real message reaches plugin as `MessageReceivedEvent`. |
+| `message.edited` | Edited message reaches plugin with message ID and new content, if declared. |
+| `message.deleted` | Deleted/recalled message reaches plugin with message ID and operator when available, if declared. |
+| `message.reaction` | Reaction add/remove reaches plugin with message ID, user, reaction, and direction, if declared. |
+| `feedback.received` | Feedback payload reaches plugin with feedback type and message/session IDs, if declared. |
+| `group.member_joined` | Join event reaches plugin with group and member. |
+| `group.member_left` | Leave/kick event reaches plugin with group, member, and kick flag. |
+| `group.member_banned` | Mute/ban event reaches plugin with group, member, operator, and duration. |
+| `group.info_updated` | Group metadata update reaches plugin with changed fields, if declared. |
+| `friend.request_received` | Friend request reaches plugin with request ID and message. |
+| `friend.added` | Friend-added event reaches plugin. |
+| `friend.removed` | Friend-removed event reaches plugin, if declared. |
+| `bot.invited_to_group` | Bot invite/join request reaches plugin with group and inviter/request ID. |
+| `bot.removed_from_group` | Bot removal reaches plugin with group and operator when available. |
+| `bot.muted` | Bot mute reaches plugin with duration. |
+| `bot.unmuted` | Bot unmute reaches plugin. |
+| `platform.specific` | At least one unmapped native event is delivered as structured platform-specific data, if declared. |
+
+Do not declare an event in the manifest unless there is an implementation path and an acceptance entry.
+
+## Required Common API Tests
+
+The plugin must call every common API declared in `manifest.yaml -> spec.supported_apis.required` and `optional`. Each call must be recorded with input summary and result.
+
+| API | Required Assertion |
+|-----|--------------------|
+| `send_message` | Plugin sends to private and group/channel targets where supported. |
+| `reply_message` | Plugin replies to the triggering message, with quoted mode tested when supported. |
+| `edit_message` | Plugin edits a bot-sent message, if declared. |
+| `delete_message` | Plugin deletes/recalls a bot-sent message, if declared and permissions allow. |
+| `forward_message` | Plugin forwards or emulates forwarding a real message, if declared. |
+| `get_message` | Plugin retrieves a real message and receives common `MessageReceivedEvent` shape. |
+| `get_group_info` | Plugin receives `UserGroup` with ID/name/count where available. |
+| `get_group_list` | Plugin receives joined groups/channels list where supported. |
+| `get_group_member_list` | Plugin receives list of `UserGroupMember` where supported. |
+| `get_group_member_info` | Plugin receives one member with role/display name where available. |
+| `set_group_name` | Plugin changes and restores a disposable group name, if declared. |
+| `mute_member` | Plugin mutes a disposable target, if declared. |
+| `unmute_member` | Plugin unmutes the same target, if declared. |
+| `kick_member` | Plugin kicks a disposable target only in destructive test mode, if declared. |
+| `leave_group` | Plugin leaves only in destructive test mode and only at the end, if declared. |
+| `get_user_info` | Plugin receives common `User` shape. |
+| `get_friend_list` | Plugin receives friend/contact list where supported. |
+| `approve_friend_request` | Plugin accepts/rejects a disposable friend request, if declared. |
+| `approve_group_invite` | Plugin accepts/rejects a disposable group invite, if declared. |
+| `upload_file` | Plugin uploads a real small file, if declared. |
+| `get_file_url` | Plugin resolves a real file ID to a URL, if declared. |
+| `call_platform_api` | Plugin calls every declared platform-specific action with safe parameters. |
+
+Destructive APIs must be opt-in and documented with the exact target used.
+
+The SDK must expose a plugin-side platform API escape hatch for adapter-specific actions. The acceptance plugin should call it from the same EBA event handler that received the real platform event, so the evidence proves both directions of the path:
+
+```text
+plugin -> SDK call_platform_api -> LangBot core -> adapter call_platform_api -> platform SDK/API
+```
+
+The result must be serialized into JSON-safe values before it is returned to the plugin runtime.
+
+## Platform-Specific API Tests
+
+Every action listed in `manifest.yaml -> spec.platform_specific_apis` must have one acceptance entry:
+
+- `plugin-e2e-ui` or `plugin-e2e-outbound`: called by the plugin against the live/simulator endpoint.
+- `plugin-e2e-protocol`: called by the plugin after a protocol-boundary injected event; useful for endpoint-specific simulators but must be labelled.
+- `not-supported`: removed from manifest or explained if the platform SDK exposes it but this adapter intentionally does not.
+- `blocked`: endpoint did not implement it, permissions missing, or safe fixture unavailable.
+
+Do not leave a platform-specific API in the manifest without a corresponding test record.
+
+## Required Compatibility Tests
+
+Each migrated adapter must also prove:
+
+- Manifest supported events match `adapter.get_supported_events()`.
+- Manifest supported APIs match `adapter.get_supported_apis()`.
+- Manifest platform-specific actions match `PLATFORM_API_MAP`.
+- Legacy `FriendMessage` / `GroupMessage` listeners still work when the core registers them.
+- EBA listener dispatch prefers the most specific event class, then `EBAEvent`, then base `Event`.
+- Self-message filtering prevents bot echo loops without dropping edit/delete/moderation events needed for API tests.
+- `source_platform_object` is present for reply/debug but not required by plugins for common behavior.
+
+## Required Documentation Per Adapter
+
+Each adapter document must include:
+
+- adapter directory and manifest name
+- config table
+- supported event table with evidence level per event
+- supported common API table with evidence level per API
+- platform-specific API table with evidence level per action
+- receive component table with evidence level per component
+- send component table with evidence level per component
+- exact test date
+- exact platform endpoint or simulator used
+- standalone runtime command
+- plugin path/name used for testing
+- evidence JSONL path
+- destructive operations performed or explicitly skipped
+- blocked items and reasons
+
+## Acceptance Rule
+
+An adapter can be marked migrated only when:
+
+1. All declared events have `plugin-e2e-ui`, justified `plugin-e2e-protocol`, or `not-supported` evidence.
+2. All declared APIs have `plugin-e2e-outbound` or `not-supported` evidence.
+3. All platform-supported receive components have `plugin-e2e-ui` evidence; protocol-only receive coverage keeps the status partial.
+4. All platform-supported send components have `plugin-e2e-outbound` evidence.
+5. Unit tests cover conversion and API-shape boundaries.
+6. The adapter document lists every blocked or skipped item honestly.
+
+If any declared capability is only covered by `adapter-live` or `unit`, the adapter status must remain partial.

docs/event-based-agents/adapters/acceptance-report.md

@@ -0,0 +1,171 @@
+# EBA Adapter Acceptance Report
+
+Date: May 10, 2026
+
+Scope:
+
+- `telegram-eba`
+- `discord-eba`
+- `aiocqhttp-eba`
+- `dingtalk-eba`
+- `lark-eba`
+- `wecom-eba`
+- `wecombot-eba`
+- `wecomcs-eba`
+- `officialaccount-eba`
+- `qqofficial-eba`
+- `slack-eba`
+
+This report follows `acceptance-checklist.md`. Evidence levels are intentionally strict:
+
+- `plugin-e2e-ui`: real platform or simulator UI event reached LangBot, standalone runtime, and `EBAEventProbe`.
+- `plugin-e2e-protocol`: real adapter endpoint event reached LangBot, standalone runtime, and `EBAEventProbe`, but the event was injected at the platform protocol boundary rather than sent through the UI.
+- `plugin-e2e-outbound`: the plugin called SDK APIs and the resulting bot message was visible on the platform.
+- `unit`: mocked converter/API coverage only.
+- `blocked`: not completed, either because the platform/simulator/client could not trigger it or because a safe disposable fixture was unavailable.
+- `not-supported`: the platform has no equivalent capability.
+
+## Summary
+
+| Adapter | Status | Honest acceptance summary |
+|---------|--------|---------------------------|
+| Telegram | Partial EBA acceptance | Real Telegram UI covered private text, group mention text, bot invite, inbound private image/file, outbound component sweep, safe SDK APIs, and safe Telegram platform APIs. Real UI inbound voice/quote was not completed in the latest plugin run. |
+| Discord | Partial EBA acceptance | Real Discord UI covered group text, outbound image/file/quote/mention components, safe SDK APIs, and safe Discord platform APIs. Real UI inbound attachment/image/file/reply/mention was not completed. A later UI retry was blocked because the Discord client kept the send button disabled. |
+| OneBot v11 / aiocqhttp | Partial EBA acceptance | Matcha UI covered real group text and outbound supported components/APIs. Multi-component inbound `Source/Plain/At/Face/Image/Voice/File/Quote` was verified through the real OneBot reverse WebSocket adapter endpoint, but not through Matcha UI upload/send. Matcha blocks file-send and merged-forward APIs. |
+| DingTalk | Partial EBA acceptance | Real DingTalk UI covered private text, emoji-as-text inbound, private inbound image/file, outbound image/file/quote/mention fallback components, safe SDK APIs, and safe DingTalk platform APIs. Real UI inbound voice/quote and group trigger were not completed. |
+| Lark / Feishu | Partial EBA acceptance | EBA adapter structure, self-built/store app config, WebSocket/Webhook mode handling, converters, common APIs, platform APIs, and unit tests are in place. One real LangBot organization WebSocket private text event reached `EBAEventProbe`; outbound component sweep was visible in Feishu. Latest real UI image/file sends did not reach local plugin evidence, so media receive remains blocked. |
+| WeCom | Partial EBA acceptance | Regular WeCom application-message adapter is split into the EBA directory with manifest, converters, API mixin, platform API map, and unit tests. Private text reached `EBAEventProbe` through standalone runtime and the real WeCom client; safe plugin APIs passed. Real inbound media and broader event coverage remain pending. |
+| WeComBot | Partial EBA acceptance | WeCom AI Bot is split into the EBA directory with WebSocket long connection mode and optional webhook mode, EBA message/feedback/platform-specific conversion, cache-backed common APIs, platform API map, unit tests, and a direct live probe. Private text, outbound component sweep, safe common APIs, and all declared WeComBot platform APIs reached `EBAEventProbe`; group, real inbound media, and feedback callback evidence remain pending. |
+| WeCom Customer Service | Partial EBA acceptance | WeCom Customer Service is split into the EBA directory with manifest, converters, API mixin, platform API map, unit tests, docs, and a direct live probe scaffold. Real WeChat customer-side UI text reached `EBAEventProbe`; plugin outbound text/image and safe cache-backed common APIs passed. Inbound media and platform-specific API live coverage remain pending; later fallback text sends were blocked by WeCom `95001 send msg count limit`. |
+| Official Account | Partial EBA acceptance | WeChat Official Account is split into the EBA directory with manifest, converters, cache-backed safe APIs, platform API map, unit tests, and a direct live probe scaffold. Real WeChat Official Account UI private text reached `EBAEventProbe`; safe cache-backed common APIs and declared platform APIs passed. Proactive outbound `send_message` is not supported because replies must be tied to inbound webhook windows; inbound image/voice live UI evidence remains pending. |
+| QQ Official API | Partial EBA acceptance | QQ Official API is split into the EBA directory with manifest, converters, cache-backed safe APIs, platform API map, unit tests, docs, and a direct live probe scaffold. A real WebSocket-mode QQ Official bot reached the LangBot pipeline on `dev.rockchin.top`; reply/outbound evidence is blocked by the test model provider returning `model_not_found` for `deepseek-v3`. |
+| Slack | Partial EBA acceptance | Slack is split into the EBA directory with manifest, converters, cache-backed safe APIs, platform API map, unit tests, docs, and a direct live probe scaffold. Real Slack private text reached `EBAEventProbe`; safe common APIs, outbound component fallback sweep, and declared Slack platform APIs passed. Channel mention and real inbound media evidence remain pending. |
+
+Telegram and DingTalk now have real user-side UI image/file upload evidence in plugin JSONL. Discord and aiocqhttp do not yet have real UI inbound image/file evidence.
+
+## Evidence Files
+
+| Adapter | Endpoint | Evidence |
+|---------|----------|----------|
+| Telegram private | Telegram Lite, `@rockchinq_bot` private chat | `data/temp/telegram-plugin-e2e-rerun.jsonl` |
+| Telegram private media | Telegram Lite, `@rockchinq_bot` private chat | `data/temp/telegram-plugin-e2e-media-ui.jsonl` |
+| Telegram group | Telegram Lite, `Rock'sBotGroup` | `data/temp/telegram-plugin-e2e-group.jsonl` |
+| Discord | Discord client, LangBot server, `#debugging` | `data/temp/discord-plugin-e2e-20260510-final.jsonl` |
+| aiocqhttp UI | local Matcha, group `test group` | `data/temp/aiocqhttp-plugin-e2e-20260510-multiformat.jsonl` |
+| aiocqhttp protocol | OneBot reverse WebSocket endpoint `127.0.0.1:2280/ws` | `data/temp/aiocqhttp-plugin-e2e-20260510-multiformat.jsonl` |
+| DingTalk | DingTalk Mac, `LangBot Team` org private chat | `data/temp/dingtalk-plugin-e2e-20260510-rerun.jsonl` |
+| DingTalk private media | DingTalk Mac, `LangBot Team` org private chat | `data/temp/dingtalk-plugin-e2e-media-ui.jsonl` |
+| Lark / Feishu unit | local mocked Feishu SDK/client paths | `tests/unit_tests/platform/test_lark_eba_adapter.py` |
+| Lark / Feishu partial live | Feishu Mac, LangBot organization `LangBotDev` private chat | `data/temp/lark-plugin-e2e-ws.jsonl` |
+| WeCom Customer Service | WeChat customer-side UI, `客服消息 -> 浪波智能客服` on `dev.rockchin.top` | `/home/wgc/LangBotxg/LangBotEbaTest/data/temp/wecomcs_eba_plugin_probe.jsonl` |
+| Official Account | WeChat desktop client, subscribed Official Account on `dev.rockchin.top` | `/home/wgc/LangBotxg/LangBotEbaTest/data/temp/officialaccount_eba_plugin_probe.jsonl` |
+| QQ Official API unit | local mocked QQ Official client paths | `tests/unit_tests/platform/test_qqofficial_eba_adapter.py` |
+| Slack unit | local mocked Slack client paths | `tests/unit_tests/platform/test_slack_eba_adapter.py` |
+| Slack private | Slack workspace private DM on `dev.rockchin.top` | `/home/wgc/LangBotxg/LangBotEbaTest/data/temp/slack_eba_plugin_probe.jsonl` |
+
+All plugin runs used SDK standalone runtime ports `5400/5401`, LangBot `--standalone-runtime`, and the real plugin at `langbot-plugin-demo/EBAEventProbe`.
+
+## Unified Shape Verification
+
+All four adapters deliver common SDK entities to plugins before LangBot core/plugin logic handles the event.
+
+| Requirement | Telegram | Discord | aiocqhttp | DingTalk | Lark / Feishu |
+|-------------|----------|---------|-----------|----------|---------------|
+| `bot_uuid` filled | plugin-e2e | plugin-e2e | plugin-e2e | plugin-e2e | live plugin-e2e pending |
+| `adapter_name` filled | `telegram` | `discord` | `aiocqhttp` | `dingtalk` | `lark-eba` in current unit/code; older live text evidence recorded `lark` before the naming fix |
+| common `MessageChain` delivered | `Plain`, group `At + Plain`, private `Image`, private `File` | `Source + Plain` | UI `Source + Plain`; protocol `Source + Plain + At + Face + Image + Voice + File + Quote + Plain` | `Source + Plain`, private `Source + Image`, private `Source + File` | live private `Source + Plain`; unit `Source + Plain + At/Image/File`; latest live image/file blocked |
+| common user/group entities | plugin-e2e | plugin-e2e | plugin-e2e | plugin-e2e private user; group not completed | live private user; unit private/group |
+| raw native object isolation | raw data stays in `source_platform_object` | raw data stays in `source_platform_object` | raw data stays in `source_platform_object` | raw data stays in `source_platform_object` | raw data stays in `source_platform_object` |
+
+## Message Receive Components
+
+| Component | Telegram | Discord | aiocqhttp | DingTalk | Lark / Feishu |
+|-----------|----------|---------|-----------|----------|---------------|
+| `Source` | design gap: event has message id but chain omits `Source` | plugin-e2e-ui | plugin-e2e-ui/protocol | plugin-e2e-ui | plugin-e2e-ui private text |
+| `Plain` | plugin-e2e-ui private/group | plugin-e2e-ui | plugin-e2e-ui/protocol | plugin-e2e-ui | plugin-e2e-ui private text |
+| `At` | plugin-e2e-ui group mention | unit; real UI mention not completed in latest run | plugin-e2e-protocol; unit | unit; group trigger not completed | unit; group trigger not completed |
+| `AtAll` | not-supported | unit only | unit only | unit/send fallback only | unit only |
+| `Image` | plugin-e2e-ui private | converter/unit; real UI attachment not completed | plugin-e2e-protocol, not Matcha UI | plugin-e2e-ui private | unit; real UI image sent but not observed in plugin evidence |
+| `Voice` | converter/unit; real UI inbound not completed | not-supported as native voice; audio is attachment/file | plugin-e2e-protocol, not Matcha UI | converter/unit; real UI inbound not completed | unit; real UI inbound not completed |
+| `File` | plugin-e2e-ui private | converter/unit; real UI attachment not completed | plugin-e2e-protocol, not Matcha UI | plugin-e2e-ui private | unit; real UI file sent but not observed in plugin evidence |
+| `Quote` | converter/unit; real UI reply not completed | unit; real UI reply not completed | plugin-e2e-protocol | converter/unit; real UI quote not completed | unit/API-backed quote lookup; real UI quote not completed |
+| `Face` | not-supported as common `Face` | not-supported as common `Face` | plugin-e2e-protocol | UI emoji becomes `Plain` (`[smile]` text), not `Face` | not-supported as common `Face` |
+| `Forward` | not-supported inbound | not-supported inbound | unit; Matcha forward UI/action blocked | not-supported inbound | not-supported inbound |
+| Mixed chain | group `At + Plain`; media tested as separate messages | not completed inbound | plugin-e2e-protocol | media tested as separate messages; mixed inbound not completed | unit only |
+
+## Message Send Components
+
+| Component | Telegram | Discord | aiocqhttp | DingTalk | Lark / Feishu |
+|-----------|----------|---------|-----------|----------|---------------|
+| `Plain` | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound |
+| `At` | plugin-e2e-outbound equivalent | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound fallback/equivalent | plugin-e2e-outbound |
+| `AtAll` | plugin-e2e-outbound fallback | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound fallback | unit; group live not completed |
+| `Image` | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound |
+| `Voice` | not-supported in current send converter | not-supported as native voice | converter path; not completed against Matcha UI | fallback as file/text depending DingTalk media support | converter path; live not completed |
+| `File` | plugin-e2e-outbound | plugin-e2e-outbound | blocked by Matcha endpoint error | plugin-e2e-outbound | plugin-e2e-outbound |
+| `Quote` | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound fallback | plugin-e2e-outbound fallback |
+| `Face` | not-supported | not-supported | plugin-e2e-outbound attempted in mixed chain | fallback text | not-supported |
+| `Forward` | flattened fallback | flattened fallback | blocked by Matcha unsupported action | flattened fallback | plugin-e2e-outbound flattened fallback |
+| Mixed chain | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound except blocked file/forward | plugin-e2e-outbound | plugin-e2e-outbound |
+
+## Event Acceptance
+
+| Event category | Telegram | Discord | aiocqhttp | DingTalk |
+|----------------|----------|---------|-----------|----------|
+| `message.received` | plugin-e2e-ui | plugin-e2e-ui | plugin-e2e-ui and plugin-e2e-protocol | plugin-e2e-ui private |
+| `message.edited` | implemented/unit, not plugin-e2e-ui | historical/direct only, not latest plugin-e2e | unit | not declared |
+| `message.deleted` | implemented/unit, not plugin-e2e-ui | historical/direct only, not latest plugin-e2e | unit | not declared |
+| `message.reaction` | implemented/unit, not plugin-e2e-ui | historical/direct only, not latest plugin-e2e | not-supported in standard OneBot message path | not declared |
+| member join/left/ban | implemented/unit or blocked without disposable users | blocked without disposable users | unit; Matcha fixture unavailable | not declared |
+| bot invited/removed | invite plugin-e2e-ui for Telegram; removal blocked | invite historical/plugin-series; removal blocked | unit; Matcha fixture unavailable | not declared |
+| requests/friend events | not applicable | not applicable | unit; Matcha fixture unavailable | not declared |
+| `platform.specific` | implemented; not latest plugin-e2e | not latest plugin-e2e | adapter lifecycle observed; plugin focus was message path | declared for fallback; not reproduced in UI run |
+
+## Common API Acceptance
+
+| API area | Telegram | Discord | aiocqhttp | DingTalk |
+|----------|----------|---------|-----------|----------|
+| send/reply | plugin-e2e-outbound | plugin-e2e-outbound | plugin-e2e-outbound, with Matcha file/forward gaps | plugin-e2e-outbound |
+| edit/delete | historical/direct or unit; destructive/current UI not repeated | historical/direct; destructive/current UI not repeated | unit/destructive blocked | not declared or blocked |
+| message lookup | not-supported | not-supported | plugin-e2e | inbound cache-backed where available; limited live coverage |
+| group info/member info | plugin-e2e safe subset | plugin-e2e safe subset | plugin-e2e safe subset | private path only; group not completed |
+| user/friend info | plugin-e2e where platform allows | plugin-e2e where platform allows | plugin-e2e | plugin-e2e private user |
+| moderation/leave | blocked without disposable safe targets | blocked without disposable safe targets | blocked without disposable safe targets | blocked/not declared |
+| `get_file_url` | implemented; latest inbound `File` carried downloadable file data in plugin evidence | URL passthrough for attachments; inbound attachment not completed | not portable/endpoint-dependent | implemented through DingTalk media API; latest inbound `File` carried a platform file URL |
+| `call_platform_api` | plugin-e2e safe actions | plugin-e2e safe actions | plugin-e2e safe actions, Matcha gaps documented | plugin-e2e safe `check_access_token` |
+
+## Platform-Specific API Acceptance
+
+| Adapter | plugin-e2e verified | Blocked or not reproduced |
+|---------|---------------------|---------------------------|
+| Telegram | safe chat/admin/member count/chat-action actions | mutating actions and callback-only actions were not repeated |
+| Discord | safe channel/guild/role/typing actions | mutating pin/reaction/invite actions were not repeated in the latest plugin run; inbound attachment paths not completed |
+| aiocqhttp | safe OneBot actions such as status/version/can-send checks | `get_group_honor_info` unsupported by Matcha; admin/card/title/ban/record/file/forward require better endpoint fixtures |
+| DingTalk | `check_access_token`; real inbound file produced a file URL in the common `File` component | separate media-download replay APIs and group actions need a working follow-up fixture |
+
+## SDK API Acceptance
+
+`EBAEventProbe` exercised the standalone runtime path for:
+
+- bot discovery and bot info lookup
+- send message
+- component sweep where enabled
+- platform API sweep where enabled
+- plugin storage
+- workspace storage
+- plugin/command/tool/knowledge-base list APIs
+
+The probe logs set `ok=true` when the sweep completed with only expected unsupported/blocked items. Individual call details are stored in the JSONL evidence files.
+
+## Residual Risks And Required Follow-Up
+
+- Discord still requires real UI inbound image/file upload evidence before it can be called media-complete.
+- aiocqhttp has rich inbound component evidence only at the OneBot reverse WebSocket boundary; Matcha UI did not provide image/file upload coverage.
+- DingTalk group trigger remains unclosed; current evidence is private chat only.
+- Lark / Feishu requires a clean follow-up live pass: the latest LangBot organization WebSocket run connected, but UI-sent text/image/file after the loop-scheduling fix did not append plugin events.
+- Discord UI retry on May 10, 2026 was blocked by the client keeping the send button disabled even after text was entered.
+- Destructive moderation and leave APIs are intentionally blocked until disposable users/groups are available.
+
+## Conclusion
+
+The EBA conversion path is implemented and partially proven for the migrated adapters. Telegram and DingTalk now have real UI private-chat image/file inbound evidence. Discord, aiocqhttp, and Lark / Feishu still have explicit UI-level media gaps, so the overall adapter set remains partial acceptance rather than production-complete media acceptance.

docs/event-based-agents/adapters/aiocqhttp.md

@@ -0,0 +1,162 @@
+# OneBot v11 / aiocqhttp EBA Adapter
+
+## Status
+
+OneBot v11 has been migrated to the EBA adapter directory:
+
+```text
+src/langbot/pkg/platform/adapters/aiocqhttp/
+├── adapter.py
+├── api_impl.py
+├── event_converter.py
+├── manifest.yaml
+├── message_converter.py
+├── platform_api.py
+├── types.py
+└── onebot.svg
+```
+
+The EBA adapter is registered as `aiocqhttp-eba`. The legacy adapter remains at `src/langbot/pkg/platform/sources/aiocqhttp.py`.
+
+## Configuration
+
+| Field | Required | Default | Description |
+|-------|----------|---------|-------------|
+| `host` | Yes | `0.0.0.0` | Host for the reverse WebSocket server that the OneBot endpoint connects to. |
+| `port` | Yes | `2280` | Reverse WebSocket listen port. |
+| `access-token` | No | `""` | OneBot access token, if the endpoint is configured to use one. |
+
+## Events
+
+The adapter declares these EBA events:
+
+- `message.received`
+- `message.deleted`
+- `group.member_joined`
+- `group.member_left`
+- `group.member_banned`
+- `friend.request_received`
+- `friend.added`
+- `bot.invited_to_group`
+- `bot.removed_from_group`
+- `bot.muted`
+- `bot.unmuted`
+- `platform.specific`
+
+`platform.specific` is used for OneBot notice/request/meta events that do not yet have a common EBA event type, such as group admin changes, group file uploads, pokes, honor changes, and group join requests from non-bot users.
+
+## Common APIs
+
+| API | Status | Notes |
+|-----|--------|-------|
+| `send_message` | Supported | Supports private and group text, mentions, images, voice, files, faces, and flattened forwards. Group merged forwards are sent through OneBot forward APIs when possible. |
+| `reply_message` | Supported | Uses the original OneBot event and can prepend a reply segment. |
+| `edit_message` | Not supported | OneBot v11 has no standard message edit action. |
+| `delete_message` | Supported | Uses `delete_msg`; permission depends on endpoint and group role. |
+| `forward_message` | Supported | Emulates forward by fetching the source message with `get_msg` and sending its content to the target chat. |
+| `get_message` | Supported | Uses `get_msg` and converts the response into `MessageReceivedEvent`. |
+| `get_group_info` | Supported | Uses `get_group_info`. |
+| `get_group_list` | Supported | Uses `get_group_list`. |
+| `get_group_member_list` | Supported | Uses `get_group_member_list`. |
+| `get_group_member_info` | Supported | Uses `get_group_member_info`. |
+| `set_group_name` | Supported | Uses `set_group_name`; may be unsupported by mock endpoints. |
+| `get_user_info` | Supported | Uses `get_stranger_info`. |
+| `get_friend_list` | Supported | Uses `get_friend_list`. |
+| `approve_friend_request` | Supported | Uses `set_friend_add_request`. |
+| `approve_group_invite` | Supported | Uses `set_group_add_request` with `sub_type=invite`. |
+| `upload_file` | Not supported | OneBot v11 has endpoint-specific file upload extensions but no portable standalone upload action. |
+| `get_file_url` | Not supported | OneBot v11 file URL resolution is endpoint-specific. Use `call_platform_api("get_image")`, `get_record`, or endpoint extensions when available. |
+| `mute_member` | Supported | Uses `set_group_ban`. |
+| `unmute_member` | Supported | Uses `set_group_ban` with duration `0`. |
+| `kick_member` | Supported | Destructive; test only with disposable members. |
+| `leave_group` | Supported | Destructive; should run last in live tests. |
+| `call_platform_api` | Supported | See below. |
+
+## Platform-Specific APIs
+
+`call_platform_api(action, params)` supports:
+
+- `get_login_info`
+- `get_status`
+- `get_version_info`
+- `get_group_honor_info`
+- `set_group_card`
+- `set_group_special_title`
+- `set_group_admin`
+- `set_group_whole_ban`
+- `send_group_forward_msg`
+- `get_forward_msg`
+- `get_record`
+- `get_image`
+- `can_send_image`
+- `can_send_record`
+
+## Message Conversion Notes
+
+Incoming OneBot segments are converted into common `MessageChain` components before LangBot core/plugin dispatch:
+
+- `text` -> `Plain`
+- `at` -> `At` / `AtAll`
+- `image` -> `Image` or `Face` for OneBot emoji-package images
+- `record` -> `Voice`
+- `file` -> `File`
+- `reply` -> `Quote`
+- `face`, `rps`, `dice` -> `Face`
+- unsupported segments -> `Unknown`
+
+Outgoing `MessageChain` components are converted back into `aiocqhttp.Message` segments. Base64 media strings are normalized to OneBot `base64://...` format.
+
+## Live Test Record
+
+The direct live probe is:
+
+```bash
+PYTHONPATH=/Users/qinjunyan/code/projects/langbot/langbot-plugin-sdk/src \
+uv run python tests/e2e/live_aiocqhttp_eba_probe.py --host 127.0.0.1 --port 2280
+```
+
+It starts the reverse WebSocket adapter directly, records observed EBA events to `data/temp/aiocqhttp_eba_live_probe.jsonl`, waits for a real Matcha or OneBot message, then tries reply/send/get/delete/group/user/platform API calls as far as the endpoint supports them.
+
+Verified on May 10, 2026 with local Matcha connected to `ws://127.0.0.1:2280/ws`:
+
+- Real inbound group message converted to `MessageReceivedEvent`.
+- Real lifecycle connection converted to `PlatformSpecificEvent`.
+- Real reply API succeeded and rendered a quoted bot reply in Matcha.
+- Real proactive send API succeeded and rendered a bot group message in Matcha.
+- Real outgoing component sweep succeeded for text, `At`, `AtAll`, `Face`, and base64 `Image`.
+- Real `get_message`, `get_group_info`, `get_login_info`, `get_status`, `get_version_info`, `can_send_image`, and `can_send_record` calls succeeded against Matcha.
+- Unit conversion and API-shape tests passed for `Plain`, `At`, `AtAll`, `Image`, `Voice`, `File`, `Quote`, `Face`, `rps`, `dice`, `Forward`, `Unknown`, private/group message events, delete notices, group join/leave/ban notices, bot mute notices, friend requests, group invites, friend added notices, dispatch specificity, send, reply, delete, forward, get message, group APIs, user APIs, request approval APIs, moderation APIs, leave group, unsupported file APIs, and all declared `call_platform_api` actions.
+
+Skipped or residual live-test items:
+
+- `edit_message`: not implemented because OneBot v11 has no standard edit action.
+- `upload_file` and `get_file_url`: not implemented as common APIs because portable OneBot v11 file upload/download URL semantics are endpoint-specific.
+- `kick_member` and `leave_group`: destructive; run only with explicit `--destructive` and disposable Matcha/OneBot state.
+- `group.info_updated`, message reactions, and message edits are not declared because OneBot v11 does not provide standard equivalents for them.
+- Matcha returned `ActionFailed` for outgoing `File` segment rendering and did not support merged-forward actions in this run. The adapter keeps the conversion/API implementations because they are valid OneBot/NapCat-style capabilities, but the Matcha live probe records them as skipped.
+- Matcha returned an empty `get_group_member_list` for the test group, so `get_group_member_info`, mute/unmute, kick, and leave were covered by unit/API-shape tests only in this run.
+
+## Standalone Runtime Plugin E2E Record
+
+Verified on May 10, 2026 with `EBAEventProbe`, SDK standalone runtime, LangBot `--standalone-runtime`, local Matcha, and group `测试群`.
+
+Evidence:
+
+- Plugin JSONL: `data/temp/aiocqhttp-plugin-e2e-20260510-multiformat.jsonl`
+
+Observed and verified:
+
+- A real Matcha group message reached the plugin as `MessageReceived` with `bot_uuid=eba-aiocqhttp-matcha`, `adapter_name=aiocqhttp`, common `Source`/`Plain` message components, common sender, and common group identifiers.
+- A protocol-level OneBot reverse WebSocket event reached the plugin as `MessageReceived` with a mixed common chain: `Source`, `Plain`, `At`, `Face`, `Image`, `Voice`, `File`, `Quote`, and trailing `Plain`. This proves the real adapter + LangBot + standalone runtime + plugin path for mixed inbound OneBot payloads, but it was not sent through Matcha UI.
+- SDK API calls succeeded: `get_langbot_version`, `get_bots`, `get_bot_info`, `send_message`, plugin storage, workspace storage, `list_plugins_manifest`, `list_commands`, `list_tools`, and `list_knowledge_bases`.
+- Outbound component sweep succeeded for plain text plus `At`/`Face`, `AtAll`, base64 `Image`, and quoted reply.
+- Common APIs succeeded through the plugin path: `get_message`, `get_user_info`, `get_friend_list`, `get_group_info`, `get_group_list`, `get_group_member_list`, and `get_group_member_info`.
+- Safe OneBot platform APIs succeeded through `call_platform_api`: `get_login_info`, `get_status`, `get_version_info`, `can_send_image`, and `can_send_record`.
+
+Documented Matcha limits in this E2E run:
+
+- Matcha UI did not provide a completed image/file upload/send path for inbound media. The rich inbound media evidence is `plugin-e2e-protocol`, not UI-level media upload evidence.
+- Outbound `File` failed in Matcha even after the adapter emitted an official `file` segment shape.
+- Outbound `Forward` failed because Matcha returned unsupported action for merged-forward.
+- `get_group_honor_info` failed because Matcha returned unsupported action.
+- Destructive/admin APIs such as mute, unmute, kick, leave, group rename, card/title/admin/whole-ban changes, and request approvals were not run without disposable fixtures.

docs/event-based-agents/adapters/dingtalk.md

@@ -0,0 +1,114 @@
+# DingTalk EBA Adapter Migration Record
+
+Status: migrated with partial plugin E2E evidence.
+
+Adapter directory: `src/langbot/pkg/platform/adapters/dingtalk/`
+
+## What Changed
+
+The DingTalk adapter now has an Event-Based Agents adapter package with:
+
+- `manifest.yaml` for adapter metadata, configuration, events, common APIs, and platform-specific APIs.
+- `adapter.py` for DingTalk client startup, native callback handling, legacy compatibility, and EBA dispatch.
+- `event_converter.py` for native DingTalk events to common EBA events.
+- `message_converter.py` for DingTalk message payloads to/from common `MessageChain` components.
+- `api_impl.py` for common EBA API implementations.
+- `platform_api.py` for DingTalk-specific `call_platform_api` actions.
+
+The legacy DingTalk HTTP client now returns successful JSON response bodies from proactive send methods and raises with response details on non-200 responses.
+
+## Configuration
+
+| Field | Required | Notes |
+|-------|----------|-------|
+| `client-id` | yes | DingTalk robot/client identifier. |
+| `client-secret` | yes | DingTalk client secret. |
+| `robot-code` | yes | Robot code used for send APIs. |
+| `robot-name` | no | Used for bot mention/self filtering and display. |
+| `encrypt-key` | no | DingTalk callback encryption key when configured. |
+| `verification-token` | no | DingTalk callback verification token when configured. |
+
+## Supported Events
+
+| Event | Support | Evidence |
+|-------|---------|----------|
+| `message.received` | implemented | `plugin-e2e-ui` private text and emoji-as-text. |
+| `platform.specific` | implemented | Not reproduced in the latest UI run. |
+
+## Receive Components
+
+| Component | Support | Evidence |
+|-----------|---------|----------|
+| `Source` | supported | `plugin-e2e-ui` private message. |
+| `Plain` | supported | `plugin-e2e-ui` private text. DingTalk emoji currently arrives as plain text such as `[smile]`. |
+| `At` | converter path | Group trigger was not completed in the latest run. |
+| `AtAll` | fallback/send-side only | Not completed inbound. |
+| `Image` | supported | Real DingTalk Mac private-chat image upload reached the plugin as common `Image`. |
+| `Voice` | converter path | Real UI inbound voice was not completed. |
+| `File` | supported | Real DingTalk Mac private-chat file upload reached the plugin as common `File`. |
+| `Quote` | converter path | Real UI inbound quote was not completed. |
+| `Face` | not native common mapping | DingTalk emoji was observed as `Plain`, not `Face`. |
+| `Forward` | not-supported inbound | DingTalk does not expose a portable structured forward event in this adapter. |
+
+## Send Components
+
+| Component | Support | Evidence |
+|-----------|---------|----------|
+| `Plain` | supported | `plugin-e2e-outbound`. |
+| `At` | supported or text fallback | `plugin-e2e-outbound`. |
+| `AtAll` | fallback | `plugin-e2e-outbound`. |
+| `Image` | supported | `plugin-e2e-outbound`. |
+| `File` | supported | `plugin-e2e-outbound`. |
+| `Quote` | fallback | `plugin-e2e-outbound`. |
+| `Face` | fallback | `plugin-e2e-outbound` as text fallback. |
+| `Forward` | flattened fallback | `plugin-e2e-outbound`. |
+| `Voice` | fallback/endpoint-dependent | Not separately verified as a native DingTalk voice send. |
+
+## Common APIs
+
+| API | Support | Notes |
+|-----|---------|-------|
+| `send_message` | supported | Verified through `EBAEventProbe`. |
+| `reply_message` | supported | Verified through quoted/fallback send path. |
+| `get_message` | cache-backed | Requires the message to have been observed by this adapter process. |
+| `get_group_info` | cache-backed/API-backed where available | Group path not completed in latest UI run. |
+| `get_group_list` | supported where DingTalk API allows | Limited live coverage. |
+| `get_group_member_info` | supported where DingTalk API allows | Limited live coverage. |
+| `get_user_info` | supported | Private sender path verified. |
+| `get_friend_list` | limited | DingTalk does not expose a portable friend-list equivalent. |
+| `get_file_url` | supported with media/file identifiers | Real inbound file yielded a platform file URL in the converted `File` component. |
+| `call_platform_api` | supported | Safe action `check_access_token` verified. |
+
+## Platform-Specific APIs
+
+| Action | Support | Evidence |
+|--------|---------|----------|
+| `check_access_token` | supported | `plugin-e2e`. |
+| `refresh_access_token` | supported | Implemented; not separately reproduced in the latest plugin run. |
+| `get_file_url` | supported | Real inbound file yielded a platform file URL in the converted `File` component. |
+| `get_audio_base64` | supported | Needs real inbound audio/media ID. |
+| `download_image_base64` | supported | Real inbound image reached the plugin as `Image`; separate image-download API replay was not completed. |
+
+## End-to-End Evidence
+
+Evidence files:
+
+- Text/API/component JSONL: `data/temp/dingtalk-plugin-e2e-20260510-rerun.jsonl`
+- Real UI inbound media JSONL: `data/temp/dingtalk-plugin-e2e-media-ui.jsonl`
+
+Verified:
+
+- DingTalk Mac private chat in the `LangBot Team` organization produced `MessageReceived` through LangBot standalone runtime and `EBAEventProbe`.
+- The common chain was `Source + Plain` for normal text.
+- DingTalk emoji was received as `Source + Plain`, not common `Face`.
+- Real DingTalk Mac private-chat image upload was received as `Source + Image`.
+- Real DingTalk Mac private-chat file upload was received as `Source + File`.
+- The plugin sent outbound text, mention/fallback, image, quote/fallback, file, and forward/fallback messages visible in DingTalk.
+- The plugin called safe SDK and DingTalk platform APIs.
+
+Not completed:
+
+- Real UI inbound voice.
+- Real UI inbound quote.
+- Group trigger with a real robot mention.
+- Destructive or organization-mutating APIs.

docs/event-based-agents/adapters/discord.md

@@ -0,0 +1,147 @@
+# Discord EBA Adapter
+
+## Status
+
+Discord has been migrated from the legacy source adapter:
+
+```text
+src/langbot/pkg/platform/sources/discord.py
+src/langbot/pkg/platform/sources/discord.yaml
+```
+
+EBA adapter directory:
+
+```text
+src/langbot/pkg/platform/adapters/discord/
+├── adapter.py
+├── api_impl.py
+├── event_converter.py
+├── manifest.yaml
+├── message_converter.py
+├── platform_api.py
+├── types.py
+└── voice.py
+```
+
+The adapter is registered as `discord-eba`.
+
+## Configuration
+
+| Field | Required | Default | Description |
+|-------|----------|---------|-------------|
+| `client_id` | Yes | `""` | Discord application client ID. |
+| `token` | Yes | `""` | Discord bot token. |
+
+The bot needs gateway permissions and intents for the target test server. Message Content intent is required for message bodies, Server Members intent is required for member APIs/events, and reaction events require the Reactions intent and channel permissions.
+
+## Events
+
+Discord declares these EBA events:
+
+- `message.received`
+- `message.edited`
+- `message.deleted`
+- `message.reaction`
+- `group.member_joined`
+- `group.member_left`
+- `group.member_banned`
+- `bot.invited_to_group`
+- `bot.removed_from_group`
+- `platform.specific`
+
+Discord-specific events that do not map cleanly to common events should be surfaced as `platform.specific`.
+
+## Common APIs
+
+| API | Status | Notes |
+|-----|-----------------|-------|
+| `send_message` | Supported | Supports text, image, file, and mixed message chains through Discord messages and attachments. |
+| `reply_message` | Supported | Uses Discord message references when replying to a received EBA message event. |
+| `edit_message` | Supported | Bot can edit its own messages. File edits are implemented by clearing old attachments and sending replacement files when needed. |
+| `delete_message` | Supported | Requires message management permissions for non-bot messages. |
+| `forward_message` | Emulated | Discord has no native forward API; the adapter copies content and attachments. |
+| `get_group_info` | Supported | Maps Discord guild metadata to EBA group info. |
+| `get_group_member_list` | Supported | Requires member cache or the Server Members intent/fetch permission. |
+| `get_group_member_info` | Supported | Maps Discord roles/permissions into EBA member roles. |
+| `get_user_info` | Supported | Uses Discord user fetch/cache. |
+| `upload_file` | Not supported | Discord uploads files as message attachments; standalone upload raises `NotSupportedError`. |
+| `get_file_url` | Supported | Discord attachment URLs are already downloadable URLs, so the adapter returns the input URL. |
+| `mute_member` | Supported where possible | Uses Discord timeout API and requires guild moderation permission. |
+| `unmute_member` | Supported where possible | Clears timeout and requires guild moderation permission. |
+| `kick_member` | Supported | Destructive; test only with a disposable account/bot. |
+| `leave_group` | Supported | Bot leaves a guild; destructive and should run last. |
+| `call_platform_api` | Supported | Discord-specific actions live here. |
+
+## Platform-Specific APIs
+
+`call_platform_api(action, params)` supports:
+
+- `get_channel`
+- `get_guild`
+- `get_guild_channels`
+- `get_guild_roles`
+- `create_invite`
+- `pin_message`
+- `unpin_message`
+- `add_reaction`
+- `remove_reaction`
+- `typing`
+
+Voice helpers are intentionally kept Discord-specific:
+
+- `join_voice_channel`
+- `leave_voice_channel`
+- `get_voice_connection_status`
+- `list_active_voice_connections`
+- `get_voice_channel_info`
+
+## Live Test Record
+
+The live probe is:
+
+```bash
+uv run python tests/e2e/live_discord_eba_probe.py --help
+```
+
+Verified on May 7, 2026 with a newly created Discord application/bot named `LangBot EBA Test 0507`, the LangBot Discord server, and the `#🐞-debugging` channel:
+
+- SDK standalone runtime started with WebSocket control/debug ports, and the `EBAEventProbe` plugin connected through `lbp run`.
+- Plugin runtime received real Discord events through LangBot: `BotInvitedToGroup`, `MessageReceived`, `MessageReactionReceived` add/remove, `MessageEdited`, and `MessageDeleted`.
+- Plugin runtime API calls succeeded through the standalone runtime: `get_langbot_version`, `get_bots`, `get_bot_info`, `send_message`, plugin storage APIs, workspace storage APIs, `list_plugins_manifest`, `list_commands`, `list_tools`, and `list_knowledge_bases`.
+- Direct live adapter probe observed `message.received`, `message.edited`, `message.deleted`, and `bot.removed_from_group`.
+- Message APIs verified: send, reply, edit, delete, forward, text/image/file mixed message chains.
+- User and guild APIs verified: `get_user_info`, `get_group_info`, `get_group_member_list`, `get_group_member_info`.
+- Platform-specific APIs verified: `get_channel`, `get_guild`, `get_guild_channels`, `get_guild_roles`, `create_invite`, `typing`, `pin_message`, `unpin_message`, `add_reaction`, `remove_reaction`.
+- Unsupported API behavior verified: `upload_file` raises `NotSupportedError`.
+- Destructive API verified at the end: `leave_group`, which emitted `bot.removed_from_group`.
+
+Not verified in the shared LangBot server live run: `mute_member`, `unmute_member`, and `kick_member`, because the run did not use a disposable target member. They are implemented through Discord timeout/kick APIs and should only be exercised against a disposable account or bot.
+
+The test fixed one real test-fixture issue: `EBAEventProbe` previously assumed `get_bots()` returned UUID strings. The current standalone runtime returns bot dictionaries, so the probe now selects an enabled bot dictionary and passes its `uuid` to `get_bot_info` and `send_message`. The probe also now subscribes to `MessageDeleted`.
+
+## Standalone Runtime Plugin E2E Record
+
+Verified again on May 10, 2026 with SDK standalone runtime, LangBot `--standalone-runtime`, Discord web client, the LangBot server, and `#🐞-debugging`.
+
+Evidence:
+
+- Main plugin JSONL: `data/temp/discord-plugin-e2e-20260510-final.jsonl`
+- LangBot runtime log: `data/temp/discord-langbot-e2e-20260510-rerun.log`
+
+Observed and verified:
+
+- A newly invited Discord bot connected to the LangBot server and received a real web-client message in `#🐞-debugging`.
+- `MessageReceived` reached the plugin with `bot_uuid=eba-discord-live`, `adapter_name=discord`, common `Source`/`Plain` message components, common `User`, and common `UserGroup` for the guild.
+- SDK API calls succeeded: `get_langbot_version`, `get_bots`, `get_bot_info`, `send_message`, plugin storage, workspace storage, `list_plugins_manifest`, `list_commands`, `list_tools`, and `list_knowledge_bases`.
+- Outbound component sweep succeeded: plain text plus user mention, `AtAll`/`@everyone`, base64 image, quoted reply, file attachment, and flattened forward fallback.
+- Common APIs succeeded: `get_user_info`, `get_group_info`, `get_group_member_list`, and `get_group_member_info`.
+- Discord platform APIs succeeded through `call_platform_api`: `get_channel`, `typing`, `get_guild`, `get_guild_channels`, and `get_guild_roles`.
+
+Documented limits in this E2E run:
+
+- Real Discord UI inbound attachment/image/file, reply/quote, and fresh mention-chain messages were not completed in the plugin E2E evidence. Outbound image/file attachments from the bot do not prove inbound attachment conversion.
+- A later May 10 UI retry could write text into the Discord message box, but the client kept the send button disabled and did not send the message, so it produced no new plugin evidence.
+- `get_message`, `get_friend_list`, and `get_group_list` are not supported by this Discord adapter.
+- Destructive moderation and guild-leave APIs were not repeated against the shared LangBot server.
+- Native Discord voice is not represented as common `Voice`; audio-like payloads are treated as file attachments.
+- `create_invite`, pin/unpin, and reaction mutation were covered by prior direct live probes but were not repeated by the final plugin run to avoid extra shared-server side effects.

docs/event-based-agents/adapters/lark.md

@@ -0,0 +1,135 @@
+# Lark / Feishu EBA Adapter Migration Record
+
+Status: migrated with unit coverage and partial live plugin E2E. WebSocket text reached the standalone runtime once in the LangBot organization test app, but the latest real UI image/file inbound attempts did not reach the local adapter log, so media receive is not release-complete yet.
+
+Adapter directory: `src/langbot/pkg/platform/adapters/lark/`
+
+## What Changed
+
+The Lark/Feishu adapter now has an Event-Based Agents adapter package with:
+
+- `manifest.yaml` for adapter metadata, configuration, events, common APIs, platform-specific APIs, app type, and communication mode.
+- `adapter.py` for self-built/store app token handling, WebSocket long connection startup, Webhook callback handling, card feedback, streaming-card replies, and EBA dispatch.
+- `event_converter.py` for native Feishu events to common EBA events.
+- `message_converter.py` for Feishu text/post/image/file/audio payloads to/from common `MessageChain` components.
+- `api_impl.py` for common EBA API implementations.
+- `platform_api.py` for Feishu-specific `call_platform_api` actions.
+
+The legacy `lark` adapter remains available while the EBA adapter is registered separately as `lark-eba`.
+
+## Configuration
+
+| Field | Required | Notes |
+|-------|----------|-------|
+| `app_id` | yes | Feishu/Lark application App ID. |
+| `app_secret` | yes | Feishu/Lark application App Secret. |
+| `bot_name` | yes | Must match the bot name so group mentions can be recognized. |
+| `enable-webhook` | yes | `false` uses WebSocket long connection; `true` uses Request URL/Webhook callbacks. |
+| `webhook_url` | no | Generated callback URL for Webhook mode. |
+| `encrypt-key` | no | Webhook decrypt key when event encryption is enabled. |
+| `enable-stream-reply` | yes | Enables streaming replies through an updating Feishu card. |
+| `app_type` | no | `self` for self-built apps; `isv` for store apps. |
+| `bot_added_welcome` | no | Optional group welcome message sent after bot-added events. |
+
+## Application And Communication Modes
+
+| Mode | Support | Implementation |
+|------|---------|----------------|
+| Self-built application | implemented | Uses standard app credentials and tenant token behavior from the Feishu SDK client. |
+| Store application | implemented | Builds an ISV client, requests app tickets, and resolves app/tenant access tokens with per-tenant caching. |
+| WebSocket long connection | implemented | Registers `im.message.receive_v1` and card-action callbacks through `lark_oapi.ws.Client`. |
+| Webhook Request URL | implemented | Handles URL verification, encrypted payloads, message events, app-ticket events, bot-added events, and card-action feedback. |
+
+## Supported Events
+
+| Event | Support | Evidence |
+|-------|---------|----------|
+| `message.received` | implemented | Unit coverage for private and group native events to common EBA events. |
+| `bot.invited_to_group` | implemented | Webhook bot-added event maps to common bot invite event and optional welcome send. |
+| `platform.specific` | implemented | Unknown callback events are preserved as `platform.specific`. |
+| `FeedbackEvent` | compatibility event | Card button feedback is still dispatched through the existing SDK `FeedbackEvent` type. |
+
+## Receive Components
+
+| Component | Support | Evidence |
+|-----------|---------|----------|
+| `Source` | supported | Unit coverage; live private text evidence. |
+| `Plain` | supported | Text and post payloads convert to common text; live private text evidence. |
+| `At` | supported | Feishu mentions map to common `At` with user ID and display name. |
+| `AtAll` | supported | `user_id=all` maps to common `AtAll`. |
+| `Image` | supported | Image payloads download through message resource API and map to common `Image`; real UI image send attempted, but not observed in local plugin evidence yet. |
+| `Voice` | supported | Audio payloads download through message resource API and map to common `Voice`. |
+| `File` | supported | File payloads download through message resource API and map to common `File`; real UI file send attempted, but not observed in local plugin evidence yet. |
+| `Quote` | supported | Parent/thread reply lookup maps quoted content into common `Quote`. |
+| `Face` | not native common mapping | Feishu emoji/stickers are not exposed as a portable common `Face` component here. |
+| `Forward` | not-supported inbound | Feishu does not expose a portable structured forward event in this adapter. |
+
+## Send Components
+
+| Component | Support | Evidence |
+|-----------|---------|----------|
+| `Plain` | supported | Unit coverage; sends Feishu `text`. |
+| `At` | supported | Unit coverage; sends Feishu `post` at element. |
+| `AtAll` | supported | Unit coverage; sends Feishu `post` at-all element. |
+| `Image` | supported | Uploads image resource and sends Feishu `image`. |
+| `Voice` | supported | Uploads OPUS/audio resource and sends Feishu `audio`. |
+| `File` | supported | Uploads file resource and sends Feishu `file`. |
+| `Quote` | supported/fallback | Sends quote marker plus origin content. |
+| `Face` | not-supported | No portable send mapping. |
+| `Forward` | flattened fallback | Flattens forward nodes into text/media messages. |
+
+## Common APIs
+
+| API | Support | Notes |
+|-----|---------|-------|
+| `send_message` | supported | Supports private/open_id and group/chat_id targets; live plugin outbound component sweep produced visible Feishu messages. |
+| `reply_message` | supported | Replies to the source Feishu message; fixed to recover the native Feishu message ID from legacy-wrapped source events. |
+| `get_message` | cache-backed/API-backed | Returns cached inbound event where possible and converts uncached Feishu message API items into common `MessageReceivedEvent`. |
+| `get_group_info` | supported | Uses cached group or Feishu chat metadata. |
+| `get_group_member_info` | limited | Uses cached user data when available. |
+| `get_user_info` | limited | Uses cached user data when available. |
+| `get_file_url` | limited | Returns `file://` paths from downloaded inbound resources; remote Feishu resource download uses platform-specific API params. |
+| `call_platform_api` | supported | See below. |
+
+## Platform-Specific APIs
+
+| Action | Support | Evidence |
+|--------|---------|----------|
+| `check_tenant_access_token` | supported | Unit coverage. |
+| `refresh_app_access_token` | supported | Store-app token path implemented. |
+| `refresh_tenant_access_token` | supported | Store-app tenant token path implemented. |
+| `get_chat` | supported | Feishu chat metadata API wrapper. |
+| `get_message` | supported | Feishu message API wrapper with JSON-safe return values for plugin calls. |
+| `get_message_resource` | supported | Feishu message resource download wrapper. |
+
+## End-to-End Evidence
+
+Current code-level evidence:
+
+- `tests/unit_tests/platform/test_lark_eba_adapter.py`
+- `PYTHONPATH=../langbot-plugin-sdk/src uv run pytest tests/unit_tests/platform/test_lark_eba_adapter.py -q`
+
+Live evidence collected on May 11, 2026:
+
+- Standalone runtime: `uv run lbp rt --ws-control-port 5400 --ws-debug-port 5401 --skip-deps-check`
+- LangBot: `uv run main.py --standalone-runtime --debug`
+- Plugin: `LangBot__EBAEventProbe`
+- Feishu org/app: LangBot organization, `LangBotDev` private chat.
+- Observed plugin JSONL: one private `MessageReceived` event with `Source + Plain`; plugin API probe then exercised bot discovery, bot info, `send_message`, outbound component sweep, storage/list APIs, and safe platform API calls.
+- Real UI sends attempted after the fixes: private text, local file, and image/video image upload. These appeared in the Feishu client but did not append new `EBAEventProbe` records in the local JSONL during this run.
+- Fixes from live testing: reply path now extracts the native Feishu `message_id` from legacy-wrapped source events; WebSocket callbacks are scheduled onto the adapter event loop instead of assuming the SDK callback has a running asyncio loop; platform API results are converted to JSON-safe values.
+
+Live E2E items still required before marking release-complete:
+
+- WebSocket self-built app in LangBot organization: repeat private text after callback-loop fix, plus private image/file/audio and group mention message received by `EBAEventProbe`.
+- Webhook self-built app in LangBot organization: URL verification plus text/image/file message received by `EBAEventProbe`.
+- Store app token path: at least token acquisition/tenant-token safe API through `call_platform_api`; full message E2E if a LangBot organization store-app fixture is available.
+- Outbound component sweep: text, mention, at-all, image, file, voice where Feishu accepts the fixture, quote/fallback, and forward/fallback.
+- Safe platform API sweep: token check, chat metadata, message lookup, and message resource download using real inbound IDs.
+
+## Known Limits
+
+- Store-app live E2E requires a real ISV app ticket/tenant installation fixture.
+- Current LangBot organization WebSocket run connected successfully but did not deliver the latest UI-sent image/file attempts to local plugin evidence; this blocks release-complete media acceptance.
+- Feishu native emoji/sticker semantics are not represented as common `Face`.
+- Destructive org or chat mutations are not declared in this adapter.

docs/event-based-agents/adapters/officialaccount.md

@@ -0,0 +1,101 @@
+# OfficialAccount EBA Adapter
+
+Adapter directory: `src/langbot/pkg/platform/adapters/officialaccount/`
+
+Manifest name: `officialaccount-eba`
+
+Status: partial migration. Unit/API-shape coverage is present, and private text `plugin-e2e-ui` plus safe API evidence has been verified against the `dev.rockchin.top` Official Account fixture. Proactive outbound `send_message` remains not supported by this adapter because WeChat Official Account replies must be tied to inbound webhook windows.
+
+## Config
+
+| Field | Required | Notes |
+| --- | --- | --- |
+| `webhook_url` | no | Generated by LangBot and copied into the Official Account callback settings. |
+| `token` | yes | WeChat callback token. |
+| `EncodingAESKey` | yes | WeChat message encryption key. |
+| `AppID` | yes | Official Account app ID. |
+| `AppSecret` | yes | Official Account app secret. |
+| `Mode` | yes | `drop` waits for an in-callback reply; `passive` returns the loading text first and queues the answer for the user's next message. |
+| `LoadingMessage` | no | Only used by `passive` mode. |
+| `api_base_url` | no | Optional API base URL for proxy deployments. |
+
+## Events
+
+| Event | Evidence | Notes |
+| --- | --- | --- |
+| `message.received` | plugin-e2e-ui, unit | Text UI message verified through WeChat Official Account on `dev.rockchin.top`; image and voice webhook payloads are covered by unit tests. |
+| `platform.specific` | unit | Subscribe/menu/etc. native events are emitted as structured `PlatformSpecificEvent`. |
+
+## Common APIs
+
+| API | Evidence | Notes |
+| --- | --- | --- |
+| `reply_message` | unit | Queues/passively returns text through the inbound webhook source event. |
+| `get_message` | plugin-e2e-ui, unit | Cached inbound message retrieved by `EBAEventProbe` platform API sweep. |
+| `get_user_info` | plugin-e2e-ui, unit | Cached inbound sender retrieved by `EBAEventProbe` platform API sweep. |
+| `get_friend_list` | plugin-e2e-ui, unit | Cached inbound sender list retrieved by `EBAEventProbe` platform API sweep. |
+| `call_platform_api` | plugin-e2e-ui, unit | Safe diagnostic actions verified through `get_mode` and `get_cached_response_status`. |
+| `send_message` | not-supported | Official Account customer-service proactive messaging is not implemented by the existing SDK adapter; only webhook reply is supported here. |
+
+## Platform APIs
+
+| Action | Evidence | Notes |
+| --- | --- | --- |
+| `get_mode` | plugin-e2e-ui, unit | Returned `{"mode": "drop", "longer_response": false}` in live probe. |
+| `get_cached_response_status` | plugin-e2e-ui, unit | Returned `{"pending": false}` in live probe. |
+
+## Components
+
+| Receive Component | Evidence | Notes |
+| --- | --- | --- |
+| `Source` | plugin-e2e-ui, unit | Uses `MsgId` and `CreateTime`; live UI text message included `Source`. |
+| `Plain` | plugin-e2e-ui, unit | Live UI text message mapped to `Plain`. |
+| `Image` | unit | `PicUrl` and `MediaId` map to common `Image`. |
+| `Voice` | unit | `MediaId` maps to common `Voice`. |
+| `Unknown` | unit | Unsupported message/event types do not crash. |
+| `At`, `AtAll`, `File`, `Quote`, `Face`, `Forward`, mixed chain | not-supported | WeChat Official Account inbound webhook payloads used by the current SDK do not expose these as common structured components. |
+
+| Send Component | Evidence | Notes |
+| --- | --- | --- |
+| `Plain` | unit | Sent as webhook reply text. |
+| `Image`, `Voice`, `File`, `Quote`, `At`, `AtAll`, `Face`, `Forward`, mixed chain | not-supported | Existing SDK reply path is text XML only; non-text components degrade to readable placeholders in tests and are not declared as supported outbound components. |
+
+## Verification Record
+
+Test date: 2026-05-28
+
+Endpoint/simulator: `dev.rockchin.top` with WeChat desktop client and a real subscribed Official Account conversation. The running EBA test stack used SDK standalone runtime ports `5400/5401`, LangBot from `/home/wgc/LangBotxg/LangBotEbaTest`, and `EBAEventProbe`.
+
+Verified UI message: `EBA officialaccount single probe 2026-05-28 16:53`
+
+Observed event/API evidence:
+
+- `MessageReceived`: `bot_uuid=d7c46880-a9f8-431a-9172-5d3e0d663dbc`, `adapter_name=officialaccount-eba`, `chat_type=private`, `chat_id=ovH9L7OW6hNpWZWvp_NMmypVh26w`, `message_chain=[Source, Plain]`.
+- Common safe APIs through probe platform sweep: `get_message`, `get_user_info`, `get_friend_list`.
+- Platform APIs through `call_platform_api`: `get_mode`, `get_cached_response_status`.
+- `send_message` and outbound component sweep returned explicit `NotSupportedError: send_message:official_account_requires_inbound_webhook_reply`, as expected for this adapter.
+
+Standalone runtime command:
+
+```bash
+cd langbot-plugin-sdk
+uv run python -m langbot_plugin.cli.__init__ rt --debug-only --ws-control-port 5400 --ws-debug-port 5401 --skip-deps-check
+```
+
+Probe plugin: `data/plugins/LangBot__EBAEventProbe` when live credentials are available.
+
+Adapter live probe:
+
+```bash
+uv run python -m py_compile tests/e2e/live_officialaccount_eba_probe.py
+OFFICIALACCOUNT_TOKEN=... OFFICIALACCOUNT_ENCODING_AES_KEY=... OFFICIALACCOUNT_APP_SECRET=... OFFICIALACCOUNT_APP_ID=... uv run python tests/e2e/live_officialaccount_eba_probe.py
+```
+
+Evidence JSONL path: `/home/wgc/LangBotxg/LangBotEbaTest/data/temp/officialaccount_eba_plugin_probe.jsonl` for plugin E2E, or `data/temp/officialaccount_eba_probe.jsonl` for direct adapter live probe.
+
+Destructive operations: none.
+
+Blocked items:
+
+- `plugin-e2e-outbound`: proactive `send_message` is not supported for this adapter; Official Account responses must be produced through the inbound webhook reply window.
+- Inbound image and voice live UI evidence remains pending; webhook conversion is covered by unit tests.

docs/event-based-agents/adapters/qqofficial.md

@@ -0,0 +1,114 @@
+# QQOfficial EBA Adapter
+
+Adapter directory: `src/langbot/pkg/platform/adapters/qqofficial/`
+
+Manifest name: `qqofficial-eba`
+
+Status: partial migration. The EBA adapter structure, manifest, converters, cache-backed safe APIs, platform API map, unit tests, and direct live probe scaffold are in place. A real QQ Official WebSocket bot on `dev.rockchin.top` received an inbound user message and drove LangBot into the normal pipeline path; the response path was blocked by the test environment model service returning `model_not_found` for `deepseek-v3`.
+
+## Config
+
+| Field | Required | Notes |
+| --- | --- | --- |
+| `appid` | yes | QQ Official app ID. |
+| `secret` | yes | QQ Official app secret. |
+| `token` | yes | QQ Official callback token. |
+| `enable-webhook` | yes | Uses LangBot unified webhook when true; otherwise uses the QQ WebSocket gateway. |
+| `enable-stream-reply` | yes | Enables C2C streaming replies when supported by the QQ Official endpoint. |
+| `webhook_url` | no | Generated by LangBot and copied into the QQ Official callback settings in webhook mode. |
+
+## Events
+
+| Event | Evidence | Notes |
+| --- | --- | --- |
+| `message.received` | adapter-live, unit | `C2C_MESSAGE_CREATE`, `DIRECT_MESSAGE_CREATE`, `GROUP_AT_MESSAGE_CREATE`, and `AT_MESSAGE_CREATE` map to common `MessageReceivedEvent`. A real WebSocket-mode QQ Official bot reached the LangBot pipeline on `dev.rockchin.top`; plugin JSONL evidence remains pending. |
+| `platform.specific` | unit, blocked | Unmapped gateway events are emitted as structured `PlatformSpecificEvent`; live evidence is pending. |
+
+## Common APIs
+
+| API | Evidence | Notes |
+| --- | --- | --- |
+| `send_message` | unit, blocked | Sends private C2C, group, and text-only channel messages through the existing QQ Official client. Live outbound UI verification is pending because the test pipeline failed before producing a bot response. |
+| `reply_message` | unit, blocked | Replies using the source `QQOfficialEvent` message ID when available. Live reply was blocked by the test environment model service returning `model_not_found`. |
+| `get_message` | unit | Returns cached inbound `MessageReceivedEvent`. |
+| `get_user_info` | unit | Returns cached inbound sender. |
+| `get_friend_list` | unit | Returns cached private senders. |
+| `get_group_info` | unit | Returns cached group/channel metadata from inbound events. |
+| `get_group_member_info` | unit | Returns cached group sender as a common member. |
+| `get_group_member_list` | unit | Returns cached group members observed by the adapter. |
+| `call_platform_api` | unit, blocked | Safe diagnostic actions are implemented; live calls are pending credentials. |
+
+## Platform APIs
+
+| Action | Evidence | Notes |
+| --- | --- | --- |
+| `check_access_token` | unit, blocked | Calls the existing client token check. |
+| `refresh_access_token` | unit, blocked | Forces token refresh. |
+| `get_gateway_url` | unit, blocked | Fetches the WebSocket gateway URL. |
+| `get_mode` | unit | Returns webhook and stream-reply mode. |
+
+## Components
+
+| Receive Component | Evidence | Notes |
+| --- | --- | --- |
+| `Source` | unit | Uses QQ message/event IDs and timestamp. |
+| `Plain` | unit | Preserves text content. |
+| `At` | unit | Group and channel mention events insert an adapter bot mention marker. |
+| `Image` | unit | QQ image attachment URL is converted to common `Image`; falls back to URL if download fails. |
+| `Unknown` | unit | Unsupported/empty native payloads become `Unknown`. |
+| `Voice`, `File`, `Quote`, `Face`, `Forward`, mixed chain | blocked | Current native parser only exposes text and image attachments; live endpoint behavior still needs verification. |
+
+| Send Component | Evidence | Notes |
+| --- | --- | --- |
+| `Plain` | unit, blocked | Sends through private, group, or channel text APIs. |
+| `At`, `AtAll` | unit, blocked | Converted to readable mention text. |
+| `Image` | unit, blocked | Sends through the QQ Official rich media upload/send path for C2C and group targets. |
+| `Voice` | unit, blocked | Sends through the QQ Official rich media upload/send path for C2C and group targets. |
+| `File` | unit, blocked | Sends through the QQ Official rich media upload/send path for C2C and group targets. |
+| `Quote`, `Forward`, mixed chain | unit, blocked | Flattened to ordered send payloads where possible. |
+| `Face` | not-supported | No common QQ Official face mapping is implemented. |
+
+## Verification Record
+
+Test date: 2026-06-02
+
+Endpoint/simulator: `dev.rockchin.top` with a real QQ Official WebSocket bot (`qqofficial-eba`, bot UUID `80a5560b-52b1-40e7-b7d6-4a2341eb4780`) and LangBot running from `/home/wgc/LangBotxg/LangBotEbaTest`.
+
+Observed evidence:
+
+- The QQ Official WebSocket bot was enabled with `enable-webhook=false`.
+- A real user message reached LangBot and entered the standard pipeline path.
+- The response path stopped at the model layer with `model_not_found` for `deepseek-v3`; this is a model/provider configuration issue, not an adapter conversion failure.
+- `qq-webhook.langbot.dev` was temporarily routed through Caddy to `127.0.0.1:5301` for webhook checks, but the observed EBA bot used WebSocket mode.
+
+Standalone runtime command:
+
+```bash
+cd langbot-plugin-sdk
+uv run python -m langbot_plugin.cli.__init__ rt --debug-only --ws-control-port 5400 --ws-debug-port 5401 --skip-deps-check
+```
+
+Probe plugin: `data/plugins/LangBot__EBAEventProbe` when live credentials are available.
+
+Adapter live probe:
+
+```bash
+uv run python -m py_compile tests/e2e/live_qqofficial_eba_probe.py
+QQOFFICIAL_APPID=... QQOFFICIAL_SECRET=... QQOFFICIAL_TOKEN=... uv run python tests/e2e/live_qqofficial_eba_probe.py
+```
+
+Webhook-mode probe:
+
+```bash
+QQOFFICIAL_APPID=... QQOFFICIAL_SECRET=... QQOFFICIAL_TOKEN=... uv run python tests/e2e/live_qqofficial_eba_probe.py --webhook --host 0.0.0.0 --port 5312
+```
+
+Evidence JSONL path: `data/temp/qqofficial_eba_probe.jsonl` for direct adapter live probe; plugin E2E evidence should use `data/temp/qqofficial_eba_plugin_probe.jsonl`.
+
+Destructive operations: none implemented.
+
+Blocked items:
+
+- `plugin-e2e-ui`: standalone probe plugin JSONL evidence is still pending; the observed live run reached LangBot core/pipeline but was not recorded by the EBA probe plugin.
+- `plugin-e2e-outbound`: waiting for visible QQ client verification of plugin `send_message`/`reply_message` output after a working model/provider is configured.
+- Inbound non-text media and platform lifecycle events require endpoint evidence before they can be marked complete.

docs/event-based-agents/adapters/slack.md

@@ -0,0 +1,84 @@
+# Slack EBA Adapter
+
+## Structure
+
+Slack is migrated into `src/langbot/pkg/platform/adapters/slack/` with the standard EBA adapter layout:
+
+- `adapter.py` owns lifecycle, listener dispatch, unified webhook handling, outbound send/reply, and event caches.
+- `event_converter.py` maps Slack `im` and `app_mention` channel events to `message.received`.
+- `message_converter.py` maps common `MessageChain` components to Slack text fallback and maps inbound Slack text/image payloads back to EBA components.
+- `api_impl.py` provides cache-backed common read APIs.
+- `platform_api.py` declares safe Slack-specific API actions.
+- `manifest.yaml` declares `slack-eba`.
+
+The legacy `src/langbot/pkg/platform/sources/slack.py` adapter is kept unchanged.
+
+## Configuration
+
+| Field | Required | Notes |
+|-------|----------|-------|
+| `webhook_url` | No | Generated by LangBot. Paste it into Slack Event Subscriptions. |
+| `bot_token` | Yes | Slack bot token, usually `xoxb-...`. |
+| `signing_secret` | Yes | Slack app signing secret. |
+
+## Events
+
+| Event | Notes |
+|-------|-------|
+| `message.received` | Emitted for private `im` messages and channel `app_mention` events. Channel messages are mapped to group chats. |
+| `platform.specific` | Reserved for Slack event types that are not converted into common message events. |
+
+## Common APIs
+
+Required:
+
+- `send_message`
+- `reply_message`
+
+Optional:
+
+- `get_message`
+- `get_user_info`
+- `get_friend_list`
+- `get_group_info`
+- `get_group_list`
+- `get_group_member_list`
+- `get_group_member_info`
+- `call_platform_api`
+
+Cache-backed APIs are only available after the relevant inbound event has been observed.
+
+## Platform APIs
+
+| Action | Notes |
+|--------|-------|
+| `get_mode` | Returns webhook mode and configured bot account id. |
+| `auth_test` | Calls Slack `auth.test` with the configured bot token. |
+
+## Known Limits
+
+- Slack file/image outbound is currently represented as text fallback because the existing Slack SDK wrapper only exposes `chat_postMessage`.
+- Inbound channel coverage follows the legacy adapter behavior: only `app_mention` events are treated as group messages.
+- Real live testing requires a public callback URL configured in Slack Event Subscriptions.
+
+## Verification
+
+Local mocked unit coverage validates manifest parity, event conversion, legacy listener compatibility, cache-backed APIs, send/reply routing, and declared platform APIs.
+
+Plugin E2E evidence was captured on June 2, 2026 against `dev.rockchin.top` with Slack private DM input and `EBAEventProbe` through the standalone runtime.
+
+Evidence file: `/home/wgc/LangBotxg/LangBotEbaTest/data/temp/slack_eba_plugin_probe.jsonl`.
+
+Observed:
+
+- Real Slack private text produced `MessageReceived` with `adapter_name=slack-eba`, `Source + Plain`, private chat type, and filled `bot_uuid`.
+- Safe common APIs passed: `get_message`, `get_user_info`, `get_friend_list`.
+- Outbound component fallback sweep passed through `send_message`: plain/at/face, image, quote, file, and forward.
+- Declared Slack platform APIs passed: `get_mode`, `auth_test`.
+
+Still pending:
+
+- Channel `app_mention` plugin E2E.
+- Real inbound Slack file/image UI evidence.
+
+Live probe scaffold: `tests/e2e/live_slack_eba_probe.py`.

docs/event-based-agents/adapters/telegram.md

@@ -0,0 +1,139 @@
+# Telegram EBA Adapter
+
+## Status
+
+Telegram has been migrated to the EBA adapter directory:
+
+```text
+src/langbot/pkg/platform/adapters/telegram/
+├── adapter.py
+├── api_impl.py
+├── event_converter.py
+├── manifest.yaml
+├── message_converter.py
+├── platform_api.py
+└── types.py
+```
+
+The adapter is registered as `telegram-eba`.
+
+## Configuration
+
+| Field | Required | Default | Description |
+|-------|----------|---------|-------------|
+| `token` | Yes | `""` | Telegram Bot API token from BotFather. |
+| `markdown_card` | No | `true` | Whether to render Markdown card style replies. |
+| `enable-stream-reply` | Yes | `false` | Whether to use Telegram streaming reply mode. |
+
+## Events
+
+Telegram declares these EBA events:
+
+- `message.received`
+- `message.edited`
+- `message.reaction`
+- `group.member_joined`
+- `group.member_left`
+- `group.member_banned`
+- `bot.invited_to_group`
+- `bot.removed_from_group`
+- `bot.muted`
+- `bot.unmuted`
+- `platform.specific`
+
+`platform.specific` is currently used for Telegram-only callback and chat-member update payloads that do not yet have a more specific common event type.
+
+## Common APIs
+
+| API | Status | Notes |
+|-----|--------|-------|
+| `send_message` | Supported | Supports text, image, file, and mixed message chains. |
+| `reply_message` | Supported | Supports quoted replies through the original message event. |
+| `edit_message` | Supported | Uses Telegram message editing APIs. |
+| `delete_message` | Supported | Deletes messages where bot permissions allow it. |
+| `forward_message` | Supported | Forwards a message between Telegram chats. |
+| `get_group_info` | Supported | Uses Telegram chat metadata. |
+| `get_group_member_list` | Supported | Telegram only exposes administrators through the Bot API; this returns the available member set. |
+| `get_group_member_info` | Supported | Maps Telegram member status to EBA member roles. |
+| `get_user_info` | Supported | Uses Telegram `get_chat` for user chat metadata. |
+| `upload_file` | Not supported | Telegram has no standalone upload endpoint; files are uploaded as part of messages. The adapter raises `NotSupportedError`. |
+| `get_file_url` | Supported | Returns the Bot API file URL. Test output redacts the bot token. |
+| `mute_member` | Supported | Requires a supergroup and bot moderation permission. |
+| `unmute_member` | Supported | Uses current `telegram.ChatPermissions` fields. |
+| `kick_member` | Supported | Destructive; should only be run against disposable users/bots in tests. |
+| `leave_group` | Supported | Destructive; should run at the end of a live test. |
+| `call_platform_api` | Supported | See below. |
+
+## Platform-Specific APIs
+
+`call_platform_api(action, params)` supports:
+
+- `pin_message`
+- `unpin_message`
+- `unpin_all_messages`
+- `get_chat_administrators`
+- `set_chat_title`
+- `set_chat_description`
+- `get_chat_member_count`
+- `send_chat_action`
+- `create_chat_invite_link`
+- `answer_callback_query`
+
+## Live Test Record
+
+The live probe is:
+
+```bash
+uv run python tests/e2e/live_telegram_eba_probe.py --help
+```
+
+It supports private chat tests, group/supergroup tests, moderation tests, destructive tests, and a callback-only mode.
+
+Verified on May 7, 2026:
+
+- Private chat message APIs: send, reply, edit, delete, forward.
+- Private chat media APIs: image/file sending and `get_file_url`.
+- User API: `get_user_info`.
+- Supergroup APIs: group info, member list, member info, administrators, member count, invite link.
+- Supergroup mutation APIs: pin, unpin, unpin all, set title, restore title, set description, restore description.
+- Moderation APIs: mute and unmute against a non-owner target bot.
+- Destructive APIs: kick a disposable target bot, then make the test bot leave the test group.
+- Event conversion observed for `message.received`, `group.member_banned`, `group.member_left`, `bot.removed_from_group`, and Telegram-specific chat-member updates.
+
+The test fixed one real compatibility issue: `unmute_member` previously used Telegram's removed `can_send_media_messages` permission field. It now uses the split media permission fields required by current `python-telegram-bot`.
+
+## Standalone Runtime Plugin E2E Record
+
+Verified on May 10, 2026 with `EBAEventProbe`, SDK standalone runtime, Telegram Lite, `@rockchinq_bot`, and `Rock'sBotGroup`.
+
+Evidence:
+
+- Private chat JSONL: `data/temp/telegram-plugin-e2e-rerun.jsonl`
+- Group chat JSONL: `data/temp/telegram-plugin-e2e-group.jsonl`
+- Private media JSONL: `data/temp/telegram-plugin-e2e-media-ui.jsonl`
+
+Observed and verified:
+
+- `MessageReceived` reached the plugin with `bot_uuid=eba-telegram-live`, `adapter_name=telegram`, common sender/chat fields, and common `MessageChain` content.
+- `BotInvitedToGroup` reached the plugin after adding the bot to `Rock'sBotGroup`.
+- SDK API calls succeeded: `get_langbot_version`, `get_bots`, `get_bot_info`, `send_message`, plugin storage, workspace storage, `list_plugins_manifest`, `list_commands`, `list_tools`, and `list_knowledge_bases`.
+- Outbound component sweep succeeded in private and group chats: plain text, mention text/equivalent, base64 image, quoted reply, file/document, and flattened forward fallback. Group mode also covered `AtAll` fallback behavior.
+- Real Telegram Lite private-chat inbound media was verified through the plugin path: a sent document arrived as common `File`, and a sent photo arrived as common `Image`.
+- Telegram platform API sweep succeeded for safe group actions: `get_chat_administrators`, `get_chat_member_count`, and `send_chat_action`.
+- Common group/user APIs succeeded in group mode: `get_user_info`, `get_group_info`, `get_group_member_list`, and `get_group_member_info`.
+
+Documented limits in this E2E run:
+
+- Real Telegram UI inbound voice, sticker/emoji-as-common-component, and reply/quote messages were not completed in the plugin E2E evidence.
+- `get_message`, `get_friend_list`, and `get_group_list` are not supported by this Telegram adapter.
+- Mutating/destructive Telegram-specific actions such as pin/unpin, title/description changes, invite-link creation, moderation, kick, and leave were not repeated in the plugin run. They remain opt-in live-probe cases.
+- Telegram does not expose a portable common `Face` component for native sticker/emoji semantics in the current adapter.
+
+## Notes for Future Adapters
+
+Telegram is the reference implementation for:
+
+- Keeping platform-specific actions behind `call_platform_api`.
+- Treating unsupported common APIs as explicit `NotSupportedError`.
+- Marking destructive live test operations behind CLI flags.
+- Redacting access tokens from live probe output.

docs/event-based-agents/adapters/wecom.md

@@ -0,0 +1,130 @@
+# WeCom EBA Adapter
+
+## Status
+
+WeCom application messages now have an EBA adapter directory:
+
+```text
+src/langbot/pkg/platform/adapters/wecom/
+├── adapter.py
+├── api_impl.py
+├── event_converter.py
+├── manifest.yaml
+├── message_converter.py
+├── platform_api.py
+└── types.py
+```
+
+The adapter is registered as `wecom-eba`.
+
+This record covers the regular WeCom application-message adapter. WeCom AI Bot (`wecombot-eba`) uses a different protocol flow and is documented separately in `wecombot.md`. WeCom Customer Service (`wecomcs`) remains a separate follow-up migration.
+
+## Configuration
+
+| Field | Required | Default | Description |
+|-------|----------|---------|-------------|
+| `webhook_url` | No | `""` | Unified webhook URL copied into the WeCom application callback settings. |
+| `corpid` | Yes | `""` | WeCom corporate ID. |
+| `secret` | Yes | `""` | WeCom application secret. |
+| `token` | Yes | `""` | WeCom callback token. |
+| `EncodingAESKey` | Yes | `""` | WeCom callback encryption key. |
+| `contacts_secret` | No | `""` | Contacts secret for contact-list based helper APIs. |
+| `api_base_url` | No | `https://qyapi.weixin.qq.com/cgi-bin` | WeCom API base URL, overrideable for proxy/private-network deployments. |
+
+## Events
+
+WeCom declares these EBA events:
+
+- `message.received`
+- `platform.specific`
+
+`message.received` currently covers text and image application callbacks. Other WeCom callback types are surfaced as `platform.specific` so plugins can inspect the raw structured payload without crashing the common message path.
+
+## Common APIs
+
+| API | Status | Notes |
+|-----|--------|-------|
+| `send_message` | Supported | Private/person target only. `target_id` must be `user_id|agent_id`. Supports text, image, voice, file, flattened forward, and quote fallback. |
+| `reply_message` | Supported | Replies to the original WeCom sender and application agent from `source_platform_object`. |
+| `get_message` | Supported from cache | Returns cached inbound `MessageReceivedEvent` by message ID. |
+| `get_user_info` | Supported | Uses cached event users first, then WeCom `user/get`. |
+| `get_friend_list` | Partial | Returns users seen by this adapter instance. Full contacts listing is not declared as common coverage. |
+| `call_platform_api` | Supported | See below. |
+| `edit_message` | Not supported | WeCom application messages do not expose a general edit endpoint for sent messages. |
+| `delete_message` | Not supported | WeCom application messages do not expose a general delete endpoint for sent messages. |
+| `get_group_info` / member APIs | Not supported | Regular WeCom application callbacks handled here are private user messages, not group-chat bot messages. |
+| `upload_file` / `get_file_url` | Not supported as common APIs | WeCom media upload is used internally while sending image/voice/file components; no portable standalone common file URL is exposed. |
+
+## Platform-Specific APIs
+
+`call_platform_api(action, params)` supports:
+
+- `check_access_token`
+- `refresh_access_token`
+- `get_user_info`
+- `send_to_all`
+
+`send_to_all` requires a configured `contacts_secret` with suitable contact visibility and should be treated as a broad-send operation in live testing.
+
+## Unit Verification
+
+Covered by:
+
+```bash
+uv run pytest tests/unit_tests/platform/test_wecom_eba_adapter.py
+```
+
+The unit tests cover:
+
+- Manifest events/APIs/platform actions match adapter declarations.
+- Outbound component conversion for text, image, voice, file, quote fallback, and byte-safe text splitting.
+- Text callback conversion to `MessageReceivedEvent`.
+- Legacy `FriendMessage` compatibility.
+- EBA listener dispatch and inbound message/user cache.
+- `send_message`, `reply_message`, and safe platform API dispatch against a mocked WeCom client.
+
+## Standalone Runtime Plugin E2E Record
+
+Verified on May 27, 2026 with `EBAEventProbe`, SDK standalone runtime, LangBot core, and a real WeCom desktop client against the server test environment.
+
+```bash
+cd langbot-plugin-sdk
+uv run python -m langbot_plugin.cli.__init__ rt --debug-only --ws-control-port 5400 --ws-debug-port 5401 --skip-deps-check
+
+cd LangBot
+uv run main.py --standalone-runtime
+
+cd data/plugins/LangBot__EBAEventProbe
+EBA_PROBE_API=1 EBA_PROBE_COMPONENT_SWEEP=1 EBA_PROBE_PLATFORM_API=1 \
+uv --project /absolute/path/to/langbot-plugin-sdk run python -m langbot_plugin.cli.__init__ run
+```
+
+Evidence:
+
+- JSONL: `data/temp/wecom_eba_plugin_probe.jsonl`
+- Bot: `wecom-eba`
+- Client: real WeCom desktop client
+- Environment: `dev.rockchin.top` test server
+
+Observed and verified:
+
+- A real private WeCom user message reached the plugin as `MessageReceived` with `adapter_name=wecom-eba`, common sender/chat fields, and `Source + Plain`.
+- SDK API calls succeeded through the standalone runtime, including `get_langbot_version`, `get_bots`, `get_bot_info`, `send_message`, plugin/workspace storage, and manifest/list APIs.
+- Safe adapter API checks succeeded through the plugin path for cached message/user data and declared safe platform API actions.
+
+Still required for stricter acceptance:
+
+- Send a private image and confirm common `Image` reaches the plugin.
+- Have the plugin call `send_message` and `reply_message` for text and one media component, then verify the WeCom client receives the bot output.
+- Exercise `send_to_all` only with a disposable visible-contact scope.
+- Trigger one non-text/image callback, if available, and confirm it becomes `PlatformSpecificEventReceived`.
+
+## Current Acceptance
+
+Current status is **partial EBA acceptance**.
+
+Blocked items:
+
+- Real inbound image/voice/file evidence was not completed in this run.
+- Inbound voice/file callback parsing is not present in the legacy `WecomClient.get_message()` path, so the EBA adapter does not claim those receive components yet.
+- Group/member/moderation APIs do not apply to this regular WeCom application-message adapter.

docs/event-based-agents/adapters/wecombot.md

@@ -0,0 +1,148 @@
+# WeComBot EBA Adapter
+
+## Status
+
+WeCom AI Bot now has an EBA adapter directory:
+
+```text
+src/langbot/pkg/platform/adapters/wecombot/
+├── adapter.py
+├── api_impl.py
+├── event_converter.py
+├── manifest.yaml
+├── message_converter.py
+├── platform_api.py
+└── types.py
+```
+
+The adapter is registered as `wecombot-eba`.
+
+This is separate from regular WeCom internal applications (`wecom-eba`). WeComBot supports WebSocket long connection mode, which does not require a webhook URL. Webhook mode remains available when `enable-webhook=true`.
+
+## Configuration
+
+| Field | Required | Default | Description |
+|-------|----------|---------|-------------|
+| `BotId` | Yes for WebSocket mode | `""` | WeCom AI Bot ID. |
+| `robot_name` | Yes | `""` | Bot display name used to strip bot mentions from incoming group text. |
+| `enable-webhook` | Yes | `false` | `false` uses WebSocket long connection mode; `true` uses webhook callback mode. |
+| `webhook_url` | No | `""` | Unified webhook URL, only needed when webhook mode is enabled. |
+| `Secret` | Yes for WebSocket mode | `""` | WeCom AI Bot secret for long connection mode. |
+| `Corpid` | Yes for webhook mode | `""` | WeCom corporate ID for webhook callback mode. |
+| `Token` | Yes for webhook mode | `""` | WeCom callback token. |
+| `EncodingAESKey` | Yes for webhook mode; optional for WebSocket media decrypt | `""` | Message encryption/decryption key. |
+| `enable-stream-reply` | No | `true` | Enables WeComBot streaming replies. |
+
+## Events
+
+WeComBot declares these EBA events:
+
+- `message.received`
+- `feedback.received`
+- `platform.specific`
+
+`message.received` covers private and group messages from the WeComBot SDK. `feedback.received` covers WeComBot like/dislike feedback callbacks. Native SDK events without a common EBA equivalent are emitted as `platform.specific`.
+
+## Common APIs
+
+| API | Status | Notes |
+|-----|--------|-------|
+| `send_message` | Supported in WebSocket mode | Sends proactive markdown/text to a person or group chat ID. Webhook mode raises `NotSupportedError` because the platform callback flow has no proactive send path here. |
+| `reply_message` | Supported | Replies through native `req_id` in WebSocket mode or stream finalization/cache in webhook mode. |
+| `get_message` | Supported from cache | Returns cached inbound `MessageReceivedEvent` by message ID. |
+| `get_user_info` | Supported from cache | WeComBot events carry user info; no full user lookup endpoint is declared. |
+| `get_friend_list` | Partial | Returns users observed by this adapter instance. |
+| `get_group_info` | Supported from cache | Returns groups observed from inbound group messages. |
+| `get_group_member_info` | Supported from cache | Returns observed sender/group-member pairs. |
+| `get_group_member_list` | Partial | Returns observed members for the cached group only. |
+| `call_platform_api` | Supported | See below. |
+| `edit_message` / `delete_message` / `forward_message` | Not supported | WeComBot does not expose portable common APIs for these operations in the current SDK wrapper. |
+| `upload_file` / `get_file_url` | Not supported as common APIs | Media is represented inside messages; no portable standalone file upload/URL API is declared. |
+| moderation / leave APIs | Not supported | WeComBot does not expose equivalent common moderation operations through this adapter. |
+
+## Platform-Specific APIs
+
+`call_platform_api(action, params)` supports:
+
+- `is_websocket_mode`
+- `get_stream_session_status`
+- `send_markdown`
+
+`send_markdown` is only available in WebSocket mode.
+
+## Unit Verification
+
+Covered by:
+
+```bash
+PYTHONPATH=/Users/wangqiang/code/python/langbot-plugin-sdk/src uv run pytest tests/unit_tests/platform/test_wecombot_eba_adapter.py
+```
+
+The unit tests cover:
+
+- Manifest events/APIs/platform actions match adapter declarations.
+- Outbound common components flatten to WeComBot markdown/text.
+- Private and group native events become `MessageReceivedEvent`.
+- Inbound image, file, voice, and quote components map to common `MessageChain`.
+- Legacy `FriendMessage`/`GroupMessage` compatibility.
+- EBA listener dispatch, message/user/group/member cache, reply, send, streaming chunk, feedback, and platform API calls.
+
+## Live Probe
+
+The direct adapter probe is:
+
+```bash
+PYTHONPATH=/absolute/path/to/langbot-plugin-sdk/src uv run python tests/e2e/live_wecombot_eba_probe.py --help
+```
+
+Default mode is WebSocket long connection and requires:
+
+- `WECOMBOT_BOT_ID`
+- `WECOMBOT_SECRET`
+- `WECOMBOT_ROBOT_NAME`
+- optional `WECOMBOT_ENCODING_AES_KEY`
+
+Webhook mode uses `--webhook` and requires:
+
+- `WECOMBOT_TOKEN`
+- `WECOMBOT_ENCODING_AES_KEY`
+- `WECOMBOT_CORPID`
+
+The probe writes JSONL evidence to `data/temp/wecombot_eba_live_probe.jsonl`, waits for a real WeComBot message, records common EBA event fields and message components, then runs safe cached/common/platform API checks.
+
+## Standalone Runtime Plugin E2E Record
+
+Verified on May 27, 2026 with `EBAEventProbe`, SDK standalone runtime, LangBot core, and the real WeCom desktop client in a WeCom AI Bot private chat.
+
+Evidence:
+
+- JSONL: `data/temp/wecombot_eba_plugin_probe.jsonl`
+- Bot UUID: `9f5d4125-7b6d-4c98-8ca2-111111111111`
+- Adapter: `wecombot-eba`
+- Client: real WeCom desktop client, private `LangBot` BOT chat
+- Mode: WebSocket long connection (`enable-webhook=false`)
+
+Observed and verified:
+
+- A real user-side message reached the plugin as `MessageReceived` with `adapter_name=wecombot-eba`, common sender/chat fields, and `Source + Plain`.
+- SDK API calls succeeded through the standalone runtime: `get_langbot_version`, `get_bots`, `get_bot_info`, `send_message`, plugin/workspace storage, manifest/list APIs, and safe cached common platform APIs.
+- Outbound component sweep was visible in the WeCom client and returned `errcode=0`: plain/mention/face fallback, base64 image marker, quote fallback, file marker, and flattened forward fallback.
+- Declared WeComBot platform APIs succeeded through `plugin.call_platform_api`: `is_websocket_mode`, `get_stream_session_status`, and `send_markdown`.
+- The `send_markdown` platform API produced visible bot output in the WeCom client.
+
+Not completed:
+
+- Clicking the visible WeCom AI feedback button did not produce a `FeedbackReceived` JSONL entry in this run, so `feedback.received` remains unverified at plugin E2E level.
+- Group chat inbound and group cache/member coverage still need a real group-side trigger.
+- Real inbound image/file/voice from the WeCom client was not exercised.
+
+## Current Acceptance
+
+Current status is **partial EBA acceptance**.
+
+Blocked or limited items:
+
+- `feedback.received` is implemented and unit-covered, but real plugin E2E feedback evidence was not observed from the desktop client click.
+- Outbound image/voice/file are flattened as textual markers because the WeComBot SDK reply/proactive path used here is markdown/text oriented.
+- Group member APIs are cache-backed and only know members observed in received messages.
+- Destructive or moderation APIs are not declared because the current WeComBot protocol surface does not provide safe common equivalents.

docs/event-based-agents/adapters/wecomcs.md

@@ -0,0 +1,161 @@
+# WeCom Customer Service EBA Adapter
+
+## Status
+
+WeCom Customer Service now has an EBA adapter directory:
+
+```text
+src/langbot/pkg/platform/adapters/wecomcs/
+├── adapter.py
+├── api_impl.py
+├── event_converter.py
+├── manifest.yaml
+├── message_converter.py
+├── platform_api.py
+└── types.py
+```
+
+The adapter is registered as `wecomcs-eba`. It is separate from regular WeCom application messages (`wecom-eba`) and WeCom AI Bot (`wecombot-eba`).
+
+## Configuration
+
+| Field | Required | Default | Description |
+|-------|----------|---------|-------------|
+| `webhook_url` | No | `""` | Unified webhook URL copied into the WeCom Customer Service callback settings. |
+| `corpid` | Yes | `""` | WeCom corporate ID. |
+| `secret` | Yes | `""` | Customer Service secret used for access tokens. |
+| `token` | Yes | `""` | Customer Service callback token. |
+| `EncodingAESKey` | Yes | `""` | Customer Service callback encryption key. |
+| `api_base_url` | No | `https://qyapi.weixin.qq.com/cgi-bin` | WeCom API base URL, overrideable for proxy/private-network deployments. |
+
+## Events
+
+| Event | Status | Notes |
+|-------|--------|-------|
+| `message.received` | Plugin E2E UI covered for text | Text, image, file, and voice payloads convert to common EBA message components in unit tests. Real WeChat customer-side UI text reached `EBAEventProbe` on May 27, 2026. |
+| `platform.specific` | Unit covered | Non-message or unknown Customer Service payloads become structured `PlatformSpecificEvent` records. |
+
+## Common APIs
+
+| API | Status | Notes |
+|-----|--------|-------|
+| `send_message` | Plugin E2E outbound covered | Private/person target only. `target_id` must be `external_userid|open_kfid`. Text and image are implemented; voice/file are explicitly unsupported. |
+| `reply_message` | Plugin E2E partial | Replies through Customer Service `kf/send_msg` using the original `source_platform_object`. The pipeline reply path reached the send API, but the dev account later hit WeCom `95001 send msg count limit`. |
+| `get_message` | Plugin E2E covered from cache | Returns cached inbound `MessageReceivedEvent` by message ID. |
+| `get_user_info` | Plugin E2E covered | Uses cached event users first, then Customer Service `customer/batchget`. |
+| `get_friend_list` | Plugin E2E covered, partial | Returns customer users seen by this adapter instance. |
+| `call_platform_api` | Unit covered | See platform-specific APIs below. |
+| `edit_message` / `delete_message` | Not supported | WeCom Customer Service does not expose a general edit/delete endpoint for bot-sent messages in this adapter. |
+| Group/member/moderation APIs | Not supported | Customer Service conversations handled here are private customer sessions, not group chats. |
+| `upload_file` / `get_file_url` | Not supported | Media upload is used internally for outbound image; no portable file URL common API is exposed. |
+
+## Platform-Specific APIs
+
+| Action | Status | Notes |
+|--------|--------|-------|
+| `check_access_token` | Unit covered | Checks whether the current access token is present. |
+| `refresh_access_token` | Unit covered | Refreshes the Customer Service access token. |
+| `get_customer_info` | Unit covered | Calls Customer Service customer lookup by `external_userid`. |
+
+## Message Components
+
+Receive:
+
+| Component | Status | Notes |
+|-----------|--------|-------|
+| `Source` | Unit covered | Uses Customer Service `msgid` and `send_time`. |
+| `Plain` | Unit covered | Text payload content is preserved. |
+| `Image` | Unit covered | Uses the base64 data URL produced by the existing SDK image download path. |
+| `Voice` | Unit covered | Maps exposed voice media ID to common `Voice.voice_id`; live UI evidence pending. |
+| `File` | Unit covered | Maps exposed file media ID/name/size to common `File`; live UI evidence pending. |
+| `Quote`, `At`, `AtAll`, `Face`, `Forward` | Not supported inbound | The current Customer Service SDK event model does not expose these as structured inbound fields. |
+| `Unknown` | Unit covered | Unsupported message types become `Unknown` in message conversion or `platform.specific` at event level. |
+
+Send:
+
+| Component | Status | Notes |
+|-----------|--------|-------|
+| `Plain` | Plugin E2E outbound covered | Sends through `kf/send_msg` text. |
+| `Image` | Plugin E2E outbound covered | Uploads media as WeCom image media and sends through `kf/send_msg` image. |
+| `Quote`, `At`, `AtAll`, `Forward` | Unit covered fallback, live partially blocked | Flattened to text where possible. In the May 27 sweep, later text sends hit WeCom `95001 send msg count limit` after the successful text/image sends. |
+| `Voice`, `File`, `Face` | Not supported | The adapter raises `NotSupportedError`; no tested Customer Service send path is implemented. |
+
+## Unit Verification
+
+Covered by:
+
+```bash
+PYTHONPATH=/Users/wangqiang/code/python/langbot-plugin-sdk/src uv run pytest tests/unit_tests/platform/test_wecomcs_eba_adapter.py
+```
+
+Result on May 27, 2026: `10 passed`.
+
+The local `PYTHONPATH` is required in this workspace because the installed SDK package in the LangBot venv does not contain the newer `langbot_plugin.api.entities.builtin.platform.errors` module; the existing EBA adapter tests need the same SDK override.
+
+## Live Probe
+
+Auxiliary direct adapter probe:
+
+```bash
+PYTHONPATH=/path/to/langbot-plugin-sdk/src uv run python -m py_compile tests/e2e/live_wecomcs_eba_probe.py
+
+WECOMCS_CORPID=... \
+WECOMCS_SECRET=... \
+WECOMCS_TOKEN=... \
+WECOMCS_ENCODING_AES_KEY=... \
+PYTHONPATH=/path/to/langbot-plugin-sdk/src \
+uv run python tests/e2e/live_wecomcs_eba_probe.py \
+  --path /wecomcs/callback \
+  --log data/temp/wecomcs_eba_live_probe.jsonl
+```
+
+This probe is diagnostic only. Final EBA acceptance still requires the standalone SDK runtime plus `EBAEventProbe` plugin path.
+
+## Standalone Runtime Plugin E2E Record
+
+Completed partial plugin E2E on May 27, 2026 against `dev.rockchin.top` and the WeChat customer-side UI entry `微信 -> 客服消息 -> 浪波智能客服`.
+
+Evidence:
+
+- Server JSONL: `/home/wgc/LangBotxg/LangBotEbaTest/data/temp/wecomcs_eba_plugin_probe.jsonl`
+- Trigger text: `EBA wecomcs dedupe probe 2026-05-27`
+- `bot_uuid`: `cc810d2c-91f3-4f92-8f27-e1bf9f7b6cb4`
+- `adapter_name`: `wecomcs-eba`
+- Observed common event: `MessageReceived`, `event.type=message.received`
+- Observed message chain: `Source + Plain`
+- Observed chat: `chat_type=private`, `chat_id=external_userid|open_kfid`
+- Observed sender: customer `User` with nickname/avatar from Customer Service lookup
+- Plugin API probe: `send_message`, `get_message`, `get_user_info`, `get_friend_list`, plugin/workspace storage, and manifest/list APIs succeeded
+- Component sweep: outbound `Plain` and `Image` succeeded; `Face` and `File` returned explicit `NotSupportedError`; later quote/forward fallback sends were blocked by WeCom `95001 send msg count limit`
+
+Command shape used:
+
+```bash
+cd langbot-plugin-sdk
+uv run python -m langbot_plugin.cli.__init__ rt --debug-only --ws-control-port 5400 --ws-debug-port 5401 --skip-deps-check
+
+cd LangBot
+PYTHONPATH=/absolute/path/to/langbot-plugin-sdk/src uv run main.py --standalone-runtime
+
+cd data/plugins/LangBot__EBAEventProbe
+DEBUG_RUNTIME_WS_URL=ws://127.0.0.1:5401/plugin/ws \
+EBA_PROBE_LOG=/absolute/path/to/LangBot/data/temp/wecomcs_eba_plugin_probe.jsonl \
+EBA_PROBE_API=1 \
+EBA_PROBE_COMPONENT_SWEEP=1 \
+EBA_PROBE_PLATFORM_API=1 \
+uv --project /absolute/path/to/langbot-plugin-sdk run python -m langbot_plugin.cli.__init__ run
+```
+
+Required real UI trigger: send a Customer Service message from the WeCom/WeChat customer-side UI to the configured `dev.rockchin.top` Customer Service account.
+
+## Current Acceptance
+
+Current status is **partial EBA acceptance**.
+
+Blocked or pending items:
+
+- Inbound UI media (`Image`, `Voice`, `File`) was not sent from the real WeChat customer UI during this run, so receive-side media remains unit-covered only.
+- Pipeline auto-reply reached `kf/send_msg`, but the test account hit WeCom `95001 send msg count limit` after successful plugin outbound text/image sends. This is recorded as an account/platform rate-limit block, not a conversion or API-shape failure.
+- The current `EBAEventProbe` run did not call the adapter-specific `call_platform_api` actions (`check_access_token`, `refresh_access_token`, `get_customer_info`); the platform API map remains unit-covered.
+- Inbound voice/file depends on whether the real Customer Service callback plus `sync_msg` endpoint returns those fields in the shape the local SDK models.
+- Group, member, edit, delete, moderation, and standalone file URL APIs are intentionally not declared because this Customer Service protocol path does not provide tested common equivalents.

main.py

@@ -1,472 +1,3 @@
-import importlib
-import json
-import os
-import shutil
-import threading
-import time
-
-import logging
-import sys
-import traceback
-
-sys.path.append(".")
-
-from pkg.utils.log import init_runtime_log_file, reset_logging
-
-try:
-    import colorlog
-except ImportError:
-    # 尝试安装
-    import pkg.utils.pkgmgr as pkgmgr
-    try:
-        pkgmgr.install_requirements("requirements.txt")
-        pkgmgr.install_upgrade("websockets")
-        import colorlog
-    except ImportError:
-        print("依赖不满足,请查看 https://github.com/RockChinQ/qcg-installer/issues/15")
-        sys.exit(1)
-import colorlog
-
-import requests
-import websockets.exceptions
-from urllib3.exceptions import InsecureRequestWarning
-import pkg.utils.context
-
-
-# 是否使用override.json覆盖配置
-# 仅在启动时提供 --override 或 -r 参数时生效
-use_override = False
-
-
-def init_db():
-    import pkg.database.manager
-    database = pkg.database.manager.DatabaseManager()
-
-    database.initialize_database()
-
-
-def ensure_dependencies():
-    import pkg.utils.pkgmgr as pkgmgr
-    pkgmgr.run_pip(["install", "openai", "Pillow", "nakuru-project-idk", "CallingGPT", "tiktoken", "--upgrade",
-                    "-i", "https://pypi.tuna.tsinghua.edu.cn/simple",
-                    "--trusted-host", "pypi.tuna.tsinghua.edu.cn"])
-
-
-known_exception_caught = False
-
-
-def override_config():
-    import config
-    # 检查override.json覆盖
-    if os.path.exists("override.json") and use_override:
-        override_json = json.load(open("override.json", "r", encoding="utf-8"))
-        overrided = []
-        for key in override_json:
-            if hasattr(config, key):
-                setattr(config, key, override_json[key])
-                # logging.info("覆写配置[{}]为[{}]".format(key, override_json[key]))
-                overrided.append(key)
-            else:
-                logging.error("无法覆写配置[{}]为[{}]，该配置不存在，请检查override.json是否正确".format(key, override_json[key]))
-        if len(overrided) > 0:
-            logging.info("已根据override.json覆写配置项: {}".format(", ".join(overrided)))
-
-
-# 临时函数，用于加载config和上下文，未来统一放在config类
-def load_config():
-    logging.info("检查config模块完整性.")
-    # 完整性校验
-    non_exist_keys = []
-
-    is_integrity = True
-    config_template = importlib.import_module('config-template')
-    config = importlib.import_module('config')
-    for key in dir(config_template):
-        if not key.startswith("__") and not hasattr(config, key):
-            setattr(config, key, getattr(config_template, key))
-            # logging.warning("[{}]不存在".format(key))
-            non_exist_keys.append(key)
-            is_integrity = False
-    
-    if not is_integrity:
-        logging.warning("以下配置字段不存在: {}".format(", ".join(non_exist_keys)))
-
-    # 检查override.json覆盖
-    override_config()
-
-    if not is_integrity:
-        logging.warning("以上不存在的配置已被设为默认值，您可以依据config-template.py检查config.py，将在3秒后继续启动... ")
-        time.sleep(3)
-
-    # 存进上下文
-    pkg.utils.context.set_config(config)
-
-
-def complete_tips():
-    """根据tips-custom-template模块补全tips模块的属性"""
-    non_exist_keys = []
-
-    is_integrity = True
-    logging.info("检查tips模块完整性.")
-    tips_template = importlib.import_module('tips-custom-template')
-    tips = importlib.import_module('tips')
-    for key in dir(tips_template):
-        if not key.startswith("__") and not hasattr(tips, key):
-            setattr(tips, key, getattr(tips_template, key))
-            # logging.warning("[{}]不存在".format(key))
-            non_exist_keys.append(key)
-            is_integrity = False
-
-    if not is_integrity:
-        logging.warning("以下提示语字段不存在: {}".format(", ".join(non_exist_keys)))
-        logging.warning("tips模块不完整，您可以依据tips-custom-template.py检查tips.py")
-        logging.warning("以上配置已被设为默认值，将在3秒后继续启动... ")
-        time.sleep(3)
-
-
-def start(first_time_init=False):
-    """启动流程，reload之后会被执行"""
-
-    global known_exception_caught
-    import pkg.utils.context
-
-    config = pkg.utils.context.get_config()
-    # 更新openai库到最新版本
-    if not hasattr(config, 'upgrade_dependencies') or config.upgrade_dependencies:
-        print("正在更新依赖库，请等待...")
-        if not hasattr(config, 'upgrade_dependencies'):
-            print("这个操作不是必须的,如果不想更新,请在config.py中添加upgrade_dependencies=False")
-        else:
-            print("这个操作不是必须的,如果不想更新,请在config.py中将upgrade_dependencies设置为False")
-        try:
-            ensure_dependencies()
-        except Exception as e:
-            print("更新openai库失败:{}, 请忽略或自行更新".format(e))
-
-    known_exception_caught = False
-    try:
-        try:
-
-            sh = reset_logging()
-            pkg.utils.context.context['logger_handler'] = sh
-
-            # 检查是否设置了管理员
-            if not (hasattr(config, 'admin_qq') and config.admin_qq != 0):
-                # logging.warning("未设置管理员QQ,管理员权限指令及运行告警将无法使用,如需设置请修改config.py中的admin_qq字段")
-                while True:
-                    try:
-                        config.admin_qq = int(input("未设置管理员QQ,管理员权限指令及运行告警将无法使用,请输入管理员QQ号: "))
-                        # 写入到文件
-
-                        # 读取文件
-                        config_file_str = ""
-                        with open("config.py", "r", encoding="utf-8") as f:
-                            config_file_str = f.read()
-                        # 替换
-                        config_file_str = config_file_str.replace("admin_qq = 0", "admin_qq = " + str(config.admin_qq))
-                        # 写入
-                        with open("config.py", "w", encoding="utf-8") as f:
-                            f.write(config_file_str)
-
-                        print("管理员QQ已设置，如需修改请修改config.py中的admin_qq字段")
-                        time.sleep(4)
-                        break
-                    except ValueError:
-                        print("请输入数字")
-
-            import pkg.openai.manager
-            import pkg.database.manager
-            import pkg.openai.session
-            import pkg.qqbot.manager
-            import pkg.openai.dprompt
-            import pkg.qqbot.cmds.aamgr
-            
-            try:
-                pkg.openai.dprompt.register_all()
-                pkg.qqbot.cmds.aamgr.register_all()
-                pkg.qqbot.cmds.aamgr.apply_privileges()
-            except Exception as e:
-                logging.error(e)
-                traceback.print_exc()
-
-            # 配置OpenAI proxy
-            import openai
-            openai.proxy = None  # 先重置，因为重载后可能需要清除proxy
-            if "http_proxy" in config.openai_config and config.openai_config["http_proxy"] is not None:
-                openai.proxy = config.openai_config["http_proxy"]
-
-            # 配置openai api_base
-            if "reverse_proxy" in config.openai_config and config.openai_config["reverse_proxy"] is not None:
-                openai.api_base = config.openai_config["reverse_proxy"]
-
-            # 主启动流程
-            database = pkg.database.manager.DatabaseManager()
-
-            database.initialize_database()
-
-            openai_interact = pkg.openai.manager.OpenAIInteract(config.openai_config['api_key'])
-
-            # 加载所有未超时的session
-            pkg.openai.session.load_sessions()
-
-            # 初始化qq机器人
-            qqbot = pkg.qqbot.manager.QQBotManager(first_time_init=first_time_init)
-
-            # 加载插件
-            import pkg.plugin.host
-            pkg.plugin.host.load_plugins()
-
-            pkg.plugin.host.initialize_plugins()
-
-            if first_time_init:  # 不是热重载之后的启动,则启动新的bot线程
-
-                import mirai.exceptions
-
-                def run_bot_wrapper():
-                    global known_exception_caught
-                    try:
-                        logging.debug("使用账号: {}".format(qqbot.bot_account_id))
-                        qqbot.adapter.run_sync()
-                    except TypeError as e:
-                        if str(e).__contains__("argument 'debug'"):
-                            logging.error(
-                                "连接bot失败:{}, 解决方案: https://github.com/RockChinQ/QChatGPT/issues/82".format(e))
-                            known_exception_caught = True
-                        elif str(e).__contains__("As of 3.10, the *loop*"):
-                            logging.error(
-                                "Websockets版本过低:{}, 解决方案: https://github.com/RockChinQ/QChatGPT/issues/5".format(e))
-                            known_exception_caught = True
-
-                    except websockets.exceptions.InvalidStatus as e:
-                        logging.error(
-                            "mirai-api-http端口无法使用:{}, 解决方案: https://github.com/RockChinQ/QChatGPT/issues/22".format(
-                                e))
-                        known_exception_caught = True
-                    except mirai.exceptions.NetworkError as e:
-                        logging.error("连接mirai-api-http失败:{}, 请检查是否已按照文档启动mirai".format(e))
-                        known_exception_caught = True
-                    except Exception as e:
-                        if str(e).__contains__("404"):
-                            logging.error(
-                                "mirai-api-http端口无法使用:{}, 解决方案: https://github.com/RockChinQ/QChatGPT/issues/22".format(
-                                    e))
-                            known_exception_caught = True
-                        elif str(e).__contains__("signal only works in main thread"):
-                            logging.error(
-                                "hypercorn异常:{}, 解决方案: https://github.com/RockChinQ/QChatGPT/issues/86".format(
-                                    e))
-                            known_exception_caught = True
-                        elif str(e).__contains__("did not receive a valid HTTP"):
-                            logging.error(
-                                "mirai-api-http端口无法使用:{}, 解决方案: https://github.com/RockChinQ/QChatGPT/issues/22".format(
-                                    e))
-                        else:
-                            import traceback
-                            traceback.print_exc()
-                            logging.error(
-                                "捕捉到未知异常:{}, 请前往 https://github.com/RockChinQ/QChatGPT/issues 查找或提issue".format(e))
-                            known_exception_caught = True
-                            raise e
-                    finally:
-                        time.sleep(12)
-                threading.Thread(
-                    target=run_bot_wrapper
-                ).start()
-        except Exception as e:
-            traceback.print_exc()
-            if isinstance(e, KeyboardInterrupt):
-                logging.info("程序被用户中止")
-                sys.exit(0)
-            elif isinstance(e, SyntaxError):
-                logging.error("配置文件存在语法错误，请检查配置文件：\n1. 是否存在中文符号\n2. 是否已按照文件中的说明填写正确")
-                sys.exit(1)
-            else:
-                logging.error("初始化失败:{}".format(e))
-                sys.exit(1)
-    finally:
-        # 判断若是Windows，输出选择模式可能会暂停程序的警告
-        if os.name == 'nt':
-            time.sleep(2)
-            logging.info("您正在使用Windows系统，若命令行窗口处于“选择”模式，程序可能会被暂停，此时请右键点击窗口空白区域使其取消选择模式。")
-
-        time.sleep(12)
-        
-        if first_time_init:
-            if not known_exception_caught:
-                import config
-                if config.msg_source_adapter == "yirimirai":
-                    logging.info("QQ: {}, MAH: {}".format(config.mirai_http_api_config['qq'], config.mirai_http_api_config['host']+":"+str(config.mirai_http_api_config['port'])))
-                    logging.critical('程序启动完成,如长时间未显示 "成功登录到账号xxxxx" ,并且不回复消息,解决办法(请勿到群里问): '
-                                'https://github.com/RockChinQ/QChatGPT/issues/37')
-                elif config.msg_source_adapter == 'nakuru':
-                    logging.info("host: {}, port: {}, http_port: {}".format(config.nakuru_config['host'], config.nakuru_config['port'], config.nakuru_config['http_port']))
-                    logging.critical('程序启动完成,如长时间未显示 "Protocol: connected" ,并且不回复消息,请检查config.py中的nakuru_config是否正确')
-            else:
-                sys.exit(1)
-        else:
-            logging.info('热重载完成')
-
-    # 发送赞赏码
-    if config.encourage_sponsor_at_start \
-        and pkg.utils.context.get_openai_manager().audit_mgr.get_total_text_length() >= 2048:
-
-        logging.info("发送赞赏码")
-        from mirai import MessageChain, Plain, Image
-        import pkg.utils.constants
-        message_chain = MessageChain([
-            Plain("自2022年12月初以来，开发者已经花费了大量时间和精力来维护本项目，如果您觉得本项目对您有帮助，欢迎赞赏开发者，"
-                  "以支持项目稳定运行😘"),
-            Image(base64=pkg.utils.constants.alipay_qr_b64),
-            Image(base64=pkg.utils.constants.wechat_qr_b64),
-            Plain("BTC: 3N4Azee63vbBB9boGv9Rjf4N5SocMe5eCq\nXMR: 89LS21EKQuDGkyQoe2nDupiuWXk4TVD6FALvSKv5owfmeJEPFpHeMsZLYtLiJ6GxLrhsRe5gMs6MyMSDn4GNQAse2Mae4KE\n\n"),
-            Plain("(本消息仅在启动时发送至管理员，如果您不想再看到此消息，请在config.py中将encourage_sponsor_at_start设置为False)")
-        ])
-        pkg.utils.context.get_qqbot_manager().notify_admin_message_chain(message_chain)
-
-    time.sleep(5)
-    import pkg.utils.updater
-    try:
-        if pkg.utils.updater.is_new_version_available():
-            logging.info("新版本可用，请发送 !update 进行自动更新\n更新日志:\n{}".format("\n".join(pkg.utils.updater.get_rls_notes())))
-        else:
-            # logging.info("当前已是最新版本")
-            pass
-
-    except Exception as e:
-        logging.warning("检查更新失败:{}".format(e))
-
-    try:
-        import pkg.utils.announcement as announcement
-        new_announcement = announcement.fetch_new()
-        if len(new_announcement) > 0:
-            for announcement in new_announcement:
-                logging.critical("[公告]<{}> {}".format(announcement['time'], announcement['content']))
-    except Exception as e:
-        logging.warning("获取公告失败:{}".format(e))
-
-    return qqbot
-
-def stop():
-    import pkg.qqbot.manager
-    import pkg.openai.session
-    try:
-        import pkg.plugin.host
-        pkg.plugin.host.unload_plugins()
-
-        qqbot_inst = pkg.utils.context.get_qqbot_manager()
-        assert isinstance(qqbot_inst, pkg.qqbot.manager.QQBotManager)
-
-        for session in pkg.openai.session.sessions:
-            logging.info('持久化session: %s', session)
-            pkg.openai.session.sessions[session].persistence()
-        pkg.utils.context.get_database_manager().close()
-    except Exception as e:
-        if not isinstance(e, KeyboardInterrupt):
-            raise e
-
-
-def check_file():
-    # 检查是否有banlist.py,如果没有就把banlist-template.py复制一份
-    if not os.path.exists('banlist.py'):
-        shutil.copy('res/templates/banlist-template.py', 'banlist.py')
-
-    # 检查是否有sensitive.json
-    if not os.path.exists("sensitive.json"):
-        shutil.copy("res/templates/sensitive-template.json", "sensitive.json")
-
-    # 检查是否有scenario/default.json
-    if not os.path.exists("scenario/default.json"):
-        shutil.copy("scenario/default-template.json", "scenario/default.json")
-
-    # 检查cmdpriv.json
-    if not os.path.exists("cmdpriv.json"):
-        shutil.copy("res/templates/cmdpriv-template.json", "cmdpriv.json")
-
-    # 检查tips_custom
-    if not os.path.exists("tips.py"):
-        shutil.copy("tips-custom-template.py", "tips.py")
-
-    # 检查temp目录
-    if not os.path.exists("temp/"):
-        os.mkdir("temp/")
-
-    # 检查并创建plugins、prompts目录
-    check_path = ["plugins", "prompts"]
-    for path in check_path:
-        if not os.path.exists(path):
-            os.mkdir(path)
-
-    # 配置文件存在性校验
-    if not os.path.exists('config.py'):
-        shutil.copy('config-template.py', 'config.py')
-        print('请先在config.py中填写配置')
-        sys.exit(0)
-
-
-def main():
-    global use_override
-    # 检查是否携带了 --override 或 -r 参数
-    if '--override' in sys.argv or '-r' in sys.argv:
-        use_override = True
-
-    # 初始化相关文件
-    check_file()
-
-    # 初始化logging
-    init_runtime_log_file()
-    pkg.utils.context.context['logger_handler'] = reset_logging()
-
-    # 加载配置
-    load_config()
-    config = pkg.utils.context.get_config()
-
-    # 检查tips模块
-    complete_tips()
-
-    # 配置线程池
-    from pkg.utils import ThreadCtl
-    thread_ctl = ThreadCtl(
-        sys_pool_num=config.sys_pool_num,
-        admin_pool_num=config.admin_pool_num,
-        user_pool_num=config.user_pool_num
-    )
-    # 存进上下文
-    pkg.utils.context.set_thread_ctl(thread_ctl)
-
-    # 启动指令处理
-    if len(sys.argv) > 1 and sys.argv[1] == 'init_db':
-        init_db()
-        sys.exit(0)
-
-    elif len(sys.argv) > 1 and sys.argv[1] == 'update':
-        print("正在进行程序更新...")
-        import pkg.utils.updater as updater
-        updater.update_all(cli=True)
-        sys.exit(0)
-
-    # 关闭urllib的http警告
-    requests.packages.urllib3.disable_warnings(InsecureRequestWarning)
-
-    pkg.utils.context.get_thread_ctl().submit_sys_task(
-        start,
-        True
-    )
-
-    # 主线程循环
-    while True:
-        try:
-            time.sleep(0xFF)
-        except:
-            stop()
-            pkg.utils.context.get_thread_ctl().shutdown()
-            import platform
-            if platform.system() == 'Windows':
-                cmd = "taskkill /F /PID {}".format(os.getpid())
-            elif platform.system() in ['Linux', 'Darwin']:
-                cmd = "kill -9 {}".format(os.getpid())
-            os.system(cmd)
-
-
-if __name__ == '__main__':
-    main()
+import langbot.__main__
 
+langbot.__main__.main()

override-all.json

@@ -1,92 +0,0 @@
-{
-    "comment": "这是override.json支持的字段全集, 关于override.json机制, 请查看https://github.com/RockChinQ/QChatGPT/pull/271",
-    "msg_source_adapter": "yirimirai",
-    "mirai_http_api_config": {
-        "adapter": "WebSocketAdapter",
-        "host": "localhost",
-        "port": 8080,
-        "verifyKey": "yirimirai",
-        "qq": 1234567890
-    },
-    "nakuru_config": {
-        "host": "localhost",
-        "port": 6700,
-        "http_port": 5700,
-        "token": ""
-    },
-    "openai_config": {
-        "api_key": {
-            "default": "openai_api_key"
-        },
-        "http_proxy": null,
-        "reverse_proxy": null
-    },
-    "switch_strategy": "active",
-    "admin_qq": 0,
-    "default_prompt": {
-        "default": "如果我之后想获取帮助，请你说“输入!help获取帮助”"
-    },
-    "preset_mode": "normal",
-    "response_rules": {
-        "default": {
-            "at": true,
-            "prefix": [
-                "/ai",
-                "!ai",
-                "！ai",
-                "ai"
-            ],
-            "regexp": [],
-            "random_rate": 0.0
-        }
-    },
-    "ignore_rules": {
-        "prefix": [
-            "/"
-        ],
-        "regexp": []
-    },
-    "income_msg_check": false,
-    "sensitive_word_filter": true,
-    "baidu_check": false,
-    "baidu_api_key": "",
-    "baidu_secret_key": "",
-    "inappropriate_message_tips": "[百度云]请珍惜机器人，当前返回内容不合规",
-    "encourage_sponsor_at_start": true,
-    "prompt_submit_length": 2048,
-    "auto_reset": true,
-    "completion_api_params": {
-        "model": "gpt-3.5-turbo",
-        "temperature": 0.9
-    },
-    "image_api_params": {
-        "size": "256x256"
-    },
-    "trace_function_calls": false,
-    "quote_origin": true,
-    "at_sender": false,
-    "include_image_description": true,
-    "process_message_timeout": 30,
-    "show_prefix": false,
-    "force_delay_range": [
-        1.5,
-        3
-    ],
-    "blob_message_threshold": 256,
-    "blob_message_strategy": "forward",
-    "wait_last_done": true,
-    "font_path": "",
-    "retry_times": 3,
-    "hide_exce_info_to_user": false,
-    "sys_pool_num": 8,
-    "admin_pool_num": 4,
-    "user_pool_num": 8,
-    "session_expire_time": 1200,
-    "rate_limitation": {
-        "default": 60
-    },
-    "rate_limit_strategy": "drop",
-    "upgrade_dependencies": true,
-    "report_usage": true,
-    "logging_level": 20
-}

pkg/audit/__init__.py

@@ -1,3 +0,0 @@
-"""
-审计相关操作
-"""

pkg/audit/gatherer.py

@@ -1,133 +0,0 @@
-"""
-使用量统计以及数据上报功能实现
-"""
-
-import hashlib
-import json
-import logging
-
-import requests
-
-import pkg.utils.context
-import pkg.utils.updater
-
-
-class DataGatherer:
-    """数据收集器"""
-
-    usage = {}
-    """各api-key的使用量
-    
-    以key值md5为key,{
-        "text": {
-            "text-davinci-003": 文字量:int,
-        },
-        "image": {
-            "256x256": 图片数量:int,
-        }
-    }为值的字典"""
-
-    version_str = "undetermined"
-
-    def __init__(self):
-        self.load_from_db()
-        try:
-            self.version_str = pkg.utils.updater.get_current_tag()  # 从updater模块获取版本号
-        except:
-            pass
-
-    def report_to_server(self, subservice_name: str, count: int):
-        """向中央服务器报告使用量
-
-        只会报告此次请求的使用量，不会报告总量。
-        不包含除版本号、使用类型、使用量以外的任何信息，仅供开发者分析使用情况。
-        """
-        try:
-            config = pkg.utils.context.get_config()
-            if not config.report_usage:
-                return
-            res = requests.get("http://reports.rockchin.top:18989/usage?service_name=qchatgpt.{}&version={}&count={}&msg_source={}".format(subservice_name, self.version_str, count, config.msg_source_adapter))
-            if res.status_code != 200 or res.text != "ok":
-                logging.warning("report to server failed, status_code: {}, text: {}".format(res.status_code, res.text))
-        except:
-            return
-
-    def get_usage(self, key_md5):
-        return self.usage[key_md5] if key_md5 in self.usage else {}
-
-    def report_text_model_usage(self, model, total_tokens):
-        """调用方报告文字模型请求文字使用量"""
-
-        key_md5 = pkg.utils.context.get_openai_manager().key_mgr.get_using_key_md5()  # 以key的md5进行储存
-
-        if key_md5 not in self.usage:
-            self.usage[key_md5] = {}
-
-        if "text" not in self.usage[key_md5]:
-            self.usage[key_md5]["text"] = {}
-
-        if model not in self.usage[key_md5]["text"]:
-            self.usage[key_md5]["text"][model] = 0
-
-        length = total_tokens
-        self.usage[key_md5]["text"][model] += length
-        self.dump_to_db()
-
-        self.report_to_server("text", length)
-
-    def report_image_model_usage(self, size):
-        """调用方报告图片模型请求图片使用量"""
-
-        key_md5 = pkg.utils.context.get_openai_manager().key_mgr.get_using_key_md5()
-
-        if key_md5 not in self.usage:
-            self.usage[key_md5] = {}
-
-        if "image" not in self.usage[key_md5]:
-            self.usage[key_md5]["image"] = {}
-
-        if size not in self.usage[key_md5]["image"]:
-            self.usage[key_md5]["image"][size] = 0
-
-        self.usage[key_md5]["image"][size] += 1
-        self.dump_to_db()
-
-        self.report_to_server("image", 1)
-
-    def get_text_length_of_key(self, key):
-        """获取指定api-key (明文) 的文字总使用量(本地记录)"""
-        key_md5 = hashlib.md5(key.encode('utf-8')).hexdigest()
-        if key_md5 not in self.usage:
-            return 0
-        if "text" not in self.usage[key_md5]:
-            return 0
-        # 遍历其中所有模型，求和
-        return sum(self.usage[key_md5]["text"].values())
-
-    def get_image_count_of_key(self, key):
-        """获取指定api-key (明文) 的图片总使用量(本地记录)"""
-
-        key_md5 = hashlib.md5(key.encode('utf-8')).hexdigest()
-        if key_md5 not in self.usage:
-            return 0
-        if "image" not in self.usage[key_md5]:
-            return 0
-        # 遍历其中所有模型，求和
-        return sum(self.usage[key_md5]["image"].values())
-
-    def get_total_text_length(self):
-        """获取所有api-key的文字总使用量(本地记录)"""
-        total = 0
-        for key in self.usage:
-            if "text" not in self.usage[key]:
-                continue
-            total += sum(self.usage[key]["text"].values())
-        return total
-
-    def dump_to_db(self):
-        pkg.utils.context.get_database_manager().dump_usage_json(self.usage)
-
-    def load_from_db(self):
-        json_str = pkg.utils.context.get_database_manager().load_usage_json()
-        if json_str is not None:
-            self.usage = json.loads(json_str)

pkg/database/__init__.py

@@ -1,3 +0,0 @@
-"""
-数据库操作封装
-"""

pkg/database/manager.py

@@ -1,366 +0,0 @@
-"""
-数据库管理模块
-"""
-import hashlib
-import json
-import logging
-import time
-from sqlite3 import Cursor
-
-import sqlite3
-
-import pkg.utils.context
-
-
-class DatabaseManager:
-    """封装数据库底层操作，并提供方法给上层使用"""
-
-    conn = None
-    cursor = None
-
-    def __init__(self):
-
-        self.reconnect()
-
-        pkg.utils.context.set_database_manager(self)
-
-    # 连接到数据库文件
-    def reconnect(self):
-        """连接到数据库"""
-        self.conn = sqlite3.connect('database.db', check_same_thread=False)
-        self.cursor = self.conn.cursor()
-
-    def close(self):
-        self.conn.close()
-
-    def __execute__(self, *args, **kwargs) -> Cursor:
-        # logging.debug('SQL: {}'.format(sql))
-        logging.debug('SQL: {}'.format(args))
-        c = self.cursor.execute(*args, **kwargs)
-        self.conn.commit()
-        return c
-
-    # 初始化数据库的函数
-    def initialize_database(self):
-        """创建数据表"""
-
-        self.__execute__("""
-        create table if not exists `sessions` (
-            `id` INTEGER PRIMARY KEY AUTOINCREMENT,
-            `name` varchar(255) not null,
-            `type` varchar(255) not null,
-            `number` bigint not null,
-            `create_timestamp` bigint not null,
-            `last_interact_timestamp` bigint not null,
-            `status` varchar(255) not null default 'on_going',
-            `default_prompt` text not null default '',
-            `prompt` text not null,
-            `token_counts` text not null default '[]'
-        )
-        """)
-
-        # 检查sessions表是否存在`default_prompt`字段, 检查是否存在`token_counts`字段
-        self.__execute__("PRAGMA table_info('sessions')")
-        columns = self.cursor.fetchall()
-        has_default_prompt = False
-        has_token_counts = False
-        for field in columns:
-            if field[1] == 'default_prompt':
-                has_default_prompt = True
-            if field[1] == 'token_counts':
-                has_token_counts = True
-            if has_default_prompt and has_token_counts:
-                break
-        if not has_default_prompt:
-            self.__execute__("alter table `sessions` add column `default_prompt` text not null default ''")
-        if not has_token_counts:
-            self.__execute__("alter table `sessions` add column `token_counts` text not null default '[]'")
-
-
-        self.__execute__("""
-        create table if not exists `account_fee`(
-            `id` INTEGER PRIMARY KEY AUTOINCREMENT,
-            `key_md5` varchar(255) not null,
-            `timestamp` bigint not null,
-            `fee` DECIMAL(12,6) not null
-        )
-        """)
-
-        self.__execute__("""
-        create table if not exists `account_usage`(
-            `id` INTEGER PRIMARY KEY AUTOINCREMENT,
-            `json` text not null
-        )
-        """)
-        print('Database initialized.')
-
-    # session持久化
-    def persistence_session(self, subject_type: str, subject_number: int, create_timestamp: int,
-                            last_interact_timestamp: int, prompt: str, default_prompt: str = '', token_counts: str = ''):
-        """持久化指定session"""
-
-        # 检查是否已经有了此name和create_timestamp的session
-        # 如果有，就更新prompt和last_interact_timestamp
-        # 如果没有，就插入一条新的记录
-        self.__execute__("""
-        select count(*) from `sessions` where `type` = '{}' and `number` = {} and `create_timestamp` = {}
-        """.format(subject_type, subject_number, create_timestamp))
-        count = self.cursor.fetchone()[0]
-        if count == 0:
-
-            sql = """
-            insert into `sessions` (`name`, `type`, `number`, `create_timestamp`, `last_interact_timestamp`, `prompt`, `default_prompt`, `token_counts`) 
-            values (?, ?, ?, ?, ?, ?, ?, ?)
-            """
-
-            self.__execute__(sql,
-                             ("{}_{}".format(subject_type, subject_number), subject_type, subject_number, create_timestamp,
-                          last_interact_timestamp, prompt, default_prompt, token_counts))
-        else:
-            sql = """
-            update `sessions` set `last_interact_timestamp` = ?, `prompt` = ?, `token_counts` = ?
-            where `type` = ? and `number` = ? and `create_timestamp` = ?
-            """
-
-            self.__execute__(sql, (last_interact_timestamp, prompt, token_counts, subject_type,
-                                   subject_number, create_timestamp))
-
-    # 显式关闭一个session
-    def explicit_close_session(self, session_name: str, create_timestamp: int):
-        self.__execute__("""
-        update `sessions` set `status` = 'explicitly_closed' where `name` = '{}' and `create_timestamp` = {}
-        """.format(session_name, create_timestamp))
-
-    def set_session_ongoing(self, session_name: str, create_timestamp: int):
-        self.__execute__("""
-        update `sessions` set `status` = 'on_going' where `name` = '{}' and `create_timestamp` = {}
-        """.format(session_name, create_timestamp))
-
-    # 设置session为过期
-    def set_session_expired(self, session_name: str, create_timestamp: int):
-        self.__execute__("""
-        update `sessions` set `status` = 'expired' where `name` = '{}' and `create_timestamp` = {}
-        """.format(session_name, create_timestamp))
-
-    # 从数据库加载还没过期的session数据
-    def load_valid_sessions(self) -> dict:
-        # 从数据库中加载所有还没过期的session
-        config = pkg.utils.context.get_config()
-        self.__execute__("""
-        select `name`, `type`, `number`, `create_timestamp`, `last_interact_timestamp`, `prompt`, `status`, `default_prompt`, `token_counts`
-        from `sessions` where `last_interact_timestamp` > {}
-        """.format(int(time.time()) - config.session_expire_time))
-        results = self.cursor.fetchall()
-        sessions = {}
-        for result in results:
-            session_name = result[0]
-            subject_type = result[1]
-            subject_number = result[2]
-            create_timestamp = result[3]
-            last_interact_timestamp = result[4]
-            prompt = result[5]
-            status = result[6]
-            default_prompt = result[7]
-            token_counts = result[8]
-
-            # 当且仅当最后一个该对象的会话是on_going状态时，才会被加载
-            if status == 'on_going':
-                sessions[session_name] = {
-                    'subject_type': subject_type,
-                    'subject_number': subject_number,
-                    'create_timestamp': create_timestamp,
-                    'last_interact_timestamp': last_interact_timestamp,
-                    'prompt': prompt,
-                    'default_prompt': default_prompt,
-                    'token_counts': token_counts
-                }
-            else:
-                if session_name in sessions:
-                    del sessions[session_name]
-
-        return sessions
-
-    # 获取此session_name前一个session的数据
-    def last_session(self, session_name: str, cursor_timestamp: int):
-
-        self.__execute__("""
-        select `name`, `type`, `number`, `create_timestamp`, `last_interact_timestamp`, `prompt`, `status`, `default_prompt`, `token_counts`
-        from `sessions` where `name` = '{}' and `last_interact_timestamp` < {} order by `last_interact_timestamp` desc
-        limit 1
-        """.format(session_name, cursor_timestamp))
-        results = self.cursor.fetchall()
-        if len(results) == 0:
-            return None
-        result = results[0]
-
-        session_name = result[0]
-        subject_type = result[1]
-        subject_number = result[2]
-        create_timestamp = result[3]
-        last_interact_timestamp = result[4]
-        prompt = result[5]
-        status = result[6]
-        default_prompt = result[7]
-        token_counts = result[8]
-
-        return {
-            'subject_type': subject_type,
-            'subject_number': subject_number,
-            'create_timestamp': create_timestamp,
-            'last_interact_timestamp': last_interact_timestamp,
-            'prompt': prompt,
-            'default_prompt': default_prompt,
-            'token_counts': token_counts
-        }
-
-    # 获取此session_name后一个session的数据
-    def next_session(self, session_name: str, cursor_timestamp: int):
-
-        self.__execute__("""
-            select `name`, `type`, `number`, `create_timestamp`, `last_interact_timestamp`, `prompt`, `status`, `default_prompt`, `token_counts`
-            from `sessions` where `name` = '{}' and `last_interact_timestamp` > {} order by `last_interact_timestamp` asc
-            limit 1
-            """.format(session_name, cursor_timestamp))
-        results = self.cursor.fetchall()
-        if len(results) == 0:
-            return None
-        result = results[0]
-
-        session_name = result[0]
-        subject_type = result[1]
-        subject_number = result[2]
-        create_timestamp = result[3]
-        last_interact_timestamp = result[4]
-        prompt = result[5]
-        status = result[6]
-        default_prompt = result[7]
-        token_counts = result[8]
-
-        return {
-            'subject_type': subject_type,
-            'subject_number': subject_number,
-            'create_timestamp': create_timestamp,
-            'last_interact_timestamp': last_interact_timestamp,
-            'prompt': prompt,
-            'default_prompt': default_prompt,
-            'token_counts': token_counts
-        }
-
-    # 列出与某个对象的所有对话session
-    def list_history(self, session_name: str, capacity: int, page: int):
-        self.__execute__("""
-        select `name`, `type`, `number`, `create_timestamp`, `last_interact_timestamp`, `prompt`, `status`, `default_prompt`, `token_counts`
-        from `sessions` where `name` = '{}' order by `last_interact_timestamp` desc limit {} offset {}
-        """.format(session_name, capacity, capacity * page))
-        results = self.cursor.fetchall()
-        sessions = []
-        for result in results:
-            session_name = result[0]
-            subject_type = result[1]
-            subject_number = result[2]
-            create_timestamp = result[3]
-            last_interact_timestamp = result[4]
-            prompt = result[5]
-            status = result[6]
-            default_prompt = result[7]
-            token_counts = result[8]
-
-            sessions.append({
-                'subject_type': subject_type,
-                'subject_number': subject_number,
-                'create_timestamp': create_timestamp,
-                'last_interact_timestamp': last_interact_timestamp,
-                'prompt': prompt,
-                'default_prompt': default_prompt,
-                'token_counts': token_counts
-            })
-
-        return sessions
-
-    def delete_history(self, session_name: str, index: int) -> bool:
-        # 删除倒序第index个session
-        # 查找其id再删除
-        self.__execute__("""
-        delete from `sessions` where `id` in (select `id` from `sessions` where `name` = '{}' order by `last_interact_timestamp` desc limit 1 offset {})
-        """.format(session_name, index))
-
-        return self.cursor.rowcount == 1
-
-    def delete_all_history(self, session_name: str) -> bool:
-        self.__execute__("""
-        delete from `sessions` where `name` = '{}'
-        """.format(session_name))
-        return self.cursor.rowcount > 0
-
-    def delete_all_session_history(self) -> bool:
-        self.__execute__("""
-        delete from `sessions`
-        """)
-        return self.cursor.rowcount > 0
-
-    # 将apikey的使用量存进数据库
-    def dump_api_key_usage(self, api_keys: dict, usage: dict):
-        logging.debug('dumping api key usage...')
-        logging.debug(api_keys)
-        logging.debug(usage)
-        for api_key in api_keys:
-            # 计算key的md5值
-            key_md5 = hashlib.md5(api_keys[api_key].encode('utf-8')).hexdigest()
-            # 获取使用量
-            usage_count = 0
-            if key_md5 in usage:
-                usage_count = usage[key_md5]
-            # 将使用量存进数据库
-            # 先检查是否已存在
-            self.__execute__("""
-            select count(*) from `api_key_usage` where `key_md5` = '{}'""".format(key_md5))
-            result = self.cursor.fetchone()
-            if result[0] == 0:
-                # 不存在则插入
-                self.__execute__("""
-                insert into `api_key_usage` (`key_md5`, `usage`,`timestamp`) values ('{}', {}, {})
-                """.format(key_md5, usage_count, int(time.time())))
-            else:
-                # 存在则更新，timestamp设置为当前
-                self.__execute__("""
-                update `api_key_usage` set `usage` = {}, `timestamp` = {} where `key_md5` = '{}'
-                """.format(usage_count, int(time.time()), key_md5))
-
-    def load_api_key_usage(self):
-        self.__execute__("""
-        select `key_md5`, `usage` from `api_key_usage`
-        """)
-        results = self.cursor.fetchall()
-        usage = {}
-        for result in results:
-            key_md5 = result[0]
-            usage_count = result[1]
-            usage[key_md5] = usage_count
-        return usage
-
-    def dump_usage_json(self, usage: dict):
-
-        json_str = json.dumps(usage)
-        self.__execute__("""
-        select count(*) from `account_usage`""")
-        result = self.cursor.fetchone()
-        if result[0] == 0:
-            # 不存在则插入
-            self.__execute__("""
-            insert into `account_usage` (`json`) values ('{}')
-            """.format(json_str))
-        else:
-            # 存在则更新
-            self.__execute__("""
-            update `account_usage` set `json` = '{}' where `id` = 1
-            """.format(json_str))
-
-    def load_usage_json(self):
-        self.__execute__("""
-        select `json` from `account_usage` order by id desc limit 1
-        """)
-        result = self.cursor.fetchone()
-        if result is None:
-            return None
-        else:
-            return result[0]

pkg/openai/api/chat_completion.py

@@ -1,204 +0,0 @@
-import openai
-import json
-import logging
-
-from .model import RequestBase
-
-from ..funcmgr import get_func_schema_list, execute_function, get_func, get_func_schema, ContentFunctionNotFoundError
-
-
-class ChatCompletionRequest(RequestBase):
-    """调用ChatCompletion接口的请求类。
-    
-    此类保证每一次返回的角色为assistant的信息的finish_reason一定为stop。
-    若有函数调用响应，本类的返回瀑布是：函数调用请求->函数调用结果->...->assistant的信息->stop。
-    """
-    model: str
-    messages: list[dict[str, str]]
-    kwargs: dict
-
-    stopped: bool = False
-
-    pending_func_call: dict = None
-
-    pending_msg: str
-
-    def flush_pending_msg(self):
-        self.append_message(
-            role="assistant",
-            content=self.pending_msg
-        )
-        self.pending_msg = ""
-
-    def append_message(self, role: str, content: str, name: str=None, function_call: dict=None):
-        msg = {
-            "role": role,
-            "content": content
-        }
-
-        if name is not None:
-            msg['name'] = name
-
-        if function_call is not None:
-            msg['function_call'] = function_call
-
-        self.messages.append(msg)
-
-    def __init__(
-        self,
-        model: str,
-        messages: list[dict[str, str]],
-        **kwargs
-    ):
-        self.model = model
-        self.messages = messages.copy()
-
-        self.kwargs = kwargs
-
-        self.req_func = openai.ChatCompletion.acreate
-
-        self.pending_func_call = None
-
-        self.stopped = False
-
-        self.pending_msg = ""
-
-    def __iter__(self):
-        return self
-
-    def __next__(self) -> dict:
-        if self.stopped:
-            raise StopIteration()
-
-        if self.pending_func_call is None:  # 没有待处理的函数调用请求
-
-            args = {
-                "model": self.model,
-                "messages": self.messages,
-            }
-
-            funcs = get_func_schema_list()
-
-            if len(funcs) > 0:
-                args['functions'] = funcs
-
-            # 拼接kwargs
-            args = {**args, **self.kwargs}
-
-            resp = self._req(**args)
-
-            choice0 = resp["choices"][0]
-
-            # 如果不是函数调用，且finish_reason为stop，则停止迭代
-            if choice0['finish_reason'] == 'stop':  #  and choice0["finish_reason"] == "stop"
-                self.stopped = True
-            
-            if 'function_call' in choice0['message']:
-                self.pending_func_call = choice0['message']['function_call']
-
-                self.append_message(
-                    role="assistant",
-                    content=choice0['message']['content'],
-                    function_call=choice0['message']['function_call']
-                )
-
-                return {
-                    "id": resp["id"],
-                    "choices": [
-                        {
-                            "index": choice0["index"],
-                            "message": {
-                                "role": "assistant",
-                                "type": "function_call",
-                                "content": choice0['message']['content'],
-                                "function_call": choice0['message']['function_call']
-                            },
-                            "finish_reason": "function_call"
-                        }
-                    ],
-                    "usage": resp["usage"]
-                }
-            else:
-
-                # self.pending_msg += choice0['message']['content']
-                # 普通回复一定处于最后方，故不用再追加进内部messages
-
-                return {
-                    "id": resp["id"],
-                    "choices": [
-                        {
-                            "index": choice0["index"],
-                            "message": {
-                                "role": "assistant",
-                                "type": "text",
-                                "content": choice0['message']['content']
-                            },
-                            "finish_reason": choice0["finish_reason"]
-                        }
-                    ],
-                    "usage": resp["usage"]
-                }
-        else:  # 处理函数调用请求
-
-            cp_pending_func_call = self.pending_func_call.copy()
-            
-            self.pending_func_call = None
-
-            func_name = cp_pending_func_call['name']
-            arguments = {}
-
-            try:
-
-                try:
-                    arguments = json.loads(cp_pending_func_call['arguments'])
-                # 若不是json格式的异常处理
-                except json.decoder.JSONDecodeError:
-                    # 获取函数的参数列表
-                    func_schema = get_func_schema(func_name)
-
-                    arguments = {
-                        func_schema['parameters']['required'][0]: cp_pending_func_call['arguments']
-                    }
-                
-                logging.info("执行函数调用: name={}, arguments={}".format(func_name, arguments))
-
-                # 执行函数调用
-                ret = ""
-                try:
-                    ret = execute_function(func_name, arguments)
-
-                    logging.info("函数执行完成。")
-                except Exception as e:
-                    ret = "error: execute function failed: {}".format(str(e))
-                    logging.error("函数执行失败: {}".format(str(e)))
-
-                self.append_message(
-                    role="function",
-                    content=json.dumps(ret, ensure_ascii=False),
-                    name=func_name
-                )
-
-                return {
-                    "id": -1,
-                    "choices": [
-                        {
-                            "index": -1,
-                            "message": {
-                                "role": "function",
-                                "type": "function_return",
-                                "function_name": func_name,
-                                "content": json.dumps(ret, ensure_ascii=False)
-                            },
-                            "finish_reason": "function_return"
-                        }
-                    ],
-                    "usage": {
-                        "prompt_tokens": 0,
-                        "completion_tokens": 0,
-                        "total_tokens": 0
-                    }
-                }
-
-            except ContentFunctionNotFoundError:
-                raise Exception("没有找到函数: {}".format(func_name))
-

pkg/openai/api/completion.py

@@ -1,111 +0,0 @@
-import openai
-
-from .model import RequestBase
-
-
-class CompletionRequest(RequestBase):
-    """调用Completion接口的请求类。
-    
-    调用方可以一直next completion直到finish_reason为stop。
-    """
-
-    model: str
-    prompt: str
-    kwargs: dict
-
-    stopped: bool = False
-
-    def __init__(
-        self,
-        model: str,
-        messages: list[dict[str, str]],
-        **kwargs
-    ):
-        self.model = model
-        self.prompt = ""
-        
-        for message in messages:
-            self.prompt += message["role"] + ": " + message["content"] + "\n"
-        
-        self.prompt += "assistant: "
-
-        self.kwargs = kwargs
-
-        self.req_func = openai.Completion.acreate
-
-    def __iter__(self):
-        return self
-
-    def __next__(self) -> dict:
-        """调用Completion接口，返回生成的文本
-        
-        {
-            "id": "id",
-            "choices": [
-                {
-                    "index": 0,
-                    "message": {
-                        "role": "assistant",
-                        "type": "text",
-                        "content": "message"
-                    },
-                    "finish_reason": "reason"
-                }
-            ],
-            "usage": {
-                "prompt_tokens": 10,
-                "completion_tokens": 20,
-                "total_tokens": 30
-            }
-        }
-        """
-
-        if self.stopped:
-            raise StopIteration()
-
-        resp = self._req(
-            model=self.model,
-            prompt=self.prompt,
-            **self.kwargs
-        )
-
-        if resp["choices"][0]["finish_reason"] == "stop":
-            self.stopped = True
-
-        choice0 = resp["choices"][0]
-
-        self.prompt += choice0["text"]
-
-        return {
-            "id": resp["id"],
-            "choices": [
-                {
-                    "index": choice0["index"],
-                    "message": {
-                        "role": "assistant",
-                        "type": "text",
-                        "content": choice0["text"]
-                    },
-                    "finish_reason": choice0["finish_reason"]
-                }
-            ],
-            "usage": resp["usage"]
-        }
-        
-if __name__ == "__main__":
-    import os
-
-    openai.api_key = os.environ["OPENAI_API_KEY"]
-
-    for resp in CompletionRequest(
-        model="text-davinci-003",
-        messages=[
-            {
-                "role": "user",
-                "content": "Hello, who are you?"
-            }
-        ]
-    ):
-        print(resp)
-        if resp["choices"][0]["finish_reason"] == "stop":
-            break

pkg/openai/api/model.py

@@ -1,62 +0,0 @@
-# 定义不同接口请求的模型
-import threading
-import asyncio
-import logging
-
-import openai
-
-
-class RequestBase:
-
-    req_func: callable
-
-    def __init__(self, *args, **kwargs):
-        raise NotImplementedError
-
-    def _next_key(self):
-        import pkg.utils.context as context
-        switched, name = context.get_openai_manager().key_mgr.auto_switch()
-        logging.debug("切换api-key: switched={}, name={}".format(switched, name))
-        openai.api_key = context.get_openai_manager().key_mgr.get_using_key()
-
-    def _req(self, **kwargs):
-        """处理代理问题"""
-        import config
-
-        ret: dict = {}
-        exception: Exception = None
-
-        async def awrapper(**kwargs):
-            nonlocal ret, exception
-
-            try:
-                ret = await self.req_func(**kwargs)
-                logging.debug("接口请求返回：%s", str(ret))
-                
-                if config.switch_strategy == 'active':
-                    self._next_key()
-
-                return ret
-            except Exception as e:
-                exception = e
-            
-        loop = asyncio.new_event_loop()
-
-        thr = threading.Thread(
-            target=loop.run_until_complete,
-            args=(awrapper(**kwargs),)
-        )
-
-        thr.start()
-        thr.join()
-
-        if exception is not None:
-            raise exception
-
-        return ret
-
-    def __iter__(self):
-        raise self
-
-    def __next__(self):
-        raise NotImplementedError

pkg/openai/dprompt.py

@@ -1,145 +0,0 @@
-# 多情景预设值管理
-import json
-import logging
-import config
-import os
-
-# __current__ = "default"
-# """当前默认使用的情景预设的名称
-
-# 由管理员使用`!default <名称>`指令切换
-# """
-
-# __prompts_from_files__ = {}
-# """从文件中读取的情景预设值"""
-
-# __scenario_from_files__ = {}
-
-
-__universal_first_reply__ = "ok, I'll follow your commands."
-"""通用首次回复"""
-
-
-class ScenarioMode:
-    """情景预设模式抽象类"""
-
-    using_prompt_name = "default"
-    """新session创建时使用的prompt名称"""
-
-    prompts: dict[str, list] = {}
-
-    def __init__(self):
-        logging.debug("prompts: {}".format(self.prompts))
-
-    def list(self) -> dict[str, list]:
-        """获取所有情景预设的名称及内容"""
-        return self.prompts
-
-    def get_prompt(self, name: str) -> tuple[list, str]:
-        """获取指定情景预设的名称及内容"""
-        for key in self.prompts:
-            if key.startswith(name):
-                return self.prompts[key], key
-        raise Exception("没有找到情景预设: {}".format(name))
-
-    def set_using_name(self, name: str) -> str:
-        """设置默认情景预设"""
-        for key in self.prompts:
-            if key.startswith(name):
-                self.using_prompt_name = key
-                return key
-        raise Exception("没有找到情景预设: {}".format(name))
-    
-    def get_full_name(self, name: str) -> str:
-        """获取完整的情景预设名称"""
-        for key in self.prompts:
-            if key.startswith(name):
-                return key
-        raise Exception("没有找到情景预设: {}".format(name))
-
-    def get_using_name(self) -> str:
-        """获取默认情景预设"""
-        return self.using_prompt_name
-
-
-class NormalScenarioMode(ScenarioMode):
-    """普通情景预设模式"""
-
-    def __init__(self):
-        global __universal_first_reply__
-        # 加载config中的default_prompt值
-        if type(config.default_prompt) == str:
-            self.using_prompt_name = "default"
-            self.prompts = {"default": [
-                {
-                    "role": "user",
-                    "content": config.default_prompt
-                },{
-                    "role": "assistant",
-                    "content": __universal_first_reply__
-                }
-            ]}
-        
-        elif type(config.default_prompt) == dict:
-            for key in config.default_prompt:
-                self.prompts[key] = [
-                    {
-                        "role": "user",
-                        "content": config.default_prompt[key]
-                    },{
-                        "role": "assistant",
-                        "content": __universal_first_reply__
-                    }
-                ]
-
-        # 从prompts/目录下的文件中载入
-        # 遍历文件
-        for file in os.listdir("prompts"):
-            with open(os.path.join("prompts", file), encoding="utf-8") as f:
-                self.prompts[file] = [
-                    {
-                        "role": "user",
-                        "content": f.read()
-                    },{
-                        "role": "assistant",
-                        "content": __universal_first_reply__
-                    }
-                ]
-
-
-class FullScenarioMode(ScenarioMode):
-    """完整情景预设模式"""
-
-    def __init__(self):
-        """从json读取所有"""
-        # 遍历scenario/目录下的所有文件，以文件名为键，文件内容中的prompt为值
-        for file in os.listdir("scenario"):
-            if file == "default-template.json":
-                continue
-            with open(os.path.join("scenario", file), encoding="utf-8") as f:
-                self.prompts[file] = json.load(f)["prompt"]
-
-        super().__init__()
-
-
-scenario_mode_mapping = {}
-"""情景预设模式名称与对象的映射"""
-
-
-def register_all():
-    """注册所有情景预设模式，不使用装饰器，因为装饰器的方式不支持热重载"""
-    global scenario_mode_mapping
-    scenario_mode_mapping = {
-        "normal": NormalScenarioMode(),
-        "full_scenario": FullScenarioMode()
-    }
-
-
-def mode_inst() -> ScenarioMode:
-    """获取指定名称的情景预设模式对象"""
-    import config
-
-    if config.preset_mode == "default":
-        config.preset_mode = "normal"
-
-    return scenario_mode_mapping[config.preset_mode]

pkg/openai/funcmgr.py

@@ -1,47 +0,0 @@
-# 封装了function calling的一些支持函数
-import logging
-
-
-from pkg.plugin import host
-
-
-class ContentFunctionNotFoundError(Exception):
-    pass
-
-
-def get_func_schema_list() -> list:
-    """从plugin包中的函数结构中获取并处理成受GPT支持的格式"""
-    if not host.__enable_content_functions__:
-        return []
-
-    schemas = []
-
-    for func in host.__callable_functions__:
-        if func['enabled']:
-            fun_cp = func.copy()
-
-            del fun_cp['enabled']
-
-            schemas.append(fun_cp)
-
-    return schemas
-
-def get_func(name: str) -> callable:
-    if name not in host.__function_inst_map__:
-        raise ContentFunctionNotFoundError("没有找到内容函数: {}".format(name))
-
-    return host.__function_inst_map__[name]
-
-def get_func_schema(name: str) -> dict:
-    for func in host.__callable_functions__:
-        if func['name'] == name:
-            return func
-    raise ContentFunctionNotFoundError("没有找到内容函数: {}".format(name))
-
-def execute_function(name: str, kwargs: dict) -> any:
-    """执行函数调用"""
-
-    logging.debug("executing function: name='{}', kwargs={}".format(name, kwargs))
-
-    func = get_func(name)
-    return func(**kwargs)

pkg/openai/keymgr.py

@@ -1,110 +0,0 @@
-# 此模块提供了维护api-key的各种功能
-import hashlib
-import logging
-
-import pkg.plugin.host as plugin_host
-import pkg.plugin.models as plugin_models
-
-
-class KeysManager:
-    api_key = {}
-    """所有api-key"""
-
-    using_key = ""
-    """当前使用的api-key"""
-
-    alerted = []
-    """已提示过超额的key
-    
-    记录在此以避免重复提示
-    """
-
-    exceeded = []
-    """已超额的key
-    
-    供自动切换功能识别
-    """
-
-    def get_using_key(self):
-        return self.using_key
-
-    def get_using_key_md5(self):
-        return hashlib.md5(self.using_key.encode('utf-8')).hexdigest()
-
-    def __init__(self, api_key):
-
-        if type(api_key) is dict:
-            self.api_key = api_key
-        elif type(api_key) is str:
-            self.api_key = {
-                "default": api_key
-            }
-        elif type(api_key) is list:
-            for i in range(len(api_key)):
-                self.api_key[str(i)] = api_key[i]
-        # 从usage中删除未加载的api-key的记录
-        # 不删了，也许会运行时添加曾经有记录的api-key
-
-        self.auto_switch()
-
-    def auto_switch(self) -> tuple[bool, str]:
-        """尝试切换api-key
-
-        Returns:
-            是否切换成功, 切换后的api-key的别名
-        """
-
-        index = 0
-
-        for key_name in self.api_key:
-            if self.api_key[key_name] == self.using_key:
-                break
-            
-            index += 1
-
-        # 从当前key开始向后轮询
-        start_index = index
-        index += 1
-        if index >= len(self.api_key):
-            index = 0
-
-        while index != start_index:
-            
-            key_name = list(self.api_key.keys())[index]
-
-            if self.api_key[key_name] not in self.exceeded:
-                self.using_key = self.api_key[key_name]
-
-                logging.info("使用api-key:" + key_name)
-
-                # 触发插件事件
-                args = {
-                    "key_name": key_name,
-                    "key_list": self.api_key.keys()
-                }
-                _ = plugin_host.emit(plugin_models.KeySwitched, **args)
-
-                return True, key_name
-
-            index += 1
-            if index >= len(self.api_key):
-                index = 0
-
-        self.using_key = list(self.api_key.values())[start_index]
-        logging.debug("使用api-key:" + list(self.api_key.keys())[start_index])
-
-        return False, list(self.api_key.keys())[start_index]
-
-    def add(self, key_name, key):
-        self.api_key[key_name] = key
-
-    def set_current_exceeded(self):
-        """设置当前使用的api-key使用量超限"""
-        self.exceeded.append(self.using_key)
-
-    def get_key_name(self, api_key):
-        """根据api-key获取其别名"""
-        for key_name in self.api_key:
-            if self.api_key[key_name] == api_key:
-                return key_name
-        return ""

pkg/openai/manager.py

@@ -1,85 +0,0 @@
-import logging
-
-import openai
-
-import pkg.openai.keymgr
-import pkg.utils.context
-import pkg.audit.gatherer
-from pkg.openai.modelmgr import select_request_cls
-
-from pkg.openai.api.model import RequestBase
-
-
-class OpenAIInteract:
-    """OpenAI 接口封装
-
-    将文字接口和图片接口封装供调用方使用
-    """
-
-    key_mgr: pkg.openai.keymgr.KeysManager = None
-
-    audit_mgr: pkg.audit.gatherer.DataGatherer = None
-
-    default_image_api_params = {
-        "size": "256x256",
-    }
-
-    def __init__(self, api_key: str):
-
-        self.key_mgr = pkg.openai.keymgr.KeysManager(api_key)
-        self.audit_mgr = pkg.audit.gatherer.DataGatherer()
-
-        # logging.info("文字总使用量：%d", self.audit_mgr.get_total_text_length())
-
-        openai.api_key = self.key_mgr.get_using_key()
-
-        pkg.utils.context.set_openai_manager(self)
-
-    def request_completion(self, messages: list):
-        """请求补全接口回复=
-        """
-        # 选择接口请求类
-        config = pkg.utils.context.get_config()
-
-        request: RequestBase
-
-        model: str = config.completion_api_params['model']
-
-        cp_parmas = config.completion_api_params.copy()
-        del cp_parmas['model']
-
-        request = select_request_cls(model, messages, cp_parmas)
-
-        # 请求接口
-        for resp in request:
-
-            if resp['usage']['total_tokens'] > 0:
-                self.audit_mgr.report_text_model_usage(
-                    model,
-                    resp['usage']['total_tokens']
-                )
-
-            yield resp
-
-    def request_image(self, prompt) -> dict:
-        """请求图片接口回复
-
-        Parameters:
-            prompt (str): 提示语
-
-        Returns:
-            dict: 响应
-        """
-        config = pkg.utils.context.get_config()
-        params = config.image_api_params
-
-        response = openai.Image.create(
-            prompt=prompt,
-            n=1,
-            **params
-        )
-
-        self.audit_mgr.report_image_model_usage(params['size'])
-
-        return response
-

pkg/openai/modelmgr.py

@@ -1,137 +0,0 @@
-"""OpenAI 接口底层封装
-
-目前使用的对话接口有：
-ChatCompletion - gpt-3.5-turbo 等模型
-Completion - text-davinci-003 等模型
-此模块封装此两个接口的请求实现，为上层提供统一的调用方式
-"""
-import openai, logging, threading, asyncio
-import openai.error as aiE
-import tiktoken
-
-from pkg.openai.api.model import RequestBase
-from pkg.openai.api.completion import CompletionRequest
-from pkg.openai.api.chat_completion import ChatCompletionRequest
-
-COMPLETION_MODELS = {
-    'text-davinci-003',
-    'text-davinci-002',
-    'code-davinci-002',
-    'code-cushman-001',
-    'text-curie-001',
-    'text-babbage-001',
-    'text-ada-001',
-}
-
-CHAT_COMPLETION_MODELS = {
-    'gpt-3.5-turbo',
-    'gpt-3.5-turbo-16k',
-    'gpt-3.5-turbo-0613',
-    'gpt-3.5-turbo-16k-0613',
-    # 'gpt-3.5-turbo-0301',
-    'gpt-4',
-    'gpt-4-0613',
-    'gpt-4-32k',
-    'gpt-4-32k-0613',
-    # One-API 接入
-    'SparkDesk',
-    'chatglm_pro',
-    'chatglm_std',
-    'chatglm_lite',
-    'qwen-v1',
-    'qwen-plus-v1',
-    'ERNIE-Bot',
-    'ERNIE-Bot-turbo',
-}
-
-EDIT_MODELS = {
-
-}
-
-IMAGE_MODELS = {
-
-}
-
-
-def select_request_cls(model_name: str, messages: list, args: dict) -> RequestBase:
-    if model_name in CHAT_COMPLETION_MODELS:
-        return ChatCompletionRequest(model_name, messages, **args)
-    elif model_name in COMPLETION_MODELS:
-        return CompletionRequest(model_name, messages, **args)
-    raise ValueError("不支持模型[{}]，请检查配置文件".format(model_name))
-
-
-def count_chat_completion_tokens(messages: list, model: str) -> int:
-    """Return the number of tokens used by a list of messages."""
-    try:
-        encoding = tiktoken.encoding_for_model(model)
-    except KeyError:
-        print("Warning: model not found. Using cl100k_base encoding.")
-        encoding = tiktoken.get_encoding("cl100k_base")
-    if model in {
-        "gpt-3.5-turbo-0613",
-        "gpt-3.5-turbo-16k-0613",
-        "gpt-4-0314",
-        "gpt-4-32k-0314",
-        "gpt-4-0613",
-        "gpt-4-32k-0613",
-        "SparkDesk",
-        "chatglm_pro",
-        "chatglm_std",
-        "chatglm_lite",
-        "qwen-v1",
-        "qwen-plus-v1",
-        "ERNIE-Bot",
-        "ERNIE-Bot-turbo",
-        }:
-        tokens_per_message = 3
-        tokens_per_name = 1
-    elif model == "gpt-3.5-turbo-0301":
-        tokens_per_message = 4  # every message follows <|start|>{role/name}\n{content}<|end|>\n
-        tokens_per_name = -1  # if there's a name, the role is omitted
-    elif "gpt-3.5-turbo" in model:
-        # print("Warning: gpt-3.5-turbo may update over time. Returning num tokens assuming gpt-3.5-turbo-0613.")
-        return count_chat_completion_tokens(messages, model="gpt-3.5-turbo-0613")
-    elif "gpt-4" in model:
-        # print("Warning: gpt-4 may update over time. Returning num tokens assuming gpt-4-0613.")
-        return count_chat_completion_tokens(messages, model="gpt-4-0613")
-    else:
-        raise NotImplementedError(
-            f"""count_chat_completion_tokens() is not implemented for model {model}. See https://github.com/openai/openai-python/blob/main/chatml.md for information on how messages are converted to tokens."""
-        )
-    num_tokens = 0
-    for message in messages:
-        num_tokens += tokens_per_message
-        for key, value in message.items():
-            num_tokens += len(encoding.encode(value))
-            if key == "name":
-                num_tokens += tokens_per_name
-    num_tokens += 3  # every reply is primed with <|start|>assistant<|message|>
-    return num_tokens
-
-
-def count_completion_tokens(messages: list, model: str) -> int:
-
-    try:
-        encoding = tiktoken.encoding_for_model(model)
-    except KeyError:
-        print("Warning: model not found. Using cl100k_base encoding.")
-        encoding = tiktoken.get_encoding("cl100k_base")
-
-    text = ""
-
-    for message in messages:
-        text += message['role'] + message['content'] + "\n"
-
-    text += "assistant: "
-
-    return len(encoding.encode(text))
-
-
-def count_tokens(messages: list, model: str):
-
-    if model in CHAT_COMPLETION_MODELS:
-        return count_chat_completion_tokens(messages, model)
-    elif model in COMPLETION_MODELS:
-        return count_completion_tokens(messages, model)
-    raise ValueError("不支持模型[{}]，请检查配置文件".format(model))

pkg/openai/session.py

@@ -1,518 +0,0 @@
-"""主线使用的会话管理模块
-
-每个人、每个群单独一个session，session内部保留了对话的上下文，
-"""
-
-import logging
-import threading
-import time
-import json
-
-import pkg.openai.manager
-import pkg.openai.modelmgr
-import pkg.database.manager
-import pkg.utils.context
-
-import pkg.plugin.host as plugin_host
-import pkg.plugin.models as plugin_models
-
-from pkg.openai.modelmgr import count_tokens
-
-# 运行时保存的所有session
-sessions = {}
-
-
-class SessionOfflineStatus:
-    ON_GOING = 'on_going'
-    EXPLICITLY_CLOSED = 'explicitly_closed'
-
-
-# 重置session.prompt
-def reset_session_prompt(session_name, prompt):
-    # 备份原始数据
-    bak_path = 'logs/{}-{}.bak'.format(
-        session_name,
-        time.strftime("%Y-%m-%d-%H-%M-%S", time.localtime())
-    )
-    f = open(bak_path, 'w+')
-    f.write(prompt)
-    f.close()
-    # 生成新数据
-    config = pkg.utils.context.get_config()
-    prompt = [
-        {
-            'role': 'system',
-            'content': config.default_prompt['default'] if type(config.default_prompt) == dict else config.default_prompt
-        }
-    ]
-    # 警告
-    logging.warning(
-        """
-用户[{}]的数据已被重置，有可能是因为数据版本过旧或存储错误
-原始数据将备份在：
-{}""".format(session_name, bak_path)
-    )  # 为保证多行文本格式正确故无缩进
-    return prompt
-
-
-# 从数据加载session
-def load_sessions():
-    """从数据库加载sessions"""
-
-    global sessions
-
-    db_inst = pkg.utils.context.get_database_manager()
-
-    session_data = db_inst.load_valid_sessions()
-
-    for session_name in session_data:
-        logging.debug('加载session: {}'.format(session_name))
-
-        temp_session = Session(session_name)
-        temp_session.name = session_name
-        temp_session.create_timestamp = session_data[session_name]['create_timestamp']
-        temp_session.last_interact_timestamp = session_data[session_name]['last_interact_timestamp']
-        try:
-            temp_session.prompt = json.loads(session_data[session_name]['prompt'])
-            temp_session.token_counts = json.loads(session_data[session_name]['token_counts'])
-        except Exception:
-            temp_session.prompt = reset_session_prompt(session_name, session_data[session_name]['prompt'])
-            temp_session.persistence()
-        temp_session.default_prompt = json.loads(session_data[session_name]['default_prompt']) if \
-            session_data[session_name]['default_prompt'] else []
-
-        sessions[session_name] = temp_session
-
-
-# 获取指定名称的session，如果不存在则创建一个新的
-def get_session(session_name: str) -> 'Session':
-    global sessions
-    if session_name not in sessions:
-        sessions[session_name] = Session(session_name)
-    return sessions[session_name]
-
-
-def dump_session(session_name: str):
-    global sessions
-    if session_name in sessions:
-        assert isinstance(sessions[session_name], Session)
-        sessions[session_name].persistence()
-        del sessions[session_name]
-
-
-# 通用的OpenAI API交互session
-# session内部保留了对话的上下文，
-# 收到用户消息后，将上下文提交给OpenAI API生成回复
-class Session:
-    name = ''
-
-    prompt = []
-    """使用list来保存会话中的回合"""
-
-    default_prompt = []
-    """本session的默认prompt"""
-
-    create_timestamp = 0
-    """会话创建时间"""
-
-    last_interact_timestamp = 0
-    """上次交互(产生回复)时间"""
-
-    just_switched_to_exist_session = False
-
-    response_lock = None
-
-    # 加锁
-    def acquire_response_lock(self):
-        logging.debug('{},lock acquire,{}'.format(self.name, self.response_lock))
-        self.response_lock.acquire()
-        logging.debug('{},lock acquire successfully,{}'.format(self.name, self.response_lock))
-
-    # 释放锁
-    def release_response_lock(self):
-        if self.response_lock.locked():
-            logging.debug('{},lock release,{}'.format(self.name, self.response_lock))
-            self.response_lock.release()
-            logging.debug('{},lock release successfully,{}'.format(self.name, self.response_lock))
-
-    # 从配置文件获取会话预设信息
-    def get_default_prompt(self, use_default: str = None):
-        import pkg.openai.dprompt as dprompt
-
-        if use_default is None:
-            use_default = dprompt.mode_inst().get_using_name()
-
-        current_default_prompt, _ = dprompt.mode_inst().get_prompt(use_default)
-        return current_default_prompt
-
-    def __init__(self, name: str):
-        self.name = name
-        self.create_timestamp = int(time.time())
-        self.last_interact_timestamp = int(time.time())
-        self.prompt = []
-        self.token_counts = []
-        self.schedule()
-
-        self.response_lock = threading.Lock()
-
-        self.default_prompt = self.get_default_prompt()
-        logging.debug("prompt is: {}".format(self.default_prompt))
-
-    # 设定检查session最后一次对话是否超过过期时间的计时器
-    def schedule(self):
-        threading.Thread(target=self.expire_check_timer_loop, args=(self.create_timestamp,)).start()
-
-    # 检查session是否已经过期
-    def expire_check_timer_loop(self, create_timestamp: int):
-        global sessions
-        while True:
-            time.sleep(60)
-
-            # 不是此session已更换，退出
-            if self.create_timestamp != create_timestamp or self not in sessions.values():
-                return
-
-            config = pkg.utils.context.get_config()
-            if int(time.time()) - self.last_interact_timestamp > config.session_expire_time:
-                logging.info('session {} 已过期'.format(self.name))
-
-                # 触发插件事件
-                args = {
-                    'session_name': self.name,
-                    'session': self,
-                    'session_expire_time': config.session_expire_time
-                }
-                event = pkg.plugin.host.emit(plugin_models.SessionExpired, **args)
-                if event.is_prevented_default():
-                    return
-
-                self.reset(expired=True, schedule_new=False)
-
-                # 删除此session
-                del sessions[self.name]
-                return
-
-    # 请求回复
-    # 这个函数是阻塞的
-    def query(self, text: str=None) -> tuple[str, str, list[str]]:
-        """向session中添加一条消息，返回接口回复
-        
-        Args:
-            text (str): 用户消息
-
-        Returns:
-            tuple[str, str]: (接口回复, finish_reason, 已调用的函数列表)
-        """
-
-        self.last_interact_timestamp = int(time.time())
-
-        # 触发插件事件
-        if not self.prompt:
-            args = {
-                'session_name': self.name,
-                'session': self,
-                'default_prompt': self.default_prompt,
-            }
-
-            event = pkg.plugin.host.emit(plugin_models.SessionFirstMessageReceived, **args)
-            if event.is_prevented_default():
-                return None, None, None
-
-        config = pkg.utils.context.get_config()
-        max_length = config.prompt_submit_length
-
-        local_default_prompt = self.default_prompt.copy()
-        local_prompt = self.prompt.copy()
-
-        # 触发PromptPreProcessing事件
-        args = {
-            'session_name': self.name,
-            'default_prompt': self.default_prompt,
-            'prompt': self.prompt,
-            'text_message': text,
-        }
-
-        event = pkg.plugin.host.emit(plugin_models.PromptPreProcessing, **args)
-        
-        if event.get_return_value('default_prompt') is not None:
-            local_default_prompt = event.get_return_value('default_prompt')
-        
-        if event.get_return_value('prompt') is not None:
-            local_prompt = event.get_return_value('prompt')
-
-        if event.get_return_value('text_message') is not None:
-            text = event.get_return_value('text_message')
-
-        prompts, _ = self.cut_out(text, max_length, local_default_prompt, local_prompt)
-
-        res_text = ""
-
-        pending_msgs = []
-
-        total_tokens = 0
-
-        finish_reason: str = ""
-
-        funcs = []
-
-        trace_func_calls = config.trace_function_calls
-        botmgr = pkg.utils.context.get_qqbot_manager()
-
-        session_name_spt: list[str] = self.name.split("_")
-
-        pending_res_text = ""
-
-        # TODO 对不起，我知道这样非常非常屎山，但我之后会重构的
-        for resp in pkg.utils.context.get_openai_manager().request_completion(prompts):
-
-            if pending_res_text != "":
-                botmgr.adapter.send_message(
-                    session_name_spt[0],
-                    session_name_spt[1],
-                    pending_res_text
-                )
-                pending_res_text = ""
-
-            finish_reason = resp['choices'][0]['finish_reason']
-
-            if resp['choices'][0]['message']['role'] == "assistant" and resp['choices'][0]['message']['content'] != None:  # 包含纯文本响应
-
-                if not trace_func_calls:
-                    res_text += resp['choices'][0]['message']['content'] + "\n"
-                else:
-                    res_text = resp['choices'][0]['message']['content']
-                    pending_res_text = resp['choices'][0]['message']['content']
-
-                total_tokens += resp['usage']['total_tokens']
-
-                msg = {
-                    "role": "assistant",
-                    "content": resp['choices'][0]['message']['content']
-                }
-
-                if 'function_call' in resp['choices'][0]['message']:
-                    msg['function_call'] = json.dumps(resp['choices'][0]['message']['function_call'])
-
-                pending_msgs.append(msg)
-
-            if resp['choices'][0]['message']['type'] == 'function_call':
-                # self.prompt.append(
-                #     {
-                #         "role": "assistant",
-                #         "content": "function call: "+json.dumps(resp['choices'][0]['message']['function_call'])
-                #     }
-                # )
-                if trace_func_calls:
-                    botmgr.adapter.send_message(
-                        session_name_spt[0],
-                        session_name_spt[1],
-                        "调用函数 "+resp['choices'][0]['message']['function_call']['name'] + "..."
-                    )
-
-                total_tokens += resp['usage']['total_tokens']
-            elif resp['choices'][0]['message']['type'] == 'function_return':
-                # self.prompt.append(
-                #     {
-                #         "role": "function",
-                #         "name": resp['choices'][0]['message']['function_name'],
-                #         "content": json.dumps(resp['choices'][0]['message']['content'])
-                #     }
-                # )
-
-                # total_tokens += resp['usage']['total_tokens']
-                funcs.append(
-                    resp['choices'][0]['message']['function_name']
-                )
-                pass
-
-
-        # 向API请求补全
-        # message, total_token = pkg.utils.context.get_openai_manager().request_completion(
-        #     prompts,
-        # )
-
-        # 成功获取，处理回复
-        # res_test = message
-        res_ans = res_text.strip()
-
-        # 将此次对话的双方内容加入到prompt中
-        # self.prompt.append({'role': 'user', 'content': text})
-        # self.prompt.append({'role': 'assistant', 'content': res_ans})
-        if text:
-            self.prompt.append({'role': 'user', 'content': text})
-        # 添加pending_msgs
-        self.prompt += pending_msgs
-
-        # 向token_counts中添加本回合的token数量
-        # self.token_counts.append(total_tokens-total_token_before_query)
-        # logging.debug("本回合使用token: {}, session counts: {}".format(total_tokens-total_token_before_query, self.token_counts))
-
-        if self.just_switched_to_exist_session:
-            self.just_switched_to_exist_session = False
-            self.set_ongoing()
-
-        return res_ans if res_ans[0] != '\n' else res_ans[1:], finish_reason, funcs
-
-    # 删除上一回合并返回上一回合的问题
-    def undo(self) -> str:
-        self.last_interact_timestamp = int(time.time())
-
-        # 删除最后两个消息
-        if len(self.prompt) < 2:
-            raise Exception('之前无对话，无法撤销')
-
-        question = self.prompt[-2]['content']
-        self.prompt = self.prompt[:-2]
-        self.token_counts = self.token_counts[:-1]
-
-        # 返回上一回合的问题
-        return question
-
-    # 构建对话体
-    def cut_out(self, msg: str, max_tokens: int, default_prompt: list, prompt: list) -> tuple[list, list]:
-        """将现有prompt进行切割处理，使得新的prompt长度不超过max_tokens
-
-        :return: (新的prompt, 新的token_counts)
-        """
-
-        # 最终由三个部分组成
-        # - default_prompt         情景预设固定值
-        # - changable_prompts      可变部分, 此会话中的历史对话回合
-        # - current_question       当前问题
-
-        # 包装目前的对话回合内容
-        changable_prompts = []
-
-        use_model = pkg.utils.context.get_config().completion_api_params['model']
-
-        ptr = len(prompt) - 1
-
-        # 直接从后向前扫描拼接，不管是否是整回合
-        while ptr >= 0:
-            if count_tokens(prompt[ptr:ptr+1]+changable_prompts, use_model) > max_tokens:
-                break
-
-            changable_prompts.insert(0, prompt[ptr])
-
-            ptr -= 1
-
-        # 将default_prompt和changable_prompts合并
-        result_prompt = default_prompt + changable_prompts
-
-        # 添加当前问题
-        if msg:
-            result_prompt.append(
-                {
-                    'role': 'user',
-                    'content': msg
-                }
-            )
-
-        logging.debug("cut_out: {}".format(json.dumps(result_prompt, ensure_ascii=False, indent=4)))
-
-        return result_prompt, count_tokens(changable_prompts, use_model)
-
-    # 持久化session
-    def persistence(self):
-        if self.prompt == self.get_default_prompt():
-            return
-
-        db_inst = pkg.utils.context.get_database_manager()
-
-        name_spt = self.name.split('_')
-
-        subject_type = name_spt[0]
-        subject_number = int(name_spt[1])
-
-        db_inst.persistence_session(subject_type, subject_number, self.create_timestamp, self.last_interact_timestamp,
-                                    json.dumps(self.prompt), json.dumps(self.default_prompt), json.dumps(self.token_counts))
-
-    # 重置session
-    def reset(self, explicit: bool = False, expired: bool = False, schedule_new: bool = True, use_prompt: str = None, persist: bool = False):
-        if self.prompt:
-            self.persistence()
-            if explicit:
-                # 触发插件事件
-                args = {
-                    'session_name': self.name,
-                    'session': self
-                }
-
-                # 此事件不支持阻止默认行为
-                _ = pkg.plugin.host.emit(plugin_models.SessionExplicitReset, **args)
-
-                pkg.utils.context.get_database_manager().explicit_close_session(self.name, self.create_timestamp)
-
-            if expired:
-                pkg.utils.context.get_database_manager().set_session_expired(self.name, self.create_timestamp)
-
-        if not persist:  # 不要求保持default prompt
-            self.default_prompt = self.get_default_prompt(use_prompt)
-        self.prompt = []
-        self.token_counts = []
-        self.create_timestamp = int(time.time())
-        self.last_interact_timestamp = int(time.time())
-        self.just_switched_to_exist_session = False
-
-        # self.response_lock = threading.Lock()
-
-        if schedule_new:
-            self.schedule()
-
-    # 将本session的数据库状态设置为on_going
-    def set_ongoing(self):
-        pkg.utils.context.get_database_manager().set_session_ongoing(self.name, self.create_timestamp)
-
-    # 切换到上一个session
-    def last_session(self):
-        last_one = pkg.utils.context.get_database_manager().last_session(self.name, self.last_interact_timestamp)
-        if last_one is None:
-            return None
-        else:
-            self.persistence()
-
-            self.create_timestamp = last_one['create_timestamp']
-            self.last_interact_timestamp = last_one['last_interact_timestamp']
-            try:
-                self.prompt = json.loads(last_one['prompt'])
-                self.token_counts = json.loads(last_one['token_counts'])
-            except json.decoder.JSONDecodeError:
-                self.prompt = reset_session_prompt(self.name, last_one['prompt'])
-                self.persistence()
-            self.default_prompt = json.loads(last_one['default_prompt']) if last_one['default_prompt'] else []
-
-            self.just_switched_to_exist_session = True
-            return self
-
-    # 切换到下一个session
-    def next_session(self):
-        next_one = pkg.utils.context.get_database_manager().next_session(self.name, self.last_interact_timestamp)
-        if next_one is None:
-            return None
-        else:
-            self.persistence()
-
-            self.create_timestamp = next_one['create_timestamp']
-            self.last_interact_timestamp = next_one['last_interact_timestamp']
-            try:
-                self.prompt = json.loads(next_one['prompt'])
-                self.token_counts = json.loads(next_one['token_counts'])
-            except json.decoder.JSONDecodeError:
-                self.prompt = reset_session_prompt(self.name, next_one['prompt'])
-                self.persistence()
-            self.default_prompt = json.loads(next_one['default_prompt']) if next_one['default_prompt'] else []
-
-            self.just_switched_to_exist_session = True
-            return self
-
-    def list_history(self, capacity: int = 10, page: int = 0):
-        return pkg.utils.context.get_database_manager().list_history(self.name, capacity, page)
-
-    def delete_history(self, index: int) -> bool:
-        return pkg.utils.context.get_database_manager().delete_history(self.name, index)
-
-    def delete_all_history(self) -> bool:
-        return pkg.utils.context.get_database_manager().delete_all_history(self.name)
-
-    def draw_image(self, prompt: str):
-        return pkg.utils.context.get_openai_manager().request_image(prompt)

pkg/plugin/host.py

@@ -1,410 +0,0 @@
-# 插件管理模块
-import asyncio
-import logging
-import importlib
-import os
-import pkgutil
-import sys
-import shutil
-import traceback
-
-import pkg.utils.updater as updater
-import pkg.utils.context as context
-import pkg.plugin.switch as switch
-import pkg.plugin.settings as settings
-import pkg.qqbot.adapter as msadapter
-
-from mirai import Mirai
-
-from CallingGPT.session.session import Session
-
-__plugins__ = {}
-"""插件列表
-
-示例:
-{
-    "example": {
-        "path": "plugins/example/main.py",
-        "enabled: True,
-        "name": "example",
-        "description": "example",
-        "version": "0.0.1",
-        "author": "RockChinQ",
-        "class": <class 'plugins.example.ExamplePlugin'>,
-        "hooks": {
-            "person_message": [
-                <function ExamplePlugin.person_message at 0x0000020E1D1B8D38>
-            ]
-        },
-        "instance": None
-    }
-}
-"""
-
-__plugins_order__ = []
-"""插件顺序"""
-
-__enable_content_functions__ = True
-"""是否启用内容函数"""
-
-__callable_functions__ = []
-"""供GPT调用的函数结构"""
-
-__function_inst_map__: dict[str, callable] = {}
-"""函数名:实例 映射"""
-
-
-def generate_plugin_order():
-    """根据__plugin__生成插件初始顺序，无视是否启用"""
-    global __plugins_order__
-    __plugins_order__ = []
-    for plugin_name in __plugins__:
-        __plugins_order__.append(plugin_name)
-
-
-def iter_plugins():
-    """按照顺序迭代插件"""
-    for plugin_name in __plugins_order__:
-        yield __plugins__[plugin_name]
-
-
-def iter_plugins_name():
-    """迭代插件名"""
-    for plugin_name in __plugins_order__:
-        yield plugin_name
-
-
-__current_module_path__ = ""
-
-
-def walk_plugin_path(module, prefix='', path_prefix=''):
-    global __current_module_path__
-    """遍历插件路径"""
-    for item in pkgutil.iter_modules(module.__path__):
-        if item.ispkg:
-            logging.debug("扫描插件包: plugins/{}".format(path_prefix + item.name))
-            walk_plugin_path(__import__(module.__name__ + '.' + item.name, fromlist=['']),
-                             prefix + item.name + '.', path_prefix + item.name + '/')
-        else:
-            try:
-                logging.debug("扫描插件模块: plugins/{}".format(path_prefix + item.name + '.py'))
-                __current_module_path__ = "plugins/"+path_prefix + item.name + '.py'
-
-                importlib.import_module(module.__name__ + '.' + item.name)
-                logging.debug('加载模块: plugins/{} 成功'.format(path_prefix + item.name + '.py'))
-            except:
-                logging.error('加载模块: plugins/{} 失败: {}'.format(path_prefix + item.name + '.py', sys.exc_info()))
-                traceback.print_exc()
-
-
-def load_plugins():
-    """加载插件"""
-    logging.debug("加载插件")
-    PluginHost()
-    walk_plugin_path(__import__('plugins'))
-
-    logging.debug(__plugins__)
-
-    # 加载开关数据
-    switch.load_switch()
-
-    # 生成初始顺序
-    generate_plugin_order()
-    # 加载插件顺序
-    settings.load_settings()
-
-    # 输出已注册的内容函数列表
-    logging.debug("registered content functions: {}".format(__callable_functions__))
-    logging.debug("function instance map: {}".format(__function_inst_map__))
-
-
-def initialize_plugins():
-    """初始化插件"""
-    logging.info("初始化插件")
-    import pkg.plugin.models as models
-
-    successfully_initialized_plugins = []
-
-    for plugin in iter_plugins():
-        # if not plugin['enabled']:
-        #     continue
-        try:
-            models.__current_registering_plugin__ = plugin['name']
-            plugin['instance'] = plugin["class"](plugin_host=context.get_plugin_host())
-            # logging.info("插件 {} 已初始化".format(plugin['name']))
-            successfully_initialized_plugins.append(plugin['name'])
-        except:
-            logging.error("插件{}初始化时发生错误: {}".format(plugin['name'], sys.exc_info()))
-    
-    logging.info("以下插件已初始化: {}".format(", ".join(successfully_initialized_plugins)))
-
-
-def unload_plugins():
-    """卸载插件"""
-    # 不再显式卸载插件，因为当程序结束时，插件的析构函数会被系统执行
-    # for plugin in __plugins__.values():
-    #     if plugin['enabled'] and plugin['instance'] is not None:
-    #         if not hasattr(plugin['instance'], '__del__'):
-    #             logging.warning("插件{}没有定义析构函数".format(plugin['name']))
-    #         else:
-    #             try:
-    #                 plugin['instance'].__del__()
-    #                 logging.info("卸载插件: {}".format(plugin['name']))
-    #                 plugin['instance'] = None
-    #             except:
-    #                 logging.error("插件{}卸载时发生错误: {}".format(plugin['name'], sys.exc_info()))
-
-
-def install_plugin(repo_url: str):
-    """安装插件，从git储存库获取并解决依赖"""
-    try:
-        import pkg.utils.pkgmgr
-        pkg.utils.pkgmgr.ensure_dulwich()
-    except:
-        pass
-
-    try:
-        import dulwich
-    except ModuleNotFoundError:
-        raise Exception("dulwich模块未安装,请查看 https://github.com/RockChinQ/QChatGPT/issues/77")
-
-    from dulwich import porcelain
-
-    logging.info("克隆插件储存库: {}".format(repo_url))
-    repo = porcelain.clone(repo_url, "plugins/"+repo_url.split(".git")[0].split("/")[-1]+"/", checkout=True)
-
-    # 检查此目录是否包含requirements.txt
-    if os.path.exists("plugins/"+repo_url.split(".git")[0].split("/")[-1]+"/requirements.txt"):
-        logging.info("检测到requirements.txt，正在安装依赖")
-        import pkg.utils.pkgmgr
-        pkg.utils.pkgmgr.install_requirements("plugins/"+repo_url.split(".git")[0].split("/")[-1]+"/requirements.txt")
-
-        import pkg.utils.log as log
-        log.reset_logging()
-
-
-def uninstall_plugin(plugin_name: str) -> str:
-    """卸载插件"""
-    if plugin_name not in __plugins__:
-        raise Exception("插件不存在")
-    
-    # 获取文件夹路径
-    plugin_path = __plugins__[plugin_name]['path'].replace("\\", "/")
-
-    # 剪切路径为plugins/插件名
-    plugin_path = plugin_path.split("plugins/")[1].split("/")[0]
-
-    # 删除文件夹
-    shutil.rmtree("plugins/"+plugin_path)
-    return "plugins/"+plugin_path
-
-
-def update_plugin(plugin_name: str):
-    """更新插件"""
-    # 检查是否有远程地址记录
-    target_plugin_dir = "plugins/" + __plugins__[plugin_name]['path'].replace("\\", "/").split("plugins/")[1].split("/")[0]
-
-    remote_url = updater.get_remote_url(target_plugin_dir)
-    if remote_url == "https://github.com/RockChinQ/QChatGPT" or remote_url == "https://gitee.com/RockChin/QChatGPT" \
-        or remote_url == "" or remote_url is None or remote_url == "http://github.com/RockChinQ/QChatGPT" or remote_url == "http://gitee.com/RockChin/QChatGPT":
-        raise Exception("插件没有远程地址记录，无法更新")
-    
-    # 把远程clone到temp/plugins/update/插件名
-    logging.info("克隆插件储存库: {}".format(remote_url))
-
-    from dulwich import porcelain
-    clone_target_dir = "temp/plugins/update/"+target_plugin_dir.split("/")[-1]+"/"
-
-    if os.path.exists(clone_target_dir):
-        shutil.rmtree(clone_target_dir)
-
-    if not os.path.exists(clone_target_dir):
-        os.makedirs(clone_target_dir)
-    repo = porcelain.clone(remote_url, clone_target_dir, checkout=True)
-
-    # 检查此目录是否包含requirements.txt
-    if os.path.exists(clone_target_dir+"requirements.txt"):
-        logging.info("检测到requirements.txt，正在安装依赖")
-        import pkg.utils.pkgmgr
-        pkg.utils.pkgmgr.install_requirements(clone_target_dir+"requirements.txt")
-
-        import pkg.utils.log as log
-        log.reset_logging()
-
-    # 将temp/plugins/update/插件名 覆盖到 plugins/插件名
-    shutil.rmtree(target_plugin_dir)
-
-    shutil.copytree(clone_target_dir, target_plugin_dir)
-
-class EventContext:
-    """事件上下文"""
-    eid = 0
-    """事件编号"""
-
-    name = ""
-
-    __prevent_default__ = False
-    """是否阻止默认行为"""
-
-    __prevent_postorder__ = False
-    """是否阻止后续插件的执行"""
-
-    __return_value__ = {}
-    """ 返回值 
-    示例:
-    {
-        "example": [
-            'value1',
-            'value2',
-            3,
-            4,
-            {
-                'key1': 'value1',
-            },
-            ['value1', 'value2']
-        ]
-    }
-    """
-
-    def add_return(self, key: str, ret):
-        """添加返回值"""
-        if key not in self.__return_value__:
-            self.__return_value__[key] = []
-        self.__return_value__[key].append(ret)
-
-    def get_return(self, key: str) -> list:
-        """获取key的所有返回值"""
-        if key in self.__return_value__:
-            return self.__return_value__[key]
-        return None
-
-    def get_return_value(self, key: str):
-        """获取key的首个返回值"""
-        if key in self.__return_value__:
-            return self.__return_value__[key][0]
-        return None
-
-    def prevent_default(self):
-        """阻止默认行为"""
-        self.__prevent_default__ = True
-
-    def prevent_postorder(self):
-        """阻止后续插件执行"""
-        self.__prevent_postorder__ = True
-
-    def is_prevented_default(self):
-        """是否阻止默认行为"""
-        return self.__prevent_default__
-
-    def is_prevented_postorder(self):
-        """是否阻止后序插件执行"""
-        return self.__prevent_postorder__
-
-    def __init__(self, name: str):
-        self.name = name
-        self.eid = EventContext.eid
-        self.__prevent_default__ = False
-        self.__prevent_postorder__ = False
-        self.__return_value__ = {}
-        EventContext.eid += 1
-
-
-def emit(event_name: str, **kwargs) -> EventContext:
-    """触发事件"""
-    import pkg.utils.context as context
-    if context.get_plugin_host() is None:
-        return None
-    return context.get_plugin_host().emit(event_name, **kwargs)
-
-
-class PluginHost:
-    """插件宿主"""
-
-    def __init__(self):
-        """初始化插件宿主"""
-        context.set_plugin_host(self)
-        self.calling_gpt_session = Session([])
-
-    def get_runtime_context(self) -> context:
-        """获取运行时上下文（pkg.utils.context模块的对象）
-
-        此上下文用于和主程序其他模块交互（数据库、QQ机器人、OpenAI接口等）
-        详见pkg.utils.context模块
-        其中的context变量保存了其他重要模块的类对象，可以使用这些对象进行交互
-        """
-        return context
-
-    def get_bot(self) -> Mirai:
-        """获取机器人对象"""
-        return context.get_qqbot_manager().bot
-
-    def get_bot_adapter(self) -> msadapter.MessageSourceAdapter:
-        """获取消息源适配器"""
-        return context.get_qqbot_manager().adapter
-
-    def send_person_message(self, person, message):
-        """发送私聊消息"""
-        self.get_bot_adapter().send_message("person", person, message)
-
-    def send_group_message(self, group, message):
-        """发送群消息"""
-        self.get_bot_adapter().send_message("group", group, message)
-
-    def notify_admin(self, message):
-        """通知管理员"""
-        context.get_qqbot_manager().notify_admin(message)
-
-    def emit(self, event_name: str, **kwargs) -> EventContext:
-        """触发事件"""
-        import json
-
-        event_context = EventContext(event_name)
-        logging.debug("触发事件: {} ({})".format(event_name, event_context.eid))
-        for plugin in iter_plugins():
-            
-            if not plugin['enabled']:
-                continue
-
-            # if plugin['instance'] is None:
-            #     # 从关闭状态切到开启状态之后，重新加载插件
-            #     try:
-            #         plugin['instance'] = plugin["class"](plugin_host=self)
-            #         logging.info("插件 {} 已初始化".format(plugin['name']))
-            #     except:
-            #         logging.error("插件 {} 初始化时发生错误: {}".format(plugin['name'], sys.exc_info()))
-            #         continue
-
-            if 'hooks' not in plugin or event_name not in plugin['hooks']:
-                continue
-
-            hooks = []
-            if event_name in plugin["hooks"]:
-                hooks = plugin["hooks"][event_name]
-            for hook in hooks:
-                try:
-                    already_prevented_default = event_context.is_prevented_default()
-
-                    kwargs['host'] = context.get_plugin_host()
-                    kwargs['event'] = event_context
-
-                    hook(plugin['instance'], **kwargs)
-
-                    if event_context.is_prevented_default() and not already_prevented_default:
-                        logging.debug("插件 {} 已要求阻止事件 {} 的默认行为".format(plugin['name'], event_name))
-
-                except Exception as e:
-                    logging.error("插件{}响应事件{}时发生错误".format(plugin['name'], event_name))
-                    logging.error(traceback.format_exc())
-
-            # print("done:{}".format(plugin['name']))
-            if event_context.is_prevented_postorder():
-                logging.debug("插件 {} 阻止了后序插件的执行".format(plugin['name']))
-                break
-
-        logging.debug("事件 {} ({}) 处理完毕，返回值: {}".format(event_name, event_context.eid,
-                                                                event_context.__return_value__))
-
-        return event_context
-
-if __name__ == "__main__":
-    pass

pkg/plugin/models.py

@@ -1,299 +0,0 @@
-import logging
-
-import pkg.plugin.host as host
-import pkg.utils.context
-
-PersonMessageReceived = "person_message_received"
-"""收到私聊消息时，在判断是否应该响应前触发
-    kwargs:
-        launcher_type: str 发起对象类型(group/person)
-        launcher_id: int 发起对象ID(群号/QQ号)
-        sender_id: int 发送者ID(QQ号)
-        message_chain: mirai.models.message.MessageChain 消息链
-"""
-
-GroupMessageReceived = "group_message_received"
-"""收到群聊消息时，在判断是否应该响应前触发（所有群消息）
-    kwargs:
-        launcher_type: str 发起对象类型(group/person)
-        launcher_id: int 发起对象ID(群号/QQ号)
-        sender_id: int 发送者ID(QQ号)
-        message_chain: mirai.models.message.MessageChain 消息链
-"""
-
-PersonNormalMessageReceived = "person_normal_message_received"
-"""判断为应该处理的私聊普通消息时触发
-    kwargs:
-        launcher_type: str 发起对象类型(group/person)
-        launcher_id: int 发起对象ID(群号/QQ号)
-        sender_id: int 发送者ID(QQ号)
-        text_message: str 消息文本
-        
-    returns (optional):
-        alter: str 修改后的消息文本
-        reply: list 回复消息组件列表
-"""
-
-PersonCommandSent = "person_command_sent"
-"""判断为应该处理的私聊指令时触发
-    kwargs:
-        launcher_type: str 发起对象类型(group/person)
-        launcher_id: int 发起对象ID(群号/QQ号)
-        sender_id: int 发送者ID(QQ号)
-        command: str 指令
-        params: list[str] 参数列表
-        text_message: str 完整指令文本
-        is_admin: bool 是否为管理员
-    
-    returns (optional):
-        alter: str 修改后的完整指令文本
-        reply: list 回复消息组件列表
-"""
-
-GroupNormalMessageReceived = "group_normal_message_received"
-"""判断为应该处理的群聊普通消息时触发
-    kwargs:
-        launcher_type: str 发起对象类型(group/person)
-        launcher_id: int 发起对象ID(群号/QQ号)
-        sender_id: int 发送者ID(QQ号)
-        text_message: str 消息文本
-        
-    returns (optional):
-        alter: str 修改后的消息文本
-        reply: list 回复消息组件列表
-"""
-
-GroupCommandSent = "group_command_sent"
-"""判断为应该处理的群聊指令时触发
-    kwargs:
-        launcher_type: str 发起对象类型(group/person)
-        launcher_id: int 发起对象ID(群号/QQ号)
-        sender_id: int 发送者ID(QQ号)
-        command: str 指令
-        params: list[str] 参数列表
-        text_message: str 完整指令文本
-        is_admin: bool 是否为管理员
-    
-    returns (optional):
-        alter: str 修改后的完整指令文本
-        reply: list 回复消息组件列表
-"""
-
-NormalMessageResponded = "normal_message_responded"
-"""获取到对普通消息的文字响应时触发
-    kwargs:
-        launcher_type: str 发起对象类型(group/person)
-        launcher_id: int 发起对象ID(群号/QQ号)
-        sender_id: int 发送者ID(QQ号)
-        session: pkg.openai.session.Session 会话对象
-        prefix: str 回复文字消息的前缀
-        response_text: str 响应文本
-        finish_reason: str 响应结束原因
-        funcs_called: list[str] 此次响应中调用的函数列表
-    
-    returns (optional):
-        prefix: str 修改后的回复文字消息的前缀
-        reply: list 替换回复消息组件列表
-"""
-
-SessionFirstMessageReceived = "session_first_message_received"
-"""会话被第一次交互时触发
-    kwargs:
-        session_name: str 会话名称(<launcher_type>_<launcher_id>)
-        session: pkg.openai.session.Session 会话对象
-        default_prompt: str 预设值
-"""
-
-SessionExplicitReset = "session_reset"
-"""会话被用户手动重置时触发，此事件不支持阻止默认行为
-    kwargs:
-        session_name: str 会话名称(<launcher_type>_<launcher_id>)
-        session: pkg.openai.session.Session 会话对象
-"""
-
-SessionExpired = "session_expired"
-"""会话过期时触发
-    kwargs:
-        session_name: str 会话名称(<launcher_type>_<launcher_id>)
-        session: pkg.openai.session.Session 会话对象
-        session_expire_time: int 已设置的会话过期时间(秒)
-"""
-
-KeyExceeded = "key_exceeded"
-"""api-key超额时触发
-    kwargs:
-        key_name: str 超额的api-key名称
-        usage: dict 超额的api-key使用情况
-        exceeded_keys: list[str] 超额的api-key列表
-"""
-
-KeySwitched = "key_switched"
-"""api-key超额切换成功时触发，此事件不支持阻止默认行为
-    kwargs:
-        key_name: str 切换成功的api-key名称
-        key_list: list[str] api-key列表
-"""
-
-PromptPreProcessing = "prompt_pre_processing"
-"""每回合调用接口前对prompt进行预处理时触发，此事件不支持阻止默认行为
-    kwargs:
-        session_name: str 会话名称(<launcher_type>_<launcher_id>)
-        default_prompt: list 此session使用的情景预设内容
-        prompt: list 此session现有的prompt内容
-        text_message: str 用户发送的消息文本
-    
-    returns (optional):
-        default_prompt: list 修改后的情景预设内容
-        prompt: list 修改后的prompt内容
-        text_message: str 修改后的消息文本
-"""
-
-
-def on(*args, **kwargs):
-    """注册事件监听器
-    """
-    return Plugin.on(*args, **kwargs)
-
-def func(*args, **kwargs):
-    """注册内容函数，声明此函数为一个内容函数，在对话中将发送此函数给GPT以供其调用
-    此函数可以具有任意的参数，但必须按照[此文档](https://github.com/RockChinQ/CallingGPT/wiki/1.-Function-Format#function-format)
-    所述的格式编写函数的docstring。
-    此功能仅支持在使用gpt-3.5或gpt-4系列模型时使用。
-    """
-    return Plugin.func(*args, **kwargs)
-
-
-__current_registering_plugin__ = ""
-
-
-def require_ver(ge: str, le: str="v999.9.9") -> bool:
-    """插件版本要求装饰器
-
-    Args:
-        ge (str): 最低版本要求
-        le (str, optional): 最高版本要求
-
-    Returns:
-        bool: 是否满足要求, False时为无法获取版本号，True时为满足要求，报错为不满足要求
-    """
-    qchatgpt_version = ""
-    
-    from pkg.utils.updater import get_current_tag, compare_version_str
-
-    try:
-        qchatgpt_version = get_current_tag()  # 从updater模块获取版本号
-    except:
-        return False
-
-    if compare_version_str(qchatgpt_version, ge) < 0 or \
-        (compare_version_str(qchatgpt_version, le) > 0):
-        raise Exception("QChatGPT 版本不满足要求，某些功能（可能是由插件提供的）无法正常使用。（要求版本：{}-{}，但当前版本：{}）".format(ge, le, qchatgpt_version))
-
-    return True
-
-
-class Plugin:
-    """插件基类"""
-
-    host: host.PluginHost
-    """插件宿主，提供插件的一些基础功能"""
-
-    @classmethod
-    def on(cls, event):
-        """事件处理器装饰器
-
-        :param
-            event: 事件类型
-        :return:
-            None
-        """
-        global __current_registering_plugin__
-
-        def wrapper(func):
-            plugin_hooks = host.__plugins__[__current_registering_plugin__]["hooks"]
-
-            if event not in plugin_hooks:
-                plugin_hooks[event] = []
-            plugin_hooks[event].append(func)
-
-            # print("registering hook: p='{}', e='{}', f={}".format(__current_registering_plugin__, event, func))
-
-            host.__plugins__[__current_registering_plugin__]["hooks"] = plugin_hooks
-
-            return func
-
-        return wrapper
-
-    @classmethod
-    def func(cls, name: str=None):
-        """内容函数装饰器
-        """
-        global __current_registering_plugin__
-        from CallingGPT.entities.namespace import get_func_schema
-
-        def wrapper(func):
-
-            function_schema = get_func_schema(func)
-            function_schema['name'] = __current_registering_plugin__ + '-' + (func.__name__ if name is None else name)
-
-            function_schema['enabled'] = True
-
-            host.__function_inst_map__[function_schema['name']] = function_schema['function']
-
-            del function_schema['function']
-
-            # logging.debug("registering content function: p='{}', f='{}', s={}".format(__current_registering_plugin__, func, function_schema))
-
-            host.__callable_functions__.append(
-                function_schema
-            )
-
-            return func
-
-        return wrapper
-
-
-def register(name: str, description: str, version: str, author: str):
-    """注册插件, 此函数作为装饰器使用
-
-    Args:
-        name (str): 插件名称
-        description (str): 插件描述
-        version (str): 插件版本
-        author (str): 插件作者
-
-    Returns:
-        None
-    """
-    global __current_registering_plugin__
-
-    __current_registering_plugin__ = name
-    # print("registering plugin: n='{}', d='{}', v={}, a='{}'".format(name, description, version, author))
-    host.__plugins__[name] = {
-        "name": name,
-        "description": description,
-        "version": version,
-        "author": author,
-        "hooks": {},
-        "path": host.__current_module_path__,
-        "enabled": True,
-        "instance": None,
-    }
-
-    def wrapper(cls: Plugin):
-        cls.name = name
-        cls.description = description
-        cls.version = version
-        cls.author = author
-        cls.host = pkg.utils.context.get_plugin_host()
-        cls.enabled = True
-        cls.path = host.__current_module_path__
-
-        # 存到插件列表
-        host.__plugins__[name]["class"] = cls
-
-        logging.info("插件注册完成: n='{}', d='{}', v={}, a='{}' ({})".format(name, description, version, author, cls))
-
-        return cls
-
-    return wrapper

pkg/plugin/settings.py

@@ -1,103 +0,0 @@
-import json
-import os
-
-import pkg.plugin.host as host
-import logging
-
-
-def wrapper_dict_from_runtime_context() -> dict:
-    """从变量中包装settings.json的数据字典"""
-    settings = {
-        "order": [],
-        "functions": {
-            "enabled": host.__enable_content_functions__
-        }
-    }
-
-    for plugin_name in host.__plugins_order__:
-        settings["order"].append(plugin_name)
-
-    return settings
-
-
-def apply_settings(settings: dict):
-    """将settings.json数据应用到变量中"""
-    if "order" in settings:
-        host.__plugins_order__ = settings["order"]
-
-    if "functions" in settings:
-        if "enabled" in settings["functions"]:
-            host.__enable_content_functions__ = settings["functions"]["enabled"]
-            # logging.debug("set content function enabled: {}".format(host.__enable_content_functions__))
-
-
-def dump_settings():
-    """保存settings.json数据"""
-    logging.debug("保存plugins/settings.json数据")
-
-    settings = wrapper_dict_from_runtime_context()
-
-    with open("plugins/settings.json", "w", encoding="utf-8") as f:
-        json.dump(settings, f, indent=4, ensure_ascii=False)
-
-
-def load_settings():
-    """加载settings.json数据"""
-    logging.debug("加载plugins/settings.json数据")
-
-    # 读取plugins/settings.json
-    settings = {
-    }
-
-    # 检查文件是否存在
-    if not os.path.exists("plugins/settings.json"):
-        # 不存在则创建
-        with open("plugins/settings.json", "w", encoding="utf-8") as f:
-            json.dump(wrapper_dict_from_runtime_context(), f, indent=4, ensure_ascii=False)
-
-    with open("plugins/settings.json", "r", encoding="utf-8") as f:
-        settings = json.load(f)
-
-    if settings is None:
-        settings = {
-        }
-
-    # 检查每个设置项
-    if "order" not in settings:
-        settings["order"] = []
-
-    settings_modified = False
-
-    settings_copy = settings.copy()
-
-    # 检查settings中多余的插件项
-
-    # order
-    for plugin_name in settings_copy["order"]:
-        if plugin_name not in host.__plugins_order__:
-            settings["order"].remove(plugin_name)
-            settings_modified = True
-
-    # 检查settings中缺少的插件项
-
-    # order
-    for plugin_name in host.__plugins_order__:
-        if plugin_name not in settings_copy["order"]:
-            settings["order"].append(plugin_name)
-            settings_modified = True
-
-    if "functions" not in settings:
-        settings["functions"] = {
-            "enabled": host.__enable_content_functions__
-        }
-        settings_modified = True
-    elif "enabled" not in settings["functions"]:
-        settings["functions"]["enabled"] = host.__enable_content_functions__
-        settings_modified = True
-
-    logging.info("已全局{}内容函数。".format("启用" if settings["functions"]["enabled"] else "禁用"))
-
-    apply_settings(settings)
-
-    if settings_modified:
-        dump_settings()

pkg/plugin/switch.py

@@ -1,94 +0,0 @@
-# 控制插件的开关
-import json
-import logging
-import os
-
-import pkg.plugin.host as host
-
-
-def wrapper_dict_from_plugin_list() -> dict:
-    """将插件列表转换为开关json"""
-    switch = {}
-
-    for plugin_name in host.__plugins__:
-        plugin = host.__plugins__[plugin_name]
-
-        switch[plugin_name] = {
-            "path": plugin["path"],
-            "enabled": plugin["enabled"],
-        }
-
-    return switch
-
-
-def apply_switch(switch: dict):
-    """将开关数据应用到插件列表中"""
-    # print("将开关数据应用到插件列表中")
-    # print(switch)
-    for plugin_name in switch:
-        host.__plugins__[plugin_name]["enabled"] = switch[plugin_name]["enabled"]
-
-        # 查找此插件的所有内容函数
-        for func in host.__callable_functions__:
-            if func['name'].startswith(plugin_name + '-'):
-                func['enabled'] = switch[plugin_name]["enabled"]
-
-
-def dump_switch():
-    """保存开关数据"""
-    logging.debug("保存开关数据")
-    # 将开关数据写入plugins/switch.json
-
-    switch = wrapper_dict_from_plugin_list()
-
-    with open("plugins/switch.json", "w", encoding="utf-8") as f:
-        json.dump(switch, f, indent=4, ensure_ascii=False)
-
-
-def load_switch():
-    """加载开关数据"""
-    logging.debug("加载开关数据")
-    # 读取plugins/switch.json
-
-    switch = {}
-
-    # 检查文件是否存在
-    if not os.path.exists("plugins/switch.json"):
-        # 不存在则创建
-        with open("plugins/switch.json", "w", encoding="utf-8") as f:
-            json.dump(switch, f, indent=4, ensure_ascii=False)
-
-    with open("plugins/switch.json", "r", encoding="utf-8") as f:
-        switch = json.load(f)
-
-    if switch is None:
-        switch = {}
-
-    switch_modified = False
-
-    switch_copy = switch.copy()
-    # 检查switch中多余的和path不相符的
-    for plugin_name in switch_copy:
-        if plugin_name not in host.__plugins__:
-            del switch[plugin_name]
-            switch_modified = True
-        elif switch[plugin_name]["path"] != host.__plugins__[plugin_name]["path"]:
-            # 删除此不相符的
-            del switch[plugin_name]
-            switch_modified = True
-
-    # 检查plugin中多余的
-    for plugin_name in host.__plugins__:
-        if plugin_name not in switch:
-            switch[plugin_name] = {
-                "path": host.__plugins__[plugin_name]["path"],
-                "enabled": host.__plugins__[plugin_name]["enabled"],
-            }
-            switch_modified = True
-
-    # 应用开关数据
-    apply_switch(switch)
-
-    # 如果switch有修改，保存
-    if switch_modified:
-        dump_switch()

pkg/qqbot/adapter.py

@@ -1,136 +0,0 @@
-# MessageSource的适配器
-import typing
-
-import mirai
-
-
-class MessageSourceAdapter:
-    def __init__(self, config: dict):
-        pass
-
-    def send_message(
-        self,
-        target_type: str,
-        target_id: str,
-        message: mirai.MessageChain
-    ):
-        """发送消息
-        
-        Args:
-            target_type (str): 目标类型，`person`或`group`
-            target_id (str): 目标ID
-            message (mirai.MessageChain): YiriMirai库的消息链
-        """
-        raise NotImplementedError
-
-    def reply_message(
-        self,
-        message_source: mirai.MessageEvent,
-        message: mirai.MessageChain,
-        quote_origin: bool = False
-    ):
-        """回复消息
-
-        Args:
-            message_source (mirai.MessageEvent): YiriMirai消息源事件
-            message (mirai.MessageChain): YiriMirai库的消息链
-            quote_origin (bool, optional): 是否引用原消息. Defaults to False.
-        """
-        raise NotImplementedError
-
-    def is_muted(self, group_id: int) -> bool:
-        """获取账号是否在指定群被禁言"""
-        raise NotImplementedError
-
-    def register_listener(
-        self,
-        event_type: typing.Type[mirai.Event],
-        callback: typing.Callable[[mirai.Event], None]
-    ):
-        """注册事件监听器
-        
-        Args:
-            event_type (typing.Type[mirai.Event]): YiriMirai事件类型
-            callback (typing.Callable[[mirai.Event], None]): 回调函数，接收一个参数，为YiriMirai事件
-        """
-        raise NotImplementedError
-    
-    def unregister_listener(
-        self,
-        event_type: typing.Type[mirai.Event],
-        callback: typing.Callable[[mirai.Event], None]
-    ):
-        """注销事件监听器
-        
-        Args:
-            event_type (typing.Type[mirai.Event]): YiriMirai事件类型
-            callback (typing.Callable[[mirai.Event], None]): 回调函数，接收一个参数，为YiriMirai事件
-        """
-        raise NotImplementedError
-
-    def run_sync(self):
-        """以阻塞的方式运行适配器"""
-        raise NotImplementedError
-
-    def kill(self) -> bool:
-        """关闭适配器
-        
-        Returns:
-            bool: 是否成功关闭，热重载时若此函数返回False则不会重载MessageSource底层
-        """
-        raise NotImplementedError
-
-
-class MessageConverter:
-    """消息链转换器基类"""
-    @staticmethod
-    def yiri2target(message_chain: mirai.MessageChain):
-        """将YiriMirai消息链转换为目标消息链
-
-        Args:
-            message_chain (mirai.MessageChain): YiriMirai消息链
-
-        Returns:
-            typing.Any: 目标消息链
-        """
-        raise NotImplementedError
-
-    @staticmethod
-    def target2yiri(message_chain: typing.Any) -> mirai.MessageChain:
-        """将目标消息链转换为YiriMirai消息链
-
-        Args:
-            message_chain (typing.Any): 目标消息链
-
-        Returns:
-            mirai.MessageChain: YiriMirai消息链
-        """
-        raise NotImplementedError
-
-
-class EventConverter:
-    """事件转换器基类"""
-
-    @staticmethod
-    def yiri2target(event: typing.Type[mirai.Event]):
-        """将YiriMirai事件转换为目标事件
-
-        Args:
-            event (typing.Type[mirai.Event]): YiriMirai事件
-
-        Returns:
-            typing.Any: 目标事件
-        """
-        raise NotImplementedError
-
-    @staticmethod
-    def target2yiri(event: typing.Any) -> mirai.Event:
-        """将目标事件的调用参数转换为YiriMirai的事件参数对象
-
-        Args:
-            event (typing.Any): 目标事件
-
-        Returns:
-            typing.Type[mirai.Event]: YiriMirai事件
-        """
-        raise NotImplementedError

pkg/qqbot/banlist.py

@@ -1,50 +0,0 @@
-import pkg.utils.context
-
-
-def is_banned(launcher_type: str, launcher_id: int, sender_id: int) -> bool:
-    if not pkg.utils.context.get_qqbot_manager().enable_banlist:
-        return False
-    
-    result = False
-    
-    if launcher_type == 'group':
-        # 检查是否显式声明发起人QQ要被person忽略
-        if sender_id in pkg.utils.context.get_qqbot_manager().ban_person:
-            result = True
-        else:
-            for group_rule in pkg.utils.context.get_qqbot_manager().ban_group:
-                if type(group_rule) == int:
-                    if group_rule == launcher_id:  # 此群群号被禁用
-                        result = True
-                elif type(group_rule) == str:
-                    if group_rule.startswith('!'):
-                        # 截取!后面的字符串作为表达式，判断是否匹配
-                        reg_str = group_rule[1:]
-                        import re
-                        if re.match(reg_str, str(launcher_id)):  # 被豁免，最高级别
-                            result = False
-                            break
-                    else:
-                        # 判断是否匹配regexp
-                        import re
-                        if re.match(group_rule, str(launcher_id)):  # 此群群号被禁用
-                            result = True
-                    
-    else:
-        # ban_person, 与群规则相同
-        for person_rule in pkg.utils.context.get_qqbot_manager().ban_person:
-            if type(person_rule) == int:
-                if person_rule == launcher_id:
-                    result = True
-            elif type(person_rule) == str:
-                if person_rule.startswith('!'):
-                    reg_str = person_rule[1:]
-                    import re
-                    if re.match(reg_str, str(launcher_id)):
-                        result = False
-                        break
-                else:
-                    import re
-                    if re.match(person_rule, str(launcher_id)):
-                        result = True
-    return result

pkg/qqbot/blob.py

@@ -1,97 +0,0 @@
-# 长消息处理相关
-import os
-import time
-import base64
-
-import config
-from mirai.models.message import MessageComponent, MessageChain, Image
-from mirai.models.message import ForwardMessageNode
-from mirai.models.base import MiraiBaseModel
-from typing import List
-import pkg.utils.context as context
-import pkg.utils.text2img as text2img
-
-
-class ForwardMessageDiaplay(MiraiBaseModel):
-    title: str = "群聊的聊天记录"
-    brief: str = "[聊天记录]"
-    source: str = "聊天记录"
-    preview: List[str] = []
-    summary: str = "查看x条转发消息"
-
-
-class Forward(MessageComponent):
-    """合并转发。"""
-    type: str = "Forward"
-    """消息组件类型。"""
-    display: ForwardMessageDiaplay
-    """显示信息"""
-    node_list: List[ForwardMessageNode]
-    """转发消息节点列表。"""
-    def __init__(self, *args, **kwargs):
-        if len(args) == 1:
-            self.node_list = args[0]
-            super().__init__(**kwargs)
-        super().__init__(*args, **kwargs)
-
-    def __str__(self):
-        return '[聊天记录]'
-
-
-def text_to_image(text: str) -> MessageComponent:
-    """将文本转换成图片"""
-    # 检查temp文件夹是否存在
-    if not os.path.exists('temp'):
-        os.mkdir('temp')
-    img_path = text2img.text_to_image(text_str=text, save_as='temp/{}.png'.format(int(time.time())))
-    
-    compressed_path, size = text2img.compress_image(img_path, outfile="temp/{}_compressed.png".format(int(time.time())))
-    # 读取图片，转换成base64
-    with open(compressed_path, 'rb') as f:
-        img = f.read()
-
-    b64 = base64.b64encode(img)
-
-    # 删除图片
-    os.remove(img_path)
-
-    # 判断compressed_path是否存在
-    if os.path.exists(compressed_path):
-        os.remove(compressed_path)
-    # 返回图片
-    return Image(base64=b64.decode('utf-8'))
-
-
-def check_text(text: str) -> list:
-    """检查文本是否为长消息，并转换成该使用的消息链组件"""
-    if len(text) > config.blob_message_threshold:
-
-        # logging.info("长消息: {}".format(text))
-        if config.blob_message_strategy == 'image':
-            # 转换成图片
-            return [text_to_image(text)]
-        elif config.blob_message_strategy == 'forward':
-
-            # 包装转发消息
-            display = ForwardMessageDiaplay(
-                title='群聊的聊天记录',
-                brief='[聊天记录]',
-                source='聊天记录',
-                preview=["bot: "+text],
-                summary="查看1条转发消息"
-            )
-
-            node = ForwardMessageNode(
-                sender_id=config.mirai_http_api_config['qq'],
-                sender_name='bot',
-                message_chain=MessageChain([text])
-            )
-
-            forward = Forward(
-                display=display,
-                node_list=[node]
-            )
-
-            return [forward]
-    else:
-        return [text]

pkg/qqbot/cmds/aamgr.py

@@ -1,337 +0,0 @@
-import importlib
-import inspect
-import logging
-import copy
-import pkgutil
-import traceback
-import types
-import json
-
-
-__command_list__ = {}
-
-import tips as tips_custom
-
-"""命令树
-
-结构：
-{
-    'cmd1': {
-        'description': 'cmd1 description',
-        'usage': 'cmd1 usage',
-        'aliases': ['cmd1 alias1', 'cmd1 alias2'],
-        'privilege': 0,
-        'parent': None,
-        'cls': <class 'pkg.qqbot.cmds.cmd1.CommandCmd1'>,
-        'sub': [
-            'cmd1-1'
-        ]
-    },
-    'cmd1.cmd1-1: {
-        'description': 'cmd1-1 description',
-        'usage': 'cmd1-1 usage',
-        'aliases': ['cmd1-1 alias1', 'cmd1-1 alias2'],
-        'privilege': 0,
-        'parent': 'cmd1',
-        'cls': <class 'pkg.qqbot.cmds.cmd1.CommandCmd1_1'>,
-        'sub': []
-    },
-    'cmd2': {
-        'description': 'cmd2 description',
-        'usage': 'cmd2 usage',
-        'aliases': ['cmd2 alias1', 'cmd2 alias2'],
-        'privilege': 0,
-        'parent': None,
-        'cls': <class 'pkg.qqbot.cmds.cmd2.CommandCmd2'>,
-        'sub': [
-            'cmd2-1'
-        ]
-    },
-    'cmd2.cmd2-1': {
-        'description': 'cmd2-1 description',
-        'usage': 'cmd2-1 usage',
-        'aliases': ['cmd2-1 alias1', 'cmd2-1 alias2'],
-        'privilege': 0,
-        'parent': 'cmd2',
-        'cls': <class 'pkg.qqbot.cmds.cmd2.CommandCmd2_1'>,
-        'sub': [
-            'cmd2-1-1'
-        ]
-    },
-    'cmd2.cmd2-1.cmd2-1-1': {
-        'description': 'cmd2-1-1 description',
-        'usage': 'cmd2-1-1 usage',
-        'aliases': ['cmd2-1-1 alias1', 'cmd2-1-1 alias2'],
-        'privilege': 0,
-        'parent': 'cmd2.cmd2-1',
-        'cls': <class 'pkg.qqbot.cmds.cmd2.CommandCmd2_1_1'>,
-        'sub': []
-    },
-}
-"""
-
-__tree_index__: dict[str, list] = {}
-"""命令树索引
-
-结构：
-{
-    'pkg.qqbot.cmds.cmd1.CommandCmd1': 'cmd1',  # 顶级指令
-    'pkg.qqbot.cmds.cmd1.CommandCmd1_1': 'cmd1.cmd1-1',  # 类名: 节点路径
-    'pkg.qqbot.cmds.cmd2.CommandCmd2': 'cmd2',
-    'pkg.qqbot.cmds.cmd2.CommandCmd2_1': 'cmd2.cmd2-1',
-    'pkg.qqbot.cmds.cmd2.CommandCmd2_1_1': 'cmd2.cmd2-1.cmd2-1-1',
-}
-"""
-
-
-class Context:
-    """命令执行上下文"""
-    command: str
-    """顶级指令文本"""
-
-    crt_command: str
-    """当前子指令文本"""
-
-    params: list
-    """完整参数列表"""
-
-    crt_params: list
-    """当前子指令参数列表"""
-
-    session_name: str
-    """会话名"""
-
-    text_message: str
-    """指令完整文本"""
-
-    launcher_type: str
-    """指令发起者类型"""
-
-    launcher_id: int
-    """指令发起者ID"""
-
-    sender_id: int
-    """指令发送者ID"""
-
-    is_admin: bool
-    """[过时]指令发送者是否为管理员"""
-
-    privilege: int
-    """指令发送者权限等级"""
-
-    def __init__(self, **kwargs):
-        self.__dict__.update(kwargs)
-
-
-class AbstractCommandNode:
-    """指令抽象类"""
-
-    parent: type
-    """父指令类"""
-
-    name: str
-    """指令名"""
-
-    description: str
-    """指令描述"""
-
-    usage: str
-    """指令用法"""
-
-    aliases: list[str]
-    """指令别名"""
-
-    privilege: int
-    """指令权限等级, 权限大于等于此值的用户才能执行指令"""
-
-    @classmethod
-    def process(cls, ctx: Context) -> tuple[bool, list]:
-        """指令处理函数
-        
-        :param ctx: 指令执行上下文
-
-        :return: (是否执行, 回复列表(若执行))
-
-        若未执行，将自动以下一个参数查找并执行子指令
-        """
-        raise NotImplementedError
-    
-    @classmethod
-    def help(cls) -> str:
-        """获取指令帮助信息"""
-        return '指令: {}\n描述: {}\n用法: \n{}\n别名: {}\n权限: {}'.format(
-            cls.name,
-            cls.description,
-            cls.usage,
-            ', '.join(cls.aliases),
-            cls.privilege
-        )
-
-    @staticmethod
-    def register(
-        parent: type = None,
-        name: str = None,
-        description: str = None,
-        usage: str = None,
-        aliases: list[str] = None,
-        privilege: int = 0
-    ):
-        """注册指令
-        
-        :param cls: 指令类
-        :param name: 指令名
-        :param parent: 父指令类
-        """
-        global __command_list__, __tree_index__
-        
-        def wrapper(cls):
-            cls.name = name
-            cls.parent = parent
-            cls.description = description
-            cls.usage = usage
-            cls.aliases = aliases
-            cls.privilege = privilege
-
-            logging.debug("cls: {}, name: {}, parent: {}".format(cls, name, parent))
-
-            if parent is None:
-                # 顶级指令注册
-                __command_list__[name] = {
-                    'description': cls.description,
-                    'usage': cls.usage,
-                    'aliases': cls.aliases,
-                    'privilege': cls.privilege,
-                    'parent': None,
-                    'cls': cls,
-                    'sub': []
-                }
-                # 更新索引
-                __tree_index__[cls.__module__ + '.' + cls.__name__] = name
-            else:
-                # 获取父节点名称
-                path = __tree_index__[parent.__module__ + '.' + parent.__name__]
-                
-                parent_node = __command_list__[path]
-                # 链接父子指令
-                __command_list__[path]['sub'].append(name)
-                # 注册子指令
-                __command_list__[path + '.' + name] = {
-                    'description': cls.description,
-                    'usage': cls.usage,
-                    'aliases': cls.aliases,
-                    'privilege': cls.privilege,
-                    'parent': path,
-                    'cls': cls,
-                    'sub': []
-                }
-                # 更新索引
-                __tree_index__[cls.__module__ + '.' + cls.__name__] = path + '.' + name
-
-            return cls
-        
-        return wrapper
-
-
-class CommandPrivilegeError(Exception):
-    """指令权限不足或不存在异常"""
-    pass
-
-
-# 传入Context对象，广搜命令树，返回执行结果
-# 若命令被处理，返回reply列表
-# 若命令未被处理，继续执行下一级指令
-# 若命令不存在，报异常
-def execute(context: Context) -> list:
-    """执行指令
-    
-    :param ctx: 指令执行上下文
-
-    :return: 回复列表
-    """
-    global __command_list__
-
-    # 拷贝ctx
-    ctx: Context = copy.deepcopy(context)
-
-    # 从树取出顶级指令
-    node = __command_list__
-    
-    path = ctx.command
-
-    while True:
-        try:
-            node = __command_list__[path]
-            logging.debug('执行指令: {}'.format(path))
-
-            # 检查权限
-            if ctx.privilege < node['privilege']:
-                raise CommandPrivilegeError(tips_custom.command_admin_message+"{}".format(path))
-            
-            # 执行
-            execed, reply = node['cls'].process(ctx)
-            if execed:
-                return reply
-            else:
-                # 删除crt_params第一个参数
-                ctx.crt_command = ctx.crt_params.pop(0)
-                # 下一个path
-                path = path + '.' + ctx.crt_command
-        except KeyError:
-            traceback.print_exc()
-            raise CommandPrivilegeError(tips_custom.command_err_message+"{}".format(path))
-
-
-def register_all():
-    """启动时调用此函数注册所有指令
-    
-    递归处理pkg.qqbot.cmds包下及其子包下所有模块的所有继承于AbstractCommand的类
-    """
-    # 模块：遍历其中的继承于AbstractCommand的类，进行注册
-    # 包：递归处理包下的模块
-    # 排除__开头的属性
-    global __command_list__, __tree_index__
-
-    import pkg.qqbot.cmds
-
-    def walk(module, prefix, path_prefix):
-        # 排除不处于pkg.qqbot.cmds中的包
-        if not module.__name__.startswith('pkg.qqbot.cmds'):
-            return
-        
-        logging.debug('walk: {}, path: {}'.format(module.__name__, module.__path__))
-        for item in pkgutil.iter_modules(module.__path__):
-            if item.name.startswith('__'):
-                continue
-
-            if item.ispkg:
-                walk(__import__(module.__name__ + '.' + item.name, fromlist=['']), prefix + item.name + '.', path_prefix + item.name + '/')
-            else:
-                m = __import__(module.__name__ + '.' + item.name, fromlist=[''])
-                # for name, cls in inspect.getmembers(m, inspect.isclass):
-                #     # 检查是否为指令类
-                #     if cls.__module__ == m.__name__ and issubclass(cls, AbstractCommandNode) and cls != AbstractCommandNode:
-                #         cls.register(cls, cls.name, cls.parent)
-
-    walk(pkg.qqbot.cmds, '', '')
-    logging.debug(__command_list__)
-
-
-def apply_privileges():
-    """读取cmdpriv.json并应用指令权限"""
-    # 读取内容
-    json_str = ""
-    with open('cmdpriv.json', 'r', encoding="utf-8") as f:
-        json_str = f.read()
-
-    data = json.loads(json_str)
-    for path, priv in data.items():
-        if path == 'comment':
-            continue
-        
-        if path not in __command_list__:
-            continue
-        
-        if __command_list__[path]['privilege'] != priv:
-            logging.debug('应用权限: {} -> {}(default: {})'.format(path, priv, __command_list__[path]['privilege']))
-
-        __command_list__[path]['privilege'] = priv

pkg/qqbot/cmds/funcs/draw.py

@@ -1,36 +0,0 @@
-from ..aamgr import AbstractCommandNode, Context
-import logging
-
-from mirai import Image
-import config
-
-
-@AbstractCommandNode.register(
-    parent=None,
-    name="draw",
-    description="使用DALL·E生成图片",
-    usage="!draw <图片提示语>",
-    aliases=[],
-    privilege=1
-)
-class DrawCommand(AbstractCommandNode):
-    @classmethod
-    def process(cls, ctx: Context) -> tuple[bool, list]:
-        import pkg.openai.session
-
-        reply = []
-        
-        if len(ctx.params) == 0:
-            reply = ["[bot]err: 未提供图片描述文字"]
-        else:
-            session = pkg.openai.session.get_session(ctx.session_name)
-
-            res = session.draw_image(" ".join(ctx.params))
-
-            logging.debug("draw_image result:{}".format(res))
-            reply = [Image(url=res['data'][0]['url'])]
-            if not (hasattr(config, 'include_image_description')
-                    and not config.include_image_description):
-                reply.append(" ".join(ctx.params))
-
-        return True, reply

pkg/qqbot/cmds/funcs/func.py

@@ -1,33 +0,0 @@
-from ..aamgr import AbstractCommandNode, Context
-import logging
-
-import json
-
-
-@AbstractCommandNode.register(
-    parent=None,
-    name="func",
-    description="管理内容函数",
-    usage="!func",
-    aliases=[],
-    privilege=1
-)
-class FuncCommand(AbstractCommandNode):
-    @classmethod
-    def process(cls, ctx: Context) -> tuple[bool, list]:
-        from pkg.plugin.models import host
-
-        reply = []
-
-        reply_str = "当前已加载的内容函数：\n\n"
-
-        logging.debug("host.__callable_functions__: {}".format(json.dumps(host.__callable_functions__, indent=4)))
-
-        index = 1
-        for func in host.__callable_functions__:
-            reply_str += "{}. {}{}:\n{}\n\n".format(index, ("(已禁用) " if not func['enabled'] else ""), func['name'], func['description'])
-            index += 1
-            
-        reply = [reply_str]
-
-        return True, reply