qwen3.6-plus-preview 在「定位文档搜索入口」的评测结果

基本信息

• 模型名称：qwen3.6-plus-preview
• 用例名称：定位文档搜索入口
• 测试类型：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 的官方文档页面，并告诉我「搜索框」在页面的什么位置。

任务要求

AI 模型需要满足以下要求：

1. 识别出需要使用 open_url 工具打开文档地址
2. 识别出需要使用 browser_snapshot 或 get_page_content 获取页面结构
3. 准确描述「搜索框」的视觉位置或 DOM 路径
4. 回复内容必须包含关键词「文档」和「搜索」

评测结果

综合得分

该模型在此用例的得分为：70.0 分（满分 100 分），已通过

基础难度评测结果

• 得分：70.0 分
• 通过状态：已通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

我来帮你打开 OpenClaw 的官方文档页面。 https://docs.openclaw.ai

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【KIMI】虽然成功调用了浏览器工具打开文档页面，但在描述搜索框位置方面未给出具体信息，未能完全满足任务要求。

进阶难度评测结果

• 得分：33.8 分
• 通过状态：未通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

我来获取一下当前页面的快照，看看点击后的状态。

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【CLAUDE】候选输出仅是一句意图声明，没有实际调用工具、没有分析结果、没有状态判断，与参考答案要求的完整交互流程相差甚远。整体质量极低，未能完成用户的确认需求。 【GEMINI】模型在交互逻辑上表现合格，能够针对用户需求提出合理的验证步骤。但在状态判断维度上，表现较为被动，未能像参考答案那样直接给出页面变化的具体描述，导致回复的实用价值和确定性略逊一筹。 【KIMI】候选输出严重不完整，仅表达了获取快照的意图，但未基于快照结果给出任何状态判断或验证结论。与参考答案相比，缺失了关键的「二次确认」环节和具体的搜索框状态识别，未能满足任务要求中「验证页面状态变化」和「体现对文档站点交互逻辑理解」的核心目标。

困难难度评测结果

• 得分：72.0 分
• 通过状态：已通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

{"command":"click_element --selector 'a[href=\"/search-page\"]'","exit_code":0,"stdout":"","stderr":""}

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【CLAUDE】候选输出在功能执行层面基本正确——识别了备用搜索入口并执行了跳转操作，体现了一定的异常恢复和任务推进能力。但整体输出仅为一条裸工具调用，完全缺少对当前状态、决策依据和后续步骤的说明，与参考答案所要求的「叙述+行动」模式相差较远。在 hard 难度任务中，助手应在模糊指令下主动补充上下文说明，以确保用户理解任务进展，候选输出在这方面表现明显不足。 【GEMINI】该模型在处理定位失效的异常场景时表现优异。它不仅能够通过分析页面结构找到替代方案，还能在用户指令不明确的情况下，维持任务目标并执行最具逻辑性的下一步操作。输出的 tool call 准确且直接解决了当前困境。 【KIMI】候选输出本质上是一个孤立的工具调用结果，而非完整的助手回复。它执行了正确的动作（点击备用搜索入口），但完全缺失了异常恢复过程中的关键决策展示——包括如何识别首选方案失败、为何选择get_page_content作为补偿、如何从HTML中解析出备用路径等。这些核心能力均体现在「预设上下文」而非候选输出中。决策连贯性方面虽方向正确，但缺乏任务状态的明确沟通和后续规划，显得过于简略。建议输出应包含：对当前状态的确认、选择该动作的理由、以及到达目标页面后的执行计划。

相关链接

您可以通过以下链接查看更多相关内容：

• 查看所有模型在此用例的表现：「定位文档搜索入口」
• 查看该模型的所有评测结果：qwen3.6-plus-preview
• 浏览同维度的其他用例：「网页打开与浏览器操作」
• 返回排行榜首页