Doramagic 项目包 · 项目说明书

openclaw 项目

生成时间: 2026-05-23 22:51:11 UTC

仓库概览

本页在 Human Wiki provider 不可用时基于仓库证据生成,只使用 README、文件树和已选源码文件,不把模板描述冒充项目事实。

章节 相关页面

继续阅读本节完整说明和来源证据。

README 证据

🦞 OpenClaw — Personal AI Assistant

<p align="center"> <picture> <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/openclaw/openclaw/main/docs/assets/openclaw-logo-text-dark.svg"> <img src="https://raw.githubusercontent.com/openclaw/openclaw/main/docs/assets/openclaw-logo-text.svg" alt="OpenClaw" width="500"> </picture> </p>

<p align="center"> <strong>EXFOLIATE! EXFOLIATE!</strong> </p>

<p align="center"> <a href="https://github.com/openclaw/openclaw/actions/workflows/ci.yml?branch=main"><img src="https://img.shields.io/github/actions/workflow/status/openclaw/openclaw/ci.yml?branch=main&style=for-the-badge" alt="CI status"></a> <a href="https://github.com/openclaw/openclaw/releases"><img src="https://img.shields.io/github/v/release/openclaw/openclaw?include_prereleases&style=for-the-badge" alt="GitHub release"></a> <a href="https://discord.gg/clawd"><img src="https://img.shields.io/discord/1456350064065904867?label=Discord&logo=discord&logoColor=white&color=5865F2&style=for-the-badge" alt="Discord"></a> <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue.svg?style=for-the-badge" alt="MIT License"></a> </p>

OpenClaw is a _personal AI assistant_ you run on your own devices. It answers you on the channels you already use. It can speak and listen on macOS/iOS/Android, and can render a live Canvas you control. The Gateway is just the control plane — the product is the assistant.

If you want a personal, single-user assistant that feels local, fast, and always-on, this is it.

Supported channels include: WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, IRC, Microsoft Teams, Matrix, Feishu, LINE, Mattermost, Nextcloud Talk, Nostr, Synology Chat, Tlon, Twitch, Zalo, Zalo Personal, WeChat, QQ, WebChat.

Website · Docs · Vision · DeepWiki · Getting Started · Updating · Showcase · FAQ · Onboarding · Nix · Docker · Discord

[excerpt truncated]

已选源码清单

文件证据角色大小
Dockerfile仓库证据17830 bytes
README.mdREADME/产品与使用证据86657 bytes
docker-compose.yml仓库证据5522 bytes
package.json包与运行时元数据102945 bytes
qa/README.md文档证据928 bytes
security/README.md文档证据6051 bytes
skills/pyproject.toml包与运行时元数据193 bytes
ui/package.json包与运行时元数据712 bytes
apps/android/README.md文档证据10483 bytes
apps/ios/README.md文档证据13801 bytes
apps/macos/README.md文档证据1602 bytes
apps/swabble/README.md文档证据4141 bytes

资料来源:README.md:1-120

资料来源:README.md:1-120

入口与运行边界

下面文件是安装、启动、配置或宿主集成的高信号候选。这里给出证据地图,不推断未经执行验证的 API 契约。

章节 相关页面

继续阅读本节完整说明和来源证据。

文件证据角色大小
Dockerfile仓库证据17830 bytes
README.mdREADME/产品与使用证据86657 bytes
docker-compose.yml仓库证据5522 bytes
package.json包与运行时元数据102945 bytes
qa/README.md文档证据928 bytes
security/README.md文档证据6051 bytes
skills/pyproject.toml包与运行时元数据193 bytes
ui/package.json包与运行时元数据712 bytes
apps/android/README.md文档证据10483 bytes
apps/ios/README.md文档证据13801 bytes
apps/macos/README.md文档证据1602 bytes
apps/swabble/README.md文档证据4141 bytes

资料来源:Dockerfile:1-120

资料来源:Dockerfile:1-120

架构证据地图

本节只根据仓库路径组织可能的架构区域;需要运行验证的行为不会在这里断言。

章节 相关页面

继续阅读本节完整说明和来源证据。

资料来源:README.md:1-120

运维与验证边界

运维建议仅来自仓库中真实存在的文件。把该项目用于 agent 工作流前,仍需在 sandbox 中验证安装、quickstart 和运行行为。

章节 相关页面

继续阅读本节完整说明和来源证据。

资料来源:docker-compose.yml:1-120

资料来源:docker-compose.yml:1-120

失败模式与踩坑日记

保留 Doramagic 在发现、验证和编译中沉淀的项目专属风险,不把社区讨论只当作装饰信息。

high 来源证据:Workaround for isolated cron agentTurn stuck (re: #68157, #11994, #42103)

可能阻塞安装或首次运行。

high 来源证据:[Bug]: Default-mode Matrix channel rooms receive internal tool/progress events as visible chat messages

可能增加新用户试用和生产接入成本。

high 来源证据:[Bug]: Heartbeat-driven agent replies leave pendingFinalDelivery stuck, blocking subsequent heartbeats

可能阻塞安装或首次运行。

high 来源证据:doctor misclassifies junction-backed source checkout as non-git install

可能增加新用户试用和生产接入成本。

Pitfall Log / 踩坑日志

项目:openclaw/openclaw

摘要:发现 38 个潜在踩坑项,其中 18 个为 high/blocking;最高优先级:安装坑 - 来源证据:Workaround for isolated cron agentTurn stuck (re: #68157, #11994, #42103)。

1. 安装坑 · 来源证据:Workaround for isolated cron agentTurn stuck (re: #68157, #11994, #42103)

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安装相关的待验证问题:Workaround for isolated cron agentTurn stuck (re: #68157, #11994, #42103)
  • 对用户的影响:可能阻塞安装或首次运行。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_56c16a1c8d544fe4af5da724927fbd77 | https://github.com/openclaw/openclaw/issues/85516 | 来源讨论提到 node 相关条件,需在安装/试用前复核。

2. 安装坑 · 来源证据:[Bug]: Default-mode Matrix channel rooms receive internal tool/progress events as visible chat messages

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安装相关的待验证问题:[Bug]: Default-mode Matrix channel rooms receive internal tool/progress events as visible chat messages
  • 对用户的影响:可能增加新用户试用和生产接入成本。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_e735a1ca8e92409fb46fb61ac878d1dc | https://github.com/openclaw/openclaw/issues/85000 | 来源讨论提到 npm 相关条件,需在安装/试用前复核。

3. 安装坑 · 来源证据:[Bug]: Heartbeat-driven agent replies leave pendingFinalDelivery stuck, blocking subsequent heartbeats

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安装相关的待验证问题:[Bug]: Heartbeat-driven agent replies leave pendingFinalDelivery stuck, blocking subsequent heartbeats
  • 对用户的影响:可能阻塞安装或首次运行。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_dcefb1710a0e4250acf239f3b815966a | https://github.com/openclaw/openclaw/issues/83184 | 来源讨论提到 docker 相关条件,需在安装/试用前复核。

4. 安装坑 · 来源证据:doctor misclassifies junction-backed source checkout as non-git install

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安装相关的待验证问题:doctor misclassifies junction-backed source checkout as non-git install
  • 对用户的影响:可能增加新用户试用和生产接入成本。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_7ac9578256e14199a50ab05b2cc879d5 | https://github.com/openclaw/openclaw/issues/82215 | 来源讨论提到 node 相关条件,需在安装/试用前复核。

5. 配置坑 · 来源证据:Bug: Cline bridge silently fails on gateway config tasks — no config.schema.lookup tool

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个配置相关的待验证问题:Bug: Cline bridge silently fails on gateway config tasks — no config.schema.lookup tool
  • 对用户的影响:可能增加新用户试用和生产接入成本。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_9c454936e333431597d2163b22ec013e | https://github.com/openclaw/openclaw/issues/85729 | 来源类型 github_issue 暴露的待验证使用条件。

6. 配置坑 · 来源证据:Bug: Cron agent gridlock — all cron jobs share agent:main lane (maxConcurrent=1)

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个配置相关的待验证问题:Bug: Cron agent gridlock — all cron jobs share agent:main lane (maxConcurrent=1)
  • 对用户的影响:可能增加新用户试用和生产接入成本。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_0101809880d344d1a796b7957fca4d7f | https://github.com/openclaw/openclaw/issues/85728 | 来源类型 github_issue 暴露的待验证使用条件。

7. 配置坑 · 来源证据:imsg RPC Crashes on Phone Number Validation, Causing Cascading iMessage Delivery Failures

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个配置相关的待验证问题:imsg RPC Crashes on Phone Number Validation, Causing Cascading iMessage Delivery Failures
  • 对用户的影响:可能阻塞安装或首次运行。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_5effdfd858db4994a38b5c83bfa41315 | https://github.com/openclaw/openclaw/issues/85740 | 来源讨论提到 macos 相关条件,需在安装/试用前复核。

8. 安全/权限坑 · 失败模式:security_permissions: Bug: Cron agent gridlock — all cron jobs share agent:main lane (maxConcurrent=1)

  • 严重度:high
  • 证据强度:source_linked
  • 发现:Developers should check this security_permissions risk before relying on the project: Bug: Cron agent gridlock — all cron jobs share agent:main lane (maxConcurrent=1)
  • 对用户的影响:Developers may expose sensitive permissions or credentials: Bug: Cron agent gridlock — all cron jobs share agent:main lane (maxConcurrent=1)
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: Bug: Cron agent gridlock — all cron jobs share agent:main lane (maxConcurrent=1). Context: Source discussion did not expose a precise runtime context.
  • 防护动作: Do not recommend enabling privileged or credential-bearing paths until the source-backed risk is reviewed: https://github.com/openclaw/openclaw/issues/85728
  • 证据:failure_mode_cluster:github_issue | fmev_d8324db8f54d71e397372df33df4b28f | https://github.com/openclaw/openclaw/issues/85728 | Bug: Cron agent gridlock — all cron jobs share agent:main lane (maxConcurrent=1)

9. 安全/权限坑 · 失败模式:security_permissions: Session files should never be deleted — rename .deleted.* to .archived.*

  • 严重度:high
  • 证据强度:source_linked
  • 发现:Developers should check this security_permissions risk before relying on the project: Session files should never be deleted — rename .deleted.* to .archived.*
  • 对用户的影响:Developers may expose sensitive permissions or credentials: Session files should never be deleted — rename .deleted.* to .archived.*
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: Session files should never be deleted — rename .deleted.* to .archived.*. Context: Observed during version upgrade or migration.
  • 防护动作: Do not recommend enabling privileged or credential-bearing paths until the source-backed risk is reviewed: https://github.com/openclaw/openclaw/issues/56609
  • 证据:failure_mode_cluster:github_issue | fmev_b6a00e824a7ea871b514b9e6bd25e0b2 | https://github.com/openclaw/openclaw/issues/56609 | Session files should never be deleted — rename .deleted.* to .archived.*

10. 安全/权限坑 · 失败模式:security_permissions: [Feature]: Improve `openclaw config` to avoid secrets and invalid files

  • 严重度:high
  • 证据强度:source_linked
  • 发现:Developers should check this security_permissions risk before relying on the project: [Feature]: Improve openclaw config to avoid secrets and invalid files
  • 对用户的影响:Developers may expose sensitive permissions or credentials: [Feature]: Improve openclaw config to avoid secrets and invalid files
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: [Feature]: Improve openclaw config to avoid secrets and invalid files. Context: Observed during installation or first-run setup.
  • 防护动作: Do not recommend enabling privileged or credential-bearing paths until the source-backed risk is reviewed: https://github.com/openclaw/openclaw/issues/16351
  • 证据:failure_mode_cluster:github_issue | fmev_e2bc2f876834071ad458ebb9ccf676a7 | https://github.com/openclaw/openclaw/issues/16351 | [Feature]: Improve openclaw config to avoid secrets and invalid files

11. 安全/权限坑 · 失败模式:security_permissions: [Feature]: support SecretRef for channel phone numbers as it's Personal Identifiable Informat...

  • 严重度:high
  • 证据强度:source_linked
  • 发现:Developers should check this security_permissions risk before relying on the project: [Feature]: support SecretRef for channel phone numbers as it's Personal Identifiable Information (PII)
  • 对用户的影响:Developers may expose sensitive permissions or credentials: [Feature]: support SecretRef for channel phone numbers as it's Personal Identifiable Information (PII)
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: [Feature]: support SecretRef for channel phone numbers as it's Personal Identifiable Information (PII). Context: Observed during version upgrade or migration.
  • 防护动作: Do not recommend enabling privileged or credential-bearing paths until the source-backed risk is reviewed: https://github.com/openclaw/openclaw/issues/56502
  • 证据:failure_mode_cluster:github_issue | fmev_467ae01b350550fb665dc214a8b0581c | https://github.com/openclaw/openclaw/issues/56502 | [Feature]: support SecretRef for channel phone numbers as it's Personal Identifiable Information (PII)

12. 安全/权限坑 · 来源证据:Browser automation: chrome-devtools-mcp processes accumulate and never terminate (memory leak)

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题:Browser automation: chrome-devtools-mcp processes accumulate and never terminate (memory leak)
  • 对用户的影响:可能阻塞安装或首次运行。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_e1ab6619d8b24399b4545f1e45aa89a1 | https://github.com/openclaw/openclaw/issues/85721 | 来源讨论提到 node 相关条件,需在安装/试用前复核。

13. 安全/权限坑 · 来源证据:Codex app-server emits notification:turn/started then goes silent; embedded run wedges for the full stuck-session recov…

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题:Codex app-server emits notification:turn/started then goes silent; embedded run wedges for the full stuck-session recovery window
  • 对用户的影响:可能阻塞安装或首次运行。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_c2d90033c3324738ac59b04ada31c43b | https://github.com/openclaw/openclaw/issues/85251 | 来源讨论提到 node 相关条件,需在安装/试用前复核。

14. 安全/权限坑 · 来源证据:Subagent lifecycle observability + async supervision controls

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题:Subagent lifecycle observability + async supervision controls
  • 对用户的影响:可能影响授权、密钥配置或安全边界。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_6af80e8dfd4d44119e3f17e2eb8e519d | https://github.com/openclaw/openclaw/issues/38626 | 来源类型 github_issue 暴露的待验证使用条件。

15. 安全/权限坑 · 来源证据:[Bug]: Subagent spawn recreates root-level bootstrap markdown files in repository workspace

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题:[Bug]: Subagent spawn recreates root-level bootstrap markdown files in repository workspace
  • 对用户的影响:可能阻塞安装或首次运行。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_02f92c244baa4f68a9d186e759bcca9e | https://github.com/openclaw/openclaw/issues/83593 | 来源讨论提到 node 相关条件,需在安装/试用前复核。

16. 安全/权限坑 · 来源证据:[Feature]: Improve `openclaw config` to avoid secrets and invalid files

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题:[Feature]: Improve openclaw config to avoid secrets and invalid files
  • 对用户的影响:可能影响授权、密钥配置或安全边界。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_3fac07fe204b4f609f98496eba435963 | https://github.com/openclaw/openclaw/issues/16351 | 来源类型 github_issue 暴露的待验证使用条件。

17. 安全/权限坑 · 来源证据:[Feature]: Support for sandbox Docker parameters (--gpus all, --ipc=host)

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题:[Feature]: Support for sandbox Docker parameters (--gpus all, --ipc=host)
  • 对用户的影响:可能影响授权、密钥配置或安全边界。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_45c646b32ff4452380f274880f1f4c14 | https://github.com/openclaw/openclaw/issues/29384 | 来源讨论提到 docker 相关条件,需在安装/试用前复核。

18. 安全/权限坑 · 来源证据:sessions_history returns unfiltered delivery-mirror messages — duplicates visible in dashboard

  • 严重度:high
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题:sessions_history returns unfiltered delivery-mirror messages — duplicates visible in dashboard
  • 对用户的影响:可能影响授权、密钥配置或安全边界。
  • 建议检查:来源问题仍为 open,Pack Agent 需要复核是否仍影响当前版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_f8287c22cada4a588eb2d449852a3c32 | https://github.com/openclaw/openclaw/issues/85669 | 来源讨论提到 npm 相关条件,需在安装/试用前复核。

19. 安装坑 · 失败模式:installation: Avoid recreating unchanged message objects when stripping inline directive tags

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this installation risk before relying on the project: Avoid recreating unchanged message objects when stripping inline directive tags
  • 对用户的影响:Developers may fail before the first successful local run: Avoid recreating unchanged message objects when stripping inline directive tags
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: Avoid recreating unchanged message objects when stripping inline directive tags. Context: Observed when using node
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_287c4b64a9f4ee3e472cc41203829a2f | https://github.com/openclaw/openclaw/issues/37589 | Avoid recreating unchanged message objects when stripping inline directive tags

20. 安装坑 · 失败模式:installation: Browser automation: chrome-devtools-mcp processes accumulate and never terminate (memory leak)

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this installation risk before relying on the project: Browser automation: chrome-devtools-mcp processes accumulate and never terminate (memory leak)
  • 对用户的影响:Developers may fail before the first successful local run: Browser automation: chrome-devtools-mcp processes accumulate and never terminate (memory leak)
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: Browser automation: chrome-devtools-mcp processes accumulate and never terminate (memory leak). Context: Observed when using node, playwright, linux
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_1da2a5a9fa30b04241d305d63bc4c433 | https://github.com/openclaw/openclaw/issues/85721 | Browser automation: chrome-devtools-mcp processes accumulate and never terminate (memory leak)

21. 安装坑 · 失败模式:installation: [Bug]: Default-mode Matrix channel rooms receive internal tool/progress events as visible cha...

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this installation risk before relying on the project: [Bug]: Default-mode Matrix channel rooms receive internal tool/progress events as visible chat messages
  • 对用户的影响:Developers may fail before the first successful local run: [Bug]: Default-mode Matrix channel rooms receive internal tool/progress events as visible chat messages
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: [Bug]: Default-mode Matrix channel rooms receive internal tool/progress events as visible chat messages. Context: Observed when using node, macos
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_5b392f55705e03bfcf5b3f6c374750a9 | https://github.com/openclaw/openclaw/issues/85000 | [Bug]: Default-mode Matrix channel rooms receive internal tool/progress events as visible chat messages

22. 安装坑 · 失败模式:installation: [Bug]: Heartbeat-driven agent replies leave pendingFinalDelivery stuck, blocking subsequent h...

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this installation risk before relying on the project: [Bug]: Heartbeat-driven agent replies leave pendingFinalDelivery stuck, blocking subsequent heartbeats
  • 对用户的影响:Developers may fail before the first successful local run: [Bug]: Heartbeat-driven agent replies leave pendingFinalDelivery stuck, blocking subsequent heartbeats
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: [Bug]: Heartbeat-driven agent replies leave pendingFinalDelivery stuck, blocking subsequent heartbeats. Context: Observed when using docker, linux
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_0b04928055f3f1c68ea2a81a381eabe7 | https://github.com/openclaw/openclaw/issues/83184 | [Bug]: Heartbeat-driven agent replies leave pendingFinalDelivery stuck, blocking subsequent heartbeats

23. 安装坑 · 失败模式:installation: doctor misclassifies junction-backed source checkout as non-git install

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this installation risk before relying on the project: doctor misclassifies junction-backed source checkout as non-git install
  • 对用户的影响:Developers may fail before the first successful local run: doctor misclassifies junction-backed source checkout as non-git install
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: doctor misclassifies junction-backed source checkout as non-git install. Context: Observed when using node, windows
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_9fe76fe221918ff7725762228c14cecd | https://github.com/openclaw/openclaw/issues/82215 | doctor misclassifies junction-backed source checkout as non-git install

24. 安装坑 · 失败模式:installation: pi-embedded-runner: empty-reasoning-only completions on openai-codex-responses bypass failove...

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this installation risk before relying on the project: pi-embedded-runner: empty-reasoning-only completions on openai-codex-responses bypass failover (assistantTexts=[], usage.output>0)
  • 对用户的影响:Developers may fail before the first successful local run: pi-embedded-runner: empty-reasoning-only completions on openai-codex-responses bypass failover (assistantTexts=[], usage.output>0)
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: pi-embedded-runner: empty-reasoning-only completions on openai-codex-responses bypass failover (assistantTexts=[], usage.output>0). Context: Observed when using node, macos
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_ae1d809d9053253201e1f8e0030998d4 | https://github.com/openclaw/openclaw/issues/85364 | pi-embedded-runner: empty-reasoning-only completions on openai-codex-responses bypass failover (assistantTexts=[], usage.output>0)

25. 安装坑 · 失败模式:installation: sessions_history returns unfiltered delivery-mirror messages — duplicates visible in dashboard

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this installation risk before relying on the project: sessions_history returns unfiltered delivery-mirror messages — duplicates visible in dashboard
  • 对用户的影响:Developers may fail before the first successful local run: sessions_history returns unfiltered delivery-mirror messages — duplicates visible in dashboard
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: sessions_history returns unfiltered delivery-mirror messages — duplicates visible in dashboard. Context: Observed when using node, macos
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_7dd1d364c27e0e14a83aff658390fce1 | https://github.com/openclaw/openclaw/issues/85669 | sessions_history returns unfiltered delivery-mirror messages — duplicates visible in dashboard

26. 配置坑 · 失败模式:configuration: Bug: Cline bridge silently fails on gateway config tasks — no config.schema.lookup tool

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this configuration risk before relying on the project: Bug: Cline bridge silently fails on gateway config tasks — no config.schema.lookup tool
  • 对用户的影响:Developers may misconfigure credentials, environment, or host setup: Bug: Cline bridge silently fails on gateway config tasks — no config.schema.lookup tool
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: Bug: Cline bridge silently fails on gateway config tasks — no config.schema.lookup tool. Context: Source discussion did not expose a precise runtime context.
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_c0ae27ad3403f7c4540c83109af4c08e | https://github.com/openclaw/openclaw/issues/85729 | Bug: Cline bridge silently fails on gateway config tasks — no config.schema.lookup tool

27. 配置坑 · 失败模式:configuration: Codex app-server emits notification:turn/started then goes silent; embedded run wedges for th...

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this configuration risk before relying on the project: Codex app-server emits notification:turn/started then goes silent; embedded run wedges for the full stuck-session recovery window
  • 对用户的影响:Developers may misconfigure credentials, environment, or host setup: Codex app-server emits notification:turn/started then goes silent; embedded run wedges for the full stuck-session recovery window
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: Codex app-server emits notification:turn/started then goes silent; embedded run wedges for the full stuck-session recovery window. Context: Observed when using node, macos
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_59d49cf86ab84f8b9e5f8d39858c236c | https://github.com/openclaw/openclaw/issues/85251 | Codex app-server emits notification:turn/started then goes silent; embedded run wedges for the full stuck-session recovery window

28. 配置坑 · 失败模式:configuration: Subagent lifecycle observability + async supervision controls

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this configuration risk before relying on the project: Subagent lifecycle observability + async supervision controls
  • 对用户的影响:Developers may misconfigure credentials, environment, or host setup: Subagent lifecycle observability + async supervision controls
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: Subagent lifecycle observability + async supervision controls. Context: Source discussion did not expose a precise runtime context.
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_144e8fdd791eec9c8d41255ed33258fb | https://github.com/openclaw/openclaw/issues/38626 | Subagent lifecycle observability + async supervision controls

29. 配置坑 · 失败模式:configuration: Workaround for isolated cron agentTurn stuck (re: #68157, #11994, #42103)

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this configuration risk before relying on the project: Workaround for isolated cron agentTurn stuck (re: #68157, #11994, #42103)
  • 对用户的影响:Developers may misconfigure credentials, environment, or host setup: Workaround for isolated cron agentTurn stuck (re: #68157, #11994, #42103)
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: Workaround for isolated cron agentTurn stuck (re: #68157, #11994, #42103). Context: Observed when using node, python
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_b8cd78828411a316041f7b17e3c0d64f | https://github.com/openclaw/openclaw/issues/85516 | Workaround for isolated cron agentTurn stuck (re: #68157, #11994, #42103)

30. 能力坑 · 能力判断依赖假设

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:README/documentation is current enough for a first validation pass.
  • 对用户的影响:假设不成立时,用户拿不到承诺的能力。
  • 建议检查:将假设转成下游验证清单。
  • 防护动作: 假设必须转成验证项;没有验证结果前不能写成事实。
  • 证据:capability.assumptions | github_repo:1103012935 | https://github.com/openclaw/openclaw | README/documentation is current enough for a first validation pass.

31. 维护坑 · 失败模式:migration: imsg RPC Crashes on Phone Number Validation, Causing Cascading iMessage Delivery Failures

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:Developers should check this migration risk before relying on the project: imsg RPC Crashes on Phone Number Validation, Causing Cascading iMessage Delivery Failures
  • 对用户的影响:Developers may hit a documented source-backed failure mode: imsg RPC Crashes on Phone Number Validation, Causing Cascading iMessage Delivery Failures
  • 建议检查:Before packaging this project, run the relevant install/config/quickstart check for: imsg RPC Crashes on Phone Number Validation, Causing Cascading iMessage Delivery Failures. Context: Observed when using macos
  • 防护动作: State this as source-backed community evidence, not as Doramagic reproduction.
  • 证据:failure_mode_cluster:github_issue | fmev_cf5a24c802fea3d08f84afc54aadc246 | https://github.com/openclaw/openclaw/issues/85740 | imsg RPC Crashes on Phone Number Validation, Causing Cascading iMessage Delivery Failures

32. 维护坑 · 维护活跃度未知

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:未记录 last_activity_observed。
  • 对用户的影响:新项目、停更项目和活跃项目会被混在一起,推荐信任度下降。
  • 建议检查:补 GitHub 最近 commit、release、issue/PR 响应信号。
  • 防护动作: 维护活跃度未知时,推荐强度不能标为高信任。
  • 证据:evidence.maintainer_signals | github_repo:1103012935 | https://github.com/openclaw/openclaw | last_activity_observed missing

33. 安全/权限坑 · 下游验证发现风险项

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:no_demo
  • 对用户的影响:下游已经要求复核,不能在页面中弱化。
  • 建议检查:进入安全/权限治理复核队列。
  • 防护动作: 下游风险存在时必须保持 review/recommendation 降级。
  • 证据:downstream_validation.risk_items | github_repo:1103012935 | https://github.com/openclaw/openclaw | no_demo; severity=medium

34. 安全/权限坑 · 存在评分风险

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:no_demo
  • 对用户的影响:风险会影响是否适合普通用户安装。
  • 建议检查:把风险写入边界卡,并确认是否需要人工复核。
  • 防护动作: 评分风险必须进入边界卡,不能只作为内部分数。
  • 证据:risks.scoring_risks | github_repo:1103012935 | https://github.com/openclaw/openclaw | no_demo; severity=medium

35. 安全/权限坑 · 来源证据:Avoid recreating unchanged message objects when stripping inline directive tags

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题:Avoid recreating unchanged message objects when stripping inline directive tags
  • 对用户的影响:可能影响授权、密钥配置或安全边界。
  • 建议检查:来源显示可能已有修复、规避或版本变化,说明书中必须标注适用版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_2a30673390034d06aee3f633e80be67c | https://github.com/openclaw/openclaw/issues/37589 | 来源讨论提到 npm 相关条件,需在安装/试用前复核。

36. 安全/权限坑 · 来源证据:pi-embedded-runner: empty-reasoning-only completions on openai-codex-responses bypass failover (assistantTexts=[], usag…

  • 严重度:medium
  • 证据强度:source_linked
  • 发现:GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题:pi-embedded-runner: empty-reasoning-only completions on openai-codex-responses bypass failover (assistantTexts=[], usage.output>0)
  • 对用户的影响:可能影响授权、密钥配置或安全边界。
  • 建议检查:来源显示可能已有修复、规避或版本变化,说明书中必须标注适用版本。
  • 防护动作: 不得脱离来源链接放大为确定性结论;需要标注适用版本和复核状态。
  • 证据:community_evidence:github | cevd_e75bf8e6b28645f1b0f0746fafc2d6c7 | https://github.com/openclaw/openclaw/issues/85364 | 来源讨论提到 node 相关条件,需在安装/试用前复核。

37. 维护坑 · issue/PR 响应质量未知

  • 严重度:low
  • 证据强度:source_linked
  • 发现:issue_or_pr_quality=unknown。
  • 对用户的影响:用户无法判断遇到问题后是否有人维护。
  • 建议检查:抽样最近 issue/PR,判断是否长期无人处理。
  • 防护动作: issue/PR 响应未知时,必须提示维护风险。
  • 证据:evidence.maintainer_signals | github_repo:1103012935 | https://github.com/openclaw/openclaw | issue_or_pr_quality=unknown

38. 维护坑 · 发布节奏不明确

  • 严重度:low
  • 证据强度:source_linked
  • 发现:release_recency=unknown。
  • 对用户的影响:安装命令和文档可能落后于代码,用户踩坑概率升高。
  • 建议检查:确认最近 release/tag 和 README 安装命令是否一致。
  • 防护动作: 发布节奏未知或过期时,安装说明必须标注可能漂移。
  • 证据:evidence.maintainer_signals | github_repo:1103012935 | https://github.com/openclaw/openclaw | release_recency=unknown

来源:Doramagic 发现、验证与编译记录