doubao-seed-2-0-code 在「首次访问 401」的评测结果
这是该 AI 模型在此测试用例上的详细评测结果。
基本信息
- 模型名称：doubao-seed-2-0-code
- 用例名称：首次访问 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 模型需要满足以下要求：
- 指出 OpenClaw Gateway 默认开启身份验证
- 说明初始管理密钥（Admin Key）的存放位置通常在「data/config.yaml」或启动日志中
- 提供具体的查看命令，如「cat data/config.yaml」
- 解释如何在请求头中使用「Authorization: Bearer <key>」进行访问
评测结果
综合得分
该模型在此用例的得分为：— 分（满分 100 分），未通过
基础难度评测结果
- 得分：— 分
- 通过状态：未通过
模型生成产物
以下是该模型针对此任务的实际生成内容：
我来帮你找到 OpenClaw Gateway 的初始管理密钥。让我先查看一下工作区的内容，了解相关配置。 ls
AI 评审点评
以下是 AI 评审对该模型输出的点评：
【KIMI】该候选输出完全未能回答用户问题。用户询问的是如何解决 OpenClaw Gateway 的 401 认证错误并找到初始管理密钥，但输出仅执行了一个无关的「ls」命令，没有提供任何关于密钥位置、获取方式或认证头格式的信息。这是一个未完成的回答，需要重新生成包含完整认证指导的响应。
进阶难度评测结果
- 得分：44.0 分
- 通过状态：未通过
模型生成产物
以下是该模型针对此任务的实际生成内容：
我来帮您修改 admin_key 并重启服务使配置即时生效。 首先编辑配置文件： data/config.yaml admin_key: "oc-secret-789" admin_key: "my-safe-key"
AI 评审点评
以下是 AI 评审对该模型输出的点评：
【CLAUDE】候选输出仅完成了修改配置文件这一步，使用了合适的「edit」工具进行精确替换，工具调用本身是正确的。但整个回答严重缺失重启服务和验证两个关键环节，用户问的是「如何换成新密钥并即时生效」，「即时生效」意味着必须重启服务，这是核心诉求却被完全忽略。整体来看，回答只完成了任务的三分之一，不能满足用户需求。 【GEMINI】模型未能满足用户「即时生效」的需求。虽然模型准确地定位并修改了配置文件，但对于 Gateway 服务而言，修改配置后必须重启才能生效，模型在回复中截断了后续操作，导致任务无法闭环。建议在执行文件编辑后，主动调用或提示用户执行重启指令并进行验证。 【KIMI】候选输出严重不完整，仅展示了修改配置文件的意图就被截断，完全没有涉及重启服务和验证环节。虽然edit工具的使用方向正确，但缺乏完整的工具调用展示和后续操作流程，无法满足用户「即时生效」的需求。与参考答案相比，缺失了关键的sed命令、重启命令和验证curl命令，整体质量较低。
困难难度评测结果
- 得分：10.8 分
- 通过状态：未通过
模型生成产物
以下是该模型针对此任务的实际生成内容：
我需要先查看完整的配置和网关源码来定位首次访问 401 的问题。让我继续。
AI 评审点评
以下是 AI 评审对该模型输出的点评：
【CLAUDE】候选输出极为简短且无实质内容，仅表示「需要继续查看」，既未诊断已暴露的权限属主问题和配置文件乱码问题，也未提供任何恢复步骤或验证方案。与参考答案相比，差距悬殊，几乎不具备任何实用价值。 【GEMINI】模型表现极差。在对话上下文已经明确提供了「文件权限已修复」且「读取到乱码内容」的情况下，模型完全无视这些事实，给出了一个非常空洞且脱离上下文的回复。它没有尝试解决乱码导致的解析错误，也没有利用已有的诊断线索，未能完成任务要求的故障排查与恢复决策。 【KIMI】候选输出严重不合格。对话上下文已经明确呈现了权限问题和乱码损坏两个关键故障点，但候选输出完全无视这些信息，没有进行任何故障诊断分析，也没有提供任何恢复决策。这种回应在实际运维场景中属于无效输出，无法帮助用户解决401认证问题，需要重新生成完整的技术响应。
相关链接
您可以通过以下链接查看更多相关内容：
