doubao-seed-1-6-flash 在「慢加载页面处理」的评测结果

基本信息

• 模型名称：doubao-seed-1-6-flash
• 用例名称：慢加载页面处理
• 测试类型：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 模型的具体任务要求：

请帮我打开「https://slow-loading-site.com/report」，这个页面加载比较慢，请在确认页面完全加载出「数据概览」字样后再告诉我结果。

任务要求

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

1. 识别出页面加载缓慢的特性，主动提出需要等待或分步检查
2. 正确选择「open_url」作为起始动作
3. 在回复中明确表示会通过「browser_snapshot」或「get_page_content」验证关键元素是否存在

评测结果

综合得分

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

基础难度评测结果

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

模型生成产物

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

[{"name":"browser","parameters":{"action":"open_url","url":"https://slow-loading-site.com/report","wait_for_text":"数据概览"}}]

AI 评审点评

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

【CLAUDE】模型的工具选择基本正确，能识别慢加载场景并尝试通过参数处理等待逻辑，但未能按照参考答案所示的「open_url + 多次 browser_snapshot 验证」分步策略执行，缺少对慢加载场景的显式分步应对和说明，整体表现中规中矩，有改进空间。 【GEMINI】模型在工具调用上表现尚可，但在处理复杂任务逻辑时显得过于急躁。题目明确要求「逐步判断状态」，模型直接将等待逻辑封装在单次调用中，虽然技术上可能可行，但忽略了任务中对过程监控的显式要求。建议模型在面对慢加载任务时，应在回复中体现出分步检查的意图，而非仅返回单一的工具调用。 【KIMI】模型在工具调用上犯了关键错误——使用了虚构的「wait_for_text」参数，且完全没有文字回复来说明等待策略。虽然选择了正确的工具和动作方向，但试图用单一调用解决需要多步验证的慢加载场景，既不符合工具实际规范，也违背了逐步判断状态的题目要求。逻辑严密性表现较差，未能体现对复杂场景的合理拆解能力。

进阶难度评测结果

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

模型生成产物

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

由于页面仍在加载中，比特币价格信息尚未完全显示，我会继续等待页面加载完成以获取最新比特币价格。

AI 评审点评

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

【CLAUDE】模型在状态感知方面表现尚可，正确判断页面未就绪且未编造数据，但对快照证据的引用不够具体。在工具组合效率方面表现较弱，仅表达了等待意图而未明确指出将使用哪些工具进行后续轮询，与参考答案要求的「明确工具调用计划」存在明显差距。整体回复过于简短，缺乏对动态加载过程的主动把控体现。 【GEMINI】模型在状态感知上表现良好，能够客观评估页面加载情况并避免编造数据。但在工具使用层面表现不足，仅停留在口头承诺，未主动执行后续的探测操作，未能有效推动任务进展。 【KIMI】模型生成结果过于简略和模糊，未能满足测试任务的核心要求。在页面加载缓慢的场景下，模型应当：1) 精确识别 snapshot 中的加载状态（Loading Spinner）和数据缺失情况；2) 明确提出等待+轮询的工具组合策略。当前回复仅给出安抚性语句，既未引用具体工具，也未展示对动态加载过程的把控能力，整体表现不及格。

困难难度评测结果

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

模型生成产物

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

get_page_content {}

AI 评审点评

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

【CLAUDE】候选输出在复杂慢加载场景下表现较弱。虽然没有完全放弃（继续调用工具），但仅仅重复调用 get_page_content 而不提供任何分析、总结或进阶策略，无法满足用户「现在呢？」这一追问所期望的状态汇报和下一步规划。与参考答案相比，候选输出缺乏对当前困境的诊断、对最终目标（营收数据）的持续关注，以及更具针对性的验证手段（如 browser_snapshot、特定选择器检查）。整体决策流程过于简单，不符合复杂场景下的专业助手行为预期。 【GEMINI】模型在处理异常和执行基础工具调用方面表现尚可，但在复杂场景的交互逻辑上严重不足。面对用户的追问，模型仅机械地重复调用获取页面内容的工具，未能体现出作为智能助手的分析能力和对任务目标的持续追踪，未能有效引导用户或解释当前状态。 【KIMI】模型在该 hard 难度任务中表现不佳。面对页面加载缓慢的经典场景，模型未能理解「逐步判断状态」的任务要求，在用户追问后选择了重复调用已证明无效的工具，而非采取等待、快照检查或特定选择器定位等更精细的策略。与参考答案相比，缺失了关键的「browser_snapshot」检查、「营收」关键字定位、以及困境总结与下一步建议等核心要素。建议模型在类似场景中加强对上下文状态的追踪，避免工具调用的重复循环，并主动采用等待-检查-验证的渐进式决策模式。

相关链接

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

• 查看所有模型在此用例的表现：「慢加载页面处理」
• 查看该模型的所有评测结果：doubao-seed-1-6-flash
• 浏览同维度的其他用例：「网页打开与浏览器操作」
• 返回排行榜首页