@dingtalk-real-ai/dingtalk-connector 0.7.1 → 0.7.3

package/.github/workflows/ai-fix-and-test.yml

@@ -0,0 +1,520 @@
+name: 🤖 AI 修复分支与测试
+
+on:
+  issues:
+    types: [labeled]
+  workflow_dispatch:
+    inputs:
+      issue_number:
+        description: 'Issue 编号'
+        required: true
+        type: string
+      test_mode:
+        description: '测试模式'
+        required: false
+        default: 'local'
+        type: choice
+        options:
+          - local
+          - github
+
+env:
+  DINGTALK_WEBHOOK: https://oapi.dingtalk.com/robot/send?access_token=8710dbbfa8b8b63a02ddfe41ae428b838d2f5e998e0ec446196981d97e7d5350
+  DINGTALK_KEYWORD: dingtalk-openclaw-connector
+  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+jobs:
+  # 检查是否需要执行 AI 修复
+  check-trigger:
+    runs-on: ubuntu-latest
+    outputs:
+      should_run: ${{ steps.check.outputs.should_run }}
+      issue_number: ${{ steps.check.outputs.issue_number }}
+      issue_title: ${{ steps.check.outputs.issue_title }}
+      issue_body: ${{ steps.check.outputs.issue_body }}
+    steps:
+      - name: 检查触发条件
+        id: check
+        uses: actions/github-script@v7
+        with:
+          script: |
+            let issueNumber, issueTitle, issueBody;
+            
+            // 判断触发方式
+            if (context.eventName === 'workflow_dispatch') {
+              // 手动触发
+              issueNumber = context.payload.inputs.issue_number;
+              
+              // 获取 Issue 信息
+              const { data: issue } = await github.rest.issues.get({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: parseInt(issueNumber)
+              });
+              
+              issueTitle = issue.title;
+              issueBody = issue.body || '';
+              
+            } else if (context.eventName === 'issues') {
+              // Issue 标签触发
+              if (context.payload.label?.name !== 'ai-fix') {
+                console.log('标签不是 ai-fix，跳过');
+                core.setOutput('should_run', 'false');
+                return;
+              }
+              
+              issueNumber = context.payload.issue.number;
+              issueTitle = context.payload.issue.title;
+              issueBody = context.payload.issue.body || '';
+            }
+            
+            core.setOutput('should_run', 'true');
+            core.setOutput('issue_number', issueNumber);
+            core.setOutput('issue_title', issueTitle);
+            core.setOutput('issue_body', issueBody);
+            
+            console.log(`✅ 触发 AI 修复流程 - Issue #${issueNumber}`);
+
+  # 创建修复分支
+  create-branch:
+    needs: check-trigger
+    runs-on: ubuntu-latest
+    if: needs.check-trigger.outputs.should_run == 'true'
+    outputs:
+      branch_name: ${{ steps.branch.outputs.branch_name }}
+    steps:
+      - name: 检出代码
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: 创建修复分支
+        id: branch
+        run: |
+          ISSUE_NUMBER=${{ needs.check-trigger.outputs.issue_number }}
+          ISSUE_TITLE="${{ needs.check-trigger.outputs.issue_title }}"
+          
+          # 生成安全的分支名
+          SAFE_TITLE=$(echo "$ISSUE_TITLE" | tr '[:upper:]' '[:lower:]' | tr -c 'a-z0-9' '-' | sed 's/-*$//' | cut -c1-50)
+          BRANCH_NAME="ai-fix/issue-${ISSUE_NUMBER}-${SAFE_TITLE}"
+          
+          echo "branch_name=$BRANCH_NAME" >> $GITHUB_OUTPUT
+          echo "🌿 创建分支: $BRANCH_NAME"
+          
+          # 配置 Git
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          
+          # 创建并推送分支
+          git checkout -b "$BRANCH_NAME"
+          git push origin "$BRANCH_NAME"
+          
+          echo "✅ 分支已创建: $BRANCH_NAME"
+
+  # 本地 AI 修复（通过 webhook 调用本地 OpenClaw）
+  ai-fix-local:
+    needs: [check-trigger, create-branch]
+    runs-on: ubuntu-latest
+    if: github.event.inputs.test_mode != 'github'
+    steps:
+      - name: 调用本地 AI 修复服务
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const issueNumber = '${{ needs.check-trigger.outputs.issue_number }}';
+            const issueTitle = '${{ needs.check-trigger.outputs.issue_title }}';
+            const issueBody = `${{ needs.check-trigger.outputs.issue_body }}`;
+            const branchName = '${{ needs.create-branch.outputs.branch_name }}';
+            
+            // 构建调用本地 OpenClaw 的 payload
+            const payload = {
+              action: 'ai-fix-issue',
+              issue: {
+                number: issueNumber,
+                title: issueTitle,
+                body: issueBody
+              },
+              branch: branchName,
+              repo: {
+                owner: context.repo.owner,
+                name: context.repo.repo
+              },
+              callback_url: `https://api.github.com/repos/${context.repo.owner}/${context.repo.repo}/issues/${issueNumber}/comments`
+            };
+            
+            console.log('📤 发送 AI 修复请求到本地服务...');
+            console.log('Payload:', JSON.stringify(payload, null, 2));
+            
+            // 这里可以通过 webhook 或 API 调用本地服务
+            // 实际实现需要根据你的本地 OpenClaw 部署方式调整
+            
+            // 在 Issue 中添加等待评论
+            await github.rest.issues.createComment({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: parseInt(issueNumber),
+              body: `⏳ **AI 修复进行中**\n\n分支 \`${branchName}\` 已创建\n\n已发送请求到本地 AI 服务，等待修复结果...\n\n**提示:** 本地 AI 修复完成后，测试结果将自动同步到钉钉群。`
+            });
+
+  # GitHub 环境 AI 修复（使用 GitHub Actions 运行器）
+  ai-fix-github:
+    needs: [check-trigger, create-branch]
+    runs-on: ubuntu-latest
+    # 标签触发时自动执行；手动触发时根据 test_mode 选择
+    if: |
+      github.event_name == 'issues' || 
+      github.event.inputs.test_mode == 'github' || 
+      (github.event_name == 'workflow_dispatch' && github.event.inputs.test_mode == 'github')
+    outputs:
+      lint_status: ${{ steps.lint.outputs.lint_status }}
+      typecheck_status: ${{ steps.typecheck.outputs.typecheck_status }}
+      test_result: ${{ steps.test.outputs.test_result }}
+    steps:
+      - name: 检出修复分支
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ needs.create-branch.outputs.branch_name }}
+          fetch-depth: 0
+
+      - name: 设置 Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+          cache: 'npm'
+
+      - name: 安装依赖
+        run: npm ci
+
+      - name: 分析 Issue 并调用 AI 生成修复
+        id: ai-analysis
+        env:
+          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+          DASHSCOPE_API_KEY: ${{ secrets.DASHSCOPE_API_KEY }}
+        run: |
+          echo "🤖 分析 Issue 内容..."
+          echo "Issue #${{ needs.check-trigger.outputs.issue_number }}: ${{ needs.check-trigger.outputs.issue_title }}"
+          
+          # 创建修复标记文件（开始分析）
+          cat > .ai-fix-info.json << EOF
+          {
+            "issue_number": ${{ needs.check-trigger.outputs.issue_number }},
+            "issue_title": "${{ needs.check-trigger.outputs.issue_title }}",
+            "fix_timestamp": "$(date -u +%Y-%m-%dT%H:%M:%SZ)",
+            "fix_method": "github-actions-ai",
+            "status": "analyzing"
+          }
+          EOF
+          
+          # 检查是否有 AI API Key
+          if [ -n "$OPENAI_API_KEY" ] || [ -n "$ANTHROPIC_API_KEY" ] || [ -n "$DASHSCOPE_API_KEY" ]; then
+            echo "✅ 发现 AI API Key，将尝试调用 AI 模型生成修复..."
+            
+            # 准备 Issue 内容
+            ISSUE_TITLE="${{ needs.check-trigger.outputs.issue_title }}"
+            ISSUE_BODY='${{ needs.check-trigger.outputs.issue_body }}'
+            
+            # 创建 AI 提示词
+            cat > /tmp/ai-prompt.txt << 'PROMPT'
+          你是一个专业的代码修复助手。请根据下面的 GitHub Issue 描述，分析代码问题并提供修复建议。
+          
+          Issue 标题: $ISSUE_TITLE
+          Issue 描述: $ISSUE_BODY
+          
+          请分析：
+          1. 问题的根本原因
+          2. 需要修改的文件
+          3. 具体的修复方案
+          
+          请以结构化的方式输出分析结果。
+          PROMPT
+            
+            # 尝试调用 OpenAI API（如果配置了）
+            if [ -n "$OPENAI_API_KEY" ]; then
+              echo "🔄 调用 OpenAI API..."
+              curl -s -X POST https://api.openai.com/v1/chat/completions \
+                -H "Authorization: Bearer $OPENAI_API_KEY" \
+                -H "Content-Type: application/json" \
+                -d '{
+                  "model": "gpt-4o-mini",
+                  "messages": [
+                    {"role": "system", "content": "你是一个专业的代码修复助手。请分析 GitHub Issue 并提供修复建议。"},
+                    {"role": "user", "content": "Issue 标题: '"$ISSUE_TITLE"'\n\nIssue 描述: '"$ISSUE_BODY"'\n\n请分析问题原因并提供修复方案。"}
+                  ],
+                  "temperature": 0.3
+                }' > /tmp/ai-response.json 2>/dev/null || echo "⚠️ OpenAI API 调用失败"
+              
+              if [ -f /tmp/ai-response.json ] && grep -q '"choices"' /tmp/ai-response.json; then
+                echo "✅ OpenAI 分析完成"
+                cat /tmp/ai-response.json | jq -r '.choices[0].message.content' > /tmp/ai-analysis.md || true
+              fi
+            fi
+            
+            # 尝试调用 Anthropic API（如果配置了且 OpenAI 失败）
+            if [ -n "$ANTHROPIC_API_KEY" ] && [ ! -f /tmp/ai-analysis.md ]; then
+              echo "🔄 调用 Anthropic API..."
+              curl -s -X POST https://api.anthropic.com/v1/messages \
+                -H "x-api-key: $ANTHROPIC_API_KEY" \
+                -H "Content-Type: application/json" \
+                -H "anthropic-version: 2023-06-01" \
+                -d '{
+                  "model": "claude-3-haiku-20240307",
+                  "max_tokens": 2000,
+                  "messages": [
+                    {"role": "user", "content": "Issue 标题: '"$ISSUE_TITLE"'\n\nIssue 描述: '"$ISSUE_BODY"'\n\n请分析问题原因并提供修复方案。"}
+                  ]
+                }' > /tmp/ai-response.json 2>/dev/null || echo "⚠️ Anthropic API 调用失败"
+              
+              if [ -f /tmp/ai-response.json ] && grep -q '"content"' /tmp/ai-response.json; then
+                echo "✅ Anthropic 分析完成"
+                cat /tmp/ai-response.json | jq -r '.content[0].text' > /tmp/ai-analysis.md || true
+              fi
+            fi
+            
+            # 尝试调用阿里云百炼 Qwen3.5 Plus API（如果配置了且前面的都失败）
+            if [ -n "$DASHSCOPE_API_KEY" ] && [ ! -f /tmp/ai-analysis.md ]; then
+              echo "🔄 调用阿里云百炼 Qwen3.5 Plus API..."
+              curl -s -X POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions \
+                -H "Authorization: Bearer $DASHSCOPE_API_KEY" \
+                -H "Content-Type: application/json" \
+                -d '{
+                  "model": "qwen3.5-plus",
+                  "messages": [
+                    {"role": "system", "content": "你是一个专业的代码修复助手。请分析 GitHub Issue 并提供修复建议。"},
+                    {"role": "user", "content": "Issue 标题: '"$ISSUE_TITLE"'\n\nIssue 描述: '"$ISSUE_BODY"'\n\n请分析问题原因并提供修复方案。"}
+                  ],
+                  "temperature": 0.3
+                }' > /tmp/ai-response.json 2>/dev/null || echo "⚠️ Qwen3.5 Plus API 调用失败"
+              
+              if [ -f /tmp/ai-response.json ] && grep -q '"choices"' /tmp/ai-response.json; then
+                echo "✅ Qwen3.5 Plus 分析完成"
+                cat /tmp/ai-response.json | jq -r '.choices[0].message.content' > /tmp/ai-analysis.md || true
+              fi
+            fi
+            
+            # 保存 AI 分析结果
+            if [ -f /tmp/ai-analysis.md ]; then
+              echo "📝 AI 分析结果："
+              cat /tmp/ai-analysis.md
+              cp /tmp/ai-analysis.md .ai-fix-analysis.md
+            else
+              echo "⚠️ AI 分析未完成，将使用默认分析流程"
+              echo "AI 分析暂不可用，请手动查看 Issue 并修复。" > .ai-fix-analysis.md
+            fi
+          else
+            echo "⚠️ 未配置 AI API Key (OPENAI_API_KEY、ANTHROPIC_API_KEY 或 DASHSCOPE_API_KEY)"
+            echo "请配置 Secrets 后重新运行，或手动修复代码。"
+            echo "未配置 AI API Key，请手动修复。" > .ai-fix-analysis.md
+          fi
+          
+          echo "analysis_complete=true" >> $GITHUB_OUTPUT
+
+      - name: 运行代码检查
+        id: lint
+        continue-on-error: true
+        run: |
+          echo "🔍 运行代码检查..."
+          npm run lint 2>&1 | tee lint-output.txt || true
+          echo "lint_status=$?" >> $GITHUB_OUTPUT
+
+      - name: 运行类型检查
+        id: typecheck
+        continue-on-error: true
+        run: |
+          echo "🔍 运行类型检查..."
+          npm run type-check 2>&1 | tee typecheck-output.txt || true
+          echo "typecheck_status=$?" >> $GITHUB_OUTPUT
+
+      - name: 运行测试
+        id: test
+        continue-on-error: true
+        run: |
+          echo "🧪 运行自动化测试..."
+          npm test 2>&1 | tee test-output.txt || true
+          echo "test_status=$?" >> $GITHUB_OUTPUT
+          
+          # 提取测试结果摘要
+          if grep -q "PASS\|✓" test-output.txt; then
+            echo "test_result=passed" >> $GITHUB_OUTPUT
+          else
+            echo "test_result=failed" >> $GITHUB_OUTPUT
+          fi
+
+      - name: 提交修复结果
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          
+          # 更新修复状态
+          cat > .ai-fix-info.json << EOF
+          {
+            "issue_number": ${{ needs.check-trigger.outputs.issue_number }},
+            "issue_title": "${{ needs.check-trigger.outputs.issue_title }}",
+            "fix_timestamp": "$(date -u +%Y-%m-%dT%H:%M:%SZ)",
+            "fix_method": "github-actions-ai",
+            "status": "completed",
+            "test_results": {
+              "lint": "${{ steps.lint.outputs.lint_status == '0' && 'passed' || 'failed' }}",
+              "typecheck": "${{ steps.typecheck.outputs.typecheck_status == '0' && 'passed' || 'failed' }}",
+              "test": "${{ steps.test.outputs.test_result }}"
+            }
+          }
+          EOF
+          
+          # 添加 AI 分析结果（如果存在）
+          if [ -f .ai-fix-analysis.md ]; then
+            git add .ai-fix-analysis.md
+          fi
+          
+          git add .ai-fix-info.json
+          git commit -m "🤖 AI 修复: Issue #${{ needs.check-trigger.outputs.issue_number }} - 自动修复结果" || echo "无变更需要提交"
+          git push origin ${{ needs.create-branch.outputs.branch_name }}
+
+  # 创建 PR
+  create-pr:
+    needs: [check-trigger, create-branch, ai-fix-github]
+    runs-on: ubuntu-latest
+    if: always() && (needs.ai-fix-github.result == 'success' || needs.ai-fix-github.result == 'skipped')
+    steps:
+      - name: 创建 Pull Request
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const issueNumber = parseInt('${{ needs.check-trigger.outputs.issue_number }}');
+            const branchName = '${{ needs.create-branch.outputs.branch_name }}';
+            
+            try {
+              const { data: pr } = await github.rest.pulls.create({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                title: `🤖 AI 修复: ${context.payload.issue?.title || `Issue #${issueNumber}`}`,
+                head: branchName,
+                base: 'main',
+                body: `## 🤖 AI 自动修复\n\n**关联 Issue:** #${issueNumber}\n\n**修复分支:** \`${branchName}\`\n\n**修复说明:**\n- 由 GitHub Actions 自动生成的修复\n- 基于 Issue 描述进行代码分析和修复\n- 包含自动化测试结果\n\n**测试状态:**\n- 代码检查: ${{ needs.ai-fix-github.outputs.lint_status == '0' && '✅ 通过' || '⚠️ 需关注' }}\n- 类型检查: ${{ needs.ai-fix-github.outputs.typecheck_status == '0' && '✅ 通过' || '⚠️ 需关注' }}\n- 单元测试: ${{ needs.ai-fix-github.outputs.test_result == 'passed' && '✅ 通过' || '⚠️ 需关注' }}\n\n**需要人工审核:**\n- [ ] 代码逻辑正确性\n- [ ] 边界情况处理\n- [ ] 性能影响评估\n\n---\n*此 PR 由 AI 修复工作流自动生成*`,
+                draft: false
+              });
+              
+              console.log(`✅ PR 创建成功: #${pr.number}`);
+              core.setOutput('pr_number', pr.number);
+              core.setOutput('pr_url', pr.html_url);
+              
+            } catch (error) {
+              console.error('创建 PR 失败:', error.message);
+              // PR 可能已存在，查找现有 PR
+              const { data: prs } = await github.rest.pulls.list({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                head: `${context.repo.owner}:${branchName}`,
+                base: 'main',
+                state: 'open'
+              });
+              
+              if (prs.length > 0) {
+                console.log(`ℹ️ PR 已存在: #${prs[0].number}`);
+                core.setOutput('pr_number', prs[0].number);
+                core.setOutput('pr_url', prs[0].html_url);
+              }
+            }
+
+  # 发送测试结果到钉钉
+  notify-result:
+    needs: [check-trigger, create-branch, ai-fix-github, create-pr]
+    runs-on: ubuntu-latest
+    if: always()
+    outputs:
+      notified: ${{ steps.notify.outputs.notified }}
+    steps:
+      - name: 发送测试结果到钉钉
+        id: notify
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const issueNumber = '${{ needs.check-trigger.outputs.issue_number }}';
+            const issueTitle = '${{ needs.check-trigger.outputs.issue_title }}';
+            const branchName = '${{ needs.create-branch.outputs.branch_name }}';
+            
+            // 确定整体状态（处理 ai-fix-github 被跳过的情况）
+            const lintStatus = '${{ needs.ai-fix-github.outputs.lint_status }}';
+            const typecheckStatus = '${{ needs.ai-fix-github.outputs.typecheck_status }}';
+            const testResult = '${{ needs.ai-fix-github.outputs.test_result }}';
+            
+            // 判断执行模式
+            const isLocalMode = '${{ github.event.inputs.test_mode }}' === 'local' && '${{ github.event_name }}' === 'workflow_dispatch';
+            const isLabelTrigger = '${{ github.event_name }}' === 'issues';
+            
+            let allPassed, statusEmoji, statusText, testResultsText;
+            
+            if (isLocalMode && lintStatus === '') {
+              // Local 模式：GitHub Actions 未执行测试
+              statusEmoji = '⏳';
+              statusText = '等待本地 AI 修复';
+              testResultsText = '- 📝 代码检查: ⏳ 等待本地执行\n- 🔍 类型检查: ⏳ 等待本地执行\n- 🧪 单元测试: ⏳ 等待本地执行';
+              allPassed = false;
+            } else {
+              // GitHub 模式（标签触发或手动选择 github 模式）：显示实际测试结果
+              allPassed = lintStatus === '0' && typecheckStatus === '0' && testResult === 'passed';
+              statusEmoji = allPassed ? '✅' : '⚠️';
+              statusText = allPassed ? '测试通过' : '需要关注';
+              testResultsText = `- 📝 代码检查: ${lintStatus === '0' ? '✅ 通过' : '❌ 失败'}\n- 🔍 类型检查: ${typecheckStatus === '0' ? '✅ 通过' : '❌ 失败'}\n- 🧪 单元测试: ${testResult === 'passed' ? '✅ 通过' : '❌ 失败'}`;
+            }
+            
+            // 构建钉钉消息
+            const keyword = process.env.DINGTALK_KEYWORD;
+            const message = {
+              msgtype: 'markdown',
+              markdown: {
+                title: `${keyword} - ${statusEmoji} AI 修复测试完成`,
+                text: `## ${statusEmoji} AI 修复测试${statusText}\n\n${keyword}\n\n**Issue:** [#${issueNumber} ${issueTitle}](https://github.com/${context.repo.owner}/${context.repo.repo}/issues/${issueNumber})\n\n**修复分支:** \`${branchName}\`\n\n**测试结果:**\n${testResultsText}\n\n**下一步:**\n${allPassed ? '✅ 所有测试通过，请审核 PR 后合并' : (lintStatus === '' ? '⏳ 本地 AI 修复完成后，请手动运行测试' : '⚠️ 部分测试未通过，请查看详细日志')}\n\n---\n⏰ ${new Date().toLocaleString('zh-CN')}`
+              }
+            };
+            
+            // 发送钉钉通知
+            const axios = require('axios');
+            try {
+              await axios.post(process.env.DINGTALK_WEBHOOK, message);
+              console.log('✅ 钉钉通知发送成功');
+              core.setOutput('notified', 'true');
+            } catch (error) {
+              console.error('❌ 钉钉通知发送失败:', error.message);
+              core.setOutput('notified', 'false');
+            }
+
+  # 更新 Issue 状态
+  update-issue:
+    needs: [check-trigger, create-branch, ai-fix-github, create-pr, notify-result]
+    runs-on: ubuntu-latest
+    if: always()
+    steps:
+      - name: 更新 Issue 评论
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const issueNumber = parseInt('${{ needs.check-trigger.outputs.issue_number }}');
+            const branchName = '${{ needs.create-branch.outputs.branch_name }}';
+            
+            const lintStatus = '${{ needs.ai-fix-github.outputs.lint_status }}';
+            const typecheckStatus = '${{ needs.ai-fix-github.outputs.typecheck_status }}';
+            const testResult = '${{ needs.ai-fix-github.outputs.test_result }}';
+            
+            // 判断执行模式
+            const isLocalMode = '${{ github.event.inputs.test_mode }}' === 'local' && '${{ github.event_name }}' === 'workflow_dispatch';
+            const isLabelTrigger = '${{ github.event_name }}' === 'issues';
+            
+            let comment = '';
+            
+            if (isLocalMode && lintStatus === '') {
+              // Local 模式：GitHub Actions 未执行测试
+              comment = `⏳ **AI 修复分支已创建**\n\n**修复分支:** \`${branchName}\`\n\n已触发本地 AI 修复流程。\n\n**注意:** 本地 AI 修复完成后，请手动推送代码并创建 PR。\n\n钉钉群已收到通知，可在群内查看进度。`;
+            } else if (lintStatus === '0' && typecheckStatus === '0' && testResult === 'passed') {
+              comment = `✅ **AI 修复完成**\n\n所有测试已通过！\n\n**修复分支:** \`${branchName}\`\n\n**测试结果:**\n- 📝 代码检查: ✅ 通过\n- 🔍 类型检查: ✅ 通过\n- 🧪 单元测试: ✅ 通过\n\n已创建 PR，请审核后合并。`;
+            } else {
+              comment = `⚠️ **AI 修复完成（需关注）**\n\n**修复分支:** \`${branchName}\`\n\n**测试结果:**\n- 📝 代码检查: ${lintStatus === '0' ? '✅ 通过' : '❌ 失败'}\n- 🔍 类型检查: ${typecheckStatus === '0' ? '✅ 通过' : '❌ 失败'}\n- 🧪 单元测试: ${testResult === 'passed' ? '✅ 通过' : '❌ 失败'}\n\n部分测试未通过，请查看详细日志并手动调整。`;
+            }
+            
+            await github.rest.issues.createComment({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: issueNumber,
+              body: comment
+            });

package/.github/workflows/issue-to-dingtalk.yml

@@ -0,0 +1,60 @@
+# Issue 自动同步到钉钉群
+# 当有新 Issue 或 Issue 评论时，自动发送到钉钉群
+name: 🔔 Issue Notification to DingTalk
+
+on:
+  issues:
+    types: [opened, reopened, closed, labeled]
+  issue_comment:
+    types: [created]
+
+jobs:
+  notify:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 📬 Send Issue to DingTalk
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const webhook = process.env.DINGTALK_WEBHOOK;
+            if (!webhook) {
+              console.log('⚠️ DINGTALK_WEBHOOK not set, skipping notification');
+              return;
+            }
+            
+            const event = context.eventName;
+            const payload = context.payload;
+            let title, content, url, action;
+            
+            if (event === 'issues') {
+              const issue = payload.issue;
+              action = payload.action;
+              title = `[${action.toUpperCase()}] Issue #${issue.number}: ${issue.title}`;
+              content = issue.body?.substring(0, 500) || 'No description';
+              url = issue.html_url;
+            } else if (event === 'issue_comment') {
+              const comment = payload.comment;
+              const issue = payload.issue;
+              action = 'commented';
+              title = `[COMMENT] Issue #${issue.number}: ${issue.title}`;
+              content = comment.body?.substring(0, 500) || 'No content';
+              url = comment.html_url;
+            }
+            
+            const message = {
+              msgtype: 'markdown',
+              markdown: {
+                title: 'GitHub Issue 通知',
+                text: `## 🔔 GitHub Issue 通知\n\n**${title}**\n\n${content}${content.length >= 500 ? '...' : ''}\n\n[点击查看详情](${url})\n\n---\n📦 ${context.repo.owner}/${context.repo.repo}`
+              }
+            };
+            
+            await fetch(webhook, {
+              method: 'POST',
+              headers: { 'Content-Type': 'application/json' },
+              body: JSON.stringify(message)
+            });
+            
+            console.log('✅ DingTalk notification sent');
+        env:
+          DINGTALK_WEBHOOK: ${{ secrets.DINGTALK_WEBHOOK }}

package/.github/workflows/pr-review.yml

@@ -0,0 +1,108 @@
+# PR 审核提醒工作流
+# PR 创建/更新时自动通知钉钉群，提醒审核
+name: 👀 PR Review Request
+
+on:
+  pull_request:
+    types: [opened, reopened, ready_for_review]
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  notify-review-request:
+    if: github.event_name == 'pull_request' && github.event.action != 'closed'
+    runs-on: ubuntu-latest
+    steps:
+      - name: 📢 Notify DingTalk - Review Request
+        if: env.DINGTALK_WEBHOOK != ''
+        run: |
+          PR_TITLE="${{ github.event.pull_request.title }}"
+          PR_URL="${{ github.event.pull_request.html_url }}"
+          PR_AUTHOR="${{ github.event.pull_request.user.login }}"
+          PR_NUMBER="${{ github.event.pull_request.number }}"
+          
+          curl -X POST "${{ secrets.DINGTALK_WEBHOOK }}" \
+            -H "Content-Type: application/json" \
+            -d "{
+              \"msgtype\": \"markdown\",
+              \"markdown\": {
+                \"title\": \"PR审核提醒\",
+                \"text\": \"## 👀 新的 PR 需要审核\\n\\n**#${PR_NUMBER}**: ${PR_TITLE}\\n\\n**作者**: @${PR_AUTHOR}\\n\\n[点击审核](${PR_URL})\\n\\n---\\n📦 ${{ github.repository }}\"
+              }
+            }"
+        env:
+          DINGTALK_WEBHOOK: ${{ secrets.DINGTALK_WEBHOOK }}
+
+  notify-review-completed:
+    if: github.event_name == 'pull_request_review'
+    runs-on: ubuntu-latest
+    steps:
+      - name: 📢 Notify DingTalk - Review Completed
+        if: env.DINGTALK_WEBHOOK != ''
+        run: |
+          REVIEW_STATE="${{ github.event.review.state }}"
+          PR_TITLE="${{ github.event.pull_request.title }}"
+          PR_URL="${{ github.event.pull_request.html_url }}"
+          REVIEWER="${{ github.event.review.user.login }}"
+          PR_NUMBER="${{ github.event.pull_request.number }}"
+          
+          if [ "$REVIEW_STATE" == "approved" ]; then
+            EMOJI="✅"
+            STATUS="已通过"
+          elif [ "$REVIEW_STATE" == "changes_requested" ]; then
+            EMOJI="🔄"
+            STATUS="需要修改"
+          else
+            EMOJI="💬"
+            STATUS="已评论"
+          fi
+          
+          curl -X POST "${{ secrets.DINGTALK_WEBHOOK }}" \
+            -H "Content-Type: application/json" \
+            -d "{
+              \"msgtype\": \"markdown\",
+              \"markdown\": {
+                \"title\": \"PR审核完成\",
+                \"text\": \"## ${EMOJI} PR 审核${STATUS}\\n\\n**#${PR_NUMBER}**: ${PR_TITLE}\\n\\n**审核人**: @${REVIEWER}\\n\\n**状态**: ${REVIEW_STATE}\\n\\n[查看详情](${PR_URL})\\n\\n---\\n📦 ${{ github.repository }}\"
+              }
+            }"
+        env:
+          DINGTALK_WEBHOOK: ${{ secrets.DINGTALK_WEBHOOK }}
+
+  auto-merge-check:
+    if: github.event_name == 'pull_request_review' && github.event.review.state == 'approved'
+    runs-on: ubuntu-latest
+    steps:
+      - name: 📥 Checkout Code
+        uses: actions/checkout@v4
+
+      - name: 🔍 Check Auto-Merge Conditions
+        id: check
+        run: |
+          # 检查是否满足自动合并条件
+          REVIEWS=$(curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+            "https://api.github.com/repos/${{ github.repository }}/pulls/${{ github.event.pull_request.number }}/reviews")
+          
+          APPROVALS=$(echo "$REVIEWS" | grep -c '"state": "APPROVED"' || true)
+          
+          echo "approvals=$APPROVALS" >> $GITHUB_OUTPUT
+          echo "✅ 当前 approvals: $APPROVALS"
+
+      - name: 📢 Notify DingTalk - Ready to Merge
+        if: steps.check.outputs.approvals >= 1 && env.DINGTALK_WEBHOOK != ''
+        run: |
+          PR_TITLE="${{ github.event.pull_request.title }}"
+          PR_URL="${{ github.event.pull_request.html_url }}"
+          PR_NUMBER="${{ github.event.pull_request.number }}"
+          
+          curl -X POST "${{ secrets.DINGTALK_WEBHOOK }}" \
+            -H "Content-Type: application/json" \
+            -d "{
+              \"msgtype\": \"markdown\",
+              \"markdown\": {
+                \"title\": \"PR可合并\",
+                \"text\": \"## 🎉 PR 已审核通过，可以合并\\n\\n**#${PR_NUMBER}**: ${PR_TITLE}\\n\\n**审核状态**: ✅ 已通过\\n\\n**操作**: 点击合并到 main\\n\\n[立即合并](${PR_URL})\\n\\n---\\n📦 ${{ github.repository }}\"
+              }
+            }"
+        env:
+          DINGTALK_WEBHOOK: ${{ secrets.DINGTALK_WEBHOOK }}

package/CHANGELOG.md

@@ -6,6 +6,44 @@
 This document records all significant changes. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and version numbers follow [Semantic Versioning](https://semver.org/).
 
+## [0.7.3] - 2026-03-09
+
+### 修复 / Fixes
+- 🐛 **兼容性修复**：修复 0.7.0 引入的默认 Agent 路由回归问题。0.7.0 之前默认路由到 `main` agent，0.7.0 之后错误地路由到 `default` agent，现已恢复为 `main` agent  
+  **Compatibility fix**: Fixed default agent routing regression introduced in 0.7.0. Before 0.7.0 default routed to `main` agent, after 0.7.0 incorrectly routed to `default` agent, now restored to `main` agent
+- 🐛 修复用户显式配置名为 `default` 的账号时被错误映射的问题：使用 `__default__` 作为内部默认账号标识  
+  Fixed issue where user-configured account named `default` was incorrectly mapped: Use `__default__` as internal default account identifier
+
+### 改进 / Improvements
+- 抽取 `DEFAULT_ACCOUNT_ID` 常量到文件顶部，统一管理默认账号标识  
+  Extracted `DEFAULT_ACCOUNT_ID` constant to file top, unified management of default account identifier
+- 更新 API 文档注释，移除对 `default` 的硬编码引用  
+  Updated API documentation comments, removed hardcoded references to `default`
+
+## [0.7.2] - 2026-03-05
+
+### 新增功能 / Added Features
+- ✅ 新增异步模式：立即回执用户消息，后台处理任务，然后主动推送最终结果作为独立消息  
+  Added async mode: immediately acknowledge user messages, process in background, then push the final result as a separate message
+- ✅ 支持自定义回执消息文本，可通过 `ackText` 配置项设置  
+  Support custom acknowledgment message text, configurable via `ackText` option
+
+### 修复 / Fixes
+- 🐛 修复异步模式下 Agent 路由问题：`streamFromGateway` 调用时缺少 `accountId` 参数，导致会话路由到 undefined agent  
+  Fixed agent routing in async mode: `streamFromGateway` was called without `accountId`, causing sessions to route to undefined agent
+- 🐛 修复默认 Agent 路由：当 `accountId` 为 `'default'` 时跳过 `X-OpenClaw-Agent-Id` header，让 gateway 路由到其配置的默认 agent  
+  Fixed default agent routing: Skip `X-OpenClaw-Agent-Id` header when `accountId` is `'default'`, letting gateway route to its configured default agent
+- 🐛 修复异步模式内容处理：使用 `userContent`（包含文件附件）替代原始 `content.text`  
+  Fixed async mode content: Use `userContent` (includes file attachments) instead of raw `content.text`
+- 🐛 修复异步模式图片支持：将 `imageLocalPaths` 传递给 gateway stream  
+  Fixed image support for async mode: Pass `imageLocalPaths` to gateway stream
+
+### 配置 / Configuration
+- 新增 `asyncMode` 配置项（默认：`false`）- 启用异步模式  
+  Added `asyncMode` configuration option (default: `false`) - Enable async mode
+- 新增 `ackText` 配置项（默认：`'🫡 任务已接收，处理中...'`）- 自定义回执消息文本  
+  Added `ackText` configuration option (default: `'🫡 任务已接收，处理中...'`) - Custom ack message text
+
 ## [0.7.1] - 2026-03-05
 
 ### 修复 / Fixes

package/README.md

@@ -2,7 +2,7 @@
 
 以下提供两种方案连接到 [OpenClaw](https://openclaw.ai) Gateway，分别是钉钉机器人和钉钉 DEAP Agent。
 
-> 📝 **版本信息**：当前版本 v0.7.1 | [查看变更日志](CHANGELOG.md) | [发布说明](RELEASE_NOTES_v0.7.1.md) | [发布指南](RELEASE.md)
+> 📝 **版本信息**：当前版本 v0.7.3 | [查看变更日志](CHANGELOG.md) | [发布说明](docs/RELEASE_NOTES_V0.7.3.md) | [发布指南](RELEASE.md)
 
 ## 快速导航
 
@@ -24,9 +24,11 @@
 - ✅ **主动发送消息** - 支持主动给钉钉个人或群发送消息
 - ✅ **富媒体接收** - 支持接收 JPEG/PNG 图片消息，自动下载并传递给视觉模型
 - ✅ **文件附件提取** - 支持解析 .docx、.pdf、纯文本文件（.txt、.md、.json 等）和二进制文件（.xlsx、.pptx、.zip 等）
+- ✅ **音频消息支持** - 支持发送音频消息，支持多种格式（mp3、wav、amr、ogg），自动提取音频时长，支持通过标记或文件附件方式发送
 - ✅ **钉钉文档 API** - 支持创建、追加、搜索、列举钉钉文档
 - ✅ **多 Agent 路由** - 支持一个连接器实例连接多个 Agent，多个钉钉机器人可分别绑定到不同 Agent，实现角色分工和专业化服务
 - ✅ **Markdown 表格转换** - 自动将 Markdown 表格转换为钉钉支持的文本格式，提升消息可读性
+- ✅ **异步模式** - 立即回执用户消息，后台处理任务，然后主动推送最终结果作为独立消息（可选）
 
 
 ## 架构
@@ -87,7 +89,9 @@ openclaw plugins install -l .
       "clientSecret": "your_secret_here", // 钉钉 AppSecret
       "gatewayToken": "",                 // 可选：Gateway 认证 token, openclaw.json配置中 gateway.auth.token 的值 
       "gatewayPassword": "",              // 可选：Gateway 认证 password（与 token 二选一）
-      "sessionTimeout": 1800000           // 可选：会话超时(ms)，默认 30 分钟
+      "sessionTimeout": 1800000,          // 可选：会话超时(ms)，默认 30 分钟
+      "asyncMode": false,                 // 可选：异步模式，立即回执用户消息，后台处理并推送结果（默认：false）
+      "ackText": "🫡 任务已接收"      // 可选：异步模式下的回执消息文本（默认：'🫡 任务已接收，处理中...'）
     }
   },
   "gateway": { // gateway通常是已有的节点，配置时注意把http部分追加到已有节点下
@@ -139,6 +143,48 @@ openclaw plugins list  # 确认 dingtalk-connector 已加载
 | `gatewayToken` | `OPENCLAW_GATEWAY_TOKEN` | Gateway 认证 token（可选） |
 | `gatewayPassword` | — | Gateway 认证 password（可选，与 token 二选一） |
 | `sessionTimeout` | — | 会话超时时间，单位毫秒（默认 1800000 = 30分钟） |
+| `asyncMode` | — | 异步模式，立即回执用户消息，后台处理并推送结果（默认：false） |
+| `ackText` | — | 异步模式下的回执消息文本（默认：'🫡 任务已接收，处理中...'） |
+
+## 异步模式
+
+异步模式允许连接器立即回执用户消息，然后在后台处理任务，最后主动推送最终结果作为独立消息。这种模式特别适合处理耗时较长的任务，可以给用户更好的交互体验。
+
+### 启用异步模式
+
+在配置中设置 `asyncMode: true`：
+
+```json5
+{
+  "channels": {
+    "dingtalk-connector": {
+      "enabled": true,
+      "clientId": "dingxxxxxxxxx",
+      "clientSecret": "your_secret_here",
+      "asyncMode": true,              // 启用异步模式
+      "ackText": "🫡 任务已接收"  // 可选：自定义回执消息
+    }
+  }
+}
+```
+
+### 工作流程
+
+1. **立即回执** - 用户发送消息后，连接器立即发送回执消息（默认：`🫡 任务已接收，处理中...`）
+2. **后台处理** - 连接器在后台调用 Gateway 处理任务，支持文件附件和图片
+3. **推送结果** - 处理完成后，连接器主动推送最终结果作为独立消息
+
+### 适用场景
+
+- ✅ 处理耗时较长的任务（如文档分析、代码生成等）
+- ✅ 需要给用户即时反馈的场景
+- ✅ 希望将处理过程和结果分离的场景
+
+### 注意事项
+
+- 异步模式下不支持 AI Card 流式响应（因为结果通过主动推送发送）
+- 异步模式支持文件附件和图片处理
+- 错误信息也会通过主动推送发送给用户
 
 ## 多 Agent 配置
 

package/docs/RELEASE_NOTES_V0.7.2.md

@@ -0,0 +1,143 @@
+# Release Notes - v0.7.2
+
+## ✨ 功能增强版本 / Feature Enhancement Release
+
+本次更新新增异步模式功能，并修复了多个关键问题，提升了连接器的稳定性和用户体验。
+
+This update adds async mode functionality and fixes several critical issues, improving connector stability and user experience.
+
+## ✨ 新增功能 / New Features
+
+### 1. 异步模式 / Async Mode
+
+**功能描述 / Feature Description**：立即回执用户消息，后台处理任务，然后主动推送最终结果作为独立消息  
+Immediately acknowledge user messages, process in background, then push the final result as a separate message
+
+**使用场景 / Use Cases**：
+- 处理耗时较长的任务（如文档分析、代码生成等）  
+  Processing time-consuming tasks (e.g., document analysis, code generation)
+- 需要给用户即时反馈的场景  
+  Scenarios requiring immediate user feedback
+- 希望将处理过程和结果分离的场景  
+  Scenarios where separating processing and results is desired
+
+**配置方式 / Configuration**：
+
+```json5
+{
+  "channels": {
+    "dingtalk-connector": {
+      "asyncMode": true,              // 启用异步模式 / Enable async mode
+      "ackText": "🫡 任务已接收"  // 可选：自定义回执消息 / Optional: Custom ack message
+    }
+  }
+}
+```
+
+**工作流程 / Workflow**：
+1. **立即回执** - 用户发送消息后，连接器立即发送回执消息  
+   **Immediate Acknowledgment** - Connector immediately sends acknowledgment message after user sends message
+2. **后台处理** - 连接器在后台调用 Gateway 处理任务，支持文件附件和图片  
+   **Background Processing** - Connector processes task in background via Gateway, supports file attachments and images
+3. **推送结果** - 处理完成后，连接器主动推送最终结果作为独立消息  
+   **Push Result** - After processing completes, connector proactively pushes final result as separate message
+
+**影响范围 / Impact**：所有用户均可选择启用此功能，默认关闭，不影响现有使用方式  
+All users can optionally enable this feature. Default is off, does not affect existing usage.
+
+## 🐛 修复 / Fixes
+
+### 1. 异步模式下 Agent 路由问题修复 / Agent Routing Fix in Async Mode
+
+**问题描述 / Issue Description**：异步模式下 `streamFromGateway` 调用时缺少 `accountId` 参数，导致会话路由到 undefined agent  
+In async mode, `streamFromGateway` was called without `accountId`, causing sessions to route to undefined agent
+
+**修复内容 / Fix**：
+- 修复 `streamFromGateway` 调用，正确传递 `accountId` 参数  
+  Fixed `streamFromGateway` call to correctly pass `accountId` parameter
+- 确保异步模式下 Agent 路由正常工作  
+  Ensures Agent routing works correctly in async mode
+
+**影响范围 / Impact**：影响使用异步模式的用户，修复后异步模式下的 Agent 路由将正常工作  
+Affects users using async mode. After the fix, Agent routing in async mode will work correctly.
+
+### 2. 默认 Agent 路由修复 / Default Agent Routing Fix
+
+**问题描述 / Issue Description**：当 `accountId` 为 `'default'` 时，仍然发送 `X-OpenClaw-Agent-Id` header，导致路由异常  
+When `accountId` is `'default'`, `X-OpenClaw-Agent-Id` header was still sent, causing routing issues
+
+**修复内容 / Fix**：
+- 当 `accountId` 为 `'default'` 时跳过 `X-OpenClaw-Agent-Id` header  
+  Skip `X-OpenClaw-Agent-Id` header when `accountId` is `'default'`
+- 让 gateway 路由到其配置的默认 agent  
+  Let gateway route to its configured default agent
+
+**影响范围 / Impact**：影响使用默认 Agent 配置的用户，修复后默认 Agent 路由将正常工作  
+Affects users with default Agent configuration. After the fix, default Agent routing will work correctly.
+
+### 3. 异步模式内容处理修复 / Async Mode Content Fix
+
+**问题描述 / Issue Description**：异步模式使用原始 `content.text`，未包含文件附件内容  
+Async mode used raw `content.text`, did not include file attachment content
+
+**修复内容 / Fix**：
+- 使用 `userContent`（包含文件附件）替代原始 `content.text`  
+  Use `userContent` (includes file attachments) instead of raw `content.text`
+- 确保文件附件内容正确传递给 Gateway  
+  Ensures file attachment content is correctly passed to Gateway
+
+**影响范围 / Impact**：影响使用异步模式且发送文件附件的用户，修复后文件附件将正确处理  
+Affects users using async mode and sending file attachments. After the fix, file attachments will be processed correctly.
+
+### 4. 异步模式图片支持修复 / Async Mode Image Support Fix
+
+**问题描述 / Issue Description**：异步模式下未将图片路径传递给 Gateway stream  
+Image paths were not passed to Gateway stream in async mode
+
+**修复内容 / Fix**：
+- 将 `imageLocalPaths` 传递给 gateway stream  
+  Pass `imageLocalPaths` to gateway stream
+- 确保图片在异步模式下正确处理  
+  Ensures images are processed correctly in async mode
+
+**影响范围 / Impact**：影响使用异步模式且发送图片的用户，修复后图片将正确处理  
+Affects users using async mode and sending images. After the fix, images will be processed correctly.
+
+## 🔧 配置更新 / Configuration Updates
+
+### 新增配置项 / New Configuration Options
+
+- **`asyncMode`**（类型：`boolean`，默认：`false`）- 启用异步模式  
+  **`asyncMode`** (type: `boolean`, default: `false`) - Enable async mode
+- **`ackText`**（类型：`string`，默认：`'🫡 任务已接收，处理中...'`）- 自定义回执消息文本  
+  **`ackText`** (type: `string`, default: `'🫡 任务已接收，处理中...'`) - Custom ack message text
+
+## 📥 安装升级 / Installation & Upgrade
+
+```bash
+# 通过 npm 安装最新版本 / Install latest version via npm
+openclaw plugins install @dingtalk-real-ai/dingtalk-connector
+
+# 或升级现有版本 / Or upgrade existing version
+openclaw plugins update dingtalk-connector
+
+# 通过 Git 安装 / Install via Git
+openclaw plugins install https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector.git
+```
+
+## 🔗 相关链接 / Related Links
+
+- [完整变更日志 / Full Changelog](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/blob/main/CHANGELOG.md)
+- [使用文档 / Documentation](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/blob/main/README.md)
+- [问题反馈 / Issue Feedback](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues)
+
+## 🙏 致谢 / Acknowledgments
+
+感谢所有贡献者和用户的支持与反馈！  
+Thanks to all contributors and users for their support and feedback!
+
+---
+
+**发布日期 / Release Date**：2026-03-05  
+**版本号 / Version**：v0.7.2  
+**兼容性 / Compatibility**：OpenClaw Gateway 0.4.0+

package/docs/RELEASE_NOTES_V0.7.3.md

@@ -0,0 +1,149 @@
+# Release Notes - v0.7.3
+
+## 🔧 兼容性修复版本 / Compatibility Fix Release
+
+本次更新主要修复了 0.7.0 版本引入的默认 Agent 路由回归问题，确保与 0.7.0 之前版本的向下兼容性。
+
+This update primarily fixes the default Agent routing regression introduced in version 0.7.0, ensuring backward compatibility with versions before 0.7.0.
+
+## 🐛 修复 / Fixes
+
+### 1. 默认 Agent 路由兼容性修复 / Default Agent Routing Compatibility Fix
+
+**问题描述 / Issue Description**：  
+在 0.7.0 版本中，默认路由（没有配置 `accountId` 时）从 `main` agent 错误地改成了 `default` agent，导致与 0.7.0 之前版本的行为不一致，可能影响现有用户的配置和会话路由。  
+In version 0.7.0, the default route (when no `accountId` was configured) was incorrectly changed from `main` agent to `default` agent, causing inconsistency with versions before 0.7.0, which may affect existing user configurations and session routing.
+
+**修复内容 / Fix**：
+- 恢复默认路由到 `main` agent，与 0.7.0 之前版本保持一致  
+  Restored default routing to `main` agent, consistent with versions before 0.7.0
+- 使用 `__default__` 作为内部默认账号标识，避免与用户配置的 `default` 账号冲突  
+  Use `__default__` as internal default account identifier to avoid conflicts with user-configured `default` accounts
+- 在 `streamFromGateway` 中将 `__default__` 正确映射到 `main` agent  
+  Correctly map `__default__` to `main` agent in `streamFromGateway`
+
+**影响范围 / Impact**：  
+影响所有使用默认配置（未配置 `accounts`）的用户。修复后，默认路由将恢复到 0.7.0 之前的行为，路由到 `main` agent，确保向下兼容性。  
+Affects all users using default configuration (without `accounts` configuration). After the fix, default routing will be restored to pre-0.7.0 behavior, routing to `main` agent, ensuring backward compatibility.
+
+### 2. 用户配置 `default` 账号映射修复 / User-Configured `default` Account Mapping Fix
+
+**问题描述 / Issue Description**：  
+当用户显式配置名为 `default` 的账号时，系统会错误地将其映射为内部默认账号，导致用户配置的 `default` 账号无法正常使用。  
+When users explicitly configure an account named `default`, the system incorrectly maps it to the internal default account, preventing the user-configured `default` account from working properly.
+
+**修复内容 / Fix**：
+- 使用 `__default__` 作为内部默认账号标识，与用户配置的 `default` 账号区分开  
+  Use `__default__` as internal default account identifier, separate from user-configured `default` accounts
+- 确保用户配置的 `default` 账号能够正常使用  
+  Ensure user-configured `default` accounts can work properly
+
+**影响范围 / Impact**：  
+影响显式配置了名为 `default` 的账号的用户。修复后，用户配置的 `default` 账号将能够正常工作，不会被错误映射。  
+Affects users who explicitly configured an account named `default`. After the fix, user-configured `default` accounts will work properly and will not be incorrectly mapped.
+
+## 🔧 改进 / Improvements
+
+### 1. 代码结构优化 / Code Structure Optimization
+
+**改进内容 / Improvements**：
+- 抽取 `DEFAULT_ACCOUNT_ID` 常量到文件顶部（值为 `__default__`），统一管理默认账号标识  
+  Extracted `DEFAULT_ACCOUNT_ID` constant to file top (value: `__default__`), unified management of default account identifier
+- 更新所有相关代码，使用常量替代硬编码的字符串  
+  Updated all related code to use constants instead of hardcoded strings
+- 提高代码可维护性和可读性  
+  Improved code maintainability and readability
+
+**影响范围 / Impact**：  
+内部代码改进，不影响用户使用，但提高了代码质量和可维护性。  
+Internal code improvements, does not affect user usage, but improves code quality and maintainability.
+
+### 2. API 文档更新 / API Documentation Updates
+
+**改进内容 / Improvements**：
+- 更新 API 文档注释，移除对 `default` 的硬编码引用  
+  Updated API documentation comments, removed hardcoded references to `default`
+- 明确说明 `accountId` 参数为可选，不传则使用默认配置  
+  Clarified that `accountId` parameter is optional, uses default configuration if not provided
+
+**影响范围 / Impact**：  
+文档改进，帮助开发者更好地理解 API 的使用方式。  
+Documentation improvements, helping developers better understand API usage.
+
+## 📋 技术细节 / Technical Details
+
+### 内部实现变更 / Internal Implementation Changes
+
+**变更前 / Before**：
+- 默认账号标识使用 `'default'` 字符串
+- 当 `accountId` 为 `'default'` 时，不发送 `X-OpenClaw-Agent-Id` header，让 gateway 路由到其配置的默认 agent
+
+**变更后 / After**：
+- 默认账号标识使用 `'__default__'` 常量
+- 在 `streamFromGateway` 中，将 `'__default__'` 映射到 `'main'` agent，并发送 `X-OpenClaw-Agent-Id: main` header
+- 用户配置的 `'default'` 账号正常使用，不会被特殊处理
+
+### 相关代码位置 / Related Code Locations
+
+主要修改文件：
+- `plugin.ts` - 核心逻辑修改
+
+关键变更点：
+- 新增 `DEFAULT_ACCOUNT_ID` 常量定义
+- `streamFromGateway` 函数中的 agent 路由逻辑
+- `listAccountIds`、`resolveAccount`、`defaultAccountId` 等配置相关函数
+- API 方法文档注释
+
+## 📥 安装升级 / Installation & Upgrade
+
+```bash
+# 通过 npm 安装最新版本 / Install latest version via npm
+openclaw plugins install @dingtalk-real-ai/dingtalk-connector
+
+# 或升级现有版本 / Or upgrade existing version
+openclaw plugins update dingtalk-connector
+
+# 通过 Git 安装 / Install via Git
+openclaw plugins install https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector.git
+```
+
+## ⚠️ 升级注意事项 / Upgrade Notes
+
+### 兼容性说明 / Compatibility Notes
+
+- **向下兼容**：本次更新恢复了 0.7.0 之前版本的默认路由行为，对现有用户完全兼容  
+  **Backward Compatible**: This update restores the default routing behavior of versions before 0.7.0, fully compatible with existing users
+- **无需配置变更**：现有配置无需修改即可正常工作  
+  **No Configuration Changes Required**: Existing configurations work without modification
+- **推荐升级**：使用默认配置的用户强烈建议升级到此版本，以确保正确的 Agent 路由  
+  **Recommended Upgrade**: Users with default configuration are strongly recommended to upgrade to this version to ensure correct Agent routing
+
+### 迁移指南 / Migration Guide
+
+如果您在 0.7.0 或 0.7.1 版本中遇到了默认路由问题，升级到此版本后：
+If you encountered default routing issues in versions 0.7.0 or 0.7.1, after upgrading to this version:
+
+1. **默认路由将自动恢复**：无需任何配置，默认路由将自动恢复到 `main` agent  
+   **Default routing will be automatically restored**: No configuration needed, default routing will automatically restore to `main` agent
+2. **检查 Agent 配置**：确认您的 Gateway 中 `main` agent 的配置是否正确  
+   **Check Agent Configuration**: Verify that your Gateway's `main` agent configuration is correct
+3. **验证路由**：升级后测试会话路由，确认消息正确路由到预期的 agent  
+   **Verify Routing**: Test session routing after upgrade to confirm messages are correctly routed to the expected agent
+
+## 🔗 相关链接 / Related Links
+
+- [完整变更日志 / Full Changelog](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/blob/main/CHANGELOG.md)
+- [使用文档 / Documentation](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/blob/main/README.md)
+- [问题反馈 / Issue Feedback](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues)
+- [Pull Request #108](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/pull/108)
+
+## 🙏 致谢 / Acknowledgments
+
+感谢所有贡献者和用户的支持与反馈！
+Thanks to all contributors and users for their support and feedback! 
+
+---
+
+**发布日期 / Release Date**：2026-03-09  
+**版本号 / Version**：v0.7.3  
+**兼容性 / Compatibility**：OpenClaw Gateway 0.4.0+

package/openclaw.plugin.json

@@ -1,7 +1,7 @@
 {
   "id": "dingtalk-connector",
   "name": "DingTalk Channel",
-  "version": "0.7.1",
+  "version": "0.7.3",
   "description": "DingTalk (钉钉) messaging channel via Stream mode with AI Card streaming",
   "author": "DingTalk Real Team",
   "channels": ["dingtalk-connector"],

package/package.json

@@ -1,11 +1,24 @@
 {
   "name": "@dingtalk-real-ai/dingtalk-connector",
-  "version": "0.7.1",
+  "version": "0.7.3",
   "description": "DingTalk (钉钉) channel connector — Stream mode with AI Card streaming",
   "main": "plugin.ts",
   "type": "module",
   "scripts": {
-    "build": "echo 'No build needed - jiti loads TS at runtime'"
+    "build": "echo 'No build needed - jiti loads TS at runtime'",
+    "lint": "echo 'Lint check skipped'",
+    "lint:fix": "echo 'Lint fix skipped'",
+    "test": "echo 'Tests skipped'",
+    "test:watch": "echo 'Tests skipped'",
+    "type-check": "npx tsc --noEmit",
+    "version:check": "echo 'Version check skipped'",
+    "release:prepare": "echo 'Release prepare skipped'",
+    "release:publish": "npm publish --access public",
+    "release:verify": "npm view @dingtalk-real-ai/dingtalk-connector version",
+    "clean": "rm -rf node_modules package-lock.json",
+    "install:fresh": "npm run clean && npm install",
+    "dev": "echo 'Run: openclaw start'",
+    "validate": "npm run lint && npm run type-check && npm run version:check"
   },
   "keywords": [
     "dingtalk",

package/plugin.ts

@@ -16,6 +16,9 @@ import type { ClawdbotPluginApi, PluginRuntime, ClawdbotConfig } from 'clawdbot/
 
 export const id = 'dingtalk-connector';
 
+/** 默认账号 ID，用于标记单账号模式（无 accounts 配置）时的内部标识，映射到 'main' agent */
+const DEFAULT_ACCOUNT_ID = '__default__';
+
 let runtime: PluginRuntime | null = null;
 
 function getRuntime(): PluginRuntime {
@@ -1220,7 +1223,9 @@ async function* streamFromGateway(options: GatewayOptions, accountId: string): A
     headers['Authorization'] = `Bearer ${gatewayAuth}`;
   }
   // 使用 HTTP Header 传递 accountId 用于 agent 路由
-  headers['X-OpenClaw-Agent-Id'] = accountId;
+  // DEFAULT_ACCOUNT_ID 映射到 'main' agent
+  const agentId = accountId === DEFAULT_ACCOUNT_ID ? 'main' : accountId;
+  headers['X-OpenClaw-Agent-Id'] = agentId;
 
   log?.info?.(`[DingTalk][Gateway] POST ${gatewayUrl}, session=${sessionKey}, accountId=${accountId}, messages=${messages.length}`);
 
@@ -2492,13 +2497,13 @@ async function handleDingTalkMessage(params: {
     let fullResponse = '';
     try {
       for await (const chunk of streamFromGateway({
-        userContent: content.text,
+        userContent,
         systemPrompts,
         sessionKey,
         gatewayAuth,
         imageLocalPaths: imageLocalPaths.length > 0 ? imageLocalPaths : undefined,
         log,
-      })) {
+      }, accountId)) {
         fullResponse += chunk;
       }
 
@@ -3042,19 +3047,21 @@ const dingtalkPlugin = {
   config: {
     listAccountIds: (cfg: ClawdbotConfig) => {
       const config = getConfig(cfg);
+      // __default__ 是内部标记，表示使用顶层配置（单账号模式）
       return config.accounts
         ? Object.keys(config.accounts)
-        : (isConfigured(cfg) ? ['default'] : []);
+        : (isConfigured(cfg) ? ['__default__'] : []);
     },
     resolveAccount: (cfg: ClawdbotConfig, accountId?: string) => {
       const config = getConfig(cfg);
-      const id = accountId || 'default';
+      const id = accountId || DEFAULT_ACCOUNT_ID;
       if (config.accounts?.[id]) {
         return { accountId: id, config: config.accounts[id], enabled: config.accounts[id].enabled !== false };
       }
-      return { accountId: 'default', config, enabled: config.enabled !== false };
+      // 没有 accounts 配置或找不到指定账号时，使用顶层配置
+      return { accountId: DEFAULT_ACCOUNT_ID, config, enabled: config.enabled !== false };
     },
-    defaultAccountId: () => 'default',
+    defaultAccountId: () => '__default__',
     isConfigured: (account: any) => Boolean(account.config?.clientId && account.config?.clientSecret),
     describeAccount: (account: any) => ({
       accountId: account.accountId,
@@ -3275,7 +3282,7 @@ const dingtalkPlugin = {
     },
   },
   status: {
-    defaultRuntime: { accountId: 'default', running: false, lastStartAt: null, lastStopAt: null, lastError: null },
+    defaultRuntime: { accountId: DEFAULT_ACCOUNT_ID, running: false, lastStartAt: null, lastStopAt: null, lastError: null },
     probe: async ({ cfg }: any) => {
       if (!isConfigured(cfg)) return { ok: false, error: 'Not configured' };
       try {
@@ -3332,7 +3339,7 @@ const plugin = {
      *   - title?: markdown 消息标题
      *   - useAICard?: 是否使用 AI Card（默认 true）
      *   - fallbackToNormal?: AI Card 失败时是否降级到普通消息（默认 true）
-     *   - accountId?: 使用的账号 ID（默认 default）
+     *   - accountId?: 使用的账号 ID（可选，不传则使用默认配置）
      */
     api.registerGatewayMethod('dingtalk-connector.sendToUser', async ({ respond, cfg, params, log }: any) => {
       const { userId, userIds, content, msgType, title, useAICard, fallbackToNormal, accountId } = params || {};
@@ -3370,7 +3377,7 @@ const plugin = {
      *   - title?: markdown 消息标题
      *   - useAICard?: 是否使用 AI Card（默认 true）
      *   - fallbackToNormal?: AI Card 失败时是否降级到普通消息（默认 true）
-     *   - accountId?: 使用的账号 ID（默认 default）
+     *   - accountId?: 使用的账号 ID（可选，不传则使用默认配置）
      */
     api.registerGatewayMethod('dingtalk-connector.sendToGroup', async ({ respond, cfg, params, log }: any) => {
       const { openConversationId, content, msgType, title, useAICard, fallbackToNormal, accountId } = params || {};