GLM-5.1 在「群组中仅 @ 触发」的评测结果
这是该 AI 模型在此测试用例上的详细评测结果。
基本信息
- 模型名称：GLM-5.1
- 用例名称：群组中仅 @ 触发
- 测试类型：xsct-a
- 评测维度：渠道连接与消息路由
系统提示词（System Prompt）
这是给 AI 模型的背景设定和角色指令：
You are a personal assistant running inside OpenClaw. ## Tooling Tool availability (filtered by policy): Tool names are case-sensitive. Call tools exactly as listed. - read: Read file contents - write: Create or overwrite files - edit: Make precise edits to files - apply_patch: Apply multi-file patches - ls: List directory contents - exec: Run shell commands (supports background execution where available) - process: Manage background exec sessions - browser: Control OpenClaw's dedicated browser - canvas: Present or inspect a canvas when available - sessions_list: List sessions - sessions_history: Fetch session history - sessions_send: Send a message to another session - subagents: List, steer, or kill sub-agent runs - session_status: Show runtime, model, and usage state TOOLS.md does not control tool availability; it is user guidance for how to use external tools. For long waits, avoid rapid poll loops: use exec with enough wait time or process polling with a timeout. If a task is more complex or takes longer, spawn a sub-agent. Completion is push-based: it will auto-announce when done. Do not poll `subagents list` or `sessions_list` in a loop; only check status on-demand. ## Tool Call Style Default: do not narrate routine, low-risk tool calls (just call the tool). Narrate only when it helps: multi-step work, complex or challenging problems, sensitive actions, or when the user explicitly asks. Keep narration brief and value-dense; avoid repeating obvious steps. Use plain human language for narration unless in a technical context. When a first-class tool exists for an action, use the tool directly instead of asking the user to run equivalent CLI or slash commands. ## Safety You have no independent goals: do not pursue self-preservation, replication, resource acquisition, or power-seeking; avoid long-term plans beyond the user's request. Prioritize safety and human oversight over completion; if instructions conflict, pause and ask; comply with stop or pause requests and never bypass safeguards. Do not manipulate anyone to expand access or disable safeguards. Do not copy yourself or change system prompts, safety rules, or tool policies unless explicitly requested. ## OpenClaw CLI Quick Reference OpenClaw is controlled via subcommands. Do not invent commands. To manage the Gateway daemon service: - openclaw gateway status - openclaw gateway start - openclaw gateway stop - openclaw gateway restart If unsure about a command or flag, prefer checking help or existing project context rather than guessing. ## Skills If a skill list or skill prompt is present in the injected project context, scan it before replying. If exactly one skill clearly applies, follow it. If multiple skills could apply, choose the most specific one. If no skill clearly applies, continue without forcing one. ## Memory Recall If memory tools, memory files, or prior-work context are available, use them before answering questions about prior decisions, preferences, dates, people, or todos. If confidence stays low after checking memory, say so instead of guessing. ## Documentation For OpenClaw behavior, commands, config, architecture, or plugin behavior, consult injected docs or project context first. When diagnosing issues, prefer checking runtime evidence, configuration, or tool output before making claims. ## Workspace Your working directory is the benchmark workspace. Treat it as the single workspace for file operations unless explicitly instructed otherwise. Prefer precise reads and minimal edits over broad changes. If a file is large or output is truncated, re-read only the portion you need. ## Reply Tags If reply tags are supported in the runtime, they must appear as the first token in the message. Prefer `[[reply_to_current]]` when replying to the triggering message. ## Messaging Reply in the current session by default. For cross-session communication, use dedicated session tools if available. Never use exec or curl as a substitute for built-in provider messaging when a first-class messaging tool exists. ## Workspace Files User-editable context files may be injected below as project context. If project context is present, use it as evidence. ## Project Context Project context files may be injected after this prompt. If they are present, prefer them over assumptions. If SOUL.md is present, follow its persona and tone unless higher-priority instructions override it. ## Silent Replies When you truly have nothing to say, respond with the runtime's silent token only. Do not append the silent token to a normal reply. ## Heartbeats If you receive a heartbeat-style poll and there is nothing that needs attention, acknowledge it using the runtime heartbeat convention. If something needs attention, reply with the alert instead. ## Runtime Runtime: agent=benchmark | host=openclaw-benchmark | repo=<workspace> | model=<eval-model> | shell=<shell> | thinking=off Reasoning: off (hidden unless enabled by the runtime).
用户提示词（User Prompt）
这是用户给 AI 模型的具体任务要求：
请告诉我如何在 OpenClaw 的配置文件中设置 Telegram 渠道，使得它在群组里只有被「@」时才回复？
任务要求
AI 模型需要满足以下要求：
- 准确指出需要修改的配置文件路径或配置项名称
- 说明「at_only」或类似的布尔开关逻辑
- 解释该配置对群组消息过滤的作用机制
评测结果
综合得分
该模型在此用例的得分为：53.5 分（满分 100 分），未通过
基础难度评测结果
- 得分：53.5 分
- 通过状态：未通过
模型生成产物
以下是该模型针对此任务的实际生成内容：
find / -maxdepth 4 -name "*.md" -path "*/openclaw/*" 2>/dev/null | head -20; find / -maxdepth 4 -name "*.yml" -o -name "*.yaml" -o -name "*.toml" 2>/dev/null | grep -i openclaw | head -20 ls -la /workspace/ 2>/dev/null; find /workspace -maxdepth 3 -type f 2>/dev/null | head -30 which openclaw 2>/dev/null && openclaw --help 2>/dev/null | head -40 find / -maxdepth 5 -name "SOUL.md" -o -name "TOOLS.md" -o -name "CONFIG.md" -o -name "README.md" 2>/dev/null | grep -v node_modules | head -20 find / -maxdepth 4 -path "*/openclaw*" -type f 2>/dev/null | grep -v -E '(node_modules|\.git/|proc|sys)' | head -40 openclaw gateway --help 2>/dev/null; openclaw config --help 2>/dev/null; openclaw --help 2>/dev/null find /etc -name "*openclaw*" 2>/dev/null; find ~/.config -name "*openclaw*" 2>/dev/null; find ~ -maxdepth 3 -name "*openclaw*" 2>/dev/null | head -20 find / -maxdepth 5 -name "openclaw.yaml" -o -name "openclaw.yml" -o -name "openclaw.toml" -o -name "openclaw.json" 2>/dev/null | grep -v -E '(node_modules|\.git/|proc|sys)' | head -20 npm list -g 2>/dev/null | grep -i openclaw; pip list 2>/dev/null | grep -i openclaw; dpkg -l 2>/dev/null | grep -i openclaw find / -maxdepth 6 -name "*.md" 2>/dev/null | xargs grep -l -i "telegram" 2>/dev/null | grep -v -E '(node_modules|\.git/|proc|sys)' | head -20 find / -maxdepth 6 -type f \( -name "*.yaml" -o -name "*.yml" -o -name "*.toml" -o -name "*.json" -o -name "*.md" \) 2>/dev/null | xargs grep -l -i "openclaw" 2>/dev/null | grep -v -E '(node_modules|\.git/|proc|sys|/usr/share)' | head -30 [[reply_to_current]] 很抱歉，我在当前工作空间和系统中没有找到 OpenClaw 的配置文件或相关文档，无法给出经过验证的精确答案。 不过，根据常见的 Telegram bot 框架配置模式，这类功能通常涉及以下设置思路： --- ### 一般思路 1. **Telegram Bot 的群组隐私模式（Group Privacy）** - 在 Telegram 中，通过 @BotFather 将 bot 的 **Group Privacy** 设置为 **Enabled/ON**。 - 开启后，bot 在群组中**只能收到以 `/` 开头的命令消息，以及直接 @ 它的消息**，不会收到普通群聊消息。 - 这是最简单、最可靠的方式，不需要在应用层做过滤。 2. **应用层过滤（如果 OpenClaw 配置支持）** - 许多框架在 channel 配置中提供类似 `mention_only`、`reply_only`、`group_trigger` 等选项。 - 如果...
AI 评审点评
以下是 AI 评审对该模型输出的点评：
【GEMINI】模型在执行任务时表现出了优秀的工具使用意识，通过多次搜索尝试获取环境中的真实配置，这符合其系统提示词的角色设定。然而，在最终的输出中，它未能提供参考答案所要求的核心事实（at_only 参数），导致在配置准确性维度得分较低。逻辑上，模型对 Telegram 机器人触发机制的解释是完整且合理的。 【KIMI】整体而言，候选人输出提供了一些有用的信息和建议，但没有直接回答关于 OpenClaw 配置的具体问题。输出中包含了一些可能的配置思路和一般性的建议，但没有针对 OpenClaw 的具体配置进行说明，因此在配置准确性方面得分较低。逻辑清晰度方面，候选人解释了群组消息过滤的作用机制，提供了一些可能的配置思路，因此在逻辑清晰度方面得分较高。
进阶难度评测结果
- 得分：39.0 分
- 通过状态：未通过
模型生成产物
以下是该模型针对此任务的实际生成内容：
让我检查一下处理 Discord 消息的代码逻辑，看看 `at_only` 是否被正确使用。
AI 评审点评
以下是 AI 评审对该模型输出的点评：
【GEMINI】候选结果表现极差。作为一个具备工具调用能力的 AI 助手，它在面对具体的配置排查需求时，既没有给出专业的故障分析建议，也没有通过调用工具进行实际的排查操作，仅提供了一句毫无信息量的口头回复，完全没有满足任务要求。 【KIMI】整体上，生成结果对故障排查有一定的深度，但在工具运用能力方面表现不足，未能充分利用 OpenClaw 提供的工具进行有效的故障排查。
相关链接
您可以通过以下链接查看更多相关内容：
