Inception: Mercury 2 在「下载超时恢复」的评测结果

基本信息

• 模型名称：Inception: Mercury 2
• 用例名称：下载超时恢复
• 测试类型：xsct-a
• 评测维度：Gateway 配置与管理

系统提示词（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 install gateway」时一直卡在下载进度条，最后报错「connection timeout」，请问有什么替代方案可以完成安装？

任务要求

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

1. 识别出下载超时的根本原因是网络环境限制
2. 提供手动下载离线包并放置到指定目录的方案
3. 给出使用镜像源或代理环境变量的配置建议
4. 说明如何通过本地路径进行离线安装

评测结果

综合得分

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

基础难度评测结果

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

模型生成产物

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

We need to inspect workspace.ls -R

AI 评审点评

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

【CLAUDE】候选输出完全未完成任务，仅输出了一个不完整的内部调试片段「We need to inspect workspace.ls -R」，没有针对 Gateway 安装超时问题提供任何有效的解决方案。用户得不到任何帮助，属于严重失败的回答。 【GEMINI】模型未能理解用户关于安装超时的求助意图，未给出任何实质性的替代方案或恢复建议，仅执行了无关的目录遍历指令，属于严重的任务失败。 【KIMI】该候选输出完全失败，没有回答用户关于 Gateway 安装超时的问题，而是输出了一个无关的工具调用意图「We need to inspect workspace.ls -R」。模型既没有理解用户问题的上下文，也没有提供任何有用的恢复方案，在方案完整性和表达专业性两个维度均为零分。

进阶难度评测结果

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

模型生成产物

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

We need to list files.Let's run exec.We need to actually run the tool.[exec{ "cmd": [ "ls", "-R" ], "timeout": 10000 }

AI 评审点评

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

【CLAUDE】候选输出极度不完整，实际上只是一个未执行的工具调用片段（ls -R），完全没有回应用户关于「安装命令」和「安装后验证」的核心问题。与参考答案相比，缺失了所有关键内容：安装命令、启动服务、端口验证、日志检查。该输出属于严重失败的回答，几乎得零分。 【GEMINI】该模型表现极差。在对话上下文已经明确当前目录存在安装包的情况下，模型不仅没有给出安装命令，反而执行了冗余且无效的「ls -R」工具调用，完全背离了用户需求，未能完成任何任务目标。 【KIMI】该候选输出严重偏离任务要求。用户明确要求「直接给出安装命令」并说明「安装后如何验证」，但模型却试图执行一个无关的「ls -R」命令，且输出内容不完整。完全没有提供参考答案中包含的任何关键要素：带「--file」参数的安装命令、服务启动命令、端口监听验证（8081）或日志检查方法。这是一个失败的响应。

困难难度评测结果

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

模型生成产物

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

We need to list files.{"path": "", "depth": 2}

AI 评审点评

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

【CLAUDE】候选输出极度不符合任务要求。对话上下文已经明确指出存在权限问题（/opt/openclaw 属于 root），且任务要求给出离线或替代恢复方案。但模型仅输出了一个对工作空间根目录进行 ls 操作的工具调用，既没有分析故障原因，也没有提供任何恢复建议。这是一个近乎无效的响应，与参考答案所要求的提权安装、权限修正、执行权检查、openclaw doctor 诊断等完整流程相去甚远。 【GEMINI】模型表现极差。在对话上下文已经明确了权限受限问题，且用户要求提供下载超时后的恢复方案时，模型未能根据上下文进行逻辑推理，反而输出了一个毫无意义的工具调用指令。完全没有执行任务描述中的恢复方案建议，属于严重的任务失败。 【KIMI】候选输出严重偏离任务目标。用户明确要求「下载超时恢复」，且对话上下文已铺垫了权限问题的诊断结论，但候选输出却执行了一个无关的文件列表操作，完全没有回应用户的恢复需求。既没有识别故障根因，也没有提供任何恢复方案，属于完全失败的响应。

相关链接

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

• 查看所有模型在此用例的表现：「下载超时恢复」
• 查看该模型的所有评测结果：Inception: Mercury 2
• 浏览同维度的其他用例：「Gateway 配置与管理」
• 返回排行榜首页