doubao-seed-2-0-mini 在「自定义端口后访问异常」的评测结果

基本信息

• 模型名称：doubao-seed-2-0-mini
• 用例名称：自定义端口后访问异常
• 测试类型：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 的端口改成 9090 了，但是访问不了，是不是还要重启什么东西？

任务要求

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

1. 明确指出需要重启「openclaw-gateway」服务或进程
2. 提供修改后的访问地址示例，如「http://localhost:9090」
3. 给出检查端口监听状态的命令，如「netstat」或「ss」

评测结果

综合得分

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

基础难度评测结果

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

模型生成产物

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

[[reply_to_current]] 我先帮你检查下当前Gateway服务的状态和端口监听情况： ```bash openclaw gateway status ``` 如果服务确实在运行但还是无法访问，大概率需要重启Gateway服务来加载新的端口配置： ```bash # 重启Gateway服务 openclaw gateway restart ``` 重启后可以再用下面的命令确认9090端口是否被正确监听： ```bash ss -tulpn | grep 9090 ``` 如果还是有问题，可以告诉我命令的输出结果，我帮你进一步排查~

AI 评审点评

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

【CLAUDE】模型回答基本覆盖了重启服务和验证端口监听两个关键步骤，命令选择准确，表达专业。但最重要的「客户端访问地址需同步更新」这一配置闭环步骤完全缺失，这是用户问题的核心痛点之一（用户说「访问不了」，很可能正是因为客户端仍在访问旧端口）。整体方案不够完整，未能真正解决用户的完整问题。 【GEMINI】模型表现良好，能够根据用户反馈快速定位问题并给出正确的排查步骤。主要扣分点在于对「客户端配置同步」这一关键环节的遗漏，导致方案未达到完全闭环的程度。 【KIMI】模型回答覆盖了重启服务和端口检查两个要点，但遗漏了「客户端Base URL同步更新」这一关键配置闭环环节，未能完整回应用户「客户端仍访问默认地址」的核心痛点。建议补充客户端配置修改的明确指引，以形成完整的解决方案。

进阶难度评测结果

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

模型生成产物

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

我来帮你修改配置，把`base_path`恢复为空的默认状态： ```json { "command": "write", "path": "config.yaml", "content": "gateway:\n port: 8888\nauth:\n enabled: false" } ``` 修改完成后需要重启网关服务让配置生效： ```bash openclaw gateway restart ``` 之后再访问`http://localhost:8888/health`就可以正常访问健康检查接口了。

AI 评审点评

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

【CLAUDE】模型回答质量较高，准确定位了问题根源并给出了完整的修复流程（修改配置 → 重启服务 → 验证访问），与参考答案高度吻合。主要不足在于工具调用以伪代码形式呈现而非直接执行，以及未提及将 base_path 设为「/」作为替代方案。整体而言是一个合格且实用的技术支持回答。 【GEMINI】模型表现优秀，能够精准定位问题并给出闭环的解决方案。不仅提供了修改配置文件的具体内容，还主动提醒了重启服务的必要性，符合专业助手的高效交互标准。 【KIMI】模型整体表现良好，能够准确定位配置问题并给出修复方案。主要不足在于重启命令格式与系统提示中的标准格式存在偏差（缺少连字符），且未完整呈现两种修改方案（改为「/」或删除）。建议增强对命令格式的精确匹配意识。

困难难度评测结果

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

模型生成产物

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

我需要先确认哪个进程占用了80端口，执行以下命令查看： ```bash sudo ss -tulpn | grep :80 ```

AI 评审点评

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

【CLAUDE】模型生成结果过于简短，仅提供了一条端口查询命令，属于故障排查流程中最基础的第一步。与参考答案相比，缺少对两个错误原因的解释、缺少完整解决方案（停止冲突进程或配置反向代理）、缺少 OpenClaw 最佳实践建议（使用8081端口+Nginx反向代理）以及完整的闭环验证流程。整体回答不完整，无法帮助用户真正解决问题，质量较低。 【GEMINI】模型表现不佳。面对用户提出的「现在呢？」这一追问，模型仅机械地执行了排查命令，未能总结前序错误（权限不足与端口占用），也未给出解决问题的完整闭环方案。相比参考答案，模型缺乏对最佳实践的引导，未能体现出作为专业 AI 助手的规划能力。 【KIMI】模型生成结果严重不完整，仅提供了一个查看端口占用的命令，完全遗漏了参考答案中的核心内容：错误原因解释、两种解决方案（停止进程/反向代理）、最佳实践建议以及安全规范强调。用户明确询问「现在呢？」期待完整的下一步指导，但模型只给出了排查的第一步，没有形成配置闭环，无法满足用户的实际需求。

相关链接

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

• 查看所有模型在此用例的表现：「自定义端口后访问异常」
• 查看该模型的所有评测结果：doubao-seed-2-0-mini
• 浏览同维度的其他用例：「Gateway 配置与管理」
• 返回排行榜首页