doubao-seed-2-0-pro 在「首次访问 401」的评测结果

这是该 AI 模型在此测试用例上的详细评测结果。

基本信息

  • 模型名称：doubao-seed-2-0-pro
  • 用例名称：首次访问 401
  • 测试类型：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 Gateway，尝试访问「/v1/models」接口却提示「401」，我该如何找到初始的管理密钥进行认证？

任务要求

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

  1. 指出 OpenClaw Gateway 默认开启身份验证
  2. 说明初始管理密钥（Admin Key）的存放位置通常在「data/config.yaml」或启动日志中
  3. 提供具体的查看命令，如「cat data/config.yaml」
  4. 解释如何在请求头中使用「Authorization: Bearer <key>」进行访问

评测结果

综合得分

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

基础难度评测结果

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

模型生成产物

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

[[reply_to_current]] 我先帮你查看Gateway运行状态和配置加载路径，从中找到初始密钥的位置： [{"name":"exec","parameters":{"command":"openclaw gateway status"}}]

AI 评审点评

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

【CLAUDE】模型生成结果严重不足，仅停留在调用状态查询命令的阶段，未能回答用户关于「如何找到初始管理密钥」的核心问题。既没有指出密钥存储位置，也没有提供查看命令，更没有说明如何在请求头中使用密钥进行认证。与参考答案相比，缺失了几乎所有关键信息，无法帮助用户解决401认证问题。 【GEMINI】模型在处理该任务时表现过于保守，未能直接利用系统提示词中关于 OpenClaw 的知识储备给出关键路径（data/config.yaml）。虽然调用了 status 命令进行诊断，但对于用户直接询问的「如何找到初始管理密钥」这一明确需求，模型未能给出直接的解决方案，导致用户体验不佳。 【KIMI】模型的回复处于任务初始阶段，仅开始诊断但未完成核心信息的提供。虽然调用工具的思路正确，但输出内容远未完成用户需要的完整解决方案，关键信息（密钥位置、认证头格式、验证命令）均缺失，整体完成度较低。

进阶难度评测结果

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

模型生成产物

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

我将先修改配置文件中的admin_key，随后重启网关服务使配置即时生效： [{"name":"exec","parameters":{"command":"sed -i 's/admin_key: \"oc-secret-789\"/admin_key: \"my-safe-key\"/g' data/config.yaml"}}]

AI 评审点评

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

【CLAUDE】模型在配置文件修改这一步骤上表现良好，使用了正确的 sed 命令替换了明确的旧值。但回答止步于此，未提及重启服务（参考答案明确指出需要重启才能生效）和验证环节，导致整体流程残缺，用户实际上无法判断操作是否成功生效。一个完整的答案应至少包含重启命令，理想情况下还应给出验证步骤。 【GEMINI】模型在执行具体文件修改任务时表现尚可，但缺乏对系统运维流程的整体把控。在用户明确要求「即时生效」的情况下，模型仅完成了修改动作，未执行重启服务及验证操作，导致任务未能闭环。 【KIMI】模型响应过于简略，仅执行了配置文件修改，未完成用户要求的「即时生效」目标。虽然 sed 命令使用正确，但缺少重启服务的实际执行和验证步骤，导致解决方案无法真正完成。建议在修改配置后，立即执行 openclaw gateway restart 或等效操作，并提供验证命令确认新密钥生效。

困难难度评测结果

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

模型生成产物

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

我先检查网关运行状态，再验证访问鉴权逻辑： [{"name":"exec","parameters":{"command":"openclaw gateway status && curl -I http://127.0.0.1:8080"}}]

AI 评审点评

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

【CLAUDE】模型生成结果严重脱离上下文，没有利用已有的诊断信息（权限问题已修复、配置文件已读取但存在乱码）做进一步分析和恢复，反而重新执行基础状态检查命令。整体表现不具备故障诊断深度，也未提供有效的恢复决策，距离参考答案的要求差距极大，综合得分极低。 【GEMINI】模型表现不佳。在面对明确的故障场景（权限错误及文件内容损坏）时，模型未能利用上下文信息进行分析，而是采取了机械化的常规检查操作。未能识别出配置文件乱码带来的解析风险，也未给出任何实质性的修复建议，导致任务无法推进。 【KIMI】模型严重忽略了预设上下文中的关键信息，表现出明显的上下文丢失问题。用户已明确完成权限修复并发现配置文件乱码，但模型仿佛重新开始任务，未针对已识别的双重问题（权限隐患 + 内容损坏）提出任何实质性解决方案。生成的命令与当前故障场景不匹配，既未深入诊断配置损坏的影响，也未提供系统性的恢复决策。建议在复杂多轮诊断场景中加强上下文保持能力。

相关链接

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

加载中...
100%