<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>agents-radar</title>
    <link>https://huang-yi-dae.github.io/agents-radar</link>
    <description>AI 开源生态每日简报 · Daily AI ecosystem digest</description>
    <language>zh-CN</language>
    <atom:link href="https://huang-yi-dae.github.io/agents-radar/feed.xml" rel="self" type="application/rss+xml"/>
    <lastBuildDate>Sat, 22 Aug 2026 18:49:39 +0000</lastBuildDate>
    <item>
      <title>AI CLI 工具社区动态日报 2026-08-23</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-cli</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-cli</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>AI CLI 工具社区动态日报 2026-08-23 生成时间: 2026-08-23 02:30 (GMT+8) | 覆盖工具: 7 个 CLI + Claude Code Skills 本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。 Claude Code OpenAI Codex Gemini CLI GitHub Copilot CLI Kimi Code CLI OpenCode Qwen Code Claude Code Skills 横向对比 AI CLI 工具社区动态横向对比分析报告（2026-08-23） 1. 生态全景 今日 AI CLI 赛道最值得记录的不是某个 release，而是口碑天平的可测量位移。Hacker News 当日最高赞技术帖是《A week of using Codex more than Claude》（94👍 / 104💬），紧随其后是《Anthropic appears to be A/B testing reduced effort levels in C...</description>
      <content:encoded><![CDATA[<h1>AI CLI 工具社区动态日报 2026-08-23</h1>
<blockquote>
<p>生成时间: 2026-08-23 02:30 (GMT+8) | 覆盖工具: 7 个 CLI + Claude Code Skills
本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。</p>
</blockquote>
<ul>
<li><a href="https://github.com/anthropics/claude-code">Claude Code</a></li>
<li><a href="https://github.com/openai/codex">OpenAI Codex</a></li>
<li><a href="https://github.com/google-gemini/gemini-cli">Gemini CLI</a></li>
<li><a href="https://github.com/github/copilot-cli">GitHub Copilot CLI</a></li>
<li><a href="https://github.com/MoonshotAI/kimi-cli">Kimi Code CLI</a></li>
<li><a href="https://github.com/anomalyco/opencode">OpenCode</a></li>
<li><a href="https://github.com/QwenLM/qwen-code">Qwen Code</a></li>
<li><a href="https://github.com/anthropics/skills">Claude Code Skills</a></li>
</ul>
<hr>
<h2>横向对比</h2>
<h1>AI CLI 工具社区动态横向对比分析报告（2026-08-23）</h1>
<h2>1. 生态全景</h2>
<p>今日 AI CLI 赛道最值得记录的不是某个 release，而是<strong>口碑天平的可测量位移</strong>。Hacker News 当日最高赞技术帖是《A week of using Codex more than Claude》（94👍 / 104💬），紧随其后是《Anthropic appears to be A/B testing reduced effort levels in Claude Code》（51👍 / 45💬）；而 Claude Code 仓库内长期第一高赞 issue #77136「模型越来越倾向于重复性修辞腔调」已累积 <strong>343👍 / 60💬</strong>。三条独立信号指向同一件事：<strong>用户开始怀疑&quot;同一个订阅买到的智能在缩水&quot;</strong>——这是比功能缺失更难修的信任问题。</p>
<p>但另一侧同样不太平。Codex 在 08-21 更新后立刻出现 #40075「Shell Helper / PowerShell / Git 命令全部无法执行」的回归，属于「核心能力当天崩」级别的事故。所以今天的准确描述不是&quot;Codex 赢了&quot;，而是<strong>两家头部产品同时在为高速迭代付出体验税，用户正在用脚投票测量哪边的税更低</strong>。</p>
<p>主干节奏上，今天出现清晰的三档分层：<strong>日更稳定档</strong>（Claude Code v2.1.240、Gemini nightly、Qwen v0.22.0 正式版）、<strong>alpha 冲刺档</strong>（Codex rust-v0.150.0-alpha.2/.3/.5/.6 一天内连发 4 个预发布）、<strong>冻结档</strong>（Copilot CLI 停在 08-14 的 v1.0.81-7、Kimi 停在 07-16 的 1.49.0）。</p>
<h2>2. 各工具活跃度对比（近 24h）</h2>
<table>
<thead>
<tr>
<th>工具</th>
<th>活跃 Issues（新建）</th>
<th>PR（新建）</th>
<th>Releases（近期）</th>
</tr>
</thead>
<tbody><tr>
<td>Claude Code</td>
<td>100+（41 条新建）</td>
<td>0（仓库不开放外部 PR）</td>
<td><strong>v2.1.240（08-22）</strong>、v2.1.239（08-21）</td>
</tr>
<tr>
<td>OpenAI Codex</td>
<td>100+（40 条新建）</td>
<td>0（仓库不开放外部 PR）</td>
<td>rust-v0.150.0-alpha.6/.5/.3/.2（08-21）</td>
</tr>
<tr>
<td>Gemini CLI</td>
<td>100+（1 条新建）</td>
<td>0</td>
<td>v0.56.0-nightly.20260822、v0.57.0-preview.0</td>
</tr>
<tr>
<td>GitHub Copilot CLI</td>
<td>8（2 条新建）</td>
<td>0</td>
<td>v1.0.81-7（08-14，<strong>8 天未发新版</strong>）</td>
</tr>
<tr>
<td>Kimi Code CLI</td>
<td>3（0 条新建）</td>
<td>2</td>
<td>1.49.0（07-16，<strong>37 天未发新版</strong>）</td>
</tr>
<tr>
<td>OpenCode</td>
<td>62（43 条新建）</td>
<td>38（29 条新建）</td>
<td>v1.18.21 / v1.18.20（08-21）</td>
</tr>
<tr>
<td>Qwen Code</td>
<td>10（3 条新建）</td>
<td><strong>90（27 条新建）</strong></td>
<td><strong>v0.22.0（08-22）</strong>、v0.21.14-nightly.20260822</td>
</tr>
<tr>
<td>Claude Code Skills</td>
<td>3（1 条新建）</td>
<td>8（5 条新建）</td>
<td>—</td>
</tr>
</tbody></table>
<blockquote>
<p>读表提示：Claude Code / Codex / Gemini 的 issue 计数触及 API 单页上限（100），其中相当比例是历史 issue 被 bot 刷新标签，故上表额外标注「新建」列——<strong>新建数才是当日真实增量</strong>。按此口径，Gemini CLI 今日近乎静默（仅 1 条新 issue，标题只有一个词 &quot;edge&quot;），而 OpenCode 的 43 条新 issue 是全场最高。</p>
</blockquote>
<h2>3. 共同关注的功能方向</h2>
<ul>
<li><strong>空响应与中途截断，正在从&quot;偶发 bug&quot;升级为&quot;计费黑洞&quot;</strong>：OpenCode 今日新开 #44148「Go plan 上出现空 completion（finish_reason=other）与长推理请求的中途截断」，与既有 #41469「空 LLM 响应导致会话静默停止（finish: unknown, 0 tokens）」、#32149「无响应停止处理」构成同一条故障链。Zeroclaw 侧的 PR #9447「classify incomplete terminal responses」是同一命题的工程解法。共性诉求已经很明确：<strong>失败必须可归因，不能既扣了 token 又当成&quot;干净结束&quot;</strong>。</li>
<li><strong>记忆持久化是今日跨工具共识度最高的缺口</strong>：Kimi #1283「Memory System — 跨会话持久上下文」以 40💬 成为该仓库讨论第一（且有中文 issue #1478「能否优化记忆层？搞大项目的时候很痛苦」直接呼应）；Codex #18343 要求「分层记忆管理（global / project / hybrid / per-thread）」；Claude Code #88862 是一份高质量田野报告——「多个并发会话共用一个 git clone，实测碰撞并给出三种用户态缓解方案」。三者从不同角度指向同一个事实：<strong>记忆与并发隔离仍是各家都没做完的地基</strong>。</li>
<li><strong>Windows 依旧是全赛道公摊的技术债</strong>：Claude Code #88818（MSIX 包异常关闭后无法启动，提示需重装）、#88864（Qemu 虚拟机 arm64 正常但 x86+KVM 100% CPU 永久挂起）、#85891（Win11 主窗口强制置顶）；Codex #39209（rollout 路径使用 <code>\\?\</code> 前缀时归档报 os error 2）、#39170（启用高级功能后 15–40 秒内丢失 ChatGPT 鉴权）、#40075（08-21 更新后 PowerShell/Git 全挂）；Copilot CLI #4111（原地自动更新后长会话仍在执行旧代码）。反向印证的是 OpenCode PR #44214——<strong>直接上原生 Windows ARM64 桌面端（Electron 38）</strong>，把 Windows 当一等公民做，是当前最实的差异化切口。</li>
<li><strong>Skills 安全边界首次被正面击穿</strong>：<code>anthropics/skills</code> 今日新开 #1631「run_eval.py 中未净化的 skill_name 导致路径穿越」。这是一条真实漏洞，不是功能请求。配合 PR #1629 / #1630（修复 eval harness 三处缺陷，此前会静默报出 0.0 触发率）可以读出：<strong>Skills 生态正从&quot;能不能跑&quot;进入&quot;跑得可信不可信&quot;阶段</strong>，而评测工具自身的正确性是第一道门。</li>
</ul>
<h2>4. 差异化定位</h2>
<ul>
<li><strong>Claude Code</strong>：v2.1.240 保持日更，工程节奏没问题，但<strong>声誉侧承压最重</strong>。#77136（343👍）指控输出腔调劣化、#87640 报告 Fable 5 的 <code>[reasoning_extraction]</code> 安全护栏对单词问候语误报、#84352（139💬）反映已通过 CVP 审核的组织仍被安全护栏拦截。再叠加 HN 上的 A/B 降智猜测，其核心矛盾已从「功能够不够」变成**「护栏与降本是否在悄悄侵蚀我付费买到的能力」**。这类问题只能靠透明度而非补丁解决。</li>
<li><strong>OpenAI Codex</strong>：一天连发 4 个 alpha，是全场迭代最激进的。社区最想要的仍是跨端连续性——#5609「在 ChatGPT 网页端与 VSCode 内的 Codex 之间同步会话历史」（66👍）与 #27565「类 Claude Code 的远程控制」（15👍）。但激进的代价是 #40075 这类当日回归，以及 #37475（0.147.0 拒收 Amazon Bedrock 输入并破坏 subagent 交接）、#22844（远程 SSH 下 <code>@browser</code> 不可用）。定位是<strong>OpenAI 全端统一入口，用稳定性换取速度</strong>。</li>
<li><strong>Gemini CLI</strong>：nightly 照常滚（v0.56.0-nightly.20260822），但社区侧今日几乎无声——唯一新建 issue #28964 标题仅一个词。存量痛点仍卡在准入与信任：#28912「提示无有效许可证」（18💬）、#28341「无限鉴权循环」、#22323「subagent 在 MAX_TURNS 后被误报为 GOAL 成功，掩盖了中断」。<strong>#22323 是今日全赛道最危险的一类 bug——失败被上报成成功，会污染一切自动化评测</strong>。</li>
<li><strong>GitHub Copilot CLI</strong>：8 天未发新版，issue 总量仅 8 条，但诉求高度收敛且一致：#3709（27👍）与 #3282（26👍）都是「一个会话内切换多个 BYOK / 本地模型」。今日新开 #4566「Agent 反复口头确认工作但不实际执行工具调用」，是典型的 agent 可信度问题。定位仍是<strong>企业受管环境入口，模型自由度是其最大的用户张力</strong>。</li>
<li><strong>Kimi Code CLI</strong>：37 天未发新版，今日 0 条新建 issue，外部声量为全场最低。有价值的信号只有一条：#1283（40💬）证明<strong>即使在低活跃仓库，记忆系统也是最高优先级的用户诉求</strong>。两条 PR（#2594 修复 StrReplaceFile 编辑丢失非 UTF-8 字节、#2614 补插件安全与持久化数据文档）说明维护者仍在，只是节奏极慢。</li>
<li><strong>OpenCode</strong>：<strong>今日新建 issue（43）与新建 PR（29）双榜第一，是社区活跃度冠军</strong>。既有高赞 #7101「支持全局/项目级自定义系统提示词」（127👍，已关闭）、#5121「Windows winget 安装」（27👍）反映其用户极重可定制。新 PR 组合能看出打磨方向非常&quot;工程&quot;:#44127（消除冗余 git 子进程 spawn，改用无 spawn 的未跟踪文件统计）、#44218（在未跟随的会话分配状态前就丢弃事件）、#44197（清理剪贴板文本）、#44219（为 Cloudflare AI Gateway 统一路由翻译带点号的 Anthropic 模型 id）。另外 #39845（27👍 / 22💬）值得单独标注——「DeepSeek V4 Flash 突然要求开启『启用中国托管模型』开关」，是<strong>地缘合规开始直接影响开发者日常工作流</strong>的实例。</li>
<li><strong>Qwen Code</strong>：<strong>PR 体系工业化程度全场第一（90 条活跃 / 27 条新建），且今日发布 v0.22.0 正式版</strong>。高讨论 PR 集中在 provider 广度与缓存效率：#8368（接入 Kimi 与小米 MiMo，72💬）、#8332（附件音频桥，70💬）、#8276（跨延迟工具发现保留 prompt cache，64💬）。今日新 PR 更偏可靠性内核：#9705（在实时会话重放期间保持 in-flight 工具调用为 pending）、#9718（依据模型声明来收敛 skill 公告）、#9745（为修复轮次设预算，且其超时不计入总上限）。唯一需要警惕的是 issue #9733——<strong>loop detection 在正常校验循环上误判，直接杀掉无人值守的 turn</strong>，这是自动化场景的致命伤。</li>
<li><strong>Claude Code Skills</strong>：今日主题就是<strong>安全与评测自净</strong>。#1631 路径穿越（新建）、#1252（<code>product-self-knowledge</code> 在文档 URL 抓取失败时降级为公网搜索——静默降级即数据来源不可控）、#1559 + PR #1629 / #1630（eval harness 会对可用描述误报 0% 触发率，并新增 <code>--scan-full-turn</code> 以测量 skill 是否真的触发）。可以概括为：<strong>Skills 正在补齐&quot;可验证&quot;这一环</strong>。</li>
</ul>
<h2>5. 值得关注的趋势信号</h2>
<ul>
<li><strong>信任正在成为比功能更硬的竞争壁垒。</strong> 今天最贵的三条信号——Claude 腔调劣化（343👍）、HN 降智 A/B 猜测（51👍）、Gemini 失败误报成功（#22323）——全都不是&quot;少了什么功能&quot;，而是&quot;我不敢确定它是否照我以为的方式在工作&quot;。<strong>能率先把 effort 等级、护栏触发、失败原因做成可观测面板的产品，会拿到不对称优势。</strong></li>
<li><strong>激进迭代与当日回归已成常态，用户开始把&quot;回归频率&quot;当选型指标。</strong> Codex 一天 4 个 alpha 对应 #40075 核心命令全挂；OpenCode 一天 29 个新 PR 但同时新开 43 个 issue。<strong>高速度不再自动等于领先，回归率才是真实的迭代质量。</strong></li>
<li><strong>合规与地缘正在下沉到 CLI 层。</strong> OpenCode #39845（DeepSeek V4 Flash 需显式开启&quot;中国托管模型&quot;）说明模型可用性已不只是技术问题。多 provider 抽象（Qwen #8368、Zeroclaw Hailo-Ollama）的真实价值，正在从&quot;性价比选择&quot;转向&quot;合规兜底&quot;。</li>
<li><strong>Skills 已过了&quot;能用&quot;阶段，正在进入&quot;可审计&quot;阶段。</strong> 同一天里，GitHub Trending 上出现 3 个 Skills 相关项目（mattpocock/skills、obra/superpowers、andrej-karpathy-skills），而 <code>anthropics/skills</code> 内部在修路径穿越和评测误报。<strong>生态热度与安全成熟度出现明显时间差，这个差就是未来事故的窗口。</strong></li>
</ul>
<hr>
<h2>各工具动态明细</h2>
<h3>Claude Code（<a href="https://github.com/anthropics/claude-code">anthropics/claude-code</a>）</h3>
<p><strong>Releases</strong>：<a href="https://github.com/anthropics/claude-code/releases/tag/v2.1.240">v2.1.240</a>（08-22）、<a href="https://github.com/anthropics/claude-code/releases/tag/v2.1.239">v2.1.239</a>（08-21）、v2.1.238 / v2.1.237（08-20）——保持接近日更的稳定节奏。</p>
<p><strong>高热度存量 issue</strong></p>
<table>
<thead>
<tr>
<th>Issue</th>
<th>热度</th>
<th>说明</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/anthropics/claude-code/issues/77136">#77136</a></td>
<td>343👍 / 60💬</td>
<td>Claude 4.7 / 4.8 / 5.0 与 Fable 越来越倾向重复性修辞腔调——该仓库长期第一高赞，属输出质量的系统性投诉</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/32479">#32479</a></td>
<td>140👍 / 90💬</td>
<td>Claude Desktop 已连接 GitHub Connector 但 Claude 不识别</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/84352">#84352</a></td>
<td>22👍 / 139💬</td>
<td>已通过 CVP 审核的组织仍被 cyber safeguard 拦截——护栏误伤企业客户</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/6305">#6305</a></td>
<td>16👍 / 40💬</td>
<td>Post/PreToolUse Hooks 不执行</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/64630">#64630</a></td>
<td>25👍 / 17💬</td>
<td>macOS 登录不走系统默认浏览器</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/42700">#42700</a></td>
<td>24👍 / 17💬</td>
<td>远程控制会话希望支持 TTS 朗读与语音模式</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/87640">#87640</a></td>
<td>13👍 / 8💬</td>
<td>Fable 5 的 <code>[reasoning_extraction]</code> 护栏对单词问候语误报</td>
</tr>
</tbody></table>
<p><strong>今日新建（41 条，摘其要）</strong></p>
<ul>
<li><a href="https://github.com/anthropics/claude-code/issues/88862">#88862</a> — 田野报告：多并发会话共用同一个 git clone，作者实测出碰撞并给出三种用户态缓解方案。<strong>今日质量最高的一条用户投稿，直指并发隔离缺位。</strong></li>
<li><a href="https://github.com/anthropics/claude-code/issues/88818">#88818</a> — Windows MSIX 包在意外关闭后无法启动，提示&quot;需要重新安装&quot;。</li>
<li><a href="https://github.com/anthropics/claude-code/issues/88865">#88865</a> — VSCode 扩展中出现被凭空注入的 tool-call / tool-result 块。<strong>伪造的工具调用记录会直接破坏会话可信度。</strong></li>
<li><a href="https://github.com/anthropics/claude-code/issues/88864">#88864</a> — Qemu 虚拟机：arm64 正常，x86+KVM 永久挂起（100% CPU），纯 x86 崩溃。</li>
<li><a href="https://github.com/anthropics/claude-code/issues/88860">#88860</a> — 移动端 GUI 的 effort 滑块在打开会话时不反映真实 effort 等级。<strong>结合 HN 上的降智猜测，effort 可见性正在变成敏感问题。</strong></li>
<li><a href="https://github.com/anthropics/claude-code/issues/88847">#88847</a> — Cowork 与 Chrome 集成问题。</li>
</ul>
<h3>OpenAI Codex（<a href="https://github.com/openai/codex">openai/codex</a>）</h3>
<p><strong>Releases</strong>（08-21 一天连发 4 个预发布）：<a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.6">rust-v0.150.0-alpha.6</a>、<a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.5">alpha.5</a>、<a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.3">alpha.3</a>、<a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.2">alpha.2</a>，另有 rust-v0.149.0-alpha.7.1。</p>
<p><strong>高热度存量 issue</strong></p>
<table>
<thead>
<tr>
<th>Issue</th>
<th>热度</th>
<th>说明</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/openai/codex/issues/5609">#5609</a></td>
<td>66👍 / 8💬</td>
<td>在 ChatGPT 网页端与 VSCode 内 Codex 之间同步会话历史——最高赞诉求，本质是跨端连续性</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/22844">#22844</a></td>
<td>25👍 / 4💬</td>
<td>远程 SSH 下应用内浏览器侧栏可用但 <code>@browser</code> 不可用</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/39162">#39162</a></td>
<td>24👍 / 36💬</td>
<td>macOS：打开已有会话会使 ChatGPT 鉴权失效并触发重定向</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/37475">#37475</a></td>
<td>22👍 / 7💬</td>
<td>CLI 0.147.0 拒收 Amazon Bedrock 输入并破坏 subagent 交接</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/21128">#21128</a></td>
<td>21👍 / 38💬</td>
<td>Desktop 静默隐藏全局 recent-50 窗口之外的项目会话</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/39170">#39170</a></td>
<td>14👍 / 13💬</td>
<td>Windows 桌面端启用高级功能后 15–40 秒内丢失 ChatGPT 鉴权</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/18343">#18343</a></td>
<td>11👍 / 11💬</td>
<td>分层记忆管理（global / project / hybrid / per-thread）</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/20864">#20864</a></td>
<td>6👍 / 23💬</td>
<td>Desktop 卡顿：全量扫描 <code>~/.codex/sessions</code> rollout 文件</td>
</tr>
</tbody></table>
<p><strong>今日新建（40 条，摘其要）</strong></p>
<ul>
<li><a href="https://github.com/openai/codex/issues/40075">#40075</a> — <strong>08-21 更新后回归：Shell Helper、PowerShell 与 Git 命令全部无法执行。今日全赛道最严重的一条当日回归。</strong></li>
<li><a href="https://github.com/openai/codex/issues/40116">#40116</a> — App Server：为 workspaceWrite 类 turn 强制限定可读根目录（沙箱收紧）。</li>
<li><a href="https://github.com/openai/codex/issues/40112">#40112</a> — Desktop：已完成的线程在重启后仍显示崩溃前的过期状态，而 rollout 与状态数据库已更新。</li>
<li><a href="https://github.com/openai/codex/issues/40136">#40136</a> — 聊天行历史被截断至 3–4 条，且渲染出未转义的 HTML 实体（如 <code>&amp;#x20;</code>）。</li>
<li><a href="https://github.com/openai/codex/issues/40052">#40052</a> — Android：语音模式隐藏已连接的应用工具，切回文字模式后同一会话中又出现。</li>
</ul>
<h3>Gemini CLI（<a href="https://github.com/google-gemini/gemini-cli">google-gemini/gemini-cli</a>）</h3>
<p><strong>Releases</strong>：<a href="https://github.com/google-gemini/gemini-cli/releases/tag/v0.56.0-nightly.20260822.g5411f113c">v0.56.0-nightly.20260822</a>、v0.56.0-nightly.20260821、<a href="https://github.com/google-gemini/gemini-cli/releases/tag/v0.57.0-preview.0">v0.57.0-preview.0</a>（08-19）、v0.56.0 正式版（08-19）。</p>
<p><strong>今日社区侧近乎静默——唯一新建 issue <a href="https://github.com/google-gemini/gemini-cli/issues/28964">#28964</a> 标题仅有一个词 &quot;edge&quot;。</strong> 存量痛点集中在准入与 agent 可信度：</p>
<ul>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/28912">#28912</a>（6👍 / 18💬）— 提示&quot;您没有此产品的有效许可证&quot;，卡在准入第一步。</li>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/28341">#28341</a>（9👍 / 7💬）— 无限鉴权循环。</li>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/21409">#21409</a>（8👍 / 8💬）— generalist agent 挂起。</li>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/22323">#22323</a>（2👍 / 13💬）— <strong>subagent 在 MAX_TURNS 后的恢复被上报为 GOAL 成功，掩盖了中断。失败伪装成成功，是自动化评测的头号污染源。</strong></li>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/26522">#26522</a> — 自动记忆对低信号会话无限重试。</li>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/21968">#21968</a> — Gemini 对 skills 与 sub-agents 的利用不足。</li>
</ul>
<h3>GitHub Copilot CLI（<a href="https://github.com/github/copilot-cli">github/copilot-cli</a>）</h3>
<p><strong>Releases</strong>：v1.0.81-7（08-14）为最新，<strong>已 8 天未发新版</strong>。</p>
<ul>
<li><a href="https://github.com/github/copilot-cli/issues/3709">#3709</a>（27👍 / 5💬）与 <a href="https://github.com/github/copilot-cli/issues/3282">#3282</a>（26👍 / 9💬）— 两条最高赞诉求指向同一件事：<strong>在单个会话内切换多个 BYOK / 本地 provider 模型</strong>。</li>
<li><a href="https://github.com/github/copilot-cli/issues/2306">#2306</a>（3👍 / 7💬）— 提示需企业或组织授权才能使用该 Copilot 功能。</li>
<li><a href="https://github.com/github/copilot-cli/issues/4370">#4370</a> — 1.0.79-1 在 <code>server/discover</code> 返回 <code>-32602</code> 时 MCP 初始化失败。</li>
<li><a href="https://github.com/github/copilot-cli/issues/4111">#4111</a> — Windows：原地自动更新后仍打开的长会话继续执行旧代码。</li>
<li><strong>今日新建</strong>：<a href="https://github.com/github/copilot-cli/issues/4566">#4566</a>「Agent 反复口头确认工作但不实际执行工具调用」——典型的&quot;假装干活&quot;可信度问题；<a href="https://github.com/github/copilot-cli/issues/4565">#4565</a> 仓库配置问题告警。</li>
</ul>
<h3>Kimi Code CLI（<a href="https://github.com/MoonshotAI/kimi-cli">MoonshotAI/kimi-cli</a>）</h3>
<p><strong>Releases</strong>：1.49.0（07-16）为最新，<strong>已 37 天未发新版</strong>。今日 0 条新建 issue，为全场最静默。</p>
<ul>
<li><a href="https://github.com/MoonshotAI/kimi-cli/issues/1283">#1283</a>（40💬）— <strong>Memory System：跨会话持久上下文。该仓库讨论量第一，印证记忆是跨工具共识缺口。</strong></li>
<li><a href="https://github.com/MoonshotAI/kimi-cli/issues/1478">#1478</a> — 中文 issue：「能否优化记忆层？而且我也没在参考文档里看到和记忆有关的东西？搞大项目的时候很痛苦。」与 #1283 同源。</li>
<li>PR <a href="https://github.com/MoonshotAI/kimi-cli/pull/2594">#2594</a>（已合）— 修复 <code>StrReplaceFile</code> 编辑时丢失非 UTF-8 字节。</li>
<li>PR <a href="https://github.com/MoonshotAI/kimi-cli/pull/2614">#2614</a> — 补充插件安全与持久化数据文档。</li>
</ul>
<h3>OpenCode（<a href="https://github.com/anomalyco/opencode">anomalyco/opencode</a>）</h3>
<p><strong>Releases</strong>：<a href="https://github.com/anomalyco/opencode/releases/tag/v1.18.21">v1.18.21</a> / <a href="https://github.com/anomalyco/opencode/releases/tag/v1.18.20">v1.18.20</a>（08-21）、v1.18.19（08-20）。</p>
<p><strong>今日新建 issue 43 条 + 新建 PR 29 条，双项全场第一。</strong></p>
<p><strong>高热度 issue</strong></p>
<table>
<thead>
<tr>
<th>Issue</th>
<th>热度</th>
<th>说明</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/anomalyco/opencode/issues/7101">#7101</a></td>
<td>127👍 / 35💬（已关闭）</td>
<td>支持全局 / 项目 / 自定义目录级自定义系统提示词</td>
</tr>
<tr>
<td><a href="https://github.com/anomalyco/opencode/issues/39845">#39845</a></td>
<td>27👍 / 22💬</td>
<td><strong>DeepSeek V4 Flash 突然要求开启「启用中国托管模型」才能用于 OpenCode Go 订阅——地缘合规直接干扰日常工作流</strong></td>
</tr>
<tr>
<td><a href="https://github.com/anomalyco/opencode/issues/5121">#5121</a></td>
<td>27👍 / 18💬（已关闭）</td>
<td>Windows winget 安装方式</td>
</tr>
<tr>
<td><a href="https://github.com/anomalyco/opencode/issues/34644">#34644</a></td>
<td>16👍 / 2💬</td>
<td>Copilot Student 计划（Auto-only 模式）下 Copilot provider 未注册</td>
</tr>
<tr>
<td><a href="https://github.com/anomalyco/opencode/issues/16349">#16349</a></td>
<td>14👍 / 7💬</td>
<td>支持左右面板布局互换</td>
</tr>
<tr>
<td><a href="https://github.com/anomalyco/opencode/issues/41469">#41469</a></td>
<td>1👍 / 13💬</td>
<td>空 LLM 响应导致会话静默停止（finish: unknown, 0 tokens）</td>
</tr>
</tbody></table>
<p><strong>今日新建摘要</strong></p>
<ul>
<li><a href="https://github.com/anomalyco/opencode/issues/44148">#44148</a> — <strong>Go plan 上出现空 completion（<code>finish_reason=other</code>）与长推理请求的中途截断。与 #41469 / #32149 构成同一条&quot;静默失败&quot;故障链。</strong></li>
<li><a href="https://github.com/anomalyco/opencode/issues/44142">#44142</a> — 向 sub-agent 派发 shell 命令时工具执行被中止，任务异常终止。</li>
<li><a href="https://github.com/anomalyco/opencode/issues/44151">#44151</a> — 请求提供 worktree 初始化脚本。</li>
<li>PR <a href="https://github.com/anomalyco/opencode/pull/44214">#44214</a> — <strong>新增原生 Windows ARM64 桌面端（Electron 38）。把 Windows 当一等公民，是当前最实的差异化。</strong></li>
<li>PR <a href="https://github.com/anomalyco/opencode/pull/44127">#44127</a> — 消除冗余 git 子进程 spawn，改用无 spawn 的未跟踪文件统计（性能）。</li>
<li>PR <a href="https://github.com/anomalyco/opencode/pull/44219">#44219</a> — 为 Cloudflare AI Gateway 统一路由翻译带点号的 Anthropic 模型 id。</li>
<li>PR <a href="https://github.com/anomalyco/opencode/pull/44218">#44218</a> — 在未跟随的会话分配状态前就丢弃其事件（内存治理）。</li>
<li>PR <a href="https://github.com/anomalyco/opencode/pull/44197">#44197</a> — 清理剪贴板文本。</li>
</ul>
<h3>Qwen Code（<a href="https://github.com/QwenLM/qwen-code">QwenLM/qwen-code</a>）</h3>
<p><strong>Releases</strong>：<strong><a href="https://github.com/QwenLM/qwen-code/releases/tag/v0.22.0">v0.22.0</a> 正式版（08-22）</strong>、v0.21.14-nightly.20260822、v0.21.15（08-20）。</p>
<p><strong>PR 体系工业化程度全场第一：90 条活跃 / 27 条新建。</strong></p>
<p><strong>高讨论 PR（provider 广度与缓存效率）</strong></p>
<table>
<thead>
<tr>
<th>PR</th>
<th>讨论</th>
<th>内容</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/QwenLM/qwen-code/pull/8368">#8368</a></td>
<td>72💬</td>
<td>新增 Kimi 与小米 MiMo provider</td>
</tr>
<tr>
<td><a href="https://github.com/QwenLM/qwen-code/pull/8332">#8332</a></td>
<td>70💬</td>
<td>为附件新增音频桥</td>
</tr>
<tr>
<td><a href="https://github.com/QwenLM/qwen-code/pull/8276">#8276</a></td>
<td>64💬</td>
<td>跨&quot;延迟工具发现&quot;保留 prompt cache</td>
</tr>
<tr>
<td><a href="https://github.com/QwenLM/qwen-code/pull/8902">#8902</a></td>
<td>44💬</td>
<td>从共享选项定义派生 bootstrap <code>--help</code></td>
</tr>
<tr>
<td><a href="https://github.com/QwenLM/qwen-code/pull/9228">#9228</a></td>
<td>39💬</td>
<td>收窄 serve-ab 的自托管清理范围至 A/B checkout 目录</td>
</tr>
</tbody></table>
<p><strong>今日新建 PR（转向可靠性内核）</strong></p>
<ul>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9705">#9705</a>（14💬）— 在实时会话重放期间保持 in-flight 工具调用为 pending 状态。</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9709">#9709</a>（11💬）— 拒绝那些照抄 prompt 自带示例的会话标题。</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9718">#9718</a> — 依据模型的声明来收敛 skill 公告。</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9745">#9745</a> — 为修复轮次设预算，且其超时不计入总上限。</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9737">#9737</a> — 强制 utils 叶层依赖方向（架构债治理）。</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9729">#9729</a> — 回填会话与 PR 的绑定并刷新其合并状态。</li>
</ul>
<p><strong>需警惕的 issue</strong>：<a href="https://github.com/QwenLM/qwen-code/issues/9733">#9733</a>「loop detection 在正常校验循环上误判，直接杀掉无人值守的 turn」——<strong>自动化场景的致命伤，与 Gemini #22323 同属&quot;检测机制自身出错&quot;这一类。</strong></p>
<h3>Claude Code Skills（<a href="https://github.com/anthropics/skills">anthropics/skills</a>）</h3>
<p>今日主题为<strong>安全与评测自净</strong>：</p>
<ul>
<li><a href="https://github.com/anthropics/skills/issues/1631">#1631</a>（今日新建）— <strong><code>run_eval.py</code> 中未净化的 <code>skill_name</code> 导致路径穿越。真实漏洞，非功能请求。</strong></li>
<li><a href="https://github.com/anthropics/skills/issues/1252">#1252</a> — <code>product-self-knowledge</code> skill 在文档 URL 抓取失败时降级为公网搜索。<strong>静默降级意味着数据来源不可控。</strong></li>
<li><a href="https://github.com/anthropics/skills/issues/1559">#1559</a> — <code>skill-creator</code> 的 <code>run_eval.py</code> 对本可工作的描述误报 0% 触发率。</li>
<li>PR <a href="https://github.com/anthropics/skills/pull/1629">#1629</a> — 修复 eval harness 三处会静默产生 0.0 触发率的缺陷。</li>
<li>PR <a href="https://github.com/anthropics/skills/pull/1630">#1630</a> — 新增 <code>--scan-full-turn</code>，让评测衡量「skill 是否真的触发过」而非仅看单点。</li>
<li>PR <a href="https://github.com/anthropics/skills/pull/1634">#1634</a> — 为 SKIP grep 模式加词边界锚定，避免在 &quot;coherent&quot; 上误命中。</li>
<li>PR <a href="https://github.com/anthropics/skills/pull/1633">#1633</a> / <a href="https://github.com/anthropics/skills/pull/1632">#1632</a> — 重命名 algorithmic-art skill；修复 README 中指向不存在目录的引用。</li>
</ul>
<p>Skills 生态的关键位移是：<strong>评测工具自身的正确性，第一次被当作前置问题来修</strong>。</p>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，所有内容基于 GitHub 公开 API 实时抓取并由执行代理人工撰写，未调用任何外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI CLI Tools Digest 2026-08-23</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-cli-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-cli-en</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>AI CLI Tools Community Daily — 2026-08-23 Generated: 2026-08-23 02:30 (GMT+8) | Coverage: 7 CLIs + Claude Code Skills This digest is produced by the agents-radar local automation. All summaries, comparisons, and writing are done by the executing agent — no external LLM API was called. Claude Code OpenAI Codex Gemini CLI GitHub Copilot CLI Kimi Code CLI OpenCode Qwen Code Claude Code Skills Cross-Tool Comparison AI CLI Tools Cross-Tool Comparison Report (2026-08-23) 1. Ecosystem Overview The most...</description>
      <content:encoded><![CDATA[<h1>AI CLI Tools Community Daily — 2026-08-23</h1>
<blockquote>
<p>Generated: 2026-08-23 02:30 (GMT+8) | Coverage: 7 CLIs + Claude Code Skills
This digest is produced by the agents-radar local automation. All summaries, comparisons, and writing are done by the executing agent — no external LLM API was called.</p>
</blockquote>
<ul>
<li><a href="https://github.com/anthropics/claude-code">Claude Code</a></li>
<li><a href="https://github.com/openai/codex">OpenAI Codex</a></li>
<li><a href="https://github.com/google-gemini/gemini-cli">Gemini CLI</a></li>
<li><a href="https://github.com/github/copilot-cli">GitHub Copilot CLI</a></li>
<li><a href="https://github.com/MoonshotAI/kimi-cli">Kimi Code CLI</a></li>
<li><a href="https://github.com/anomalyco/opencode">OpenCode</a></li>
<li><a href="https://github.com/QwenLM/qwen-code">Qwen Code</a></li>
<li><a href="https://github.com/anthropics/skills">Claude Code Skills</a></li>
</ul>
<hr>
<h2>Cross-Tool Comparison</h2>
<h1>AI CLI Tools Cross-Tool Comparison Report (2026-08-23)</h1>
<h2>1. Ecosystem Overview</h2>
<p>The most notable thing in the AI CLI space today isn&#39;t a release — it&#39;s a <strong>measurable shift in sentiment</strong>. Today&#39;s top technical story on Hacker News was <em>&quot;A week of using Codex more than Claude&quot;</em> (94👍 / 104💬), followed by <em>&quot;Anthropic appears to be A/B testing reduced effort levels in Claude Code&quot;</em> (51👍 / 45💬). Meanwhile, Claude Code&#39;s long-standing top-voted issue #77136 — &quot;models increasingly default to repetitive rhetorical tics&quot; — has accumulated <strong>343👍 / 60💬</strong>. Three independent signals point at the same thing: <strong>users are starting to suspect the intelligence they pay for is quietly shrinking.</strong> That&#39;s a trust problem, and trust is harder to patch than a missing feature.</p>
<p>But the other side isn&#39;t calm either. Right after its 08-21 update, Codex shipped regression #40075 — &quot;Shell Helper, PowerShell and Git commands no longer execute&quot; — a same-day core-capability outage. So the accurate framing today isn&#39;t &quot;Codex won.&quot; It&#39;s that <strong>both leaders are paying an experience tax for aggressive iteration, and users are voting with their feet on whose tax is lower.</strong></p>
<p>On release cadence, three clear tiers emerged: <strong>daily-stable</strong> (Claude Code v2.1.240, Gemini nightlies, Qwen v0.22.0 GA), <strong>alpha sprint</strong> (Codex shipped rust-v0.150.0-alpha.2/.3/.5/.6 — four prereleases in one day), and <strong>frozen</strong> (Copilot CLI stuck at v1.0.81-7 from 08-14; Kimi at 1.49.0 from 07-16).</p>
<h2>2. Activity Comparison (last 24h)</h2>
<table>
<thead>
<tr>
<th>Tool</th>
<th>Active Issues (newly opened)</th>
<th>PRs (newly opened)</th>
<th>Recent Releases</th>
</tr>
</thead>
<tbody><tr>
<td>Claude Code</td>
<td>100+ (41 new)</td>
<td>0 (repo closed to external PRs)</td>
<td><strong>v2.1.240 (08-22)</strong>, v2.1.239 (08-21)</td>
</tr>
<tr>
<td>OpenAI Codex</td>
<td>100+ (40 new)</td>
<td>0 (repo closed to external PRs)</td>
<td>rust-v0.150.0-alpha.6/.5/.3/.2 (08-21)</td>
</tr>
<tr>
<td>Gemini CLI</td>
<td>100+ (1 new)</td>
<td>0</td>
<td>v0.56.0-nightly.20260822, v0.57.0-preview.0</td>
</tr>
<tr>
<td>GitHub Copilot CLI</td>
<td>8 (2 new)</td>
<td>0</td>
<td>v1.0.81-7 (08-14, <strong>8 days without a release</strong>)</td>
</tr>
<tr>
<td>Kimi Code CLI</td>
<td>3 (0 new)</td>
<td>2</td>
<td>1.49.0 (07-16, <strong>37 days without a release</strong>)</td>
</tr>
<tr>
<td>OpenCode</td>
<td>62 (43 new)</td>
<td>38 (29 new)</td>
<td>v1.18.21 / v1.18.20 (08-21)</td>
</tr>
<tr>
<td>Qwen Code</td>
<td>10 (3 new)</td>
<td><strong>90 (27 new)</strong></td>
<td><strong>v0.22.0 (08-22)</strong>, v0.21.14-nightly.20260822</td>
</tr>
<tr>
<td>Claude Code Skills</td>
<td>3 (1 new)</td>
<td>8 (5 new)</td>
<td>—</td>
</tr>
</tbody></table>
<blockquote>
<p>How to read this table: Claude Code / Codex / Gemini issue counts hit the API&#39;s 100-per-page ceiling, and a large share are historical issues touched by label bots. That&#39;s why the &quot;newly opened&quot; column is broken out — <strong>it&#39;s the only honest measure of same-day activity.</strong> By that measure, Gemini CLI was nearly silent today (a single new issue titled just &quot;edge&quot;), while OpenCode&#39;s 43 new issues led the field.</p>
</blockquote>
<h2>3. Shared Themes</h2>
<ul>
<li><strong>Empty responses and mid-stream cutoffs are graduating from &quot;occasional bug&quot; to &quot;billing black hole.&quot;</strong> OpenCode opened #44148 today — &quot;empty completions (<code>finish_reason=other</code>) and mid-stream cutoffs on long-reasoning requests on the Go plan&quot; — joining existing #41469 (session silently stops on empty LLM response, <code>finish: unknown, 0 tokens</code>) and #32149 (stops processing without response) in one failure chain. Zeroclaw&#39;s PR #9447 (&quot;classify incomplete terminal responses&quot;) is the engineering answer to the same question. The demand is now explicit: <strong>failures must be attributable — you can&#39;t burn tokens and then report a &quot;clean stop.&quot;</strong></li>
<li><strong>Memory persistence is today&#39;s highest-consensus gap across tools.</strong> Kimi #1283 (&quot;Memory System — persistent context across sessions&quot;) is that repo&#39;s most-discussed thread at 40💬, echoed by Chinese-language issue #1478 (&quot;Can the memory layer be optimized? It&#39;s painful on large projects&quot;). Codex #18343 asks for tiered memory management (global / project / hybrid / per-thread). Claude Code #88862 is a high-quality field report: concurrent sessions sharing one git clone, with measured collisions and three userland mitigations. Different angles, same conclusion: <strong>memory and concurrency isolation remain unfinished foundations everywhere.</strong></li>
<li><strong>Windows is still the industry&#39;s shared technical debt.</strong> Claude Code #88818 (MSIX package won&#39;t launch after a spontaneous close, demands reinstall), #88864 (Qemu VM: arm64 fine, x86+KVM hangs forever at 100% CPU), #85891 (Win11 main window forced always-on-top). Codex #39209 (archiving fails with os error 2 when rollout paths use the <code>\\?\</code> prefix), #39170 (loses ChatGPT auth within 15–40s after enabling advanced features), #40075 (PowerShell/Git broken after update). Copilot CLI #4111 (long sessions keep executing stale code across in-place auto-update). The counter-example proves the point: OpenCode PR #44214 <strong>ships a native Windows ARM64 desktop agent (Electron 38)</strong> — treating Windows as a first-class citizen is the most concrete differentiator available right now.</li>
<li><strong>Skills security was breached head-on for the first time.</strong> <code>anthropics/skills</code> opened #1631 today: &quot;path traversal via unsanitized <code>skill_name</code> in <code>run_eval.py</code>.&quot; That&#39;s a real vulnerability, not a feature request. Read alongside PRs #1629 / #1630 (fixing three eval-harness defects that silently reported a 0.0 trigger rate), the signal is clear: <strong>the Skills ecosystem is moving from &quot;does it run?&quot; to &quot;can I trust the run?&quot; — and the correctness of the eval tooling itself is the first gate.</strong></li>
</ul>
<h2>4. Positioning</h2>
<ul>
<li><strong>Claude Code</strong>: v2.1.240 keeps the near-daily cadence — engineering velocity is fine, but <strong>reputational pressure is the heaviest in the field.</strong> #77136 (343👍) alleges degraded output voice; #87640 reports the Fable 5 <code>[reasoning_extraction]</code> safeguard false-positiving on a one-word greeting; #84352 (139💬) shows CVP-approved organizations still hitting safeguard blocks. Layer the HN effort-throttling speculation on top and the core tension has shifted from &quot;does it have the features?&quot; to <strong>&quot;are guardrails and cost-cutting quietly eroding the capability I paid for?&quot;</strong> That can only be answered with transparency, not patches.</li>
<li><strong>OpenAI Codex</strong>: Four alphas in one day — the most aggressive iterator here. The community&#39;s top ask remains cross-surface continuity: #5609 (sync conversation history between the ChatGPT website and Codex in VSCode, 66👍) and #27565 (Claude Code-like remote control, 15👍). The cost of that speed is same-day regressions like #40075, plus #37475 (0.147.0 rejects Amazon Bedrock input and corrupts subagent handoff) and #22844 (<code>@browser</code> unavailable over remote SSH). Positioning: <strong>OpenAI&#39;s unified all-surface entry point, trading stability for speed.</strong></li>
<li><strong>Gemini CLI</strong>: Nightlies keep rolling (v0.56.0-nightly.20260822), but the community side was essentially silent — the only new issue, #28964, has a one-word title. Existing pain sits at access and trust: #28912 (&quot;You do not have a valid license of this product,&quot; 18💬), #28341 (infinite auth loop), #22323 (subagent recovery after MAX_TURNS reported as GOAL success, hiding the interruption). <strong>#22323 is the most dangerous class of bug in the field today — failure reported as success poisons every downstream automated eval.</strong></li>
<li><strong>GitHub Copilot CLI</strong>: 8 days without a release and only 8 open issues, but the asks are tightly converged: #3709 (27👍) and #3282 (26👍) both want <strong>multiple BYOK / local provider models switchable within one session</strong>. Today&#39;s new #4566 (&quot;agent repeatedly acknowledges work without executing tool actions&quot;) is a textbook agent-credibility problem. Positioning remains <strong>the enterprise-managed entry point, with model freedom as its biggest user tension.</strong></li>
<li><strong>Kimi Code CLI</strong>: 37 days without a release, zero new issues today — the quietest in the field. The one meaningful signal: #1283 (40💬) proves that <strong>even in a low-activity repo, a memory system is the top user demand.</strong> Two PRs (#2594 preserving non-UTF-8 bytes in <code>StrReplaceFile</code> edits; #2614 documenting plugin security and persistent data) confirm maintainers are still present — just very slow.</li>
<li><strong>OpenCode</strong>: <strong>Led both new issues (43) and new PRs (29) — today&#39;s community activity champion.</strong> Existing high-vote threads #7101 (custom system prompts at global/project/custom-dir level, 127👍, closed) and #5121 (Windows winget install, 27👍) show a user base that cares deeply about customization. The new PR mix reads distinctly <em>engineering</em>: #44127 (eliminate redundant git subprocess spawns, spawn-free untracked stats), #44218 (drop events for unfollowed sessions before they allocate state), #44197 (sanitize clipboard text), #44219 (translate dotted Anthropic ids for the Cloudflare AI Gateway unified route). Worth flagging separately: #39845 (27👍 / 22💬) — &quot;DeepSeek V4 Flash suddenly requires &#39;Enable models hosted in China&#39;&quot; — a concrete case of <strong>geopolitical compliance directly interrupting a developer&#39;s daily workflow.</strong></li>
<li><strong>Qwen Code</strong>: <strong>The most industrialized PR pipeline in the field (90 active / 27 new), and shipped v0.22.0 GA today.</strong> High-discussion PRs cluster on provider breadth and cache efficiency: #8368 (add Kimi and Xiaomi MiMo providers, 72💬), #8332 (audio bridge for attachments, 70💬), #8276 (preserve prompt cache across deferred tool discovery, 64💬). Today&#39;s new PRs pivot toward reliability internals: #9705 (keep in-flight tool calls pending during live session replay), #9718 (gate skill announcements on what the model declared), #9745 (budget the repair pass, keep its timeouts out of the cap). The one red flag is issue #9733 — <strong>loop detection false-positives on legitimate verification cycles and kills unattended turns</strong> — fatal in automation contexts.</li>
<li><strong>Claude Code Skills</strong>: Today&#39;s theme is <strong>security and eval self-cleaning.</strong> #1631 (path traversal, new), #1252 (<code>product-self-knowledge</code> falls through to open web search when the docs URL fetch fails — <strong>a silent fallback means an uncontrolled data source</strong>), #1559 + PRs #1629 / #1630 (the eval harness misreported a 0% trigger rate for working descriptions; <code>--scan-full-turn</code> now measures whether a skill fires at all). In short: <strong>Skills is filling in the &quot;verifiable&quot; gap.</strong></li>
</ul>
<h2>5. Trend Signals</h2>
<ul>
<li><strong>Trust is becoming a harder moat than features.</strong> The three most expensive signals today — Claude&#39;s degraded voice (343👍), the HN effort-throttling A/B speculation (51👍), Gemini&#39;s failure-reported-as-success (#22323) — are none of them &quot;a missing feature.&quot; They&#39;re all &quot;I can&#39;t confirm it&#39;s working the way I think it is.&quot; <strong>Whoever first exposes effort level, guardrail triggers, and failure causes as an observable surface gains an asymmetric advantage.</strong></li>
<li><strong>Aggressive iteration plus same-day regressions is now the norm, and users are starting to treat regression rate as a selection criterion.</strong> Codex&#39;s four alphas in a day came with #40075 breaking core commands; OpenCode&#39;s 29 new PRs came alongside 43 new issues. <strong>Speed no longer automatically means leadership — regression rate is the real measure of iteration quality.</strong></li>
<li><strong>Compliance and geopolitics are sinking down to the CLI layer.</strong> OpenCode #39845 (DeepSeek V4 Flash requiring an explicit &quot;China-hosted models&quot; toggle) shows model availability is no longer purely technical. The real value of multi-provider abstraction (Qwen #8368, Zeroclaw&#39;s Hailo-Ollama support) is shifting from &quot;price/performance choice&quot; to <strong>&quot;compliance fallback.&quot;</strong></li>
<li><strong>Skills has passed &quot;usable&quot; and is entering &quot;auditable.&quot;</strong> On the same day, GitHub Trending surfaced three Skills-related projects (mattpocock/skills, obra/superpowers, andrej-karpathy-skills) while <code>anthropics/skills</code> was internally patching path traversal and eval false-negatives. <strong>Ecosystem hype and security maturity are visibly out of phase — and that gap is the window where future incidents happen.</strong></li>
</ul>
<hr>
<h2>Per-Tool Details</h2>
<h3>Claude Code (<a href="https://github.com/anthropics/claude-code">anthropics/claude-code</a>)</h3>
<p><strong>Releases</strong>: <a href="https://github.com/anthropics/claude-code/releases/tag/v2.1.240">v2.1.240</a> (08-22), <a href="https://github.com/anthropics/claude-code/releases/tag/v2.1.239">v2.1.239</a> (08-21), v2.1.238 / v2.1.237 (08-20) — near-daily cadence maintained.</p>
<p><strong>High-heat existing issues</strong></p>
<table>
<thead>
<tr>
<th>Issue</th>
<th>Heat</th>
<th>Notes</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/anthropics/claude-code/issues/77136">#77136</a></td>
<td>343👍 / 60💬</td>
<td>Claude 4.7 / 4.8 / 5.0 and Fable increasingly default to repetitive rhetorical tics — the repo&#39;s all-time top-voted issue; a systemic output-quality complaint</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/32479">#32479</a></td>
<td>140👍 / 90💬</td>
<td>GitHub Connector connected in Claude Desktop but not recognized by Claude</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/84352">#84352</a></td>
<td>22👍 / 139💬</td>
<td>CVP-approved organizations still receive cyber safeguard blocks — guardrails misfiring on enterprise customers</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/6305">#6305</a></td>
<td>16👍 / 40💬</td>
<td>Post/PreToolUse hooks not executing</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/64630">#64630</a></td>
<td>25👍 / 17💬</td>
<td>macOS login doesn&#39;t use the system default browser</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/42700">#42700</a></td>
<td>24👍 / 17💬</td>
<td>TTS readback + voice mode for remote control sessions</td>
</tr>
<tr>
<td><a href="https://github.com/anthropics/claude-code/issues/87640">#87640</a></td>
<td>13👍 / 8💬</td>
<td>Fable 5&#39;s <code>[reasoning_extraction]</code> safeguard false-positives on a one-word greeting</td>
</tr>
</tbody></table>
<p><strong>Newly opened today (41 total; highlights)</strong></p>
<ul>
<li><a href="https://github.com/anthropics/claude-code/issues/88862">#88862</a> — Field report: concurrent sessions sharing one git clone, with measured collisions and three userland mitigations. <strong>The highest-quality user submission today; points straight at missing concurrency isolation.</strong></li>
<li><a href="https://github.com/anthropics/claude-code/issues/88818">#88818</a> — Windows MSIX package fails to launch after a spontaneous close, demanding a reinstall.</li>
<li><a href="https://github.com/anthropics/claude-code/issues/88865">#88865</a> — Fabricated tool-call / tool-result blocks injected into the conversation (VSCode extension). <strong>Forged tool records destroy session trustworthiness outright.</strong></li>
<li><a href="https://github.com/anthropics/claude-code/issues/88864">#88864</a> — Qemu VM: arm64 OK, x86+KVM hangs forever at 100% CPU, plain x86 crashes.</li>
<li><a href="https://github.com/anthropics/claude-code/issues/88860">#88860</a> — Mobile GUI effort slider doesn&#39;t reflect the session&#39;s actual effort level on open. <strong>Combined with the HN throttling speculation, effort visibility is becoming a sensitive topic.</strong></li>
<li><a href="https://github.com/anthropics/claude-code/issues/88847">#88847</a> — Cowork and Chrome integration issues.</li>
</ul>
<h3>OpenAI Codex (<a href="https://github.com/openai/codex">openai/codex</a>)</h3>
<p><strong>Releases</strong> (four prereleases on 08-21): <a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.6">rust-v0.150.0-alpha.6</a>, <a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.5">alpha.5</a>, <a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.3">alpha.3</a>, <a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.2">alpha.2</a>, plus rust-v0.149.0-alpha.7.1.</p>
<p><strong>High-heat existing issues</strong></p>
<table>
<thead>
<tr>
<th>Issue</th>
<th>Heat</th>
<th>Notes</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/openai/codex/issues/5609">#5609</a></td>
<td>66👍 / 8💬</td>
<td>Sync conversation history between the ChatGPT website and Codex in VSCode — top ask; fundamentally about cross-surface continuity</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/22844">#22844</a></td>
<td>25👍 / 4💬</td>
<td>Remote SSH: in-app browser sidebar works but <code>@browser</code> is unavailable</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/39162">#39162</a></td>
<td>24👍 / 36💬</td>
<td>macOS: opening an existing conversation invalidates ChatGPT auth and redirects</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/37475">#37475</a></td>
<td>22👍 / 7💬</td>
<td>CLI 0.147.0 rejects Amazon Bedrock input and corrupts subagent handoff</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/21128">#21128</a></td>
<td>21👍 / 38💬</td>
<td>Desktop silently hides project conversations outside the global recent-50 window</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/39170">#39170</a></td>
<td>14👍 / 13💬</td>
<td>Windows desktop loses ChatGPT auth within 15–40s after enabling advanced features</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/18343">#18343</a></td>
<td>11👍 / 11💬</td>
<td>Scoped memory management (global, project, hybrid, per-thread)</td>
</tr>
<tr>
<td><a href="https://github.com/openai/codex/issues/20864">#20864</a></td>
<td>6👍 / 23💬</td>
<td>Desktop becomes laggy — scans all <code>~/.codex/sessions</code> rollout files</td>
</tr>
</tbody></table>
<p><strong>Newly opened today (40 total; highlights)</strong></p>
<ul>
<li><a href="https://github.com/openai/codex/issues/40075">#40075</a> — <strong>Regression after the Aug 21 update: Shell Helper, PowerShell and Git commands no longer execute. The most severe same-day regression in the field today.</strong></li>
<li><a href="https://github.com/openai/codex/issues/40116">#40116</a> — App Server: enforce restricted readable roots for <code>workspaceWrite</code> turns (sandbox tightening).</li>
<li><a href="https://github.com/openai/codex/issues/40112">#40112</a> — Desktop: a completed thread shows stale pre-crash state after restart while the rollout &amp; state DB have advanced.</li>
<li><a href="https://github.com/openai/codex/issues/40136">#40136</a> — Chat line history truncated to 3–4 messages, rendering unescaped HTML entities (e.g. <code>&amp;#x20;</code>).</li>
<li><a href="https://github.com/openai/codex/issues/40052">#40052</a> — Android: Voice Mode hides connected app tools; switching to text exposes them in the same chat.</li>
</ul>
<h3>Gemini CLI (<a href="https://github.com/google-gemini/gemini-cli">google-gemini/gemini-cli</a>)</h3>
<p><strong>Releases</strong>: <a href="https://github.com/google-gemini/gemini-cli/releases/tag/v0.56.0-nightly.20260822.g5411f113c">v0.56.0-nightly.20260822</a>, v0.56.0-nightly.20260821, <a href="https://github.com/google-gemini/gemini-cli/releases/tag/v0.57.0-preview.0">v0.57.0-preview.0</a> (08-19), v0.56.0 GA (08-19).</p>
<p><strong>The community side was nearly silent today — the only new issue, <a href="https://github.com/google-gemini/gemini-cli/issues/28964">#28964</a>, has a one-word title: &quot;edge.&quot;</strong> Existing pain concentrates on access and agent trustworthiness:</p>
<ul>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/28912">#28912</a> (6👍 / 18💬) — &quot;You do not have a valid license of this product&quot; — blocked at step one.</li>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/28341">#28341</a> (9👍 / 7💬) — Infinite auth loop.</li>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/21409">#21409</a> (8👍 / 8💬) — Generalist agent hangs.</li>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/22323">#22323</a> (2👍 / 13💬) — <strong>Subagent recovery after MAX_TURNS reported as GOAL success, hiding the interruption. Failure disguised as success is the #1 contaminant of automated evaluation.</strong></li>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/26522">#26522</a> — Auto memory retries low-signal sessions indefinitely.</li>
<li><a href="https://github.com/google-gemini/gemini-cli/issues/21968">#21968</a> — Gemini doesn&#39;t use skills and sub-agents enough.</li>
</ul>
<h3>GitHub Copilot CLI (<a href="https://github.com/github/copilot-cli">github/copilot-cli</a>)</h3>
<p><strong>Releases</strong>: v1.0.81-7 (08-14) is the latest — <strong>8 days without a release.</strong></p>
<ul>
<li><a href="https://github.com/github/copilot-cli/issues/3709">#3709</a> (27👍 / 5💬) and <a href="https://github.com/github/copilot-cli/issues/3282">#3282</a> (26👍 / 9💬) — The two top-voted asks want the same thing: <strong>switching among multiple BYOK / local provider models within a single session.</strong></li>
<li><a href="https://github.com/github/copilot-cli/issues/2306">#2306</a> (3👍 / 7💬) — &quot;You are not authorized to use this Copilot feature; it requires an enterprise or organization plan.&quot;</li>
<li><a href="https://github.com/github/copilot-cli/issues/4370">#4370</a> — 1.0.79-1 fails MCP initialization when <code>server/discover</code> returns <code>-32602</code>.</li>
<li><a href="https://github.com/github/copilot-cli/issues/4111">#4111</a> — Windows: sessions left open across an in-place auto-update keep executing stale code.</li>
<li><strong>New today</strong>: <a href="https://github.com/github/copilot-cli/issues/4566">#4566</a> — &quot;Agent repeatedly acknowledges work without executing tool actions,&quot; a textbook &quot;pretending to work&quot; credibility problem; <a href="https://github.com/github/copilot-cli/issues/4565">#4565</a> — repo app-configuration problems flagged.</li>
</ul>
<h3>Kimi Code CLI (<a href="https://github.com/MoonshotAI/kimi-cli">MoonshotAI/kimi-cli</a>)</h3>
<p><strong>Releases</strong>: 1.49.0 (07-16) is the latest — <strong>37 days without a release.</strong> Zero new issues today; the quietest repo in the field.</p>
<ul>
<li><a href="https://github.com/MoonshotAI/kimi-cli/issues/1283">#1283</a> (40💬) — <strong>Memory System: persistent context across sessions. The repo&#39;s most-discussed thread, confirming memory as the cross-tool consensus gap.</strong></li>
<li><a href="https://github.com/MoonshotAI/kimi-cli/issues/1478">#1478</a> — Chinese-language issue: &quot;Can the memory layer be optimized? I don&#39;t even see anything memory-related in the reference docs. It&#39;s painful on large projects.&quot; Same root as #1283.</li>
<li>PR <a href="https://github.com/MoonshotAI/kimi-cli/pull/2594">#2594</a> (merged) — Preserve non-UTF-8 bytes in <code>StrReplaceFile</code> edits.</li>
<li>PR <a href="https://github.com/MoonshotAI/kimi-cli/pull/2614">#2614</a> — Document plugin security and persistent data.</li>
</ul>
<h3>OpenCode (<a href="https://github.com/anomalyco/opencode">anomalyco/opencode</a>)</h3>
<p><strong>Releases</strong>: <a href="https://github.com/anomalyco/opencode/releases/tag/v1.18.21">v1.18.21</a> / <a href="https://github.com/anomalyco/opencode/releases/tag/v1.18.20">v1.18.20</a> (08-21), v1.18.19 (08-20).</p>
<p><strong>43 new issues + 29 new PRs today — first place on both counts.</strong></p>
<p><strong>High-heat issues</strong></p>
<table>
<thead>
<tr>
<th>Issue</th>
<th>Heat</th>
<th>Notes</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/anomalyco/opencode/issues/7101">#7101</a></td>
<td>127👍 / 35💬 (closed)</td>
<td>Allow custom system prompts in global / project / custom directories</td>
</tr>
<tr>
<td><a href="https://github.com/anomalyco/opencode/issues/39845">#39845</a></td>
<td>27👍 / 22💬</td>
<td><strong>DeepSeek V4 Flash suddenly requires &quot;Enable models hosted in China&quot; for the OpenCode Go subscription — geopolitical compliance directly disrupting daily workflow</strong></td>
</tr>
<tr>
<td><a href="https://github.com/anomalyco/opencode/issues/5121">#5121</a></td>
<td>27👍 / 18💬 (closed)</td>
<td>Winget installation option for Windows</td>
</tr>
<tr>
<td><a href="https://github.com/anomalyco/opencode/issues/34644">#34644</a></td>
<td>16👍 / 2💬</td>
<td>Copilot provider not registered for the Copilot Student plan (Auto-only mode)</td>
</tr>
<tr>
<td><a href="https://github.com/anomalyco/opencode/issues/16349">#16349</a></td>
<td>14👍 / 7💬</td>
<td>Option to swap left/right panel layout</td>
</tr>
<tr>
<td><a href="https://github.com/anomalyco/opencode/issues/41469">#41469</a></td>
<td>1👍 / 13💬</td>
<td>Session silently stops on empty LLM response (<code>finish: unknown, 0 tokens</code>)</td>
</tr>
</tbody></table>
<p><strong>Newly opened today</strong></p>
<ul>
<li><a href="https://github.com/anomalyco/opencode/issues/44148">#44148</a> — <strong>Empty completions (<code>finish_reason=other</code>) and mid-stream cutoffs on long-reasoning requests on the Go plan. Forms one &quot;silent failure&quot; chain with #41469 / #32149.</strong></li>
<li><a href="https://github.com/anomalyco/opencode/issues/44142">#44142</a> — Tool execution aborted when dispatching a shell command to a sub-agent; task aborts.</li>
<li><a href="https://github.com/anomalyco/opencode/issues/44151">#44151</a> — Request for a worktree setup script.</li>
<li>PR <a href="https://github.com/anomalyco/opencode/pull/44214">#44214</a> — <strong>Adds a native Windows ARM64 desktop agent (Electron 38). Treating Windows as first-class is the most concrete differentiator available.</strong></li>
<li>PR <a href="https://github.com/anomalyco/opencode/pull/44127">#44127</a> — Eliminate redundant git subprocess spawns; spawn-free untracked stats (perf).</li>
<li>PR <a href="https://github.com/anomalyco/opencode/pull/44219">#44219</a> — Translate dotted Anthropic ids for the Cloudflare AI Gateway unified route.</li>
<li>PR <a href="https://github.com/anomalyco/opencode/pull/44218">#44218</a> — Drop events for unfollowed sessions before they allocate state (memory hygiene).</li>
<li>PR <a href="https://github.com/anomalyco/opencode/pull/44197">#44197</a> — Sanitize clipboard text.</li>
</ul>
<h3>Qwen Code (<a href="https://github.com/QwenLM/qwen-code">QwenLM/qwen-code</a>)</h3>
<p><strong>Releases</strong>: <strong><a href="https://github.com/QwenLM/qwen-code/releases/tag/v0.22.0">v0.22.0</a> GA (08-22)</strong>, v0.21.14-nightly.20260822, v0.21.15 (08-20).</p>
<p><strong>The most industrialized PR pipeline in the field: 90 active / 27 new.</strong></p>
<p><strong>High-discussion PRs (provider breadth &amp; cache efficiency)</strong></p>
<table>
<thead>
<tr>
<th>PR</th>
<th>Discussion</th>
<th>Content</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/QwenLM/qwen-code/pull/8368">#8368</a></td>
<td>72💬</td>
<td>Add Kimi and Xiaomi MiMo providers</td>
</tr>
<tr>
<td><a href="https://github.com/QwenLM/qwen-code/pull/8332">#8332</a></td>
<td>70💬</td>
<td>Audio bridge for attachments</td>
</tr>
<tr>
<td><a href="https://github.com/QwenLM/qwen-code/pull/8276">#8276</a></td>
<td>64💬</td>
<td>Preserve prompt cache across deferred tool discovery</td>
</tr>
<tr>
<td><a href="https://github.com/QwenLM/qwen-code/pull/8902">#8902</a></td>
<td>44💬</td>
<td>Derive bootstrap <code>--help</code> from shared option definitions</td>
</tr>
<tr>
<td><a href="https://github.com/QwenLM/qwen-code/pull/9228">#9228</a></td>
<td>39💬</td>
<td>Narrow serve-ab&#39;s self-hosted wipe to the A/B checkout dirs</td>
</tr>
</tbody></table>
<p><strong>Newly opened PRs (pivoting to reliability internals)</strong></p>
<ul>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9705">#9705</a> (14💬) — Keep in-flight tool calls pending during live session replay.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9709">#9709</a> (11💬) — Reject session titles that echo the prompt&#39;s own examples.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9718">#9718</a> — Gate skill announcements on what the model was declared.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9745">#9745</a> — Budget the repair pass and keep its timeouts out of the cap.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9737">#9737</a> — Enforce utils leaf-layer dependency direction (architecture-debt work).</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9729">#9729</a> — Backfill session PR bindings and refresh their merge state.</li>
</ul>
<p><strong>Issue to watch</strong>: <a href="https://github.com/QwenLM/qwen-code/issues/9733">#9733</a> — &quot;loop detection false-positives on verification cycles and kills unattended turns.&quot; <strong>Fatal in automation, and the same class as Gemini #22323: the detection mechanism itself is wrong.</strong></p>
<h3>Claude Code Skills (<a href="https://github.com/anthropics/skills">anthropics/skills</a>)</h3>
<p>Today&#39;s theme is <strong>security and eval self-cleaning</strong>:</p>
<ul>
<li><a href="https://github.com/anthropics/skills/issues/1631">#1631</a> (new today) — <strong>Path traversal via unsanitized <code>skill_name</code> in <code>run_eval.py</code>. A real vulnerability, not a feature request.</strong></li>
<li><a href="https://github.com/anthropics/skills/issues/1252">#1252</a> — <code>product-self-knowledge</code> skill falls through to open web search when the docs URL fetch fails. <strong>A silent fallback means an uncontrolled data source.</strong></li>
<li><a href="https://github.com/anthropics/skills/issues/1559">#1559</a> — <code>skill-creator</code>&#39;s <code>run_eval.py</code> reports a 0% trigger rate for descriptions that actually work.</li>
<li>PR <a href="https://github.com/anthropics/skills/pull/1629">#1629</a> — Fix three eval-harness defects that silently reported a 0.0 trigger rate.</li>
<li>PR <a href="https://github.com/anthropics/skills/pull/1630">#1630</a> — Add <code>--scan-full-turn</code> so evals measure whether a skill fires at all.</li>
<li>PR <a href="https://github.com/anthropics/skills/pull/1634">#1634</a> — Word-anchor the SKIP grep pattern to prevent false positives on &quot;coherent.&quot;</li>
<li>PR <a href="https://github.com/anthropics/skills/pull/1633">#1633</a> / <a href="https://github.com/anthropics/skills/pull/1632">#1632</a> — Rename the algorithmic-art skill; fix a README reference to a nonexistent folder.</li>
</ul>
<p>The key shift: <strong>the correctness of the eval tooling itself is being treated as a prerequisite problem for the first time.</strong></p>
<hr>
<p><em>This digest is generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. All content is fetched live from GitHub&#39;s public API and written by the executing agent — no external LLM was called.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Agents 生态日报 2026-08-23</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-agents</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-agents</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>OpenClaw 生态社区动态日报 2026-08-23 生成时间: 2026-08-23 02:30 (GMT+8) | 覆盖: OpenClaw + 12 个 peer 项目 本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。 OpenClaw NanoBot Zeroclaw PicoClaw NanoClaw NullClaw IronClaw LobsterAI TinyClaw CoPaw Moltis ZeptoClaw EasyClaw 跨生态对比 OpenClaw 跨生态对比分析报告（2026-08-23） 1. 生态全景 今日 OpenClaw 生态最清晰的信号是：安全治理已经从&amp;quot;加个开关&amp;quot;进化为&amp;quot;重构信任模型&amp;quot;。Zeroclaw 今日一次性推进了 #8289 安全史诗的三个阶段——#10248（canonical principals 与共享授权解析，stage 2）、#10259（RPC 上强制认证主体，native + peercred，stage...</description>
      <content:encoded><![CDATA[<h1>OpenClaw 生态社区动态日报 2026-08-23</h1>
<blockquote>
<p>生成时间: 2026-08-23 02:30 (GMT+8) | 覆盖: OpenClaw + 12 个 peer 项目
本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。</p>
</blockquote>
<ul>
<li><a href="https://github.com/openclaw/openclaw">OpenClaw</a></li>
<li><a href="https://github.com/HKUDS/nanobot">NanoBot</a></li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw">Zeroclaw</a></li>
<li><a href="https://github.com/sipeed/picoclaw">PicoClaw</a></li>
<li><a href="https://github.com/qwibitai/nanoclaw">NanoClaw</a></li>
<li><a href="https://github.com/nullclaw/nullclaw">NullClaw</a></li>
<li><a href="https://github.com/nearai/ironclaw">IronClaw</a></li>
<li><a href="https://github.com/netease-youdao/LobsterAI">LobsterAI</a></li>
<li><a href="https://github.com/TinyAGI/tinyclaw">TinyClaw</a></li>
<li><a href="https://github.com/agentscope-ai/CoPaw">CoPaw</a></li>
<li><a href="https://github.com/moltis-org/moltis">Moltis</a></li>
<li><a href="https://github.com/qhkm/zeptoclaw">ZeptoClaw</a></li>
<li><a href="https://github.com/gaoyangz77/easyclaw">EasyClaw</a></li>
</ul>
<hr>
<h2>跨生态对比</h2>
<h1>OpenClaw 跨生态对比分析报告（2026-08-23）</h1>
<h2>1. 生态全景</h2>
<p>今日 OpenClaw 生态最清晰的信号是：<strong>安全治理已经从&quot;加个开关&quot;进化为&quot;重构信任模型&quot;</strong>。Zeroclaw 今日一次性推进了 <code>#8289</code> 安全史诗的三个阶段——<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10248">#10248</a>（canonical principals 与共享授权解析，stage 2）、<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10259">#10259</a>（RPC 上强制认证主体，native + peercred，stage 3）、<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10255">#10255</a>（<code>oidc.&lt;alias&gt;</code> 令牌校验 provider，stage 5）。这不是零散补丁，而是<strong>把&quot;谁在调用&quot;做成一等公民</strong>的系统性改造。同一天里 Moltis 新开 <a href="https://github.com/moltis-org/moltis/issues/1230">#1230</a>（为修改型安全 hook 提供可选的 fail-closed 错误策略）、CoPaw 提交 <a href="https://github.com/agentscope-ai/CoPaw/pull/7214">#7214</a>（把 Access Policy 列为第五道安全层）——三个独立项目在同一天从三个角度收紧权限边界。</p>
<p>活跃度分布则延续了强烈的两极化。<strong>Zeroclaw（91 PR）与 OpenClaw 本体（54 PR / 46 issue）领跑</strong>，IronClaw（19 PR）、NanoClaw（16 PR）、NanoBot（11 PR）次之；而 <strong>NullClaw、TinyClaw、ZeptoClaw 三个项目连续多日 0 issue / 0 PR，已可判定为事实性停更</strong>（最新 release 分别为 2026-05-29、2026-03-26、2026-04-07）。EasyClaw 是个特例：issue 与 PR 均为 0，但在 08-21 至 08-22 两天内连发 v1.8.108 至 v1.8.112 共 5 个版本——<strong>纯发布流水线，无公开协作痕迹</strong>（且其 release 实际指向 <code>gaoyangz77/rivonclaw</code>，仓库已改名）。</p>
<h2>2. 各项目活跃度对比（近 24h）</h2>
<table>
<thead>
<tr>
<th>项目</th>
<th>活跃 Issues（新建）</th>
<th>PR（新建）</th>
<th>最新 Release</th>
<th>状态判断</th>
</tr>
</thead>
<tbody><tr>
<td><strong>OpenClaw</strong></td>
<td>46（3）</td>
<td>54（22）</td>
<td>v2026.8.1-beta.2（08-15）</td>
<td>主干高强度打磨</td>
</tr>
<tr>
<td><strong>Zeroclaw</strong></td>
<td>9（4）</td>
<td><strong>91（12）</strong></td>
<td>v0.8.4（08-02）</td>
<td>PR 量第一，安全史诗推进</td>
</tr>
<tr>
<td>IronClaw</td>
<td>9（5）</td>
<td>19（8）</td>
<td>ironclaw-v1.3.0（08-19）</td>
<td>CI/CD 与 onboarding 双线</td>
</tr>
<tr>
<td>NanoClaw</td>
<td>0（0）</td>
<td>16（7）</td>
<td>v2.2.0（08-13）</td>
<td>纯 PR 驱动，多 bot 接入</td>
</tr>
<tr>
<td>NanoBot</td>
<td>0（0）</td>
<td>11（6）</td>
<td>v0.3.0（07-25）</td>
<td>可观测性重构</td>
</tr>
<tr>
<td>PicoClaw</td>
<td>2（1）</td>
<td>6（0）</td>
<td>v0.3.1（06-30）</td>
<td>低速，MCP 稳定性修复中</td>
</tr>
<tr>
<td>LobsterAI</td>
<td>2（0）</td>
<td>6（0）</td>
<td>2026.8.18</td>
<td>中文用户驱动的功能补齐</td>
</tr>
<tr>
<td>CoPaw</td>
<td>5（2）</td>
<td>5（1）</td>
<td>v2.1.1-beta.1（08-20）</td>
<td>多模态限额与安全分层</td>
</tr>
<tr>
<td>Moltis</td>
<td>1（1）</td>
<td>2（2）</td>
<td>20260820.01（08-20）</td>
<td>小而稳，安全 hook 策略</td>
</tr>
<tr>
<td>EasyClaw</td>
<td>0（0）</td>
<td>0（0）</td>
<td><strong>v1.8.112（08-22）</strong></td>
<td>高频发布但零公开协作</td>
</tr>
<tr>
<td>NullClaw</td>
<td>0（0）</td>
<td>0（0）</td>
<td>v2026.5.29</td>
<td><strong>事实停更（~3 个月）</strong></td>
</tr>
<tr>
<td>TinyClaw</td>
<td>0（0）</td>
<td>0（0）</td>
<td>v0.0.20（03-26）</td>
<td><strong>事实停更（~5 个月）</strong></td>
</tr>
<tr>
<td>ZeptoClaw</td>
<td>0（0）</td>
<td>0（0）</td>
<td>v0.9.2（04-07）</td>
<td><strong>事实停更（~4.5 个月）</strong></td>
</tr>
</tbody></table>
<h2>3. OpenClaw 本体：性能与可信交付是今日双主线</h2>
<p>OpenClaw 今日 PR 讨论量最高的一条是 <a href="https://github.com/openclaw/openclaw/pull/123535">#123535</a>「避免会话目录刷新风暴」——<strong>153💬，是全生态讨论量第一</strong>。搭配 <a href="https://github.com/openclaw/openclaw/issues/127379">#127379</a>（<code>/models</code> 命令让 gateway 主线程 CPU 打满 100%+，因 <code>buildModelsProviderData</code> 反复重建）与 <a href="https://github.com/openclaw/openclaw/issues/72717">#72717</a>（为 <code>wiki_search</code> 引入 SQLite FTS 索引以提升合成查询性能），可以看出<strong>主干正在集中偿还&quot;重复重建&quot;这一类性能债</strong>。</p>
<p>第二条主线是<strong>消息投递的上下文正确性</strong>。今日新建 PR <a href="https://github.com/openclaw/openclaw/pull/127962">#127962</a>（为入站 turn 保留 gateway 上下文）、<a href="https://github.com/openclaw/openclaw/pull/127797">#127797</a>（统一同步消息 hook，8💬）、已合并的 <a href="https://github.com/openclaw/openclaw/pull/126424">#126424</a>（把会话投递限制在 agent 绑定范围内）、<a href="https://github.com/openclaw/openclaw/pull/124548">#124548</a>（为私聊 turn 持久化发送者身份）连成一条链：<strong>多渠道多 agent 场景下，&quot;这条消息属于谁、该由谁答&quot;必须可靠</strong>。今日新 issue <a href="https://github.com/openclaw/openclaw/issues/128003">#128003</a>（OpenAI 兼容 HTTP 会话下 subagent 完成通告从不触发，报&quot;In-process gateway di…&quot;）正是这条链上的缺口。</p>
<p>值得单独标注的是两条<strong>自我诊断失真</strong>问题：<a href="https://github.com/openclaw/openclaw/issues/87637">#87637</a>（<code>openclaw doctor</code> 报告记忆搜索已禁用，但 memory-core dreaming 实际在运行）与今日新 PR <a href="https://github.com/openclaw/openclaw/pull/127998">#127998</a>（Doctor 的权限修复建议里列出了已禁用的自动化）。<strong>诊断工具说的话和系统实际状态不一致，比没有诊断工具更危险</strong>——这与今日 CLI 侧 Gemini #22323「失败被报成成功」属于同一类元问题。</p>
<h2>4. Peer 项目差异化定位</h2>
<ul>
<li><strong>Zeroclaw</strong>：<strong>今日 PR 量第一（91 条活跃 / 12 条新建），且是全生态唯一在做&quot;体系化安全重构&quot;的项目。</strong> <code>#8289</code> 史诗的 stage 2/3/5 同日推进（canonical principals、RPC 认证主体、OIDC 令牌校验），配合 <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9574">#9574</a>（授权审批响应者）、<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9203">#9203</a>（认证 HTTP fan-in），构成完整的身份-授权链路。另一条主线是<strong>上下文与 token 会计</strong>：<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9535">#9535</a>（按模型窗口比例锚定上下文压缩，22💬）、<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9713">#9713</a>（在 history-trim 事件上暴露 token 会计，25💬）、<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9447">#9447</a>（分类不完整的终端响应，20💬）。<strong>#9447 与今日 CLI 侧 OpenCode 的空响应问题是同一命题的两端——一边报 bug，一边写解法。</strong> provider 侧最亮眼的是 <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9109">#9109</a>（原生 Hailo-Ollama 支持，44💬），指向本地/边缘推理。治理上 <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8692">#8692</a>（维护者 RFC 决策队列 Tracker，13💬）与 <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8396">#8396</a>（RFC：让 wire protocol 在 provider 构造与 onboarding 中成为一等公民，9💬）说明项目已进入需要显式治理流程的规模。</li>
<li><strong>IronClaw</strong>：今日呈现<strong>CI/CD 基建 + onboarding 体验双线并进</strong>。CI 侧一口气推了 T1–T4 四条 PR：<a href="https://github.com/nearai/ironclaw/pull/7821">#7821</a>（单一 setup-rust 复合动作，toolchain 固定、mold、集中构建 profile）、<a href="https://github.com/nearai/ironclaw/pull/7817">#7817</a>（nextest 测试流水线、全失败信号、PR 解除限流）、<a href="https://github.com/nearai/ironclaw/pull/7819">#7819</a>（PR/队列检查收敛，planner 漂移守卫）、<a href="https://github.com/nearai/ironclaw/pull/7809">#7809</a>（规范化 preflight：统一门禁列表、worktree 安全钩子、自打印 REPRO）——<strong>这是典型的&quot;团队规模到了，必须先修路&quot;信号</strong>。产品侧最高讨论是 <a href="https://github.com/nearai/ironclaw/pull/7650">#7650</a>（从运行时证据推导 run outcome，45💬）与 <a href="https://github.com/nearai/ironclaw/pull/7818">#7818</a>（subagent 后台模式：回执式派生、逐子投递、激活与自愈扫描）。onboarding 侧连开 4 条 issue（<a href="https://github.com/nearai/ironclaw/issues/7815">#7815</a> 打通 connect→suggest→thread 流程、<a href="https://github.com/nearai/ironclaw/issues/7812">#7812</a> 建议生成时尊重用户级工具权限并用只读工具、<a href="https://github.com/nearai/ironclaw/issues/7823">#7823</a> Notion 安装失败、<a href="https://github.com/nearai/ironclaw/issues/7822">#7822</a> Slack 配置失败）——<strong>集成成功率是它当前最真实的瓶颈</strong>。</li>
<li><strong>NanoClaw</strong>：0 issue / 16 PR，是全生态<strong>最&quot;纯 PR 驱动&quot;的项目</strong>。今日新 PR 高度集中在多 bot 与 provider 接入：<a href="https://github.com/qwibitai/nanoclaw/pull/3438">#3438</a>（配置向导在已有 bot 时提供&quot;再加一个 Telegram bot&quot;）、<a href="https://github.com/qwibitai/nanoclaw/pull/3437">#3437</a>（对应文档与 instance 感知配对）、<a href="https://github.com/qwibitai/nanoclaw/pull/3435">#3435</a>（把 adapter instance 贯穿配对/首个 agent 初始化/CLI 欢迎流）、<a href="https://github.com/qwibitai/nanoclaw/pull/3355">#3355</a> + <a href="https://github.com/qwibitai/nanoclaw/pull/3356">#3356</a>（新增 <code>/add-cursor</code> provider skill 与 Cursor Agent SDK payload）。工程侧 <a href="https://github.com/qwibitai/nanoclaw/pull/3442">#3442</a>（按 driver 隔离能力校验 runtimeTier 并据此选档）与 <a href="https://github.com/qwibitai/nanoclaw/pull/3443">#3443</a>（弃用 better-sqlite3 自建、改用其自带预编译产物）都是务实取舍。定位：<strong>多 IM 渠道 + 多 agent provider 的接入层</strong>。</li>
<li><strong>NanoBot</strong>（★47,283，peer 中 star 最高）：今日 11 条 PR 全部指向<strong>可观测性与会话生命周期</strong>：<a href="https://github.com/HKUDS/nanobot/pull/5486">#5486</a>（统一 turn 可观测性，已合）、<a href="https://github.com/HKUDS/nanobot/pull/5487">#5487</a>（WebUI 文件预览路径修复 + subagent 活动与生命周期回放）、<a href="https://github.com/HKUDS/nanobot/pull/5420">#5420</a>（用户可控的 turn 恢复）、<a href="https://github.com/HKUDS/nanobot/pull/5483">#5483</a>（防止已删除会话被延迟消息重建）、<a href="https://github.com/HKUDS/nanobot/pull/5471">#5471</a>（临时 run 不改动会话状态）。另有 <a href="https://github.com/HKUDS/nanobot/pull/5484">#5484</a>（标记那些 <code>isError=false</code> 却返回业务错误信封的 MCP 响应）——<strong>这类&quot;表面成功实则失败&quot;的识别，是今日跨生态反复出现的主题</strong>。<a href="https://github.com/HKUDS/nanobot/pull/5156">#5156</a>（从静默停滞的 Telegram 轮询中恢复，已合）同理。</li>
<li><strong>CoPaw</strong>：主线是<strong>多模态限额与安全分层</strong>。<a href="https://github.com/agentscope-ai/CoPaw/issues/7201">#7201</a>（按 provider 分别设置 <code>max_image_bytes</code> / <code>max_video_bytes</code> / <code>max_audio_bytes</code>）与 <a href="https://github.com/agentscope-ai/CoPaw/issues/7212">#7212</a>（内联像素尺寸超出 provider 限制的图片会导致请求崩溃）是一对因果——<strong>限额缺位直接变成崩溃</strong>。<a href="https://github.com/agentscope-ai/CoPaw/pull/7214">#7214</a> 把 Access Policy 写进 README 作为第五道安全层。中文用户体验反馈依然密集：<a href="https://github.com/agentscope-ai/CoPaw/issues/7196">#7196</a>（一直显示推理过程是严重视觉干扰，希望可设默认折叠）、<a href="https://github.com/agentscope-ai/CoPaw/issues/7213">#7213</a>（会话输出总有无意义空行）、<a href="https://github.com/agentscope-ai/CoPaw/issues/7043">#7043</a>（启动时自动 <code>chcp 65001</code> 切 UTF-8，已关闭）。运维侧 <a href="https://github.com/agentscope-ai/CoPaw/pull/7050">#7050</a>（按 cron job 覆盖模型选择器）与 <a href="https://github.com/agentscope-ai/CoPaw/pull/7190">#7190</a>（PyPI 运行时路径、docker-compose 一键 demo、环境继承）降低自托管门槛。</li>
<li><strong>PicoClaw</strong>：低速但有效。核心 bug <a href="https://github.com/sipeed/picoclaw/issues/3269">#3269</a>（MCP server 连接失败会导致 agent loop 挂起，进而拖死 PicoClaw 聊天，1👍/6💬）已有对应修复 PR <a href="https://github.com/sipeed/picoclaw/pull/3337">#3337</a>。今日新 issue <a href="https://github.com/sipeed/picoclaw/issues/3343">#3343</a>（失败 turn 之后工具反馈动画会无限编辑同一条 Telegram 消息）是同源的&quot;失败态收尾不干净&quot;。<a href="https://github.com/sipeed/picoclaw/pull/3222">#3222</a>（deltachat 实现重构，减少 200 行，16💬）体现其嵌入式取向的精简偏好。</li>
<li><strong>LobsterAI</strong>（网易有道）：完全由<strong>中文用户需求驱动</strong>且闭环极快——<a href="https://github.com/netease-youdao/LobsterAI/issues/1213">#1213</a>「为会话详情添加导出为 Markdown」提出后即由 <a href="https://github.com/netease-youdao/LobsterAI/pull/1214">#1214</a> 实现并合并。其余修复同样贴近日常：<a href="https://github.com/netease-youdao/LobsterAI/pull/1208">#1208</a>（新增手动重试按钮应对瞬时错误）、<a href="https://github.com/netease-youdao/LobsterAI/pull/1212">#1212</a>（自定义 provider 上限放宽到 20 个）、<a href="https://github.com/netease-youdao/LobsterAI/pull/1205">#1205</a>（会话重命名失败时给出 error toast）、<a href="https://github.com/netease-youdao/LobsterAI/issues/1206">#1206</a>（私有化部署的 kimi2.5 分析文档会重复处理，已关闭）。<strong>&quot;用户提—当天合&quot;的节奏是它最大的差异化。</strong></li>
<li><strong>Moltis</strong>：项目小但方向明确。今日全部 3 条均为新建：<a href="https://github.com/moltis-org/moltis/issues/1230">#1230</a>（为修改型安全 hook 提供可选 fail-closed 错误策略——<strong>hook 出错时默认放行还是拦截，是安全模型的根本选择</strong>）、<a href="https://github.com/moltis-org/moltis/pull/1229">#1229</a>（支持 Browserless v2 容器）、<a href="https://github.com/moltis-org/moltis/pull/1231">#1231</a>（服务重启后重新解析当前 MCP client）。后者与 OpenClaw <a href="https://github.com/openclaw/openclaw/issues/68187">#68187</a>（SSE 支撑的 MCP 会话在服务重启后仍陈旧、报 &quot;Session not found&quot;）<strong>是完全同一个 bug 在两个项目里的独立复现——MCP 重启语义是全生态公摊的坑</strong>。</li>
<li><strong>停更三项（NullClaw / TinyClaw / ZeptoClaw）</strong>：连续多日 0 issue / 0 PR，最新 release 距今 3–5 个月。<strong>建议在后续选型与追踪中降权。</strong></li>
<li><strong>EasyClaw</strong>：08-21 至 08-22 连发 5 个版本（v1.8.108 → v1.8.112），但 issue 与 PR 双零，且 release 指向 <code>gaoyangz77/rivonclaw</code>（仓库已改名）。<strong>高频发布 + 零公开协作，无法从公开信号判断其社区健康度。</strong></li>
</ul>
<h2>5. 值得关注的趋势信号</h2>
<ul>
<li><strong>&quot;表面成功、实则失败&quot;成为全生态第一大元问题。</strong> 今天至少有五处独立出现：OpenClaw #87637（doctor 误报记忆搜索已禁用）与 #128003（subagent 完成通告从不触发）、NanoBot #5484（<code>isError=false</code> 却携带业务错误信封）、Zeroclaw #9447（分类不完整的终端响应）、PicoClaw #3343（失败 turn 后动画无限编辑）。<strong>当 agent 开始无人值守长跑，&quot;失败必须响&quot;比&quot;失败别发生&quot;更关键</strong>——这也与今日 CLI 侧 Gemini #22323、Qwen #9733 完全同源。</li>
<li><strong>安全模型正在从&quot;功能开关&quot;升级为&quot;身份基础设施&quot;。</strong> Zeroclaw 的 canonical principals / RPC 认证 / OIDC 三阶段，Moltis 的 fail-closed hook 策略，CoPaw 的第五安全层，OpenClaw 的安装策略告警强制确认（<a href="https://github.com/openclaw/openclaw/pull/116489">#116489</a>，49💬，已合）——<strong>四个项目同日从四个层次收紧权限，说明&quot;agent 有真实执行权&quot;这件事的风险已被普遍认知。</strong></li>
<li><strong>MCP 的重启与会话语义是公摊技术债。</strong> Moltis #1231 与 OpenClaw #68187 独立复现同一 bug，PicoClaw #3269 的 MCP 连接失败会挂死整个 agent loop。<strong>MCP 生态缺少统一的&quot;连接失效—重建—幂等恢复&quot;规范，每个项目都在自己重新踩一遍。</strong></li>
<li><strong>性能债的形态高度一致：重复重建。</strong> OpenClaw #123535（会话目录刷新风暴，153💬）、#127379（<code>buildModelsProviderData</code> 反复重建打满 CPU）、#72717（<code>wiki_search</code> 缺 FTS 索引），与 CLI 侧 OpenCode #44127（冗余 git 子进程 spawn）、Codex #20864（全量扫描 sessions 目录）形态完全一致。<strong>agent 框架普遍在&quot;每次都重算&quot;的阶段，缓存与增量是下一轮明确的优化红利。</strong></li>
<li><strong>生态尾部正在自然淘汰。</strong> 13 个 peer 中已有 3 个事实停更、1 个仅有发布流水线，真正有持续协作信号的约 8 个。<strong>&quot;claw 系&quot;项目的爆发期已过，进入集中度提升阶段。</strong></li>
</ul>
<hr>
<h2>各项目动态明细</h2>
<h3>OpenClaw（<a href="https://github.com/openclaw/openclaw">openclaw/openclaw</a>）</h3>
<p><strong>最新 Release</strong>：<a href="https://github.com/openclaw/openclaw/releases/tag/v2026.8.1-beta.2">v2026.8.1-beta.2</a>（08-15）；正式版最新为 v2026.7.1-2（08-04）。</p>
<p><strong>高讨论 PR</strong></p>
<table>
<thead>
<tr>
<th>PR</th>
<th>讨论</th>
<th>内容</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/openclaw/openclaw/pull/123535">#123535</a></td>
<td><strong>153💬</strong></td>
<td>避免会话目录刷新风暴——全生态讨论量第一</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/116489">#116489</a></td>
<td>49💬（已合）</td>
<td>安装策略告警需强制确认</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/123975">#123975</a></td>
<td>45💬</td>
<td>typecheck 在 tsgo 卡死而非失败时会永久挂起</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/120900">#120900</a></td>
<td>44💬（已合）</td>
<td>UI 支持审阅安装策略告警</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/123189">#123189</a></td>
<td>28💬</td>
<td>在聊天启动投影中恢复嵌入式 channel run</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/126618">#126618</a></td>
<td>25💬</td>
<td>Tool Search 的 directory/tools 把原生 read/exec 包进 tool_call</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/117114">#117114</a></td>
<td>21💬</td>
<td>隔离 <code>pnpm link</code> 以免污染源码检出更新，并在自链接损坏时告警</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/126424">#126424</a></td>
<td>19💬（已合）</td>
<td>把会话投递限制在 agent 绑定范围内</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/118067">#118067</a></td>
<td>19💬</td>
<td>Discord 支持私有 provider 端点</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/124548">#124548</a></td>
<td>18💬</td>
<td>为私聊 turn 持久化发送者身份</td>
</tr>
</tbody></table>
<p><strong>关键 issue</strong></p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/127379">#127379</a> — <code>/models</code> 命令让 gateway 主线程 CPU 打满 100%+，因 <code>buildModelsProviderData</code> 反复重建。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/87637">#87637</a>（2👍 / 3💬）— <strong><code>openclaw doctor</code> 报告记忆搜索已禁用，但 memory-core dreaming 实际在运行——诊断失真。</strong></li>
<li><a href="https://github.com/openclaw/openclaw/issues/125570">#125570</a> — Skill Workshop 应用更新时会覆盖线上 skill 的描述，静默破坏其触发。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/124099">#124099</a> — 升级到 2026.8.1-beta.2 后出现 <code>SessionCanonicalKeyMigrationRequiredError</code> 循环，trigger-pending 行受影响。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/68187">#68187</a> — SSE 支撑的 MCP 会话在服务重启后仍陈旧，报 &quot;Session not found&quot;。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/72717">#72717</a> — 为 <code>wiki_search</code> 引入 SQLite FTS 索引以提升合成查询性能。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/88334">#88334</a> — Gateway 应在凭据轮换后立即刷新 auth epoch。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/45184">#45184</a> — 当消息 @ 的是另一账号的 bot 时应跳过派发。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/33102">#33102</a> — TUI 支持配置 <code>--deliver</code> 默认值。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/119254">#119254</a> — 设计 WhatsApp <code>poll_vote_received</code> 插件 hook。</li>
</ul>
<p><strong>今日新建（3 issue / 22 PR，摘其要）</strong></p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/128003">#128003</a> — OpenAI 兼容 HTTP 会话下 subagent 完成通告从不触发。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/128006">#128006</a> — ACPX 直连 agent 启动缺少持久化进程租约覆盖（无上游生命周期 hook）。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/128005">#128005</a> — Android <code>location.get</code> 在回退到实时定位时忽略 <code>maxAgeMs</code>。</li>
<li>PR <a href="https://github.com/openclaw/openclaw/pull/127797">#127797</a>（8💬）— 统一同步消息 hook。</li>
<li>PR <a href="https://github.com/openclaw/openclaw/pull/127998">#127998</a>（6💬）— <strong>Doctor 的权限修复建议里列出了已禁用的自动化（诊断准确性修复）。</strong></li>
<li>PR <a href="https://github.com/openclaw/openclaw/pull/127962">#127962</a>（6💬）— 为入站 turn 保留 gateway 上下文。</li>
<li>PR <a href="https://github.com/openclaw/openclaw/pull/128004">#128004</a>（已合）— 共享 schema 校验的 format scope（性能）。</li>
<li>PR <a href="https://github.com/openclaw/openclaw/pull/128001">#128001</a> — 把请求方的 abort 传播到 ACP spawn。</li>
</ul>
<h3>Zeroclaw（<a href="https://github.com/zeroclaw-labs/zeroclaw">zeroclaw-labs/zeroclaw</a>）</h3>
<p><strong>最新 Release</strong>：v0.8.4（08-02）。<strong>今日 PR 量全生态第一（91 活跃 / 12 新建）。</strong></p>
<p><strong><code>#8289</code> 安全史诗（今日同时推进三阶段）</strong></p>
<ul>
<li>PR <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10248">#10248</a> — canonical principals 与共享授权解析（stage 2）。</li>
<li>PR <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10259">#10259</a> — RPC 上强制认证主体，native + peercred（stage 3）。</li>
<li>PR <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10255">#10255</a> — <code>oidc.&lt;alias&gt;</code> 令牌校验 provider（stage 5）。</li>
</ul>
<p><strong>高讨论 PR</strong></p>
<table>
<thead>
<tr>
<th>PR</th>
<th>讨论</th>
<th>内容</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9109">#9109</a></td>
<td>44💬</td>
<td>原生 Hailo-Ollama 支持（边缘推理）</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9707">#9707</a></td>
<td>33💬</td>
<td>把裸 <code>vision_model_provider</code> 迁移为点号式别名引用</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9713">#9713</a></td>
<td>25💬</td>
<td>在 history-trim 事件上暴露 token 会计</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9535">#9535</a></td>
<td>22💬</td>
<td>按模型窗口比例锚定上下文压缩</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9447">#9447</a></td>
<td>20💬</td>
<td><strong>分类不完整的终端响应（与 CLI 侧空响应问题同源的解法）</strong></td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9772">#9772</a></td>
<td>20💬</td>
<td>Telegram 群聊共享会话的 <code>per_user_session</code> 开关</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9203">#9203</a></td>
<td>19💬</td>
<td>认证 HTTP fan-in</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9281">#9281</a></td>
<td>18💬</td>
<td><code>config set</code> 失败时回滚自动创建的 map 别名</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9574">#9574</a></td>
<td>17💬</td>
<td>授权审批响应者</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9291">#9291</a></td>
<td>17💬</td>
<td>检测已安装的 AppImage 并使用可用的桌面端下载 URL</td>
</tr>
</tbody></table>
<p><strong>治理与今日新建</strong></p>
<ul>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8692">#8692</a>（13💬）— 维护者 RFC 与设计 issue 决策队列 Tracker。</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8396">#8396</a>（9💬）— RFC：让 wire protocol 在 provider 构造与 onboarding 中成为一等公民。</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10141">#10141</a> — 「请让 sessions 变得可用」。</li>
<li>今日新 issue：<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10251">#10251</a>（17 个 telegram <code>listen_*</code> 测试依赖挂钟超时断言）、<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10257">#10257</a>（<code>cron update --command</code> 在 agent job 上写入未使用列）、<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10249">#10249</a>（重复 webhook 处理会把调用方可控的幂等键原样写进日志）、<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10261">#10261</a>。</li>
<li>今日新 PR：<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10256">#10256</a>（从日志中脱敏重复幂等键，对应 #10249）、<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10258">#10258</a>（把 command patch 映射到 agent job prompt）、<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10260">#10260</a>（断连时让 RPC 调用失败）。</li>
</ul>
<h3>IronClaw（<a href="https://github.com/nearai/ironclaw">nearai/ironclaw</a>）</h3>
<p><strong>最新 Release</strong>：<a href="https://github.com/nearai/ironclaw/releases/tag/ironclaw-v1.3.0">ironclaw-v1.3.0</a>（08-19），此前 rc.1 / rc.2（08-17 / 08-18）。</p>
<p><strong>产品侧高讨论 PR</strong></p>
<ul>
<li><a href="https://github.com/nearai/ironclaw/pull/7650">#7650</a>（45💬）— 从运行时证据推导 run outcome。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7818">#7818</a> — subagent 后台模式：回执式派生、逐子投递、激活与自愈扫描。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7516">#7516</a>（14💬）— 为 IronHub agent link 提供操作者界面。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7257">#7257</a>（11💬）— WebUI 设计系统的提案、计划与检查清单（Epic #7038）。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7816">#7816</a> — 在 OOBE 建议抽屉中加入刷新与连接入口。</li>
</ul>
<p><strong>CI 基建四连（T1–T4，均为今日新建）</strong></p>
<ul>
<li><a href="https://github.com/nearai/ironclaw/pull/7821">#7821</a> — 单一 setup-rust 复合动作：toolchain 固定、mold、集中构建 profile（T1）。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7817">#7817</a> — nextest 测试流水线、全失败信号、PR 解除限流（T2）。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7820">#7820</a> — scope-isolation 测试套件合并探针（T2 后续）。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7819">#7819</a> — PR / 队列检查收敛：planner 漂移守卫、PR 上跑 default-features clippy（T3）。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7809">#7809</a> — 规范化 preflight：统一门禁列表、worktree 安全钩子、自打印 REPRO（T4）。</li>
</ul>
<p><strong>onboarding / 集成 issue（今日新建 5 条）</strong></p>
<ul>
<li><a href="https://github.com/nearai/ironclaw/issues/7815">#7815</a> — onboarding 建议：打通 connect → suggest → thread 流程所需的累积净新增工作量。</li>
<li><a href="https://github.com/nearai/ironclaw/issues/7812">#7812</a> — onboarding 建议应尊重用户级工具权限，并使用只读工具访问生成。</li>
<li><a href="https://github.com/nearai/ironclaw/issues/7823">#7823</a> — Notion 安装在 IronClaw 中失败。</li>
<li><a href="https://github.com/nearai/ironclaw/issues/7822">#7822</a> — Slack 用户无法在 IronClaw 中完成 Slack 配置。</li>
<li><a href="https://github.com/nearai/ironclaw/issues/7813">#7813</a> — 建议面板出现时标题被裁切。</li>
</ul>
<h3>NanoClaw（<a href="https://github.com/qwibitai/nanoclaw">qwibitai/nanoclaw</a>）</h3>
<p><strong>最新 Release</strong>：v2.2.0（08-13）。0 issue / 16 PR，纯 PR 驱动。</p>
<ul>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3438">#3438</a> — 配置向导在已配置 bot 时提供「再加一个 Telegram bot」。</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3437">#3437</a> — add-another-bot 路径文档、instance 感知配对与接线。</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3435">#3435</a> — 把 adapter instance 贯穿配对、首个 agent 初始化与 CLI 欢迎流。</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3355">#3355</a> / <a href="https://github.com/qwibitai/nanoclaw/pull/3356">#3356</a> — 新增 <code>/add-cursor</code> provider skill；新增 Cursor Agent SDK payload。</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3434">#3434</a> — 轮询型 adapter 不再开启 webhook server。</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3446">#3446</a> — 在未知发送者门禁中自动丢弃自动化发送者。</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3442">#3442</a> — 按 driver 隔离能力校验 <code>runtimeTier</code> 并据此选档。</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3443">#3443</a> — 从 <code>onlyBuiltDependencies</code> 中移除 better-sqlite3，改用其自带预编译产物。</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3441">#3441</a> — <code>git show</code> 失败时保留文件。</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3431">#3431</a> — 配对卡片文案更正为 6 位数字。</li>
</ul>
<h3>NanoBot（<a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a>）★47,283</h3>
<p><strong>最新 Release</strong>：v0.3.0（07-25）。0 issue / 11 PR，主题为可观测性与会话生命周期。</p>
<ul>
<li><a href="https://github.com/HKUDS/nanobot/pull/5486">#5486</a>（已合）— 统一 turn 可观测性。</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5487">#5487</a> — WebUI 文件预览路径修复 + subagent 活动与生命周期回放。</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5420">#5420</a> — 新增用户可控的 turn 恢复。</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5484">#5484</a> — <strong>标记那些 <code>isError=false</code> 却返回业务错误信封的 MCP 响应。</strong></li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5483">#5483</a> — 防止已删除会话被延迟消息重新创建。</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5471">#5471</a> — 让临时（ephemeral）run 不改动会话状态。</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5485">#5485</a> — 为原生 provider 恢复 LangSmith 追踪。</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5156">#5156</a>（已合）— 从静默停滞的 Telegram 轮询中恢复。</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/3294">#3294</a>（已合）— dream 可选 kill switch + 自定义 Phase 1/2 模板路径。</li>
</ul>
<h3>CoPaw（<a href="https://github.com/agentscope-ai/CoPaw">agentscope-ai/CoPaw</a>）</h3>
<p><strong>最新 Release</strong>：v2.1.1-beta.1（08-20）；正式版 v2.1.0（08-13）。</p>
<ul>
<li><a href="https://github.com/agentscope-ai/CoPaw/issues/7196">#7196</a>（1👍 / 2💬）— 一直显示推理过程是严重的视觉干扰，希望可设默认是否折叠。</li>
<li><a href="https://github.com/agentscope-ai/CoPaw/issues/7201">#7201</a> — 按 provider 分别设置 <code>max_image_bytes</code> / <code>max_video_bytes</code> / <code>max_audio_bytes</code> 上限。</li>
<li><a href="https://github.com/agentscope-ai/CoPaw/issues/7212">#7212</a> — 内联像素尺寸超出 provider 限制的图片会导致请求崩溃（与 #7201 构成因果）。</li>
<li><a href="https://github.com/agentscope-ai/CoPaw/issues/7213">#7213</a> — 会话输出总是有无意义的空行。</li>
<li><a href="https://github.com/agentscope-ai/CoPaw/issues/7043">#7043</a>（已关闭）— 希望启动时自动执行 <code>chcp 65001</code> 切到 UTF-8 环境。</li>
<li>PR <a href="https://github.com/agentscope-ai/CoPaw/pull/7214">#7214</a> — README 中把 Access Policy 列为第五道安全层。</li>
<li>PR <a href="https://github.com/agentscope-ai/CoPaw/pull/7054">#7054</a> — Chrome 支持 LAN/网络浏览器的远程 bridge 端点。</li>
<li>PR <a href="https://github.com/agentscope-ai/CoPaw/pull/7050">#7050</a> — 按 cron job 提供模型覆盖选择器。</li>
<li>PR <a href="https://github.com/agentscope-ai/CoPaw/pull/7190">#7190</a> — qwenpaw-data 的 PyPI 运行时路径、docker-compose 一键 demo 与环境继承。</li>
<li>PR <a href="https://github.com/agentscope-ai/CoPaw/pull/6808">#6808</a> — Console 显示自定义 profile 的 markdown 文件。</li>
</ul>
<h3>PicoClaw（<a href="https://github.com/sipeed/picoclaw">sipeed/picoclaw</a>）</h3>
<p><strong>最新 Release</strong>：v0.3.1（06-30）、nightly（07-02）。</p>
<ul>
<li><a href="https://github.com/sipeed/picoclaw/issues/3269">#3269</a>（1👍 / 6💬）— <strong>MCP server 连接失败会导致 agent loop 挂起，进而拖死整个 PicoClaw 聊天。</strong> 对应修复 PR <a href="https://github.com/sipeed/picoclaw/pull/3337">#3337</a>。</li>
<li><a href="https://github.com/sipeed/picoclaw/issues/3343">#3343</a>（今日新建）— 失败 turn 之后，工具反馈动画会无限编辑同一条 Telegram 消息。</li>
<li>PR <a href="https://github.com/sipeed/picoclaw/pull/3222">#3222</a>（16💬）— deltachat 实现重构与文档整理，净减约 200 行。</li>
<li>PR <a href="https://github.com/sipeed/picoclaw/pull/3319">#3319</a>（已合）— 尊重 exec 超时与布尔型运行选项。</li>
</ul>
<h3>LobsterAI（<a href="https://github.com/netease-youdao/LobsterAI">netease-youdao/LobsterAI</a>）</h3>
<p><strong>最新 Release</strong>：2026.8.18（08-18）。中文用户需求驱动，提出到合并极快。</p>
<ul>
<li><a href="https://github.com/netease-youdao/LobsterAI/issues/1213">#1213</a>（已关闭）— 为会话详情添加「导出为 Markdown」功能 → 由 PR <a href="https://github.com/netease-youdao/LobsterAI/pull/1214">#1214</a> 实现并合并。</li>
<li><a href="https://github.com/netease-youdao/LobsterAI/issues/1206">#1206</a>（已关闭）— 私有化部署的 kimi2.5 模型分析文档会重复处理或重复回复进度。</li>
<li>PR <a href="https://github.com/netease-youdao/LobsterAI/pull/1208">#1208</a>（已合）— 新增手动重试按钮，支持频繁请求等瞬时错误快速重试。</li>
<li>PR <a href="https://github.com/netease-youdao/LobsterAI/pull/1212">#1212</a>（已合）— 自定义 provider 上限放宽至 20 个。</li>
<li>PR <a href="https://github.com/netease-youdao/LobsterAI/pull/1205">#1205</a>（已合）— 会话重命名失败时给出 error toast。</li>
<li>PR <a href="https://github.com/netease-youdao/LobsterAI/pull/1209">#1209</a>（已合）— 修复 web-search 阻断不受支持的 Chrome flags。</li>
<li>PR <a href="https://github.com/netease-youdao/LobsterAI/pull/2452">#2452</a> — 为带斜杠的 model id 保留 provider 信息。</li>
</ul>
<h3>Moltis（<a href="https://github.com/moltis-org/moltis">moltis-org/moltis</a>）</h3>
<p><strong>最新 Release</strong>：20260820.01（08-20）。今日 3 条全为新建。</p>
<ul>
<li><a href="https://github.com/moltis-org/moltis/issues/1230">#1230</a> — <strong>为修改型安全 hook 提供可选的 fail-closed 错误策略（hook 出错时默认拦截而非放行）。</strong></li>
<li>PR <a href="https://github.com/moltis-org/moltis/pull/1229">#1229</a>（1👍 / 3💬）— 支持 Browserless v2 容器。</li>
<li>PR <a href="https://github.com/moltis-org/moltis/pull/1231">#1231</a>（1👍 / 2💬）— <strong>服务重启后重新解析当前 MCP client（与 OpenClaw #68187 同一 bug 的独立复现）。</strong></li>
</ul>
<h3>低活跃 / 停更项目</h3>
<table>
<thead>
<tr>
<th>项目</th>
<th>最新 Release</th>
<th>停滞时长</th>
<th>今日活动</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/gaoyangz77/easyclaw">EasyClaw</a></td>
<td>v1.8.112（08-22）</td>
<td>—</td>
<td><strong>5 个版本连发但 0 issue / 0 PR</strong>；release 实际指向 <code>gaoyangz77/rivonclaw</code>（已改名）</td>
</tr>
<tr>
<td><a href="https://github.com/nullclaw/nullclaw">NullClaw</a></td>
<td>v2026.5.29</td>
<td>~3 个月</td>
<td>0 / 0</td>
</tr>
<tr>
<td><a href="https://github.com/qhkm/zeptoclaw">ZeptoClaw</a></td>
<td>v0.9.2（04-07）</td>
<td>~4.5 个月</td>
<td>0 / 0</td>
</tr>
<tr>
<td><a href="https://github.com/TinyAGI/tinyclaw">TinyClaw</a></td>
<td>v0.0.20（03-26）</td>
<td>~5 个月</td>
<td>0 / 0</td>
</tr>
</tbody></table>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，所有内容基于 GitHub 公开 API 实时抓取并由执行代理人工撰写，未调用任何外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Agents Ecosystem Digest 2026-08-23</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-agents-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-agents-en</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>OpenClaw Ecosystem Community Daily — 2026-08-23 Generated: 2026-08-23 02:30 (GMT+8) | Coverage: OpenClaw + 12 peer projects This digest is produced by the agents-radar local automation. All summaries, comparisons, and writing are done by the executing agent — no external LLM API was called. OpenClaw NanoBot Zeroclaw PicoClaw NanoClaw NullClaw IronClaw LobsterAI TinyClaw CoPaw Moltis ZeptoClaw EasyClaw Cross-Ecosystem Comparison OpenClaw Cross-Ecosystem Comparison Report (2026-08-23) 1. Ecosystem...</description>
      <content:encoded><![CDATA[<h1>OpenClaw Ecosystem Community Daily — 2026-08-23</h1>
<blockquote>
<p>Generated: 2026-08-23 02:30 (GMT+8) | Coverage: OpenClaw + 12 peer projects
This digest is produced by the agents-radar local automation. All summaries, comparisons, and writing are done by the executing agent — no external LLM API was called.</p>
</blockquote>
<ul>
<li><a href="https://github.com/openclaw/openclaw">OpenClaw</a></li>
<li><a href="https://github.com/HKUDS/nanobot">NanoBot</a></li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw">Zeroclaw</a></li>
<li><a href="https://github.com/sipeed/picoclaw">PicoClaw</a></li>
<li><a href="https://github.com/qwibitai/nanoclaw">NanoClaw</a></li>
<li><a href="https://github.com/nullclaw/nullclaw">NullClaw</a></li>
<li><a href="https://github.com/nearai/ironclaw">IronClaw</a></li>
<li><a href="https://github.com/netease-youdao/LobsterAI">LobsterAI</a></li>
<li><a href="https://github.com/TinyAGI/tinyclaw">TinyClaw</a></li>
<li><a href="https://github.com/agentscope-ai/CoPaw">CoPaw</a></li>
<li><a href="https://github.com/moltis-org/moltis">Moltis</a></li>
<li><a href="https://github.com/qhkm/zeptoclaw">ZeptoClaw</a></li>
<li><a href="https://github.com/gaoyangz77/easyclaw">EasyClaw</a></li>
</ul>
<hr>
<h2>Cross-Ecosystem Comparison</h2>
<h1>OpenClaw Cross-Ecosystem Comparison Report (2026-08-23)</h1>
<h2>1. Ecosystem Overview</h2>
<p>The clearest signal across the OpenClaw ecosystem today: <strong>security governance has graduated from &quot;add a toggle&quot; to &quot;rebuild the trust model.&quot;</strong> Zeroclaw pushed three stages of its <code>#8289</code> security epic in a single day — <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10248">#10248</a> (canonical principals and shared authorization resolution, stage 2), <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10259">#10259</a> (enforce authenticated principals over RPC, native + peercred, stage 3), and <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10255">#10255</a> (<code>oidc.&lt;alias&gt;</code> token validation provider, stage 5). These are not scattered patches but a systematic rework that makes <strong>&quot;who is calling&quot; a first-class citizen</strong>. On the same day Moltis opened <a href="https://github.com/moltis-org/moltis/issues/1230">#1230</a> (optional fail-closed error policy for mutating security hooks) and CoPaw landed <a href="https://github.com/agentscope-ai/CoPaw/pull/7214">#7214</a> (documenting Access Policy as a fifth security layer) — three independent projects tightening the permission boundary from three angles on the same day.</p>
<p>Activity distribution remains sharply bimodal. <strong>Zeroclaw (91 PRs) and OpenClaw core (54 PRs / 46 issues) lead</strong>, followed by IronClaw (19 PRs), NanoClaw (16 PRs), and NanoBot (11 PRs). Meanwhile <strong>NullClaw, TinyClaw, and ZeptoClaw have posted 0 issues / 0 PRs for multiple consecutive days and can be treated as de facto abandoned</strong> (latest releases dated 2026-05-29, 2026-03-26, and 2026-04-07 respectively). EasyClaw is a special case: zero issues and zero PRs, yet it shipped five versions (v1.8.108 → v1.8.112) across 08-21 and 08-22 — <strong>a pure release pipeline with no visible collaboration</strong>, and its releases actually point at <code>gaoyangz77/rivonclaw</code> (the repo has been renamed).</p>
<h2>2. Project Activity Comparison (last 24h)</h2>
<table>
<thead>
<tr>
<th>Project</th>
<th>Active Issues (new)</th>
<th>PRs (new)</th>
<th>Latest Release</th>
<th>Assessment</th>
</tr>
</thead>
<tbody><tr>
<td><strong>OpenClaw</strong></td>
<td>46 (3)</td>
<td>54 (22)</td>
<td>v2026.8.1-beta.2 (08-15)</td>
<td>High-intensity mainline polish</td>
</tr>
<tr>
<td><strong>Zeroclaw</strong></td>
<td>9 (4)</td>
<td><strong>91 (12)</strong></td>
<td>v0.8.4 (08-02)</td>
<td>#1 by PR volume, security epic advancing</td>
</tr>
<tr>
<td>IronClaw</td>
<td>9 (5)</td>
<td>19 (8)</td>
<td>ironclaw-v1.3.0 (08-19)</td>
<td>CI/CD plus onboarding, in parallel</td>
</tr>
<tr>
<td>NanoClaw</td>
<td>0 (0)</td>
<td>16 (7)</td>
<td>v2.2.0 (08-13)</td>
<td>Purely PR-driven, multi-bot wiring</td>
</tr>
<tr>
<td>NanoBot</td>
<td>0 (0)</td>
<td>11 (6)</td>
<td>v0.3.0 (07-25)</td>
<td>Observability rework</td>
</tr>
<tr>
<td>PicoClaw</td>
<td>2 (1)</td>
<td>6 (0)</td>
<td>v0.3.1 (06-30)</td>
<td>Slow cadence, fixing MCP stability</td>
</tr>
<tr>
<td>LobsterAI</td>
<td>2 (0)</td>
<td>6 (0)</td>
<td>2026.8.18</td>
<td>Chinese-user-driven feature fills</td>
</tr>
<tr>
<td>CoPaw</td>
<td>5 (2)</td>
<td>5 (1)</td>
<td>v2.1.1-beta.1 (08-20)</td>
<td>Multimodal limits + security layering</td>
</tr>
<tr>
<td>Moltis</td>
<td>1 (1)</td>
<td>2 (2)</td>
<td>20260820.01 (08-20)</td>
<td>Small but steady, security hook policy</td>
</tr>
<tr>
<td>EasyClaw</td>
<td>0 (0)</td>
<td>0 (0)</td>
<td><strong>v1.8.112 (08-22)</strong></td>
<td>Frequent releases, zero public collaboration</td>
</tr>
<tr>
<td>NullClaw</td>
<td>0 (0)</td>
<td>0 (0)</td>
<td>v2026.5.29</td>
<td><strong>De facto abandoned (~3 months)</strong></td>
</tr>
<tr>
<td>TinyClaw</td>
<td>0 (0)</td>
<td>0 (0)</td>
<td>v0.0.20 (03-26)</td>
<td><strong>De facto abandoned (~5 months)</strong></td>
</tr>
<tr>
<td>ZeptoClaw</td>
<td>0 (0)</td>
<td>0 (0)</td>
<td>v0.9.2 (04-07)</td>
<td><strong>De facto abandoned (~4.5 months)</strong></td>
</tr>
</tbody></table>
<h2>3. OpenClaw Core: Performance and Trustworthy Delivery Are Today&#39;s Two Threads</h2>
<p>The most-discussed OpenClaw PR today is <a href="https://github.com/openclaw/openclaw/pull/123535">#123535</a> &quot;avoid session directory refresh storms&quot; — <strong>153💬, the highest discussion count in the entire ecosystem</strong>. Pair it with <a href="https://github.com/openclaw/openclaw/issues/127379">#127379</a> (the <code>/models</code> command pins the gateway main thread at 100%+ CPU because <code>buildModelsProviderData</code> is rebuilt repeatedly) and <a href="https://github.com/openclaw/openclaw/issues/72717">#72717</a> (introduce a SQLite FTS index for <code>wiki_search</code> to speed up synthetic queries), and the pattern is obvious: <strong>the mainline is paying down a specific class of performance debt — redundant rebuilds.</strong></p>
<p>The second thread is <strong>contextual correctness of message delivery</strong>. Today&#39;s new PRs <a href="https://github.com/openclaw/openclaw/pull/127962">#127962</a> (preserve gateway context for inbound turns) and <a href="https://github.com/openclaw/openclaw/pull/127797">#127797</a> (unify synchronous message hooks, 8💬), plus the already-merged <a href="https://github.com/openclaw/openclaw/pull/126424">#126424</a> (scope session delivery to agent bindings) and <a href="https://github.com/openclaw/openclaw/pull/124548">#124548</a> (persist sender identity for DM turns), form a single chain: <strong>in multi-channel, multi-agent setups, &quot;who does this message belong to and who should answer it&quot; must be reliable.</strong> Today&#39;s new issue <a href="https://github.com/openclaw/openclaw/issues/128003">#128003</a> (subagent completion announcements never fire on OpenAI-compatible HTTP sessions, reporting &quot;In-process gateway di…&quot;) is the gap in that chain.</p>
<p>Two <strong>self-diagnosis distortion</strong> problems deserve separate mention: <a href="https://github.com/openclaw/openclaw/issues/87637">#87637</a> (<code>openclaw doctor</code> reports memory search as disabled while memory-core dreaming is actually running) and today&#39;s new PR <a href="https://github.com/openclaw/openclaw/pull/127998">#127998</a> (Doctor&#39;s permission-fix suggestions list already-disabled automations). <strong>A diagnostic tool whose story disagrees with system reality is more dangerous than having no diagnostics at all</strong> — the same meta-problem as Gemini #22323 (&quot;failure reported as success&quot;) on the CLI side today.</p>
<h2>4. Peer Project Differentiation</h2>
<ul>
<li><strong>Zeroclaw</strong>: <strong>#1 by PR volume today (91 active / 12 new) and the only project in the ecosystem doing systematic security rework.</strong> Stages 2/3/5 of the <code>#8289</code> epic all advanced the same day (canonical principals, RPC authenticated principals, OIDC token validation), together with <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9574">#9574</a> (authorization approval responder) and <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9203">#9203</a> (authenticated HTTP fan-in), forming a complete identity-to-authorization path. The second thread is <strong>context and token accounting</strong>: <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9535">#9535</a> (anchor context compaction to a ratio of the model window, 22💬), <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9713">#9713</a> (expose token accounting on history-trim events, 25💬), and <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9447">#9447</a> (classify incomplete terminal responses, 20💬). <strong>#9447 and today&#39;s empty-response complaint on the OpenCode CLI side are two ends of the same problem — one files the bug, the other writes the fix.</strong> The standout provider work is <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9109">#9109</a> (native Hailo-Ollama support, 44💬), pointing at local/edge inference. On governance, <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8692">#8692</a> (maintainer RFC decision-queue tracker, 13💬) and <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8396">#8396</a> (RFC: make the wire protocol a first-class concept in provider construction and onboarding, 9💬) show the project has reached a scale that needs explicit process.</li>
<li><strong>IronClaw</strong>: today shows <strong>CI/CD infrastructure and onboarding experience advancing in parallel.</strong> On CI it landed four PRs, T1–T4: <a href="https://github.com/nearai/ironclaw/pull/7821">#7821</a> (single setup-rust composite action: pinned toolchain, mold, centralized build profiles), <a href="https://github.com/nearai/ironclaw/pull/7817">#7817</a> (nextest test pipeline, full failure signal, unthrottled on PRs), <a href="https://github.com/nearai/ironclaw/pull/7819">#7819</a> (converge PR/queue checks, planner drift guard, default-features clippy on PRs), and <a href="https://github.com/nearai/ironclaw/pull/7809">#7809</a> (normalize preflight: unified gate list, worktree safety hooks, self-printing REPRO) — <strong>the classic &quot;the team got big enough that we must pave the road first&quot; signal.</strong> On product, the highest-discussion items are <a href="https://github.com/nearai/ironclaw/pull/7650">#7650</a> (derive run outcome from runtime evidence, 45💬) and <a href="https://github.com/nearai/ironclaw/pull/7818">#7818</a> (subagent background mode: receipt-based spawn, per-child delivery, activation and self-healing sweeps). On onboarding it opened four issues in a row (<a href="https://github.com/nearai/ironclaw/issues/7815">#7815</a> close the connect→suggest→thread loop, <a href="https://github.com/nearai/ironclaw/issues/7812">#7812</a> suggestion generation should respect user-level tool permissions and use read-only tools, <a href="https://github.com/nearai/ironclaw/issues/7823">#7823</a> Notion install fails, <a href="https://github.com/nearai/ironclaw/issues/7822">#7822</a> Slack configuration fails) — <strong>integration success rate is its most honest current bottleneck.</strong></li>
<li><strong>NanoClaw</strong>: 0 issues / 16 PRs, the <strong>most purely PR-driven project</strong> in the ecosystem. Today&#39;s new PRs cluster tightly around multi-bot and provider wiring: <a href="https://github.com/qwibitai/nanoclaw/pull/3438">#3438</a> (config wizard offers &quot;add another Telegram bot&quot; when one already exists), <a href="https://github.com/qwibitai/nanoclaw/pull/3437">#3437</a> (matching docs plus instance-aware pairing), <a href="https://github.com/qwibitai/nanoclaw/pull/3435">#3435</a> (thread adapter instance through pairing, first-agent init, and the CLI welcome flow), and <a href="https://github.com/qwibitai/nanoclaw/pull/3355">#3355</a> + <a href="https://github.com/qwibitai/nanoclaw/pull/3356">#3356</a> (add an <code>/add-cursor</code> provider skill and a Cursor Agent SDK payload). On the engineering side, <a href="https://github.com/qwibitai/nanoclaw/pull/3442">#3442</a> (validate <code>runtimeTier</code> via driver-isolated capability checks and pick a tier accordingly) and <a href="https://github.com/qwibitai/nanoclaw/pull/3443">#3443</a> (drop better-sqlite3 from <code>onlyBuiltDependencies</code> and use its bundled prebuilds) are pragmatic trade-offs. Positioning: <strong>the integration layer for many IM channels and many agent providers.</strong></li>
<li><strong>NanoBot</strong> (★47,283, the highest-starred peer): all 11 PRs today point at <strong>observability and session lifecycle</strong>: <a href="https://github.com/HKUDS/nanobot/pull/5486">#5486</a> (unify turn observability, merged), <a href="https://github.com/HKUDS/nanobot/pull/5487">#5487</a> (WebUI file-preview path fix plus subagent activity and lifecycle replay), <a href="https://github.com/HKUDS/nanobot/pull/5420">#5420</a> (user-controlled turn resume), <a href="https://github.com/HKUDS/nanobot/pull/5483">#5483</a> (prevent deleted sessions from being recreated by delayed messages), and <a href="https://github.com/HKUDS/nanobot/pull/5471">#5471</a> (ephemeral runs must not mutate session state). There is also <a href="https://github.com/HKUDS/nanobot/pull/5484">#5484</a> (flag MCP responses that return <code>isError=false</code> while carrying a business-error envelope) — <strong>detecting &quot;looks successful, actually failed&quot; is today&#39;s recurring cross-ecosystem theme.</strong> <a href="https://github.com/HKUDS/nanobot/pull/5156">#5156</a> (recover from silently stalled Telegram polling, merged) is the same idea.</li>
<li><strong>CoPaw</strong>: the main thread is <strong>multimodal limits and security layering</strong>. <a href="https://github.com/agentscope-ai/CoPaw/issues/7201">#7201</a> (per-provider <code>max_image_bytes</code> / <code>max_video_bytes</code> / <code>max_audio_bytes</code>) and <a href="https://github.com/agentscope-ai/CoPaw/issues/7212">#7212</a> (inlining images whose pixel dimensions exceed provider limits crashes the request) are cause and effect — <strong>missing limits turn directly into crashes.</strong> <a href="https://github.com/agentscope-ai/CoPaw/pull/7214">#7214</a> writes Access Policy into the README as a fifth security layer. Chinese-language UX feedback remains dense: <a href="https://github.com/agentscope-ai/CoPaw/issues/7196">#7196</a> (always showing the reasoning trace is a serious visual distraction; make collapse-by-default configurable), <a href="https://github.com/agentscope-ai/CoPaw/issues/7213">#7213</a> (session output always contains meaningless blank lines), and <a href="https://github.com/agentscope-ai/CoPaw/issues/7043">#7043</a> (auto-run <code>chcp 65001</code> to switch to UTF-8 at startup, closed). On operations, <a href="https://github.com/agentscope-ai/CoPaw/pull/7050">#7050</a> (per-cron-job model override selector) and <a href="https://github.com/agentscope-ai/CoPaw/pull/7190">#7190</a> (PyPI runtime paths, one-command docker-compose demo, env inheritance) lower the self-hosting bar.</li>
<li><strong>PicoClaw</strong>: slow but effective. The core bug <a href="https://github.com/sipeed/picoclaw/issues/3269">#3269</a> (a failed MCP server connection hangs the agent loop and takes down PicoClaw chat with it, 1👍/6💬) already has a matching fix in PR <a href="https://github.com/sipeed/picoclaw/pull/3337">#3337</a>. Today&#39;s new issue <a href="https://github.com/sipeed/picoclaw/issues/3343">#3343</a> (after a failed turn the tool-feedback animation edits the same Telegram message forever) is the same &quot;failure paths don&#39;t clean up&quot; family. <a href="https://github.com/sipeed/picoclaw/pull/3222">#3222</a> (deltachat implementation refactor, ~200 lines removed, 16💬) reflects its embedded-oriented preference for minimalism.</li>
<li><strong>LobsterAI</strong> (NetEase Youdao): entirely <strong>driven by Chinese-language user requests</strong>, with an extremely fast loop — <a href="https://github.com/netease-youdao/LobsterAI/issues/1213">#1213</a> &quot;add export-to-Markdown for session details&quot; was filed and then implemented and merged via <a href="https://github.com/netease-youdao/LobsterAI/pull/1214">#1214</a>. Other fixes are equally close to daily use: <a href="https://github.com/netease-youdao/LobsterAI/pull/1208">#1208</a> (manual retry button for transient errors), <a href="https://github.com/netease-youdao/LobsterAI/pull/1212">#1212</a> (raise the custom-provider cap to 20), <a href="https://github.com/netease-youdao/LobsterAI/pull/1205">#1205</a> (error toast when session rename fails), and <a href="https://github.com/netease-youdao/LobsterAI/issues/1206">#1206</a> (on-prem kimi2.5 reprocesses analysis documents, closed). <strong>&quot;Filed today, merged today&quot; is its biggest differentiator.</strong></li>
<li><strong>Moltis</strong>: small project, clear direction. All three items today are new: <a href="https://github.com/moltis-org/moltis/issues/1230">#1230</a> (optional fail-closed error policy for mutating security hooks — <strong>whether a failing hook defaults to allow or deny is a foundational security-model choice</strong>), <a href="https://github.com/moltis-org/moltis/pull/1229">#1229</a> (support Browserless v2 containers), and <a href="https://github.com/moltis-org/moltis/pull/1231">#1231</a> (re-resolve the current MCP client after a service restart). That last one and OpenClaw <a href="https://github.com/openclaw/openclaw/issues/68187">#68187</a> (SSE-backed MCP sessions remain stale after a service restart and report &quot;Session not found&quot;) <strong>are the exact same bug independently reproduced in two projects — MCP restart semantics are shared ecosystem-wide debt.</strong></li>
<li><strong>The three abandoned projects (NullClaw / TinyClaw / ZeptoClaw)</strong>: 0 issues / 0 PRs for multiple consecutive days, latest releases 3–5 months old. <strong>Recommend down-weighting them in future selection and tracking.</strong></li>
<li><strong>EasyClaw</strong>: five releases across 08-21 to 08-22 (v1.8.108 → v1.8.112), but zero issues and zero PRs, and releases point at <code>gaoyangz77/rivonclaw</code> (repo renamed). <strong>Frequent releases plus zero public collaboration means community health cannot be judged from public signals.</strong></li>
</ul>
<h2>5. Trend Signals Worth Watching</h2>
<ul>
<li><strong>&quot;Looks successful, actually failed&quot; is now the ecosystem&#39;s #1 meta-problem.</strong> It appeared independently in at least five places today: OpenClaw #87637 (doctor misreports memory search as disabled) and #128003 (subagent completion announcements never fire), NanoBot #5484 (<code>isError=false</code> while carrying a business-error envelope), Zeroclaw #9447 (incomplete terminal responses classified), and PicoClaw #3343 (animation edits forever after a failed turn). <strong>Once agents run unattended for long stretches, &quot;failures must be loud&quot; matters more than &quot;failures must not happen&quot;</strong> — the same root as Gemini #22323 and Qwen #9733 on the CLI side today.</li>
<li><strong>The security model is being upgraded from &quot;feature toggle&quot; to &quot;identity infrastructure.&quot;</strong> Zeroclaw&#39;s canonical-principals / RPC-auth / OIDC three stages, Moltis&#39;s fail-closed hook policy, CoPaw&#39;s fifth security layer, and OpenClaw&#39;s install-policy warning acknowledgement requirement (<a href="https://github.com/openclaw/openclaw/pull/116489">#116489</a>, 49💬, merged) — <strong>four projects tightening permissions at four levels on the same day means the risk of &quot;agents hold real execution power&quot; is now broadly understood.</strong></li>
<li><strong>MCP restart and session semantics are shared technical debt.</strong> Moltis #1231 and OpenClaw #68187 independently reproduce the same bug, and PicoClaw #3269 shows a failed MCP connection can hang an entire agent loop. <strong>The MCP ecosystem lacks a shared &quot;connection invalidation → rebuild → idempotent recovery&quot; convention, so every project re-learns it the hard way.</strong></li>
<li><strong>Performance debt has a highly consistent shape: redundant rebuilds.</strong> OpenClaw #123535 (session directory refresh storms, 153💬), #127379 (<code>buildModelsProviderData</code> rebuilt repeatedly, pinning CPU), and #72717 (<code>wiki_search</code> lacks an FTS index) share the exact shape of OpenCode #44127 (redundant git subprocess spawns) and Codex #20864 (full scan of the sessions directory) on the CLI side. <strong>Agent frameworks are broadly still in the &quot;recompute everything each time&quot; phase; caching and incrementality are the next clear optimization dividend.</strong></li>
<li><strong>The ecosystem tail is thinning out naturally.</strong> Of 13 peers, three are de facto abandoned and one has only a release pipeline; roughly eight show genuine ongoing collaboration. <strong>The &quot;claw family&quot; explosion is over; consolidation has begun.</strong></li>
</ul>
<hr>
<h2>Per-Project Details</h2>
<h3>OpenClaw (<a href="https://github.com/openclaw/openclaw">openclaw/openclaw</a>)</h3>
<p><strong>Latest release</strong>: <a href="https://github.com/openclaw/openclaw/releases/tag/v2026.8.1-beta.2">v2026.8.1-beta.2</a> (08-15); latest stable is v2026.7.1-2 (08-04).</p>
<p><strong>High-discussion PRs</strong></p>
<table>
<thead>
<tr>
<th>PR</th>
<th>Discussion</th>
<th>Summary</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/openclaw/openclaw/pull/123535">#123535</a></td>
<td><strong>153💬</strong></td>
<td>Avoid session directory refresh storms — highest in the ecosystem</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/116489">#116489</a></td>
<td>49💬 (merged)</td>
<td>Install-policy warnings require explicit acknowledgement</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/123975">#123975</a></td>
<td>45💬</td>
<td>typecheck hangs forever when tsgo stalls instead of failing</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/120900">#120900</a></td>
<td>44💬 (merged)</td>
<td>UI support for reviewing install-policy warnings</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/123189">#123189</a></td>
<td>28💬</td>
<td>Restore embedded channel runs in chat startup projection</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/126618">#126618</a></td>
<td>25💬</td>
<td>Tool Search directory/tools wrap native read/exec in tool_call</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/117114">#117114</a></td>
<td>21💬</td>
<td>Isolate <code>pnpm link</code> so it cannot pollute source-checkout updates; warn on broken self-links</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/126424">#126424</a></td>
<td>19💬 (merged)</td>
<td>Scope session delivery to agent bindings</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/118067">#118067</a></td>
<td>19💬</td>
<td>Discord support for private provider endpoints</td>
</tr>
<tr>
<td><a href="https://github.com/openclaw/openclaw/pull/124548">#124548</a></td>
<td>18💬</td>
<td>Persist sender identity for DM turns</td>
</tr>
</tbody></table>
<p><strong>Key issues</strong></p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/127379">#127379</a> — The <code>/models</code> command pins the gateway main thread at 100%+ CPU because <code>buildModelsProviderData</code> is rebuilt repeatedly.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/87637">#87637</a> (2👍 / 3💬) — <strong><code>openclaw doctor</code> reports memory search as disabled while memory-core dreaming is actually running — diagnostic distortion.</strong></li>
<li><a href="https://github.com/openclaw/openclaw/issues/125570">#125570</a> — Applying a Skill Workshop update overwrites the live skill&#39;s description, silently breaking its triggers.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/124099">#124099</a> — After upgrading to 2026.8.1-beta.2, a <code>SessionCanonicalKeyMigrationRequiredError</code> loop appears and trigger-pending rows are affected.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/68187">#68187</a> — SSE-backed MCP sessions remain stale after a service restart and report &quot;Session not found&quot;.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/72717">#72717</a> — Introduce a SQLite FTS index for <code>wiki_search</code> to speed up synthetic queries.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/88334">#88334</a> — Gateway should refresh the auth epoch immediately after credential rotation.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/45184">#45184</a> — Skip dispatch when a message @-mentions another account&#39;s bot.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/33102">#33102</a> — Allow the TUI to configure a default for <code>--deliver</code>.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/119254">#119254</a> — Design a WhatsApp <code>poll_vote_received</code> plugin hook.</li>
</ul>
<p><strong>Opened today (3 issues / 22 PRs, selected)</strong></p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/128003">#128003</a> — Subagent completion announcements never fire on OpenAI-compatible HTTP sessions.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/128006">#128006</a> — ACPX direct-agent startup lacks a persistent process-lease override (no upstream lifecycle hook).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/128005">#128005</a> — Android <code>location.get</code> ignores <code>maxAgeMs</code> when falling back to live positioning.</li>
<li>PR <a href="https://github.com/openclaw/openclaw/pull/127797">#127797</a> (8💬) — Unify synchronous message hooks.</li>
<li>PR <a href="https://github.com/openclaw/openclaw/pull/127998">#127998</a> (6💬) — <strong>Doctor&#39;s permission-fix suggestions list already-disabled automations (diagnostic accuracy fix).</strong></li>
<li>PR <a href="https://github.com/openclaw/openclaw/pull/127962">#127962</a> (6💬) — Preserve gateway context for inbound turns.</li>
<li>PR <a href="https://github.com/openclaw/openclaw/pull/128004">#128004</a> (merged) — Share the format scope for schema validation (performance).</li>
<li>PR <a href="https://github.com/openclaw/openclaw/pull/128001">#128001</a> — Propagate the caller&#39;s abort into the ACP spawn.</li>
</ul>
<h3>Zeroclaw (<a href="https://github.com/zeroclaw-labs/zeroclaw">zeroclaw-labs/zeroclaw</a>)</h3>
<p><strong>Latest release</strong>: v0.8.4 (08-02). <strong>#1 by PR volume in the ecosystem today (91 active / 12 new).</strong></p>
<p><strong>The <code>#8289</code> security epic (three stages advanced the same day)</strong></p>
<ul>
<li>PR <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10248">#10248</a> — Canonical principals and shared authorization resolution (stage 2).</li>
<li>PR <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10259">#10259</a> — Enforce authenticated principals over RPC, native + peercred (stage 3).</li>
<li>PR <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10255">#10255</a> — <code>oidc.&lt;alias&gt;</code> token validation provider (stage 5).</li>
</ul>
<p><strong>High-discussion PRs</strong></p>
<table>
<thead>
<tr>
<th>PR</th>
<th>Discussion</th>
<th>Summary</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9109">#9109</a></td>
<td>44💬</td>
<td>Native Hailo-Ollama support (edge inference)</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9707">#9707</a></td>
<td>33💬</td>
<td>Migrate bare <code>vision_model_provider</code> to dotted alias references</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9713">#9713</a></td>
<td>25💬</td>
<td>Expose token accounting on history-trim events</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9535">#9535</a></td>
<td>22💬</td>
<td>Anchor context compaction to a ratio of the model window</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9447">#9447</a></td>
<td>20💬</td>
<td><strong>Classify incomplete terminal responses (the fix side of the CLI empty-response problem)</strong></td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9772">#9772</a></td>
<td>20💬</td>
<td><code>per_user_session</code> toggle for shared Telegram group sessions</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9203">#9203</a></td>
<td>19💬</td>
<td>Authenticated HTTP fan-in</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9281">#9281</a></td>
<td>18💬</td>
<td>Roll back auto-created map aliases when <code>config set</code> fails</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9574">#9574</a></td>
<td>17💬</td>
<td>Authorization approval responder</td>
</tr>
<tr>
<td><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9291">#9291</a></td>
<td>17💬</td>
<td>Detect installed AppImages and use an available desktop download URL</td>
</tr>
</tbody></table>
<p><strong>Governance and items opened today</strong></p>
<ul>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8692">#8692</a> (13💬) — Tracker for the maintainer RFC and design-issue decision queue.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8396">#8396</a> (9💬) — RFC: make the wire protocol a first-class concept in provider construction and onboarding.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10141">#10141</a> — &quot;Please make sessions usable.&quot;</li>
<li>New issues today: <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10251">#10251</a> (17 telegram <code>listen_*</code> tests depend on wall-clock timeout assertions), <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10257">#10257</a> (<code>cron update --command</code> writes an unused column on agent jobs), <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10249">#10249</a> (duplicate webhook handling logs a caller-controlled idempotency key verbatim), <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10261">#10261</a>.</li>
<li>New PRs today: <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10256">#10256</a> (redact duplicate idempotency keys from logs, addresses #10249), <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10258">#10258</a> (map command patches onto the agent job prompt), <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10260">#10260</a> (fail RPC calls on disconnect).</li>
</ul>
<h3>IronClaw (<a href="https://github.com/nearai/ironclaw">nearai/ironclaw</a>)</h3>
<p><strong>Latest release</strong>: <a href="https://github.com/nearai/ironclaw/releases/tag/ironclaw-v1.3.0">ironclaw-v1.3.0</a> (08-19), preceded by rc.1 / rc.2 (08-17 / 08-18).</p>
<p><strong>High-discussion product PRs</strong></p>
<ul>
<li><a href="https://github.com/nearai/ironclaw/pull/7650">#7650</a> (45💬) — Derive run outcome from runtime evidence.</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7818">#7818</a> — Subagent background mode: receipt-based spawn, per-child delivery, activation and self-healing sweeps.</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7516">#7516</a> (14💬) — Operator surface for IronHub agent link.</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7257">#7257</a> (11💬) — WebUI design-system proposal, plan, and checklist (Epic #7038).</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7816">#7816</a> — Add refresh and connect entries to the OOBE suggestions drawer.</li>
</ul>
<p><strong>CI infrastructure, four in a row (T1–T4, all opened today)</strong></p>
<ul>
<li><a href="https://github.com/nearai/ironclaw/pull/7821">#7821</a> — Single setup-rust composite action: pinned toolchain, mold, centralized build profiles (T1).</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7817">#7817</a> — nextest test pipeline, full failure signal, unthrottled on PRs (T2).</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7820">#7820</a> — Merge probe for the scope-isolation test suite (T2 follow-up).</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7819">#7819</a> — Converge PR / queue checks: planner drift guard, default-features clippy on PRs (T3).</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7809">#7809</a> — Normalize preflight: unified gate list, worktree safety hooks, self-printing REPRO (T4).</li>
</ul>
<p><strong>Onboarding / integration issues (5 opened today)</strong></p>
<ul>
<li><a href="https://github.com/nearai/ironclaw/issues/7815">#7815</a> — Onboarding suggestions: cumulative net-new work needed to close the connect → suggest → thread loop.</li>
<li><a href="https://github.com/nearai/ironclaw/issues/7812">#7812</a> — Onboarding suggestions should respect user-level tool permissions and use read-only tool access for generation.</li>
<li><a href="https://github.com/nearai/ironclaw/issues/7823">#7823</a> — Notion install fails in IronClaw.</li>
<li><a href="https://github.com/nearai/ironclaw/issues/7822">#7822</a> — Slack users cannot complete Slack configuration in IronClaw.</li>
<li><a href="https://github.com/nearai/ironclaw/issues/7813">#7813</a> — Title is clipped when the suggestions panel appears.</li>
</ul>
<h3>NanoClaw (<a href="https://github.com/qwibitai/nanoclaw">qwibitai/nanoclaw</a>)</h3>
<p><strong>Latest release</strong>: v2.2.0 (08-13). 0 issues / 16 PRs — purely PR-driven.</p>
<ul>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3438">#3438</a> — Config wizard offers &quot;add another Telegram bot&quot; when one is already configured.</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3437">#3437</a> — Docs for the add-another-bot path, instance-aware pairing, and wiring.</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3435">#3435</a> — Thread adapter instance through pairing, first-agent init, and the CLI welcome flow.</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3355">#3355</a> / <a href="https://github.com/qwibitai/nanoclaw/pull/3356">#3356</a> — Add an <code>/add-cursor</code> provider skill; add a Cursor Agent SDK payload.</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3434">#3434</a> — Polling adapters no longer start a webhook server.</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3446">#3446</a> — Auto-drop automation senders in the unknown-sender gate.</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3442">#3442</a> — Validate <code>runtimeTier</code> via driver-isolated capability checks and pick a tier accordingly.</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3443">#3443</a> — Remove better-sqlite3 from <code>onlyBuiltDependencies</code> and use its bundled prebuilds.</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3441">#3441</a> — Preserve files when <code>git show</code> fails.</li>
<li><a href="https://github.com/qwibitai/nanoclaw/pull/3431">#3431</a> — Correct pairing-card copy to six digits.</li>
</ul>
<h3>NanoBot (<a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a>) ★47,283</h3>
<p><strong>Latest release</strong>: v0.3.0 (07-25). 0 issues / 11 PRs, themed on observability and session lifecycle.</p>
<ul>
<li><a href="https://github.com/HKUDS/nanobot/pull/5486">#5486</a> (merged) — Unify turn observability.</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5487">#5487</a> — WebUI file-preview path fix plus subagent activity and lifecycle replay.</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5420">#5420</a> — Add user-controlled turn resume.</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5484">#5484</a> — <strong>Flag MCP responses that return <code>isError=false</code> while carrying a business-error envelope.</strong></li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5483">#5483</a> — Prevent deleted sessions from being recreated by delayed messages.</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5471">#5471</a> — Ensure ephemeral runs do not mutate session state.</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5485">#5485</a> — Restore LangSmith tracing for native providers.</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/5156">#5156</a> (merged) — Recover from silently stalled Telegram polling.</li>
<li><a href="https://github.com/HKUDS/nanobot/pull/3294">#3294</a> (merged) — Optional dream kill switch plus custom Phase 1/2 template paths.</li>
</ul>
<h3>CoPaw (<a href="https://github.com/agentscope-ai/CoPaw">agentscope-ai/CoPaw</a>)</h3>
<p><strong>Latest release</strong>: v2.1.1-beta.1 (08-20); stable v2.1.0 (08-13).</p>
<ul>
<li><a href="https://github.com/agentscope-ai/CoPaw/issues/7196">#7196</a> (1👍 / 2💬) — Always showing the reasoning trace is a serious visual distraction; make collapse-by-default configurable.</li>
<li><a href="https://github.com/agentscope-ai/CoPaw/issues/7201">#7201</a> — Per-provider <code>max_image_bytes</code> / <code>max_video_bytes</code> / <code>max_audio_bytes</code> limits.</li>
<li><a href="https://github.com/agentscope-ai/CoPaw/issues/7212">#7212</a> — Inlining images whose pixel dimensions exceed provider limits crashes the request (cause-and-effect with #7201).</li>
<li><a href="https://github.com/agentscope-ai/CoPaw/issues/7213">#7213</a> — Session output always contains meaningless blank lines.</li>
<li><a href="https://github.com/agentscope-ai/CoPaw/issues/7043">#7043</a> (closed) — Auto-run <code>chcp 65001</code> at startup to switch to a UTF-8 environment.</li>
<li>PR <a href="https://github.com/agentscope-ai/CoPaw/pull/7214">#7214</a> — Document Access Policy as a fifth security layer in the README.</li>
<li>PR <a href="https://github.com/agentscope-ai/CoPaw/pull/7054">#7054</a> — Chrome support for remote bridge endpoints on LAN/network browsers.</li>
<li>PR <a href="https://github.com/agentscope-ai/CoPaw/pull/7050">#7050</a> — Per-cron-job model override selector.</li>
<li>PR <a href="https://github.com/agentscope-ai/CoPaw/pull/7190">#7190</a> — PyPI runtime paths for qwenpaw-data, one-command docker-compose demo, and env inheritance.</li>
<li>PR <a href="https://github.com/agentscope-ai/CoPaw/pull/6808">#6808</a> — Console shows markdown files for custom profiles.</li>
</ul>
<h3>PicoClaw (<a href="https://github.com/sipeed/picoclaw">sipeed/picoclaw</a>)</h3>
<p><strong>Latest release</strong>: v0.3.1 (06-30), nightly (07-02).</p>
<ul>
<li><a href="https://github.com/sipeed/picoclaw/issues/3269">#3269</a> (1👍 / 6💬) — <strong>A failed MCP server connection hangs the agent loop and takes down the whole PicoClaw chat.</strong> Matching fix: PR <a href="https://github.com/sipeed/picoclaw/pull/3337">#3337</a>.</li>
<li><a href="https://github.com/sipeed/picoclaw/issues/3343">#3343</a> (opened today) — After a failed turn the tool-feedback animation edits the same Telegram message forever.</li>
<li>PR <a href="https://github.com/sipeed/picoclaw/pull/3222">#3222</a> (16💬) — deltachat implementation refactor and docs cleanup, ~200 lines net removed.</li>
<li>PR <a href="https://github.com/sipeed/picoclaw/pull/3319">#3319</a> (merged) — Respect exec timeouts and boolean run options.</li>
</ul>
<h3>LobsterAI (<a href="https://github.com/netease-youdao/LobsterAI">netease-youdao/LobsterAI</a>)</h3>
<p><strong>Latest release</strong>: 2026.8.18 (08-18). Driven by Chinese-language user requests, with a very short file-to-merge loop.</p>
<ul>
<li><a href="https://github.com/netease-youdao/LobsterAI/issues/1213">#1213</a> (closed) — Add &quot;export to Markdown&quot; for session details → implemented and merged via PR <a href="https://github.com/netease-youdao/LobsterAI/pull/1214">#1214</a>.</li>
<li><a href="https://github.com/netease-youdao/LobsterAI/issues/1206">#1206</a> (closed) — On-prem kimi2.5 reprocesses analysis documents or repeats progress replies.</li>
<li>PR <a href="https://github.com/netease-youdao/LobsterAI/pull/1208">#1208</a> (merged) — Add a manual retry button for transient errors such as rate limiting.</li>
<li>PR <a href="https://github.com/netease-youdao/LobsterAI/pull/1212">#1212</a> (merged) — Raise the custom-provider cap to 20.</li>
<li>PR <a href="https://github.com/netease-youdao/LobsterAI/pull/1205">#1205</a> (merged) — Show an error toast when session rename fails.</li>
<li>PR <a href="https://github.com/netease-youdao/LobsterAI/pull/1209">#1209</a> (merged) — Fix web-search blocking unsupported Chrome flags.</li>
<li>PR <a href="https://github.com/netease-youdao/LobsterAI/pull/2452">#2452</a> — Preserve provider information for model ids containing slashes.</li>
</ul>
<h3>Moltis (<a href="https://github.com/moltis-org/moltis">moltis-org/moltis</a>)</h3>
<p><strong>Latest release</strong>: 20260820.01 (08-20). All three items today are new.</p>
<ul>
<li><a href="https://github.com/moltis-org/moltis/issues/1230">#1230</a> — <strong>Optional fail-closed error policy for mutating security hooks (deny rather than allow when a hook errors).</strong></li>
<li>PR <a href="https://github.com/moltis-org/moltis/pull/1229">#1229</a> (1👍 / 3💬) — Support Browserless v2 containers.</li>
<li>PR <a href="https://github.com/moltis-org/moltis/pull/1231">#1231</a> (1👍 / 2💬) — <strong>Re-resolve the current MCP client after a service restart (an independent reproduction of OpenClaw #68187).</strong></li>
</ul>
<h3>Low-Activity / Stalled Projects</h3>
<table>
<thead>
<tr>
<th>Project</th>
<th>Latest Release</th>
<th>Stalled For</th>
<th>Activity Today</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/gaoyangz77/easyclaw">EasyClaw</a></td>
<td>v1.8.112 (08-22)</td>
<td>—</td>
<td><strong>5 releases in a row but 0 issues / 0 PRs</strong>; releases actually point at <code>gaoyangz77/rivonclaw</code> (renamed)</td>
</tr>
<tr>
<td><a href="https://github.com/nullclaw/nullclaw">NullClaw</a></td>
<td>v2026.5.29</td>
<td>~3 months</td>
<td>0 / 0</td>
</tr>
<tr>
<td><a href="https://github.com/qhkm/zeptoclaw">ZeptoClaw</a></td>
<td>v0.9.2 (04-07)</td>
<td>~4.5 months</td>
<td>0 / 0</td>
</tr>
<tr>
<td><a href="https://github.com/TinyAGI/tinyclaw">TinyClaw</a></td>
<td>v0.0.20 (03-26)</td>
<td>~5 months</td>
<td>0 / 0</td>
</tr>
</tbody></table>
<hr>
<p><em>This digest is generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. All content is fetched live from GitHub&#39;s public API and written by the executing agent — no external LLM was called.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI 开源趋势日报 2026-08-23</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-trending</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-trending</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>开源 AI 趋势日报 2026-08-23 生成时间: 2026-08-23 02:30 (GMT+8) 数据来源：GitHub Trending（每日榜）+ gh search repos 6 个 AI 主题（按 stars 排序，7 天窗口） 本日报由 agents-radar 本地自动化生成，所有撰写由执行代理人工完成，未调用任何外部大模型 API。 一、GitHub Trending 每日飙升榜（2026-08-23） 说明：本次抓取时 GitHub Trending 页面仍未对外暴露「当日新增 Star」数值（连续第二日，疑为未登录视图/版式变更），故下表仅列出入榜项目与简介，不含 star 增量。排名按页面原始顺序。 # 项目 简介 1 openai/codex 运行在终端里的轻量编码 agent 2 mattpocock/skills 「给真实工程师的 Skills」，直接取自作者 .agents 目录 3 affaan-m/ECC agent harness 性能优化系统：Skills / instincts / memory / security / research...</description>
      <content:encoded><![CDATA[<h1>开源 AI 趋势日报 2026-08-23</h1>
<blockquote>
<p>生成时间: 2026-08-23 02:30 (GMT+8)
数据来源：GitHub Trending（每日榜）+ <code>gh search repos</code> 6 个 AI 主题（按 stars 排序，7 天窗口）
本日报由 agents-radar 本地自动化生成，所有撰写由执行代理人工完成，未调用任何外部大模型 API。</p>
</blockquote>
<hr>
<h2>一、GitHub Trending 每日飙升榜（2026-08-23）</h2>
<blockquote>
<p>说明：本次抓取时 GitHub Trending 页面仍未对外暴露「当日新增 Star」数值（连续第二日，疑为未登录视图/版式变更），故下表仅列出入榜项目与简介，不含 star 增量。排名按页面原始顺序。</p>
</blockquote>
<table>
<thead>
<tr>
<th>#</th>
<th>项目</th>
<th>简介</th>
</tr>
</thead>
<tbody><tr>
<td>1</td>
<td><a href="https://github.com/openai/codex">openai/codex</a></td>
<td>运行在终端里的轻量编码 agent</td>
</tr>
<tr>
<td>2</td>
<td><a href="https://github.com/mattpocock/skills">mattpocock/skills</a></td>
<td>「给真实工程师的 Skills」，直接取自作者 <code>.agents</code> 目录</td>
</tr>
<tr>
<td>3</td>
<td><a href="https://github.com/affaan-m/ECC">affaan-m/ECC</a></td>
<td>agent harness 性能优化系统：Skills / instincts / memory / security / research-first，适配 Claude Code、Codex、OpenCode、Cursor</td>
</tr>
<tr>
<td>4</td>
<td><a href="https://github.com/obra/superpowers">obra/superpowers</a></td>
<td>可落地的 agentic skills 框架与软件开发方法论</td>
</tr>
<tr>
<td>5</td>
<td><a href="https://github.com/Wei-Shaw/sub2api">Wei-Shaw/sub2api</a></td>
<td>一站式开源中转服务，让 Claude / OpenAI / Gemini / Grok 订阅统一接入，支持拼车共享分摊成本</td>
</tr>
<tr>
<td>6</td>
<td><a href="https://github.com/makeplane/plane">makeplane/plane</a></td>
<td>开源 Jira / Linear / Monday / ClickUp 替代</td>
</tr>
<tr>
<td>7</td>
<td><a href="https://github.com/n8n-io/n8n">n8n-io/n8n</a></td>
<td>带原生 AI 能力的 fair-code 工作流自动化平台，400+ 集成</td>
</tr>
<tr>
<td>8</td>
<td><a href="https://github.com/anthropics/claude-code">anthropics/claude-code</a></td>
<td>终端里的 agentic 编码工具，理解代码库并执行日常任务</td>
</tr>
<tr>
<td>9</td>
<td><a href="https://github.com/AprilNEA/OpenLogi">AprilNEA/OpenLogi</a></td>
<td>原生、本地优先的 Logitech Options+ 替代，Rust 编写，无账号无遥测</td>
</tr>
<tr>
<td>10</td>
<td><a href="https://github.com/modular/modular">modular/modular</a></td>
<td>Modular 平台（含 MAX 与 Mojo）</td>
</tr>
<tr>
<td>11</td>
<td><a href="https://github.com/multica-ai/andrej-karpathy-skills">multica-ai/andrej-karpathy-skills</a></td>
<td>单个 CLAUDE.md 文件改善 Claude Code 行为，源自 Karpathy 对 LLM 编码陷阱的观察</td>
</tr>
<tr>
<td>12</td>
<td><a href="https://github.com/mahlernim/google-timeline-visualizer">mahlernim/google-timeline-visualizer</a></td>
<td>用 Google 位置历史可视化全年旅行轨迹</td>
</tr>
<tr>
<td>13</td>
<td><a href="https://github.com/ripienaar/free-for-dev">ripienaar/free-for-dev</a></td>
<td>对 devops/infra 有价值的免费额度 SaaS/PaaS/IaaS 清单</td>
</tr>
<tr>
<td>14</td>
<td><a href="https://github.com/microsoft/TypeScript">microsoft/TypeScript</a></td>
<td>TypeScript 语言本体</td>
</tr>
<tr>
<td>15</td>
<td><a href="https://github.com/cursor/plugins">cursor/plugins</a></td>
<td>Cursor 插件规范与官方插件</td>
</tr>
<tr>
<td>16</td>
<td><a href="https://github.com/PostHog/posthog">PostHog/posthog</a></td>
<td>自驱动产品平台（AI 可观测、分析、会话回放、特性开关等）</td>
</tr>
<tr>
<td>17</td>
<td><a href="https://github.com/Tencent/AI-Infra-Guard">Tencent/AI-Infra-Guard</a></td>
<td>全栈 AI 红队平台：Agent Scan / Skills Scan / MCP scan / AI Infra scan</td>
</tr>
</tbody></table>
<p><strong>今日榜单最强信号：Codex 登顶，Claude Code 同榜第 8。</strong> 这是三份日报罕见的三方共振——Trending 第 1 是 <code>openai/codex</code>，HN 今日热度第 1 是「A week of using Codex more than Claude」（94👍），而 Claude Code 侧今日最高热度 issue <a href="https://github.com/anthropics/claude-code/issues/77136">#77136</a>（343👍）是对模型口头习惯的集体吐槽。<strong>社区注意力正在从 Claude Code 向 Codex 迁移，且这一迁移同时体现在 star 榜、讨论榜和情绪面三个维度上。</strong></p>
<p><strong>第二个信号：Skills / harness 元层占据 5 席。</strong> #2 mattpocock/skills、#3 affaan-m/ECC、#4 obra/superpowers、#11 multica-ai/andrej-karpathy-skills、#15 cursor/plugins——<strong>前四名里有三个是「给 agent 装能力」的项目，而不是 agent 本身</strong>。值得注意的是 #11 的形态极端到只有一个 <code>CLAUDE.md</code> 文件却能上榜，说明<strong>当前最稀缺的不是工具，而是&quot;怎么让模型少犯错&quot;的经验沉淀</strong>。</p>
<p><strong>第三个信号：成本焦虑显性化。</strong> #5 <code>Wei-Shaw/sub2api</code> 做的是「订阅统一接入 + 拼车共享分摊成本」，#13 <code>ripienaar/free-for-dev</code> 是免费额度清单。这与今日 CLI 日报中 GPT-5.6 Sol 降价 20%、以及 HN 上关于「A/B 测试降低推理强度」的争议属于同一背景——<strong>用户对 agent 的月度支出已经到了要专门做工具去摊平的程度。</strong></p>
<h2>二、六大 AI 主题搜索热度（按 stars，Top 15）</h2>
<h3>1. AI Agent 框架</h3>
<ul>
<li><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a> ⭐234,323 — The agent that grows with you</li>
<li><a href="https://github.com/shareAI-lab/learn-claude-code">shareAI-lab/learn-claude-code</a> ⭐74,949 — 从 0 到 1 构建类 claude code 的 agent harness</li>
<li><a href="https://github.com/Panniantong/Agent-Reach">Panniantong/Agent-Reach</a> ⭐74,085 — 给 AI agent 全网的眼睛（Twitter / Reddit / YouTube / GitHub / B 站 / 小红书），一个 CLI 零 API 费用</li>
<li><a href="https://github.com/thedaviddias/Front-End-Checklist">thedaviddias/Front-End-Checklist</a> ⭐73,609 — 现代 Web 开发必备清单（人类与 AI agent 通用）</li>
<li><a href="https://github.com/santifer/career-ops">santifer/career-ops</a> ⭐67,764 — 开源 AI 求职：扫描招聘站点、A–F 评分体系、简历定制与投递追踪，可本地跑在各 AI 编码 CLI</li>
<li><a href="https://github.com/ZhuLinsen/daily_stock_analysis">ZhuLinsen/daily_stock_analysis</a> ⭐63,624 — LLM 驱动的多市场股票智能分析（多源行情、实时新闻、决策看板、自动推送）</li>
<li><a href="https://github.com/CherryHQ/cherry-studio">CherryHQ/cherry-studio</a> ⭐50,919 — AI 生产力工作室，300+ 助手统一接入前沿 LLM</li>
<li><a href="https://github.com/hugohe3/ppt-master">hugohe3/ppt-master</a> ⭐48,617 — AI 把文档或主题变成真正的原生 PPT（原生形状、转场动画、数据图表、语音旁白）</li>
<li><a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a> ⭐47,283 — 超轻量、自托管的个人 AI agent 框架（WebUI/工具/记忆/MCP/多 agent 工作流）</li>
<li><a href="https://github.com/zhayujie/CowAgent">zhayujie/CowAgent</a> ⭐46,632 — 开源超级 AI 助手与 Agent Harness，带记忆与知识自进化</li>
<li><a href="https://github.com/siyuan-note/siyuan">siyuan-note/siyuan</a> ⭐45,931 — 开源、隐私优先、自托管的知识工作空间</li>
<li><a href="https://github.com/bojieli/ai-agent-book">bojieli/ai-agent-book</a> ⭐40,913 — 《深入理解 AI Agent：设计原理与工程实践》全书正文 + PDF + 配套代码</li>
<li><a href="https://github.com/Hmbown/CodeWhale">Hmbown/CodeWhale</a> ⭐40,841 — Rust 编写的终端开源编码 agent</li>
<li><a href="https://github.com/CopilotKit/CopilotKit">CopilotKit/CopilotKit</a> ⭐36,960 — Agent 与 Generative UI 的前端栈（AG-UI 协议作者）</li>
<li><a href="https://github.com/esengine/DeepSeek-Reasonix">esengine/DeepSeek-Reasonix</a> ⭐35,032 — DeepSeek 原生的终端编码 agent，围绕前缀缓存稳定性设计</li>
</ul>
<h3>2. 大模型（LLM）</h3>
<ul>
<li><a href="https://github.com/affaan-m/ECC">affaan-m/ECC</a> ⭐242,087 — agent harness 性能优化系统</li>
<li><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a> ⭐234,323 — The agent that grows with you</li>
<li><a href="https://github.com/Significant-Gravitas/AutoGPT">Significant-Gravitas/AutoGPT</a> ⭐186,764 — 人人可用的自主 AI</li>
<li><a href="https://github.com/ollama/ollama">ollama/ollama</a> ⭐179,192 — 一键跑起 Kimi-K2.6 / GLM-5.2 / MiniMax / DeepSeek / gpt-oss / Qwen / Gemma</li>
<li><a href="https://github.com/firecrawl/firecrawl">firecrawl/firecrawl</a> ⭐170,855 — 大规模搜索/抓取/交互 Web 的上下文 API</li>
<li><a href="https://github.com/f/prompts.chat">f/prompts.chat</a> ⭐167,752 — Awesome ChatGPT Prompts 社区共享（可自托管）</li>
<li><a href="https://github.com/huggingface/transformers">huggingface/transformers</a> ⭐164,339 — 文本/视觉/音频/多模态 SOTA 模型框架</li>
<li><a href="https://github.com/langgenius/dify">langgenius/dify</a> ⭐153,205 — Agentic 工作流与 RAG 管线协作平台</li>
<li><a href="https://github.com/open-webui/open-webui">open-webui/open-webui</a> ⭐149,579 — 用户友好的 AI 界面</li>
<li><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a> ⭐144,777 — agent 工程平台</li>
<li><a href="https://github.com/harry0703/MoneyPrinterTurbo">harry0703/MoneyPrinterTurbo</a> ⭐114,563 — AI 一键生成高清短视频</li>
<li><a href="https://github.com/browser-use/browser-use">browser-use/browser-use</a> ⭐110,116 — 让网站对 AI agent 可用，轻松自动化线上任务</li>
<li><a href="https://github.com/Graphify-Labs/graphify">Graphify-Labs/graphify</a> ⭐109,501 — 把代码库（含文档/SQL schema/配置/PDF）变成可查询知识图谱，作为 <code>/graphify</code> skill 供各 CLI 使用</li>
<li><a href="https://github.com/DietrichGebert/ponytail">DietrichGebert/ponytail</a> ⭐108,073 — 让 AI agent 像「屋里最懒的资深工程师」一样思考：最好的代码是你没写的代码</li>
<li><a href="https://github.com/rasbt/LLMs-from-scratch">rasbt/LLMs-from-scratch</a> ⭐103,224 — 从零逐步用 PyTorch 实现类 ChatGPT LLM</li>
</ul>
<h3>3. RAG 检索增强生成</h3>
<ul>
<li><a href="https://github.com/langgenius/dify">langgenius/dify</a> ⭐153,205 — Agentic 工作流与 RAG 管线</li>
<li><a href="https://github.com/open-webui/open-webui">open-webui/open-webui</a> ⭐149,579 — 用户友好的 AI 界面</li>
<li><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a> ⭐144,777 — agent 工程平台</li>
<li><a href="https://github.com/Shubhamsaboo/awesome-llm-apps">Shubhamsaboo/awesome-llm-apps</a> ⭐133,588 — 100+ AI Agents / Agent Skills / RAG 应用</li>
<li><a href="https://github.com/Graphify-Labs/graphify">Graphify-Labs/graphify</a> ⭐109,501 — 代码库转可查询知识图谱（本地确定性解析）</li>
<li><a href="https://github.com/thedotmack/claude-mem">thedotmack/claude-mem</a> ⭐91,519 — 跨会话持久上下文：记录 agent 全过程、AI 压缩、按需注入未来会话</li>
<li><a href="https://github.com/infiniflow/ragflow">infiniflow/ragflow</a> ⭐89,036 — 领先的开源 RAG 引擎，融合 Agent 能力</li>
<li><a href="https://github.com/PaddlePaddle/PaddleOCR">PaddlePaddle/PaddleOCR</a> ⭐88,110 — 轻量 OCR 工具包，支持 100+ 语言，桥接图像/PDF 与 LLM</li>
<li><a href="https://github.com/dair-ai/Prompt-Engineering-Guide">dair-ai/Prompt-Engineering-Guide</a> ⭐77,693 — 提示工程/上下文工程/RAG/AI Agents 指南</li>
<li><a href="https://github.com/datawhalechina/hello-agents">datawhalechina/hello-agents</a> ⭐74,217 — 《从零开始构建智能体》教程</li>
<li><a href="https://github.com/headroomlabs-ai/headroom">headroomlabs-ai/headroom</a> ⭐67,179 — 在工具输出/日志/文件/RAG 块进入 LLM 前压缩：编码 agent 省 20% token，JSON 省 60–95%</li>
<li><a href="https://github.com/Mintplex-Labs/anything-llm">Mintplex-Labs/anything-llm</a> ⭐65,052 — 本地优先的强力 agent 体验</li>
<li><a href="https://github.com/mem0ai/mem0">mem0ai/mem0</a> ⭐63,821 — AI Agent 的通用记忆层</li>
<li><a href="https://github.com/pathwaycom/llm-app">pathwaycom/llm-app</a> ⭐59,005 — RAG / AI 管线与企业搜索云模板</li>
<li><a href="https://github.com/FlowiseAI/Flowise">FlowiseAI/Flowise</a> ⭐55,383 — 可视化构建 AI Agent</li>
</ul>
<h3>4. 向量数据库</h3>
<ul>
<li><a href="https://github.com/Mintplex-Labs/anything-llm">Mintplex-Labs/anything-llm</a> ⭐65,052 — 本地优先的 agent 体验</li>
<li><a href="https://github.com/meilisearch/meilisearch">meilisearch/meilisearch</a> ⭐59,054 — 极速搜索 API，AI 混合搜索</li>
<li><a href="https://github.com/pathwaycom/llm-app">pathwaycom/llm-app</a> ⭐59,005 — RAG/AI 管线云模板</li>
<li><a href="https://github.com/run-llama/llama_index">run-llama/llama_index</a> ⭐51,801 — 文档 agent 与 OCR 平台</li>
<li><a href="https://github.com/milvus-io/milvus">milvus-io/milvus</a> ⭐45,736 — 高性能云原生向量数据库</li>
<li><a href="https://github.com/VectifyAI/PageIndex">VectifyAI/PageIndex</a> ⭐35,291 — 无向量的推理式 RAG 文档索引</li>
<li><a href="https://github.com/qdrant/qdrant">qdrant/qdrant</a> ⭐34,124 — 大规模向量数据库与向量搜索引擎</li>
<li><a href="https://github.com/topoteretes/cognee">topoteretes/cognee</a> ⭐30,183 — 开源 AI 记忆平台（自托管知识图谱引擎）</li>
<li><a href="https://github.com/NirDiamant/RAG_Techniques">NirDiamant/RAG_Techniques</a> ⭐29,174 — RAG 高级技术笔记本合集</li>
<li><a href="https://github.com/weaviate/weaviate">weaviate/weaviate</a> ⭐16,746 — 开源向量数据库，向量搜索 + 结构化过滤</li>
<li><a href="https://github.com/memvid/memvid">memvid/memvid</a> ⭐16,437 — 用无服务器单文件记忆层替代复杂 RAG 管线</li>
<li><a href="https://github.com/alibaba/zvec">alibaba/zvec</a> ⭐15,502 — 轻量、极速的进程内向量数据库</li>
<li><a href="https://github.com/langchain4j/langchain4j">langchain4j/langchain4j</a> ⭐12,929 — JVM 上的 LLM 应用库，统一 provider 与向量库 API</li>
<li><a href="https://github.com/neuml/txtai">neuml/txtai</a> ⭐12,897 — 语义搜索、LLM 编排与语言模型工作流的一体化框架</li>
<li><a href="https://github.com/StarTrail-org/LEANN">StarTrail-org/LEANN</a> ⭐12,827 — [MLsys2026] 节省 97% 存储的本地私有 RAG</li>
</ul>
<h3>5. LLM 模型</h3>
<ul>
<li><a href="https://github.com/jingyaogong/minimind">jingyaogong/minimind</a> ⭐54,927 — 2 小时从零训练 64M 参数 LLM</li>
<li><a href="https://github.com/ScrapeGraphAI/Scrapegraph-ai">ScrapeGraphAI/Scrapegraph-ai</a> ⭐29,812 — 基于 AI 的 Python 爬虫</li>
<li><a href="https://github.com/The-Pocket/PocketFlow-Tutorial-Codebase-Knowledge">The-Pocket/PocketFlow-Tutorial-Codebase-Knowledge</a> ⭐12,630 — Codebase to Tutorial</li>
<li><a href="https://github.com/The-Pocket/PocketFlow">The-Pocket/PocketFlow</a> ⭐11,124 — 100 行 LLM 框架，让 agent 构建 agent</li>
<li><a href="https://github.com/OpenSPG/KAG">OpenSPG/KAG</a> ⭐9,004 — 逻辑形式引导的推理与检索框架</li>
<li><a href="https://github.com/0xPlaygrounds/rig">0xPlaygrounds/rig</a> ⭐8,358 — Rust 构建模块化可扩展 LLM 应用</li>
<li><a href="https://github.com/open-compass/opencompass">open-compass/opencompass</a> ⭐7,327 — LLM 评测平台，100+ 数据集</li>
<li><a href="https://github.com/InternLM/InternLM">InternLM/InternLM</a> ⭐7,266 — InternLM 系列官方发布</li>
<li><a href="https://github.com/Eigenwise/atomic-agents">Eigenwise/atomic-agents</a> ⭐6,191 — 原子化构建 AI agent</li>
<li><a href="https://github.com/gluonfield/enchanted">gluonfield/enchanted</a> ⭐5,998 — iOS/macOS 私有自托管模型聊天客户端</li>
<li><a href="https://github.com/skyzh/tiny-llm">skyzh/tiny-llm</a> ⭐4,513 — 在 Apple Silicon 上学 LLM 推理系统：造一个小 vLLM + Qwen</li>
<li><a href="https://github.com/verazuo/jailbreak_llms">verazuo/jailbreak_llms</a> ⭐3,791 — [CCS&#39;24] 15,140 条 ChatGPT prompt 数据集（含 1,405 条越狱 prompt）</li>
<li><a href="https://github.com/ridgerchu/matmulfreellm">ridgerchu/matmulfreellm</a> ⭐3,088 — 无矩阵乘法语言模型实现</li>
<li><a href="https://github.com/InternLM/InternLM-XComposer">InternLM/InternLM-XComposer</a> ⭐2,925 — 长时流式视音频交互的多模态系统</li>
<li><a href="https://github.com/JIA-Lab-research/LISA">JIA-Lab-research/LISA</a> ⭐2,671 — 用大语言模型做推理式分割</li>
</ul>
<h3>6. 机器学习</h3>
<ul>
<li><a href="https://github.com/tensorflow/tensorflow">tensorflow/tensorflow</a> ⭐197,323 — 人人可用的开源机器学习框架</li>
<li><a href="https://github.com/f/prompts.chat">f/prompts.chat</a> ⭐167,752 — Awesome ChatGPT Prompts</li>
<li><a href="https://github.com/huggingface/transformers">huggingface/transformers</a> ⭐164,339 — SOTA 机器学习模型框架</li>
<li><a href="https://github.com/rasbt/LLMs-from-scratch">rasbt/LLMs-from-scratch</a> ⭐103,224 — 从零逐步实现类 ChatGPT LLM</li>
<li><a href="https://github.com/pytorch/pytorch">pytorch/pytorch</a> ⭐102,543 — 带 GPU 加速的张量与动态神经网络</li>
<li><a href="https://github.com/microsoft/ML-For-Beginners">microsoft/ML-For-Beginners</a> ⭐89,682 — 12 周 26 课 52 测验的经典机器学习</li>
<li><a href="https://github.com/Developer-Y/cs-video-courses">Developer-Y/cs-video-courses</a> ⭐83,148 — 带视频讲座的 CS 课程清单</li>
<li><a href="https://github.com/mlabonne/llm-course">mlabonne/llm-course</a> ⭐81,915 — LLM 学习路线与 Colab 笔记本</li>
<li><a href="https://github.com/netdata/netdata">netdata/netdata</a> ⭐80,261 — 最快的 AI 驱动全栈可观测</li>
<li><a href="https://github.com/d2l-ai/d2l-zh">d2l-ai/d2l-zh</a> ⭐79,877 — 《动手学深度学习》中文版</li>
<li><a href="https://github.com/tesseract-ocr/tesseract">tesseract-ocr/tesseract</a> ⭐76,116 — Tesseract 开源 OCR 引擎</li>
<li><a href="https://github.com/binhnguyennus/awesome-scalability">binhnguyennus/awesome-scalability</a> ⭐73,459 — 大规模系统的可扩展性/可靠性/性能模式</li>
<li><a href="https://github.com/OpenBB-finance/OpenBB">OpenBB-finance/OpenBB</a> ⭐72,154 — 面向分析师、量化与 AI agent 的开放数据平台</li>
<li><a href="https://github.com/labmlai/annotated_deep_learning_paper_implementations">labmlai/annotated_deep_learning_paper_implementations</a> ⭐67,331 — 60+ 深度学习论文实现与逐行注释</li>
<li><a href="https://github.com/scikit-learn/scikit-learn">scikit-learn/scikit-learn</a> ⭐67,010 — Python 机器学习库</li>
</ul>
<h2>三、24 小时 Star 增量榜（与昨日快照对比）</h2>
<blockquote>
<p>说明：本表由 agents-radar 自身连续两日抓取的 star 快照相减得出，可视为「过去 24h 真实新增」。仅统计昨日日报中已出现的项目。</p>
</blockquote>
<table>
<thead>
<tr>
<th>排名</th>
<th>项目</th>
<th>昨日 ★</th>
<th>今日 ★</th>
<th>24h 增量</th>
</tr>
</thead>
<tbody><tr>
<td>1</td>
<td><a href="https://github.com/santifer/career-ops">santifer/career-ops</a></td>
<td>67,306</td>
<td>67,764</td>
<td><strong>+458</strong></td>
</tr>
<tr>
<td>2</td>
<td><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a></td>
<td>233,911</td>
<td>234,323</td>
<td><strong>+412</strong></td>
</tr>
<tr>
<td>3</td>
<td><a href="https://github.com/Graphify-Labs/graphify">Graphify-Labs/graphify</a></td>
<td>109,096</td>
<td>109,501</td>
<td><strong>+405</strong></td>
</tr>
<tr>
<td>4</td>
<td><a href="https://github.com/firecrawl/firecrawl">firecrawl/firecrawl</a></td>
<td>170,460</td>
<td>170,855</td>
<td><strong>+395</strong></td>
</tr>
<tr>
<td>5</td>
<td><a href="https://github.com/affaan-m/ECC">affaan-m/ECC</a></td>
<td>241,701</td>
<td>242,087</td>
<td><strong>+386</strong></td>
</tr>
<tr>
<td>6</td>
<td><a href="https://github.com/Panniantong/Agent-Reach">Panniantong/Agent-Reach</a></td>
<td>73,818</td>
<td>74,085</td>
<td>+267</td>
</tr>
<tr>
<td>7</td>
<td><a href="https://github.com/tensorflow/tensorflow">tensorflow/tensorflow</a></td>
<td>197,220</td>
<td>197,323</td>
<td>+103</td>
</tr>
<tr>
<td>8</td>
<td><a href="https://github.com/Shubhamsaboo/awesome-llm-apps">Shubhamsaboo/awesome-llm-apps</a></td>
<td>133,487</td>
<td>133,588</td>
<td>+101</td>
</tr>
<tr>
<td>9</td>
<td><a href="https://github.com/thedotmack/claude-mem">thedotmack/claude-mem</a></td>
<td>91,430</td>
<td>91,519</td>
<td>+89</td>
</tr>
<tr>
<td>10</td>
<td><a href="https://github.com/open-webui/open-webui">open-webui/open-webui</a></td>
<td>149,491</td>
<td>149,579</td>
<td>+88</td>
</tr>
<tr>
<td>11</td>
<td><a href="https://github.com/ollama/ollama">ollama/ollama</a></td>
<td>179,115</td>
<td>179,192</td>
<td>+77</td>
</tr>
<tr>
<td>12</td>
<td><a href="https://github.com/langgenius/dify">langgenius/dify</a></td>
<td>153,134</td>
<td>153,205</td>
<td>+71</td>
</tr>
<tr>
<td>13</td>
<td><a href="https://github.com/infiniflow/ragflow">infiniflow/ragflow</a></td>
<td>88,983</td>
<td>89,036</td>
<td>+53</td>
</tr>
<tr>
<td>14</td>
<td><a href="https://github.com/rasbt/LLMs-from-scratch">rasbt/LLMs-from-scratch</a></td>
<td>103,171</td>
<td>103,224</td>
<td>+53</td>
</tr>
<tr>
<td>15</td>
<td><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a></td>
<td>144,726</td>
<td>144,777</td>
<td>+51</td>
</tr>
</tbody></table>
<p><strong>读法</strong>：前五名里有四个是「agent 能力/上下文供给」类项目——career-ops（把 agent 用在求职）、hermes-agent、graphify（代码库转知识图谱）、ECC（harness 优化），只有 firecrawl 属于纯数据抓取基础设施。<strong>增量的钱在往&quot;怎么把 agent 用起来&quot;和&quot;给 agent 喂什么上下文&quot;两个方向走，而不是往模型本体走。</strong> 相比之下 pytorch（+26）、transformers（+29）、milvus（+8）、qdrant（+9）这些传统 ML/向量库的增速已经是前者的十分之一量级。</p>
<h2>四、趋势小结</h2>
<ul>
<li><strong>Codex 与 Claude Code 同日登榜，Codex 居首。</strong> 叠加 HN 头条与 Claude Code 侧 343👍 的吐槽 issue，<strong>这是今日最值得记录的生态位变化信号</strong>——不是某一个榜的偶然，而是 star、讨论、情绪三个独立维度同时指向同一方向。</li>
<li><strong>「Skills / harness 元层」已成为独立赛道且极度拥挤。</strong> Trending 前四有三席（mattpocock/skills、affaan-m/ECC、obra/superpowers），第 11 名是单个 <code>CLAUDE.md</code> 文件，第 15 名是 cursor/plugins。<strong>当&quot;经验沉淀&quot;本身可以成为爆款仓库，说明模型能力已不是瓶颈，怎么约束模型才是。</strong></li>
<li><strong>成本工程正式浮出水面。</strong> sub2api（订阅中转/拼车）+ free-for-dev（免费额度清单）+ headroom（进 LLM 前压缩 token，省 20–95%）+ DeepSeek-Reasonix（围绕前缀缓存稳定性设计）——<strong>四个项目从四个角度砍同一笔账单</strong>，与 CLI 侧 GPT-5.6 Sol 降价 20% 构成供需两端的同一个故事。</li>
<li><strong>记忆/上下文赛道持续加厚。</strong> claude-mem（+89）、graphify（+405）、mem0、cognee、memvid、LEANN、zvec 同屏，且 graphify 的增量排到全榜第 3。<strong>这与 OpenClaw 生态日报里&quot;性能债 = 重复重建&quot;、CLI 侧&quot;上下文压缩&quot;完全同源：上下文是当前最贵的资源，围绕它的工具化正在加速。</strong></li>
<li><strong>安全治理连续在榜。</strong> Tencent/AI-Infra-Guard 连续第二日入榜（Agent Scan / Skills Scan / MCP scan），与 Zeroclaw 的身份基础设施改造、Moltis 的 fail-closed hook、CoPaw 的第五安全层形成呼应——<strong>&quot;agent 有真实执行权&quot;的风险共识已经从框架内部扩散到工具链外部。</strong></li>
<li><strong>传统 ML 基础设施增速趋缓。</strong> pytorch +26 / transformers +29 / milvus +8 / qdrant +9，与 agent 层项目的 +400 量级差了一个数量级。<strong>注意力与新增关注度几乎全部集中在应用与 harness 层。</strong></li>
</ul>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，所有内容基于 GitHub 公开数据实时抓取并由执行代理人工撰写，未调用任何外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Open Source Trends 2026-08-23</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-trending-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-trending-en</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Open-Source AI Trends Daily — 2026-08-23 Generated: 2026-08-23 02:30 (GMT+8) Sources: GitHub Trending (daily) + gh search repos across 6 AI topics (sorted by stars, 7-day window) This digest is produced by the agents-radar local automation. All writing is done by the executing agent — no external LLM API was called. 1. GitHub Trending — Daily Risers (2026-08-23) Note: at fetch time the GitHub Trending page still did not expose &amp;quot;stars today&amp;quot; values (second consecutive day; likely an ano...</description>
      <content:encoded><![CDATA[<h1>Open-Source AI Trends Daily — 2026-08-23</h1>
<blockquote>
<p>Generated: 2026-08-23 02:30 (GMT+8)
Sources: GitHub Trending (daily) + <code>gh search repos</code> across 6 AI topics (sorted by stars, 7-day window)
This digest is produced by the agents-radar local automation. All writing is done by the executing agent — no external LLM API was called.</p>
</blockquote>
<hr>
<h2>1. GitHub Trending — Daily Risers (2026-08-23)</h2>
<blockquote>
<p>Note: at fetch time the GitHub Trending page still did not expose &quot;stars today&quot; values (second consecutive day; likely an anonymous-view or layout change), so the table below lists ranked entries and descriptions without star deltas. Order follows the page&#39;s original ranking.</p>
</blockquote>
<table>
<thead>
<tr>
<th>#</th>
<th>Project</th>
<th>Summary</th>
</tr>
</thead>
<tbody><tr>
<td>1</td>
<td><a href="https://github.com/openai/codex">openai/codex</a></td>
<td>Lightweight coding agent that runs in your terminal</td>
</tr>
<tr>
<td>2</td>
<td><a href="https://github.com/mattpocock/skills">mattpocock/skills</a></td>
<td>&quot;Skills for Real Engineers,&quot; straight from the author&#39;s <code>.agents</code> directory</td>
</tr>
<tr>
<td>3</td>
<td><a href="https://github.com/affaan-m/ECC">affaan-m/ECC</a></td>
<td>Agent-harness performance optimization system: skills, instincts, memory, security, research-first development for Claude Code, Codex, OpenCode, Cursor</td>
</tr>
<tr>
<td>4</td>
<td><a href="https://github.com/obra/superpowers">obra/superpowers</a></td>
<td>An agentic skills framework and software development methodology that works</td>
</tr>
<tr>
<td>5</td>
<td><a href="https://github.com/Wei-Shaw/sub2api">Wei-Shaw/sub2api</a></td>
<td>One-stop open-source relay unifying Claude / OpenAI / Gemini / Grok subscriptions, with shared/pooled access to split costs</td>
</tr>
<tr>
<td>6</td>
<td><a href="https://github.com/makeplane/plane">makeplane/plane</a></td>
<td>Open-source Jira / Linear / Monday / ClickUp alternative</td>
</tr>
<tr>
<td>7</td>
<td><a href="https://github.com/n8n-io/n8n">n8n-io/n8n</a></td>
<td>Fair-code workflow automation platform with native AI capabilities, 400+ integrations</td>
</tr>
<tr>
<td>8</td>
<td><a href="https://github.com/anthropics/claude-code">anthropics/claude-code</a></td>
<td>Agentic coding tool in your terminal that understands your codebase</td>
</tr>
<tr>
<td>9</td>
<td><a href="https://github.com/AprilNEA/OpenLogi">AprilNEA/OpenLogi</a></td>
<td>Native, local-first Logitech Options+ alternative written in Rust; no account, no telemetry</td>
</tr>
<tr>
<td>10</td>
<td><a href="https://github.com/modular/modular">modular/modular</a></td>
<td>The Modular Platform (includes MAX &amp; Mojo)</td>
</tr>
<tr>
<td>11</td>
<td><a href="https://github.com/multica-ai/andrej-karpathy-skills">multica-ai/andrej-karpathy-skills</a></td>
<td>A single CLAUDE.md file to improve Claude Code behavior, derived from Karpathy&#39;s observations on LLM coding pitfalls</td>
</tr>
<tr>
<td>12</td>
<td><a href="https://github.com/mahlernim/google-timeline-visualizer">mahlernim/google-timeline-visualizer</a></td>
<td>Visualize your year in travel from Google Location History</td>
</tr>
<tr>
<td>13</td>
<td><a href="https://github.com/ripienaar/free-for-dev">ripienaar/free-for-dev</a></td>
<td>A list of SaaS/PaaS/IaaS offerings with free tiers relevant to devops and infra</td>
</tr>
<tr>
<td>14</td>
<td><a href="https://github.com/microsoft/TypeScript">microsoft/TypeScript</a></td>
<td>The TypeScript language itself</td>
</tr>
<tr>
<td>15</td>
<td><a href="https://github.com/cursor/plugins">cursor/plugins</a></td>
<td>Cursor plugin specification and official plugins</td>
</tr>
<tr>
<td>16</td>
<td><a href="https://github.com/PostHog/posthog">PostHog/posthog</a></td>
<td>Platform for self-driving products (AI observability, analytics, session replay, flags)</td>
</tr>
<tr>
<td>17</td>
<td><a href="https://github.com/Tencent/AI-Infra-Guard">Tencent/AI-Infra-Guard</a></td>
<td>Full-stack AI red-teaming platform: Agent Scan / Skills Scan / MCP scan / AI Infra scan</td>
</tr>
</tbody></table>
<p><strong>The strongest signal today: Codex is #1 and Claude Code is #8 on the same board.</strong> This is a rare three-way resonance across all three digests — Trending #1 is <code>openai/codex</code>, today&#39;s top HN story is &quot;A week of using Codex more than Claude&quot; (94👍), and on the Claude Code side today&#39;s highest-heat issue <a href="https://github.com/anthropics/claude-code/issues/77136">#77136</a> (343👍) is a collective complaint about the model&#39;s verbal tics. <strong>Community attention is migrating from Claude Code toward Codex, and that migration shows up simultaneously in the star board, the discussion board, and the sentiment.</strong></p>
<p><strong>Second signal: the skills/harness meta-layer holds five slots.</strong> #2 mattpocock/skills, #3 affaan-m/ECC, #4 obra/superpowers, #11 multica-ai/andrej-karpathy-skills, and #15 cursor/plugins — <strong>three of the top four are projects that give agents capabilities rather than being agents themselves.</strong> Notably #11 is extreme in form: a single <code>CLAUDE.md</code> file, yet it trends. <strong>What is scarcest right now is not tooling but codified experience about how to make the model make fewer mistakes.</strong></p>
<p><strong>Third signal: cost anxiety has become explicit.</strong> #5 <code>Wei-Shaw/sub2api</code> unifies subscriptions and supports pooled/shared access to split costs; #13 <code>ripienaar/free-for-dev</code> is a free-tier catalogue. This shares a background with GPT-5.6 Sol&#39;s 20% price cut in today&#39;s CLI digest and the HN controversy over A/B-tested reduced reasoning effort — <strong>users&#39; monthly agent spend has reached the point where people build dedicated tooling to flatten it.</strong></p>
<h2>2. Six AI Topics by Stars (Top 15)</h2>
<h3>1. AI Agent Frameworks</h3>
<ul>
<li><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a> ⭐234,323 — The agent that grows with you</li>
<li><a href="https://github.com/shareAI-lab/learn-claude-code">shareAI-lab/learn-claude-code</a> ⭐74,949 — Build a nano claude-code-like agent harness from 0 to 1</li>
<li><a href="https://github.com/Panniantong/Agent-Reach">Panniantong/Agent-Reach</a> ⭐74,085 — Give your agent eyes on the whole internet (Twitter / Reddit / YouTube / GitHub / Bilibili / XiaoHongShu), one CLI, zero API fees</li>
<li><a href="https://github.com/thedaviddias/Front-End-Checklist">thedaviddias/Front-End-Checklist</a> ⭐73,609 — Essential checklist for modern web development, for humans and AI agents</li>
<li><a href="https://github.com/santifer/career-ops">santifer/career-ops</a> ⭐67,764 — Open-source AI job search: scan portals, A–F rubric scoring, tailor CVs, track applications, runs locally in your coding CLI</li>
<li><a href="https://github.com/ZhuLinsen/daily_stock_analysis">ZhuLinsen/daily_stock_analysis</a> ⭐63,624 — LLM-powered multi-market stock analysis with live news, dashboards, and automated notifications</li>
<li><a href="https://github.com/CherryHQ/cherry-studio">CherryHQ/cherry-studio</a> ⭐50,919 — AI productivity studio with 300+ assistants and unified frontier-LLM access</li>
<li><a href="https://github.com/hugohe3/ppt-master">hugohe3/ppt-master</a> ⭐48,617 — AI turns documents or topics into real native PowerPoint decks with shapes, transitions, charts, and narration</li>
<li><a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a> ⭐47,283 — Ultra-lightweight self-hosted personal AI agent framework (WebUI, tools, memory, MCP, multi-agent workflows)</li>
<li><a href="https://github.com/zhayujie/CowAgent">zhayujie/CowAgent</a> ⭐46,632 — Open-source super assistant and agent harness that self-evolves with memory and knowledge</li>
<li><a href="https://github.com/siyuan-note/siyuan">siyuan-note/siyuan</a> ⭐45,931 — Open-source, privacy-first, self-hosted knowledge workspace</li>
<li><a href="https://github.com/bojieli/ai-agent-book">bojieli/ai-agent-book</a> ⭐40,913 — Full text, compiled PDF, and per-chapter code for a book on AI agent design and engineering</li>
<li><a href="https://github.com/Hmbown/CodeWhale">Hmbown/CodeWhale</a> ⭐40,841 — Open-source terminal coding agent built in Rust</li>
<li><a href="https://github.com/CopilotKit/CopilotKit">CopilotKit/CopilotKit</a> ⭐36,960 — The frontend stack for agents and generative UI (makers of the AG-UI protocol)</li>
<li><a href="https://github.com/esengine/DeepSeek-Reasonix">esengine/DeepSeek-Reasonix</a> ⭐35,032 — DeepSeek-native terminal coding agent, engineered around prefix-cache stability</li>
</ul>
<h3>2. Large Language Models</h3>
<ul>
<li><a href="https://github.com/affaan-m/ECC">affaan-m/ECC</a> ⭐242,087 — Agent-harness performance optimization system</li>
<li><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a> ⭐234,323 — The agent that grows with you</li>
<li><a href="https://github.com/Significant-Gravitas/AutoGPT">Significant-Gravitas/AutoGPT</a> ⭐186,764 — Accessible AI for everyone</li>
<li><a href="https://github.com/ollama/ollama">ollama/ollama</a> ⭐179,192 — Run Kimi-K2.6 / GLM-5.2 / MiniMax / DeepSeek / gpt-oss / Qwen / Gemma locally</li>
<li><a href="https://github.com/firecrawl/firecrawl">firecrawl/firecrawl</a> ⭐170,855 — Context API to search, scrape, and interact with the web at scale</li>
<li><a href="https://github.com/f/prompts.chat">f/prompts.chat</a> ⭐167,752 — Community prompt sharing, self-hostable</li>
<li><a href="https://github.com/huggingface/transformers">huggingface/transformers</a> ⭐164,339 — Model-definition framework for text, vision, audio, multimodal</li>
<li><a href="https://github.com/langgenius/dify">langgenius/dify</a> ⭐153,205 — Agentic workflows and RAG pipelines on one workspace</li>
<li><a href="https://github.com/open-webui/open-webui">open-webui/open-webui</a> ⭐149,579 — User-friendly AI interface</li>
<li><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a> ⭐144,777 — The agent engineering platform</li>
<li><a href="https://github.com/harry0703/MoneyPrinterTurbo">harry0703/MoneyPrinterTurbo</a> ⭐114,563 — Generate HD short videos from a topic via an automated AI workflow</li>
<li><a href="https://github.com/browser-use/browser-use">browser-use/browser-use</a> ⭐110,116 — Make websites accessible for AI agents</li>
<li><a href="https://github.com/Graphify-Labs/graphify">Graphify-Labs/graphify</a> ⭐109,501 — Turn a codebase (docs, SQL schemas, configs, PDFs) into a queryable knowledge graph as a <code>/graphify</code> skill</li>
<li><a href="https://github.com/DietrichGebert/ponytail">DietrichGebert/ponytail</a> ⭐108,073 — Make your agent think like the laziest senior dev in the room: the best code is code you never wrote</li>
<li><a href="https://github.com/rasbt/LLMs-from-scratch">rasbt/LLMs-from-scratch</a> ⭐103,224 — Implement a ChatGPT-like LLM in PyTorch step by step</li>
</ul>
<h3>3. RAG (Retrieval-Augmented Generation)</h3>
<ul>
<li><a href="https://github.com/langgenius/dify">langgenius/dify</a> ⭐153,205 — Agentic workflows and RAG pipelines</li>
<li><a href="https://github.com/open-webui/open-webui">open-webui/open-webui</a> ⭐149,579 — User-friendly AI interface</li>
<li><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a> ⭐144,777 — The agent engineering platform</li>
<li><a href="https://github.com/Shubhamsaboo/awesome-llm-apps">Shubhamsaboo/awesome-llm-apps</a> ⭐133,588 — 100+ AI agents, agent skills, and RAG apps</li>
<li><a href="https://github.com/Graphify-Labs/graphify">Graphify-Labs/graphify</a> ⭐109,501 — Codebase to queryable knowledge graph, local deterministic parsing</li>
<li><a href="https://github.com/thedotmack/claude-mem">thedotmack/claude-mem</a> ⭐91,519 — Persistent cross-session context: capture, compress, and re-inject</li>
<li><a href="https://github.com/infiniflow/ragflow">infiniflow/ragflow</a> ⭐89,036 — Leading open-source RAG engine fused with agent capabilities</li>
<li><a href="https://github.com/PaddlePaddle/PaddleOCR">PaddlePaddle/PaddleOCR</a> ⭐88,110 — Lightweight OCR toolkit for 100+ languages, bridging images/PDFs and LLMs</li>
<li><a href="https://github.com/dair-ai/Prompt-Engineering-Guide">dair-ai/Prompt-Engineering-Guide</a> ⭐77,693 — Guides for prompt engineering, context engineering, RAG, and AI agents</li>
<li><a href="https://github.com/datawhalechina/hello-agents">datawhalechina/hello-agents</a> ⭐74,217 — Building agents from scratch: principles and practice</li>
<li><a href="https://github.com/headroomlabs-ai/headroom">headroomlabs-ai/headroom</a> ⭐67,179 — Compress tool outputs, logs, files, and RAG chunks before they reach the LLM: 20% fewer tokens for coding agents, 60–95% for JSON</li>
<li><a href="https://github.com/Mintplex-Labs/anything-llm">Mintplex-Labs/anything-llm</a> ⭐65,052 — Local-first, powerful agent experience</li>
<li><a href="https://github.com/mem0ai/mem0">mem0ai/mem0</a> ⭐63,821 — Universal memory layer for AI agents</li>
<li><a href="https://github.com/pathwaycom/llm-app">pathwaycom/llm-app</a> ⭐59,005 — Cloud templates for RAG, AI pipelines, and enterprise search</li>
<li><a href="https://github.com/FlowiseAI/Flowise">FlowiseAI/Flowise</a> ⭐55,383 — Build AI agents visually</li>
</ul>
<h3>4. Vector Databases</h3>
<ul>
<li><a href="https://github.com/Mintplex-Labs/anything-llm">Mintplex-Labs/anything-llm</a> ⭐65,052 — Local-first agent experience</li>
<li><a href="https://github.com/meilisearch/meilisearch">meilisearch/meilisearch</a> ⭐59,054 — Lightning-fast search API with AI hybrid search</li>
<li><a href="https://github.com/pathwaycom/llm-app">pathwaycom/llm-app</a> ⭐59,005 — Cloud templates for RAG and AI pipelines</li>
<li><a href="https://github.com/run-llama/llama_index">run-llama/llama_index</a> ⭐51,801 — Document agent and OCR platform</li>
<li><a href="https://github.com/milvus-io/milvus">milvus-io/milvus</a> ⭐45,736 — High-performance cloud-native vector database</li>
<li><a href="https://github.com/VectifyAI/PageIndex">VectifyAI/PageIndex</a> ⭐35,291 — Document index for vectorless, reasoning-based RAG</li>
<li><a href="https://github.com/qdrant/qdrant">qdrant/qdrant</a> ⭐34,124 — High-performance, massive-scale vector database and search engine</li>
<li><a href="https://github.com/topoteretes/cognee">topoteretes/cognee</a> ⭐30,183 — Open-source AI memory platform with a self-hosted knowledge-graph engine</li>
<li><a href="https://github.com/NirDiamant/RAG_Techniques">NirDiamant/RAG_Techniques</a> ⭐29,174 — Advanced RAG techniques with notebook tutorials</li>
<li><a href="https://github.com/weaviate/weaviate">weaviate/weaviate</a> ⭐16,746 — Open-source vector database combining vector search with structured filtering</li>
<li><a href="https://github.com/memvid/memvid">memvid/memvid</a> ⭐16,437 — Replace complex RAG pipelines with a serverless single-file memory layer</li>
<li><a href="https://github.com/alibaba/zvec">alibaba/zvec</a> ⭐15,502 — Lightweight, lightning-fast in-process vector database</li>
<li><a href="https://github.com/langchain4j/langchain4j">langchain4j/langchain4j</a> ⭐12,929 — Idiomatic Java library for LLM apps on the JVM with a unified provider and vector-store API</li>
<li><a href="https://github.com/neuml/txtai">neuml/txtai</a> ⭐12,897 — All-in-one framework for semantic search, LLM orchestration, and language-model workflows</li>
<li><a href="https://github.com/StarTrail-org/LEANN">StarTrail-org/LEANN</a> ⭐12,827 — [MLsys2026] Private on-device RAG with 97% storage savings</li>
</ul>
<h3>5. LLM Models</h3>
<ul>
<li><a href="https://github.com/jingyaogong/minimind">jingyaogong/minimind</a> ⭐54,927 — Train a 64M-parameter LLM from scratch in 2 hours</li>
<li><a href="https://github.com/ScrapeGraphAI/Scrapegraph-ai">ScrapeGraphAI/Scrapegraph-ai</a> ⭐29,812 — AI-based Python scraper</li>
<li><a href="https://github.com/The-Pocket/PocketFlow-Tutorial-Codebase-Knowledge">The-Pocket/PocketFlow-Tutorial-Codebase-Knowledge</a> ⭐12,630 — Codebase to tutorial</li>
<li><a href="https://github.com/The-Pocket/PocketFlow">The-Pocket/PocketFlow</a> ⭐11,124 — 100-line LLM framework; let agents build agents</li>
<li><a href="https://github.com/OpenSPG/KAG">OpenSPG/KAG</a> ⭐9,004 — Logical-form-guided reasoning and retrieval framework</li>
<li><a href="https://github.com/0xPlaygrounds/rig">0xPlaygrounds/rig</a> ⭐8,358 — Build modular, scalable LLM applications in Rust</li>
<li><a href="https://github.com/open-compass/opencompass">open-compass/opencompass</a> ⭐7,327 — LLM evaluation platform across 100+ datasets</li>
<li><a href="https://github.com/InternLM/InternLM">InternLM/InternLM</a> ⭐7,266 — Official InternLM series releases</li>
<li><a href="https://github.com/Eigenwise/atomic-agents">Eigenwise/atomic-agents</a> ⭐6,191 — Building AI agents atomically</li>
<li><a href="https://github.com/gluonfield/enchanted">gluonfield/enchanted</a> ⭐5,998 — iOS/macOS client for private self-hosted models</li>
<li><a href="https://github.com/skyzh/tiny-llm">skyzh/tiny-llm</a> ⭐4,513 — Learn LLM inference systems on Apple Silicon: build a tiny vLLM + Qwen</li>
<li><a href="https://github.com/verazuo/jailbreak_llms">verazuo/jailbreak_llms</a> ⭐3,791 — [CCS&#39;24] 15,140 ChatGPT prompts including 1,405 jailbreak prompts</li>
<li><a href="https://github.com/ridgerchu/matmulfreellm">ridgerchu/matmulfreellm</a> ⭐3,088 — Implementation of MatMul-free LM</li>
<li><a href="https://github.com/InternLM/InternLM-XComposer">InternLM/InternLM-XComposer</a> ⭐2,925 — Multimodal system for long-term streaming video and audio interaction</li>
<li><a href="https://github.com/JIA-Lab-research/LISA">JIA-Lab-research/LISA</a> ⭐2,671 — Reasoning segmentation via large language models</li>
</ul>
<h3>6. Machine Learning</h3>
<ul>
<li><a href="https://github.com/tensorflow/tensorflow">tensorflow/tensorflow</a> ⭐197,323 — Open-source machine learning framework for everyone</li>
<li><a href="https://github.com/f/prompts.chat">f/prompts.chat</a> ⭐167,752 — Community prompt sharing</li>
<li><a href="https://github.com/huggingface/transformers">huggingface/transformers</a> ⭐164,339 — State-of-the-art ML model framework</li>
<li><a href="https://github.com/rasbt/LLMs-from-scratch">rasbt/LLMs-from-scratch</a> ⭐103,224 — Implement a ChatGPT-like LLM step by step</li>
<li><a href="https://github.com/pytorch/pytorch">pytorch/pytorch</a> ⭐102,543 — Tensors and dynamic neural networks with GPU acceleration</li>
<li><a href="https://github.com/microsoft/ML-For-Beginners">microsoft/ML-For-Beginners</a> ⭐89,682 — 12 weeks, 26 lessons, 52 quizzes of classic ML</li>
<li><a href="https://github.com/Developer-Y/cs-video-courses">Developer-Y/cs-video-courses</a> ⭐83,148 — CS courses with video lectures</li>
<li><a href="https://github.com/mlabonne/llm-course">mlabonne/llm-course</a> ⭐81,915 — LLM roadmaps and Colab notebooks</li>
<li><a href="https://github.com/netdata/netdata">netdata/netdata</a> ⭐80,261 — Fastest path to AI-powered full-stack observability</li>
<li><a href="https://github.com/d2l-ai/d2l-zh">d2l-ai/d2l-zh</a> ⭐79,877 — Dive into Deep Learning, Chinese edition</li>
<li><a href="https://github.com/tesseract-ocr/tesseract">tesseract-ocr/tesseract</a> ⭐76,116 — Tesseract open-source OCR engine</li>
<li><a href="https://github.com/binhnguyennus/awesome-scalability">binhnguyennus/awesome-scalability</a> ⭐73,459 — Patterns of scalable, reliable, performant large-scale systems</li>
<li><a href="https://github.com/OpenBB-finance/OpenBB">OpenBB-finance/OpenBB</a> ⭐72,154 — Open data platform for analysts, quants, and AI agents</li>
<li><a href="https://github.com/labmlai/annotated_deep_learning_paper_implementations">labmlai/annotated_deep_learning_paper_implementations</a> ⭐67,331 — 60+ deep learning paper implementations with side-by-side notes</li>
<li><a href="https://github.com/scikit-learn/scikit-learn">scikit-learn/scikit-learn</a> ⭐67,010 — Machine learning in Python</li>
</ul>
<h2>3. 24-Hour Star Growth (vs. Yesterday&#39;s Snapshot)</h2>
<blockquote>
<p>Note: this table is computed by differencing agents-radar&#39;s own star snapshots from two consecutive days, so it reflects genuine 24h growth. Only projects that appeared in yesterday&#39;s digest are included.</p>
</blockquote>
<table>
<thead>
<tr>
<th>Rank</th>
<th>Project</th>
<th>Yesterday ★</th>
<th>Today ★</th>
<th>24h Δ</th>
</tr>
</thead>
<tbody><tr>
<td>1</td>
<td><a href="https://github.com/santifer/career-ops">santifer/career-ops</a></td>
<td>67,306</td>
<td>67,764</td>
<td><strong>+458</strong></td>
</tr>
<tr>
<td>2</td>
<td><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a></td>
<td>233,911</td>
<td>234,323</td>
<td><strong>+412</strong></td>
</tr>
<tr>
<td>3</td>
<td><a href="https://github.com/Graphify-Labs/graphify">Graphify-Labs/graphify</a></td>
<td>109,096</td>
<td>109,501</td>
<td><strong>+405</strong></td>
</tr>
<tr>
<td>4</td>
<td><a href="https://github.com/firecrawl/firecrawl">firecrawl/firecrawl</a></td>
<td>170,460</td>
<td>170,855</td>
<td><strong>+395</strong></td>
</tr>
<tr>
<td>5</td>
<td><a href="https://github.com/affaan-m/ECC">affaan-m/ECC</a></td>
<td>241,701</td>
<td>242,087</td>
<td><strong>+386</strong></td>
</tr>
<tr>
<td>6</td>
<td><a href="https://github.com/Panniantong/Agent-Reach">Panniantong/Agent-Reach</a></td>
<td>73,818</td>
<td>74,085</td>
<td>+267</td>
</tr>
<tr>
<td>7</td>
<td><a href="https://github.com/tensorflow/tensorflow">tensorflow/tensorflow</a></td>
<td>197,220</td>
<td>197,323</td>
<td>+103</td>
</tr>
<tr>
<td>8</td>
<td><a href="https://github.com/Shubhamsaboo/awesome-llm-apps">Shubhamsaboo/awesome-llm-apps</a></td>
<td>133,487</td>
<td>133,588</td>
<td>+101</td>
</tr>
<tr>
<td>9</td>
<td><a href="https://github.com/thedotmack/claude-mem">thedotmack/claude-mem</a></td>
<td>91,430</td>
<td>91,519</td>
<td>+89</td>
</tr>
<tr>
<td>10</td>
<td><a href="https://github.com/open-webui/open-webui">open-webui/open-webui</a></td>
<td>149,491</td>
<td>149,579</td>
<td>+88</td>
</tr>
<tr>
<td>11</td>
<td><a href="https://github.com/ollama/ollama">ollama/ollama</a></td>
<td>179,115</td>
<td>179,192</td>
<td>+77</td>
</tr>
<tr>
<td>12</td>
<td><a href="https://github.com/langgenius/dify">langgenius/dify</a></td>
<td>153,134</td>
<td>153,205</td>
<td>+71</td>
</tr>
<tr>
<td>13</td>
<td><a href="https://github.com/infiniflow/ragflow">infiniflow/ragflow</a></td>
<td>88,983</td>
<td>89,036</td>
<td>+53</td>
</tr>
<tr>
<td>14</td>
<td><a href="https://github.com/rasbt/LLMs-from-scratch">rasbt/LLMs-from-scratch</a></td>
<td>103,171</td>
<td>103,224</td>
<td>+53</td>
</tr>
<tr>
<td>15</td>
<td><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a></td>
<td>144,726</td>
<td>144,777</td>
<td>+51</td>
</tr>
</tbody></table>
<p><strong>How to read this</strong>: four of the top five are &quot;agent capability / context supply&quot; projects — career-ops (agents applied to job search), hermes-agent, graphify (codebase to knowledge graph), and ECC (harness optimization); only firecrawl is pure data-fetch infrastructure. <strong>New attention is flowing toward &quot;how do I actually use an agent&quot; and &quot;what context do I feed it,&quot; not toward the models themselves.</strong> By contrast pytorch (+26), transformers (+29), milvus (+8), and qdrant (+9) are growing an order of magnitude slower.</p>
<h2>4. Trend Summary</h2>
<ul>
<li><strong>Codex and Claude Code both trended today, with Codex on top.</strong> Combined with the top HN story and the 343👍 complaint issue on the Claude Code side, <strong>this is today&#39;s most notable positional shift</strong> — not one board&#39;s noise, but stars, discussion, and sentiment pointing the same direction at once.</li>
<li><strong>The skills/harness meta-layer is now its own crowded category.</strong> Three of the top four (mattpocock/skills, affaan-m/ECC, obra/superpowers), plus a single <code>CLAUDE.md</code> at #11 and cursor/plugins at #15. <strong>When codified experience alone can trend, model capability is no longer the bottleneck — constraining the model is.</strong></li>
<li><strong>Cost engineering has surfaced.</strong> sub2api (subscription relay and pooling) + free-for-dev (free tiers) + headroom (compress tokens before the LLM, 20–95% savings) + DeepSeek-Reasonix (engineered around prefix-cache stability) — <strong>four projects attacking the same bill from four angles</strong>, the demand-side counterpart to GPT-5.6 Sol&#39;s 20% price cut on the supply side.</li>
<li><strong>The memory/context lane keeps thickening.</strong> claude-mem (+89), graphify (+405), mem0, cognee, memvid, LEANN, and zvec all appear together, and graphify&#39;s growth ranks third overall. <strong>Same root as &quot;performance debt = redundant rebuilds&quot; in the OpenClaw digest and &quot;context compaction&quot; on the CLI side: context is the most expensive resource right now, and tooling around it is accelerating.</strong></li>
<li><strong>Security governance trends for a second day.</strong> Tencent/AI-Infra-Guard (Agent Scan / Skills Scan / MCP scan) echoes Zeroclaw&#39;s identity-infrastructure rework, Moltis&#39;s fail-closed hook, and CoPaw&#39;s fifth security layer — <strong>the consensus that &quot;agents hold real execution power&quot; has spread from inside frameworks out to the tooling ecosystem.</strong></li>
<li><strong>Traditional ML infrastructure growth is flattening.</strong> pytorch +26 / transformers +29 / milvus +8 / qdrant +9 versus +400-scale growth in agent-layer projects — <strong>attention and new interest are concentrated almost entirely at the application and harness layers.</strong></li>
</ul>
<hr>
<p><em>This digest is generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. All content is fetched live from public GitHub data and written by the executing agent — no external LLM was called.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>Hacker News AI 社区动态日报 2026-08-23</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-hn</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-hn</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Hacker News AI 每日精选 2026-08-23 生成时间: 2026-08-23 02:30 (GMT+8) 数据来源：HN Algolia Search API（6 个查询：AI / LLM / Claude / OpenAI / Anthropic / machine learning，近 24h，去重后按 points 排序 Top 30；本批次共 75 条 unique 故事） 本日报由 agents-radar 本地自动化生成，所有内容由执行代理人工撰写，未调用任何外部大模型 API。 1. AI 编程智能体：Codex 与 Claude 的此消彼长 Codex 使用一周速写：用 Codex 多过 Claude (94👍 / 104💬) — speckx 一篇「用 Codex 多于 Claude 的一周」体验文登顶本批次，评论破百。这是 CLI 日报与 Trending 榜「Codex 反超 Claude Code」（Trending #1）叙事在 HN 侧的强佐证：社区对 Codex 的实战评价正在快速升温。 Anthropic 疑似在 Claude Co...</description>
      <content:encoded><![CDATA[<h1>Hacker News AI 每日精选 2026-08-23</h1>
<blockquote>
<p>生成时间: 2026-08-23 02:30 (GMT+8)
数据来源：HN Algolia Search API（6 个查询：AI / LLM / Claude / OpenAI / Anthropic / machine learning，近 24h，去重后按 points 排序 Top 30；本批次共 75 条 unique 故事）
本日报由 agents-radar 本地自动化生成，所有内容由执行代理人工撰写，未调用任何外部大模型 API。</p>
</blockquote>
<hr>
<h2>1. AI 编程智能体：Codex 与 Claude 的此消彼长</h2>
<ul>
<li><strong><a href="https://allaboutcoding.ghinda.com/a-week-of-using-codex-more-than-claude/">Codex 使用一周速写：用 Codex 多过 Claude</a></strong> (94👍 / 104💬) — speckx 一篇「用 Codex 多于 Claude 的一周」体验文登顶本批次，评论破百。这是 CLI 日报与 Trending 榜「Codex 反超 Claude Code」（Trending #1）叙事在 HN 侧的强佐证：社区对 Codex 的实战评价正在快速升温。</li>
<li><strong><a href="https://twitter.com/argofowl/status/2091150597374537729">Anthropic 疑似在 Claude Code 中 A/B 测试「降低 effort 级别」</a></strong> (51👍 / 45💬) — argofowl 的推文引爆社区，用户质疑「是否悄悄降级了模型投入」。与 Codex 的势头形成对照，Claude Code 正面临「投入缩水」的信任拷问。</li>
<li><strong><a href="https://github.com/gtapps/claude-code-hermit/">把 Claude Code 变成 24/7 智能体</a></strong> (3👍 / 1💬) — gtapps 开源项目，让 Claude Code 常驻运行，呼应「智能体全天候化」主线。</li>
<li><strong><a href="https://frigade.com/blog/we-replaced-grafana-with-a-claude-code-skill">我们用一个 Claude Code skill 替换了整套 Grafana 栈</a></strong> (3👍 / 0💬) — Frigade 的实践文，展示「用单个 skill 收敛可观测性工具链」的极简思路。</li>
</ul>
<h2>2. OpenAI 降价与资本动作</h2>
<ul>
<li><strong><a href="https://developers.openai.com/api/docs/models/gpt-5.6-sol">GPT-5.6 Sol 降价 20%</a></strong> (83👍 / 76💬) — OpenAI 开发者文档更新模型定价，引发热烈讨论（76 条评论），本批次第二高热度。</li>
<li><strong><a href="https://www.reuters.com/technology/openai-cuts-developer-pricing-frontier-gpt-56-sol-model-by-more-than-20-2026-08-21/">OpenAI 将前沿 GPT-5.6 Sol 模型的开发者定价下调超 20%</a></strong> (35👍 / 3💬) — Reuters 报道，官方动作获主流媒体确认。</li>
<li><strong><a href="https://twitter.com/OpenAI/status/2090885187634905500">OpenAI：GPT-5.6 Sol 的 API 与额度定价下调超 20%</a></strong> (10👍 / 5💬) — OpenAI 官方推文，与文档更新、Reuters 报道三处呼应，降价信号一致且密集。</li>
<li><strong><a href="https://www.instantdb.com/essays/instant_team_joins_openai">The Instant 团队加入 OpenAI</a></strong> (13👍 / 8💬) — instantdb 公告，人才向头部实验室聚拢的又一例。</li>
</ul>
<h2>3. Anthropic：IPO、安全能力与版权</h2>
<ul>
<li><strong><a href="https://claude.com/blog/bringing-claude-mythos-5-to-more-defenders">将 Claude Mythos 5 的网络安全能力带给更多防御者</a></strong> (47👍 / 51💬) — Anthropic 官方博客，把前沿模型的安全能力下沉到更多安全团队，讨论度可观。</li>
<li><strong><a href="https://www.cnbc.com/2026/08/21/-anthropic-ipo-filing-will-show-ai-backlash-as-risk-sources-say.html">Anthropic IPO 文件将把「AI backlash」列为风险因素</a></strong> (32👍 / 51💬) — CNBC 援引消息人士，AI 反弹首次作为上市风险因素被正式写入文件，监管与舆论风险进入资本叙事。</li>
<li><strong><a href="https://www.heise.de/en/news/Rights-infringing-copies-of-NEINhorn-Carlsen-sues-OpenAI-11420677.html">Carlsen 起诉 OpenAI 侵权复制「NEINhorn」</a></strong> (4👍 / 0💬) — heise 报道，版权诉讼继续蔓延至棋类内容生成。</li>
<li><strong><a href="https://news.mit.edu/2026/when-ai-art-has-no-author-generated-images-often-cant-be-traced-to-training-data-0818">当 AI 艺术「没有作者」：生成图常常无法溯源至训练数据（研究）</a></strong> (3👍 / 0💬) — MIT News 报道的研究，直指生成式图像的版权溯源困境。</li>
<li><strong><a href="https://code.claude.com/docs/en/output-styles">Claude 提供「Concise」输出风格</a></strong> (4👍 / 1💬) — code.claude.com 文档，模型新增精简输出档位，回应社区对冗长回复的审美疲劳。</li>
</ul>
<h2>4. Show HN 与开发者工具</h2>
<ul>
<li><strong><a href="https://ozbrain.com">Show HN: OzBrain —— 智能体与团队之间的共享「大脑」</a></strong> (72👍 / 45💬) — dariusmonsef 的项目，在智能体与团队知识间做共享层，本批次第三高热度，呼应「智能体记忆/知识复用」主线。</li>
<li><strong><a href="https://ringlochid.me/imagesage/index.html">Show HN: 用私有本地 AI 查找并整理照片</a></strong> (3👍 / 0💬) — 本地隐私优先的图像管理工具。</li>
<li><strong><a href="https://riyadhtechweek.com/">Show HN: Riyadh Tech Week —— 沙特科技生态全年导览</a></strong> (3👍 / 0💬) — 区域性科技活动聚合站。</li>
<li><strong><a href="https://www.netic.ai/blog/replacing-node-agent-graph-with-open-source-llm">用单个开源 LLM 替换 223 节点的智能体图</a></strong> (3👍 / 1💬) — netic.ai 的实践，主张「少而精的单模型」优于庞杂的多智能体编排。</li>
</ul>
<h2>5. 成本、可信与安全治理</h2>
<ul>
<li><strong><a href="https://deepsql.ai/blog/giving-an-llm-your-database-is-easy-taking-access-away-is-hard">给 LLM 你的生产数据库很容易，收回权限才是难点</a></strong> (4👍 / 5💬) — deepsql.ai 博客，点出「授权易、回收难」的运维现实，与 agents 日报的「权限治理」主线呼应。</li>
<li><strong><a href="https://syntheticauth.ai/posts/agent-nation-03-the-threshold">AI 智能体合并了两种曾被分开的危险：触达与判断</a></strong> (3👍 / 1💬) — syntheticauth 的观点文，讨论智能体同时握有「执行触达」与「自主判断」后的新风险面。</li>
<li><strong><a href="https://arxiv.org/abs/2608.13573">一年 LLM Serving：负载演化、缓存与负载均衡</a></strong> (4👍 / 0💬) — arXiv 论文，系统侧讨论推理服务的工程演进。</li>
<li><strong><a href="https://hotcrp.com/news/2026/ai-agents-202608">AI 代理与机器人账号（HotCRP）</a></strong> (3👍 / 0💬) — 学术会议系统 HotCRP 谈论文评审中的 AI 代理/机器人账号治理。</li>
</ul>
<h2>6. 社会、学术与其他</h2>
<ul>
<li><strong><a href="https://www.theguardian.com/technology/2026/aug/22/the-hollywood-creatives-training-ai-to-do-their-jobs">为好莱坞创意工作者「掘墓」：他们正在训练 AI 来做自己的工作</a></strong> (46👍 / 61💬) — Guardian 深度报道，创意劳动者用 AI 自我替代的悖论，本批次讨论量第四。</li>
<li><strong><a href="https://www.zdnet.com/article/80-of-developers-find-ai-coding-more-addictive-than-helpful/">80% 开发者觉得 AI 编程比「有用」更「上瘾」</a></strong> (9👍 / 0💬) — ZDNet 调查，AI 编程工具的黏性与依赖性引发关注。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49397022">Ask HN: 关于 AI 股市泡沫，证据有哪些？</a></strong> (9👍 / 7💬) — 社区对 AI 估值泡沫的审慎讨论。</li>
<li><strong><a href="https://cen.acs.org/biological-chemistry/genomics/single-complete-diploid-human-genome/104/web/2026/08">新人类基因组几乎无缺口</a></strong> (6👍 / 0💬) — C&amp;EN 报道首个近乎完整的二倍体人类基因组。</li>
<li><strong><a href="https://aengelke.net/llvm23-ct.html">LLVM 23 的编译期改进</a></strong> (3👍 / 0💬) — 编译器底层性能演进。</li>
<li><strong><a href="https://en.wikipedia.org/wiki/Limnic_eruption">湖泊喷发（Limnic Eruption）</a></strong> (3👍 / 0💬) — 科普条目。</li>
<li><strong><a href="https://lemire.me/blog/2026/08/02/how-fast-is-c26s-stdhive/">C++26 的 std::hive 有多快</a></strong> (3👍 / 1💬) — 性能基准实测。</li>
<li><strong><a href="https://lumilanguage.com/">个性化语言学习</a></strong> (3👍 / 0💬) — 语言学习产品。</li>
<li><strong><a href="https://ourworldindata.org/data-insights/air-conditioning-is-almost-universal-in-the-us-and-japan-but-not-elsewhere">空调在美国与日本几乎普及，但其他地区不是</a></strong> (3👍 / 1💬) — Our World in Data 的数据洞察。</li>
</ul>
<h2>趋势小结</h2>
<ul>
<li><strong>Codex 反超 Claude 成为本日最强主线</strong>：HN 登顶文「用 Codex 多过 Claude 的一周」（94👍/104💬）与 Trending 榜 Codex #1、Claude Code #8 互相印证；而 Anthropic 被曝「A/B 测试降低 Claude Code effort」（51👍/45💬）则给这股势头添了信任阴影。</li>
<li><strong>降价密集但叙事分裂</strong>：OpenAI GPT-5.6 Sol 在文档、官方推文、Reuters 三处同步降价超 20%（83👍 领跑），但「AI 股市泡沫」(Ask HN 9👍/7💬) 与「80% 开发者觉得上瘾而非有用」(9👍) 显示社区对估值与依赖性的双重保留。</li>
<li><strong>智能体治理进入实操层</strong>：从「给 LLM 生产库易收回难」(4👍)、HotCRP 的机器人账号治理、到「智能体合并触达与判断两种危险」，权限与身份治理正从口号走向工程细节。</li>
<li><strong>版权与 IP 持续升温</strong>：Carlsen 诉 OpenAI、MIT「AI 艺术无作者」研究、好莱坞创意者训练 AI 自替代——创作权属与替代焦虑交织。</li>
</ul>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，所有内容基于 HN Algolia API 实时抓取并由执行代理人工撰写，未调用任何外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>Hacker News AI Community Digest 2026-08-23</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-hn-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-23/ai-hn-en</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Hacker News AI Daily — 2026-08-23 Generated: 2026-08-23 02:30 (GMT+8) Source: HN Algolia Search API (6 queries: AI / LLM / Claude / OpenAI / Anthropic / machine learning, last 24h, deduped, Top 30 by points; 75 unique stories this batch) This digest is produced by the agents-radar local automation. All writing is done by the executing agent — no external LLM API was called. 1. AI Coding Agents: Codex vs. Claude Quick impressions: A week of using Codex more than Claude (94👍 / 104💬) — speckx&amp;#39...</description>
      <content:encoded><![CDATA[<h1>Hacker News AI Daily — 2026-08-23</h1>
<blockquote>
<p>Generated: 2026-08-23 02:30 (GMT+8)
Source: HN Algolia Search API (6 queries: AI / LLM / Claude / OpenAI / Anthropic / machine learning, last 24h, deduped, Top 30 by points; 75 unique stories this batch)
This digest is produced by the agents-radar local automation. All writing is done by the executing agent — no external LLM API was called.</p>
</blockquote>
<hr>
<h2>1. AI Coding Agents: Codex vs. Claude</h2>
<ul>
<li><strong><a href="https://allaboutcoding.ghinda.com/a-week-of-using-codex-more-than-claude/">Quick impressions: A week of using Codex more than Claude</a></strong> (94👍 / 104💬) — speckx&#39;s write-up of a week leaning on Codex over Claude tops this batch with 100+ comments. It&#39;s the HN-side confirmation of the &quot;Codex overtaking Claude Code&quot; narrative seen in today&#39;s CLI and Trending digests (Codex #1 on Trending) — community field reports on Codex are heating up fast.</li>
<li><strong><a href="https://twitter.com/argofowl/status/2091150597374537729">Anthropic appears to be A/B testing reduced effort levels in Claude Code</a></strong> (51👍 / 45💬) — argofowl&#39;s tweet went off, with users suspecting a &quot;quiet downgrade&quot; of model effort. Against Codex&#39;s momentum, Claude Code now faces a trust question about &quot;shrinking投入&quot;.</li>
<li><strong><a href="https://github.com/gtapps/claude-code-hermit/">Turn Claude Code into a 24/7 Agent</a></strong> (3👍 / 1💬) — gtapps&#39; OSS project keeps Claude Code running around the clock, echoing the &quot;always-on agent&quot;主线.</li>
<li><strong><a href="https://frigade.com/blog/we-replaced-grafana-with-a-claude-code-skill">We replaced our Grafana stack with a single Claude Code skill</a></strong> (3👍 / 0💬) — Frigade&#39;s field report showing how a single skill can collapse an entire observability toolchain.</li>
</ul>
<h2>2. OpenAI Pricing Cuts &amp; Talent Moves</h2>
<ul>
<li><strong><a href="https://developers.openai.com/api/docs/models/gpt-5.6-sol">GPT 5.6 Sol 20% price reduction</a></strong> (83👍 / 76💬) — OpenAI&#39;s developer docs updated model pricing, sparking a lively 76-comment thread — the second-hottest item this batch.</li>
<li><strong><a href="https://www.reuters.com/technology/openai-cuts-developer-pricing-frontier-gpt-56-sol-model-by-more-than-20-2026-08-21/">OpenAI cuts developer pricing for frontier GPT-5.6 Sol model by more than 20%</a></strong> (35👍 / 3💬) — Reuters coverage confirming the official move.</li>
<li><strong><a href="https://twitter.com/OpenAI/status/2090885187634905500">OpenAI: We&#39;re dropping API and credit pricing of GPT-5.6 Sol by over 20%</a></strong> (10👍 / 5💬) — OpenAI&#39;s official tweet, tri-synced with the docs update and Reuters — a consistent, dense price-cut signal.</li>
<li><strong><a href="https://www.instantdb.com/essays/instant_team_joins_openai">The Instant team joins OpenAI</a></strong> (13👍 / 8💬) — instantdb announcement, another case of talent consolidating toward the top labs.</li>
</ul>
<h2>3. Anthropic: IPO, Safety, &amp; Copyright</h2>
<ul>
<li><strong><a href="https://claude.com/blog/bringing-claude-mythos-5-to-more-defenders">Bringing the cybersecurity capabilities of Claude Mythos 5 to more defenders</a></strong> (47👍 / 51💬) — Anthropic&#39;s official blog pushing frontier-model safety capabilities down to more security teams; solid discussion.</li>
<li><strong><a href="https://www.cnbc.com/2026/08/21/-anthropic-ipo-filing-will-show-ai-backlash-as-risk-sources-say.html">Anthropic IPO filing will show AI backlash as a risk factor, sources say</a></strong> (32👍 / 51💬) — CNBC, citing sources, reports &quot;AI backlash&quot; being formally written into the IPO risk section for the first time — regulatory and public-opinion risk entering the capital narrative.</li>
<li><strong><a href="https://www.heise.de/en/news/Rights-infringing-copies-of-NEINhorn-Carlsen-sues-OpenAI-11420677.html">Rights-infringing copies of &quot;NEINhorn&quot;: Carlsen sues OpenAI</a></strong> (4👍 / 0💬) — heise reports copyright litigation spreading to chess-content generation.</li>
<li><strong><a href="https://news.mit.edu/2026/when-ai-art-has-no-author-generated-images-often-cant-be-traced-to-training-data-0818">When AI art has no author: Generated images can&#39;t trace to training data (study)</a></strong> (3👍 / 0💬) — MIT News on a study exposing the provenance gap in generative imagery.</li>
<li><strong><a href="https://code.claude.com/docs/en/output-styles">Claude has a &quot;Concise&quot; output style</a></strong> (4👍 / 1💬) — code.claude.com docs add a concise output tier, answering community fatigue with verbose replies.</li>
</ul>
<h2>4. Show HN &amp; Developer Tools</h2>
<ul>
<li><strong><a href="https://ozbrain.com">Show HN: OzBrain, a shared brain for knowledge between agents and your team</a></strong> (72👍 / 45💬) — dariusmonsef&#39;s project building a shared knowledge layer between agents and teams; third-hottest this batch, echoing the &quot;agent memory / knowledge reuse&quot;主线.</li>
<li><strong><a href="https://ringlochid.me/imagesage/index.html">Show HN: Find and Organize Photos with Private, Local AI</a></strong> (3👍 / 0💬) — A local, privacy-first image-management tool.</li>
<li><strong><a href="https://riyadhtechweek.com/">Show HN: Riyadh Tech Week – a year-round guide to Saudi Arabia&#39;s tech ecosystem</a></strong> (3👍 / 0💬) — A regional tech-event aggregator.</li>
<li><strong><a href="https://www.netic.ai/blog/replacing-node-agent-graph-with-open-source-llm">Replacing 223-node agent graph with a single OSS LLM</a></strong> (3👍 / 1💬) — netic.ai argues a &quot;small, sharp single model&quot; beats sprawling multi-agent orchestration.</li>
</ul>
<h2>5. Cost, Trust &amp; Security Governance</h2>
<ul>
<li><strong><a href="https://deepsql.ai/blog/giving-an-llm-your-database-is-easy-taking-access-away-is-hard">Giving an LLM your prod database is easy. Taking access away is the hard part</a></strong> (4👍 / 5💬) — deepsql.ai points at the &quot;grant-is-easy, revoke-is-hard&quot; ops reality, resonating with the agents digest&#39;s &quot;permission governance&quot;主线.</li>
<li><strong><a href="https://syntheticauth.ai/posts/agent-nation-03-the-threshold">AI agents merged two dangers once kept separate: reach and judgment</a></strong> (3👍 / 1💬) — syntheticauth on the new risk surface when agents hold both &quot;execution reach&quot; and &quot;autonomous judgment&quot;.</li>
<li><strong><a href="https://arxiv.org/abs/2608.13573">A Year in LLM Serving: Workload Evolution, Caching and Load-Balancing</a></strong> (4👍 / 0💬) — arXiv paper on the systems-side evolution of inference serving.</li>
<li><strong><a href="https://hotcrp.com/news/2026/ai-agents-202608">Hotcrp.com – AI agents and bot accounts</a></strong> (3👍 / 0💬) — Conference system HotCRP on governing AI agents / bot accounts in paper review.</li>
</ul>
<h2>6. Society, Academia &amp; Misc</h2>
<ul>
<li><strong><a href="https://www.theguardian.com/technology/2026/aug/22/the-hollywood-creatives-training-ai-to-do-their-jobs">Digging the grave of my skills: Hollywood creatives training AI to do their jobs</a></strong> (46👍 / 61💬) — Guardian long-read on the paradox of creative laborers training AI to replace themselves; fourth by discussion volume.</li>
<li><strong><a href="https://www.zdnet.com/article/80-of-developers-find-ai-coding-more-addictive-than-helpful/">80% of developers find AI coding more addictive than helpful</a></strong> (9👍 / 0💬) — ZDNet survey flags stickiness and dependency on AI coding tools.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49397022">Ask HN: What is the evidence for a stock market bubble in AI?</a></strong> (9👍 / 7💬) — Community caution on AI valuation froth.</li>
<li><strong><a href="https://cen.acs.org/biological-chemistry/genomics/single-complete-diploid-human-genome/104/web/2026/08">New human genome has almost no gaps</a></strong> (6👍 / 0💬) — C&amp;EN on the first near-complete diploid human genome.</li>
<li><strong>the rest (≤3👍):</strong> LLVM 23 compile-time improvements (3👍), Limnic Eruption (3👍), How fast is C++26&#39;s std::hive? (3👍/1💬), Personalized Language Learning (3👍), Air Conditioning is almost universal in US/Japan but not elsewhere (3👍/1💬).</li>
</ul>
<h2>Trend Takeaways</h2>
<ul>
<li><strong>Codex overtaking Claude is the day&#39;s strongest thread</strong>: the HN-topping &quot;week of using Codex more than Claude&quot; (94👍/104💬) cross-confirms Trending&#39;s Codex #1 / Claude Code #8; meanwhile Anthropic&#39;s alleged &quot;reduced effort A/B test in Claude Code&quot; (51👍/45💬) casts a trust shadow over that momentum.</li>
<li><strong>Dense price cuts, split narrative</strong>: OpenAI&#39;s GPT-5.6 Sol cut &gt;20% syncs across docs, official tweet, and Reuters (83👍 leads), yet &quot;AI stock bubble&quot; (Ask HN 9👍/7💬) and &quot;80% find AI coding addictive not helpful&quot; (9👍) show dual community reservations on valuation and dependency.</li>
<li><strong>Agent governance goes operational</strong>: from &quot;prod DB grant-is-easy/revoke-is-hard&quot; (4👍) to HotCRP&#39;s bot-account governance to &quot;agents merge reach + judgment&quot; — permission and identity governance are moving from slogans to engineering细节.</li>
<li><strong>Copyright &amp; IP keep heating up</strong>: Carlsen v. OpenAI, MIT&#39;s &quot;AI art has no author&quot; study, and Hollywood creatives training AI to self-replace — authorship and displacement anxiety intertwine.</li>
</ul>
<hr>
<p><em>This digest is generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. All content is fetched live from the HN Algolia API and written by the executing agent — no external LLM was called.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI CLI 工具社区动态日报 2026-08-22</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-cli</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-cli</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
      <description>AI CLI 工具社区动态日报 2026-08-22 生成时间: 2026-08-22 02:30 (GMT+8) | 覆盖工具: 7 个 CLI + Claude Code Skills 本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。 Claude Code OpenAI Codex Gemini CLI GitHub Copilot CLI Kimi Code CLI OpenCode Qwen Code Claude Code Skills 横向对比 AI CLI 工具社区动态横向对比分析报告（2026-08-22） 1. 生态全景 今日 AI CLI 赛道呈现「两端分化」：一端是 OpenCode（78 PR）与 Qwen Code（82 PR） 的社区贡献洪流，另一端是 Claude Code 与 Kimi Code 的近静默——Claude Code 近 24h 0 条 PR 合入、Kimi Code 仅 1 条 issue。OpenAI Codex 则集中在 alpha 系列快速迭代（rust-...</description>
      <content:encoded><![CDATA[<h1>AI CLI 工具社区动态日报 2026-08-22</h1>
<blockquote>
<p>生成时间: 2026-08-22 02:30 (GMT+8) | 覆盖工具: 7 个 CLI + Claude Code Skills
本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。</p>
</blockquote>
<ul>
<li><a href="https://github.com/anthropics/claude-code">Claude Code</a></li>
<li><a href="https://github.com/openai/codex">OpenAI Codex</a></li>
<li><a href="https://github.com/google-gemini/gemini-cli">Gemini CLI</a></li>
<li><a href="https://github.com/github/copilot-cli">GitHub Copilot CLI</a></li>
<li><a href="https://github.com/MoonshotAI/kimi-cli">Kimi Code CLI</a></li>
<li><a href="https://github.com/anomalyco/opencode">OpenCode</a></li>
<li><a href="https://github.com/QwenLM/qwen-code">Qwen Code</a></li>
<li><a href="https://github.com/anthropics/skills">Claude Code Skills</a></li>
</ul>
<hr>
<h2>横向对比</h2>
<h1>AI CLI 工具社区动态横向对比分析报告（2026-08-22）</h1>
<h2>1. 生态全景</h2>
<p>今日 AI CLI 赛道呈现「两端分化」：一端是 <strong>OpenCode（78 PR）与 Qwen Code（82 PR）</strong> 的社区贡献洪流，另一端是 <strong>Claude Code 与 Kimi Code 的近静默</strong>——Claude Code 近 24h 0 条 PR 合入、Kimi Code 仅 1 条 issue。OpenAI Codex 则集中在 <strong>alpha 系列快速迭代</strong>（rust-v0.150.0-alpha.x 与 v0.149.0-alpha.x 于 08-21 连发 5 个预发布），并伴随高赞功能诉求。</p>
<p>共性议题收口到三条主线：<strong>记忆持久化</strong>（Claude #34556 跨压缩记忆、OpenCode #41469「空响应被记为干净停止」）、<strong>Windows/跨平台质量</strong>（Codex #39136 插件初始化失败、#27117 PSModulePath 污染、#37104 WSL 终端静默失败）、以及 <strong>provider 广度与成本透明</strong>（Qwen #8368 接入 Kimi/MiMo、#8276 跨延迟工具发现的 prompt cache 保留；CoPaw/NanoClaw/IronClaw 均在扩展 provider 矩阵）。</p>
<h2>2. 各工具活跃度对比（近 24h）</h2>
<table>
<thead>
<tr>
<th>工具</th>
<th>活跃 Issues</th>
<th>重要 PR</th>
<th>Releases（近期）</th>
</tr>
</thead>
<tbody><tr>
<td>Claude Code</td>
<td>100（多为历史 issue 的标签/bot 更新）</td>
<td>0</td>
<td>v2.1.238（08-20）</td>
</tr>
<tr>
<td>OpenAI Codex</td>
<td>84</td>
<td>16</td>
<td>rust-v0.150.0-alpha.5/.3/.2、v0.149.0-alpha.7.1/.4.1（08-21）</td>
</tr>
<tr>
<td>Gemini CLI</td>
<td>98</td>
<td>2</td>
<td>v0.56.0-nightly.20260821、v0.57.0-preview.0</td>
</tr>
<tr>
<td>GitHub Copilot CLI</td>
<td>33</td>
<td>0</td>
<td>v1.0.81-6（08-14，无新发）</td>
</tr>
<tr>
<td>Kimi Code CLI</td>
<td>1</td>
<td>0</td>
<td>1.49.0（07-16，无新发）</td>
</tr>
<tr>
<td>OpenCode</td>
<td>22</td>
<td>78</td>
<td>v1.18.21 / v1.18.20（08-21）</td>
</tr>
<tr>
<td>Qwen Code</td>
<td>18</td>
<td>82</td>
<td>v0.21.14-nightly.20260821、v0.21.15（08-20）</td>
</tr>
</tbody></table>
<h2>3. 共同关注的功能方向</h2>
<ul>
<li><strong>记忆与上下文压缩</strong>：Claude Code #34556「跨压缩持久记忆」仍居讨论热度前列（111💬，已关闭但被反复引用）；OpenCode #41469「空 LLM 响应导致会话静默停止（finish: unknown, 0 tokens）」是直接污染评测与计费的质量黑洞。两者共同指向「压缩后历史可回溯 + 失败可诊断」的缺口。</li>
<li><strong>Windows / 跨平台质量</strong>：Codex 的 #39136 内置浏览器插件 Trusted RPC 依赖不在可信路径（82💬）、#27117 Windows 独立更新把 PSModulePath 带进 powershell.exe、#37104 WSL 集成终端在 PTY 启动前静默失败，构成 Windows 第一痛点平台；Copilot CLI #4521「沙箱无法禁用」、Kimi #2615 后台 subagent 在 TaskStop 后仍持续调用，反映终端/进程生命周期治理仍是共性难题。</li>
<li><strong>Provider 广度与模型路由</strong>：Qwen #8368 新增 Kimi 与小米 MiMo provider、#8276 跨「延迟工具发现」保留 prompt cache；NanoClaw 接入 Dial（SMS+语音）、Mattermost；CoPaw 接入 Volcengine Agent Plan &amp; MiMo V2.5；IronClaw 推可插拔 memory over MCP。多模型、多渠道已成各工具差异化主轴。</li>
<li><strong>Agent 可靠性与可观测</strong>：Gemini #22323 subagent 在 MAX_TURNS 后被误报为 GOAL 成功、#21409 generalist agent 挂起；OpenCode #785「能否关闭流式模式」（38👍/31💬）与 #34473「随机停止响应」反映流式/中断语义不稳定。</li>
</ul>
<h2>4. 差异化定位</h2>
<ul>
<li><strong>Claude Code</strong>：主干进入稳定打磨期，近 24h PR 侧静默、issue 侧以历史问题被 bot/标签刷新为主；最新 v2.1.238（08-20）延续「跨会话记忆」「多会话协作」主线（#34556、#24798 跨会话通信）。定位专业开发者的日常主力终端，体验细节被零容忍审视。</li>
<li><strong>OpenAI Codex</strong>：Rust 重写持续推进，alpha 系列日更；社区最高赞诉求是 #11626「/rewind 检查点恢复（同时回滚聊天上下文与已应用代码）」（204👍）。Windows 质量（冻结、插件、安装包）与「本地/私有插件市场被 API Key 用户阻挡」（#20621）是核心矛盾。定位 OpenAI 全场景入口。</li>
<li><strong>Gemini CLI</strong>：PR 侧极静（仅 2 条 pr-generation 相关），issue 集中在许可校验（#28912「无有效许可证」）、subagent 信任（#22323 误报成功）与「未充分利用 skills/sub-agents」（#21968）。成熟度中等，进入功能深化前的信任建设期。</li>
<li><strong>GitHub Copilot CLI</strong>：企业受管语境最明确，#3282/#3709「多 BYOK 模型、单会话内切换模型」（各 26👍）是最高频诉求；#4521「沙箱无法禁用」仍是治理痛点。近期无新发，定位企业受管环境的 Copilot 入口。</li>
<li><strong>Kimi Code CLI</strong>：今日仅 1 条 issue（#2615 后台 subagent 在 TaskStop/timeout 后仍调用 LLM），生态处于早期静默期，外部声量最低。</li>
<li><strong>OpenCode</strong>：社区贡献极活跃（78 PR），v1.18.21/20（08-21）持续推进；高赞诉求 #785「关闭流式模式」、#24153「归档会话的 unarchive/restore」。定位追求最新模型与高度可定制的开发者，provider 广度（llmgateway、QwenCloud、Vertex 等）持续扩展。</li>
<li><strong>Qwen Code</strong>：工业化 PR 体系成熟（82 PR），#8368 接入 Kimi/MiMo、#8332 附件音频桥、#8276 保留 prompt cache、#8992 MCP 2026 core + WebShell Apps host。定位验证严谨性与中国 IM/云生态用户。</li>
</ul>
<h2>5. 值得关注的趋势信号</h2>
<ul>
<li><strong>贡献者驱动 vs 主干静默分化加剧</strong>：OpenCode/Qwen 由社区 PR 洪流推动，Claude Code/Kimi 主干近乎静默，说明「开放贡献通道」正成为生态活跃度的分水岭。</li>
<li><strong>记忆持久化是下一轮分水岭</strong>：跨压缩记忆（Claude）、空响应误判（OpenCode）、自动记忆无限重试（Gemini #26522）三者都指向「失败可诊断、历史可回溯」的统一命题。</li>
<li><strong>Windows 仍是未被充分满足的硬市场</strong>：Codex 插件/安装/路径、Copilot 沙箱、Kimi 进程生命周期——后来者把 Windows 质量当一等公民即是切口。</li>
<li><strong>provider 矩阵军备竞赛</strong>：Kimi、MiMo、Volcengine、Dial、Mattermost 等接连被接入，多模型/多渠道正从「特色」变为「基线」。</li>
</ul>
<hr>
<h2>各工具详细报告</h2>
<details>
<summary><strong>Claude Code</strong> — <a href="https://github.com/anthropics/claude-code">anthropics/claude-code</a></summary>

<h1>Claude Code 社区动态日报（2026-08-22）</h1>
<h2>今日速览</h2>
<ul>
<li>最新发布为 <strong>v2.1.238</strong>（2026-08-20），前向 v2.1.237 / v2.1.236 同为该日连续更新；近 24h 内无新版本、PR 侧合入为 0，主干进入稳定打磨期。</li>
<li>社区高赞议题延续「跨压缩持久记忆」（#34556，111💬）、「多 Claude 工作流的跨会话通信」（#24798，83💬）。</li>
<li>新活跃 bug 集中在文件编码、git 代理、/rewind 与 Esc 交互细节。</li>
</ul>
<h2>版本发布</h2>
<ul>
<li><a href="https://github.com/anthropics/claude-code/releases/tag/v2.1.238">v2.1.238</a>（2026-08-20，最新稳定）</li>
<li><a href="https://github.com/anthropics/claude-code/releases/tag/v2.1.237">v2.1.237</a>（2026-08-20）</li>
<li><a href="https://github.com/anthropics/claude-code/releases/tag/v2.1.236">v2.1.236</a>（2026-08-19）</li>
</ul>
<h2>社区热点 Issues（近 24h 活跃）</h2>
<ol>
<li><strong>#34556 跨上下文压缩的持久记忆</strong>（111💬，已关闭）— 社区长期最高共鸣，用户自建 59 次压缩的记忆系统。</li>
<li><strong>#24798 多 Claude 工作流的跨会话通信</strong>（26👍/83💬，已关闭）— 多 agent 协作的会话互通诉求。</li>
<li><strong>#7134 不尊重文件编码，破坏 Windows-1252 文件</strong>（23👍/25💬，开放）— 编码处理跨平台回归。</li>
<li><strong>#76248 Cloud/Cowork 会话：git 代理现在阻断所有 push</strong>（8👍/28💬，开放）—「不在本会话授权」误伤合法推送。</li>
<li><strong>#87575 Auto 模式系统提示导致 /rewind 在 Bash 编辑文件上静默失败</strong>（12👍/10💬，开放）。</li>
<li><strong>#64568 按 Esc 退出 /btw 模式会拒绝待定工具调用而非仅关闭</strong>（9👍/11💬，开放）。</li>
<li><strong>#63092 主会话进行中时按 Esc 不关闭 /BTW 对话</strong>（12👍/6💬，开放）。</li>
<li><strong>#77071 Windows 11 Pro 计划下 Dispatch 标签从 Claude Desktop 侧边栏消失</strong>（1👍/14💬，开放）。</li>
<li><strong>#78264 自定义会话标题被 AI 生成标题覆盖；/resume 分叉出重复标题</strong>（3👍/9💬，已关闭）。</li>
<li><strong>#66005 --resume 丢弃会话的 --effort 级别，使 prompt cache 失效</strong>（2👍/9💬，开放）。</li>
</ol>
<h2>功能需求趋势</h2>
<table>
<thead>
<tr>
<th>方向</th>
<th>代表 Issues</th>
<th>社区诉求</th>
</tr>
</thead>
<tbody><tr>
<td>记忆/会话</td>
<td>#34556、#24798、#66005</td>
<td>跨压缩持久记忆、跨会话通信、resume 保真</td>
</tr>
<tr>
<td>编码/跨平台</td>
<td>#7134、#76248</td>
<td>Windows-1252 编码、git 代理不误伤</td>
</tr>
<tr>
<td>TUI/交互</td>
<td>#64568、#63092、#87575</td>
<td>Esc 语义、/rewind 在 Auto 模式下的稳定性</td>
</tr>
</tbody></table>
<h2>开发者关注点</h2>
<ol>
<li><strong>记忆是核心资产</strong>：#34556 以 111💬 居首，压缩后历史不可回看仍驱动用户自建方案。</li>
<li><strong>跨平台编码回归</strong>：#7134 影响 Windows-1252 文件，属基础可靠性。</li>
<li><strong>git 代理误伤</strong>：#76248 显示 Cowork 会话的代理策略过严，误阻断 push。</li>
</ol>
</details>

<details>
<summary><strong>OpenAI Codex</strong> — <a href="https://github.com/openai/codex">openai/codex</a></summary>

<h1>OpenAI Codex 社区动态日报 — 2026-08-22</h1>
<h2>今日速览</h2>
<ul>
<li>08-21 连发 5 个预发布：rust-v0.150.0-alpha.5/.3/.2 与 rust-v0.149.0-alpha.7.1/.4.1，Rust 重写迭代节奏快。</li>
<li>社区最高赞功能诉求 <strong>#11626「/rewind 检查点恢复，同时回滚聊天上下文与 Codex 已应用代码」</strong>（204👍/39💬）。</li>
<li>Windows 质量仍是高频痛点（插件初始化、PSModulePath 污染、WSL 终端静默失败）。</li>
</ul>
<h2>版本发布（近期）</h2>
<ul>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.5">rust-v0.150.0-alpha.5</a>（2026-08-21）</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.3">rust-v0.150.0-alpha.3</a>（2026-08-21）</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.2">rust-v0.150.0-alpha.2</a>（2026-08-21）</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.7.1">rust-v0.149.0-alpha.7.1</a>（2026-08-21）</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.4.1">rust-v0.149.0-alpha.4.1</a>（2026-08-21）</li>
</ul>
<h2>社区热点 Issues（近 24h 活跃）</h2>
<ol>
<li><strong>#11626 /rewind 检查点恢复</strong>（204👍/39💬，开放）— 最高赞功能诉求，要求回滚上下文与代码。</li>
<li><strong>#39136 内置浏览器插件初始化失败：Trusted RPC 依赖不在可信代码路径</strong>（42👍/82💬，开放）— Windows 回归。</li>
<li><strong>#38455 ChatGPT 桌面端反复 spawn Computer Use worker 并 V8 OOM</strong>（14👍/34💬，开放）。</li>
<li><strong>#27117 Windows 独立更新从 pwsh 继承 PSModulePath 进入 powershell.exe</strong>（13👍/20💬，开放）。</li>
<li><strong>#38350 周期性定时任务在成功运行后自行禁用，无用户授权</strong>（31💬，开放）。</li>
<li><strong>#20621 Codex App 阻止 API Key 用户使用本地/私有插件市场</strong>（28👍/3💬，开放）。</li>
<li><strong>#37475 Codex CLI 0.147.0 拒绝 Amazon Bedrock 输入并破坏 subagent 交接</strong>（22👍/6💬，开放）。</li>
<li><strong>#33493 本地 compaction v2 保留无界 input_image 负载，导致反复自动压缩</strong>（5👍/20💬，开放）。</li>
<li><strong>#37104 Windows/WSL 集成终端在 PTY/WSL 启动前静默失败</strong>（9👍/16💬，开放）。</li>
<li><strong>#39161 无法归档会话</strong>（14👍/10💬，开放）。</li>
</ol>
<h2>重要 PR 进展（近 24h）</h2>
<ol>
<li><strong>#39971 修复提权的 Windows 沙箱设置激活</strong></li>
<li><strong>#39980 对远程执行强制环境网络策略</strong></li>
<li><strong>#39976 在 macOS 沙箱允许 semaphore 限制查询</strong></li>
<li><strong>#39969 合并 code mode 输出辅助测试</strong></li>
<li><strong>#39967 升级 pnpm 至 10.34.5</strong></li>
<li><strong>#39962 将 Guardian 审查与 executor MCP server 隔离</strong></li>
<li><strong>#39961 通过 executor WebSocket 测试 browser MCP bearer token</strong></li>
<li><strong>#39958 停止从本地 exec server 广播 shell 快照</strong></li>
<li><strong>#39953 支持语音感知配置与版本偏移构建</strong></li>
<li><strong>#39952 尊重所选 executor 的必需 MCP server</strong></li>
</ol>
<h2>功能需求趋势</h2>
<ul>
<li><strong>可回滚的检查点</strong>（#11626）是头号诉求：用户要的不只是聊天回滚，而是「代码+上下文」一致性恢复。</li>
<li><strong>Windows 稳定性</strong>仍是第一痛点平台：插件、安装包、PSModulePath、WSL 终端四处独立高赞。</li>
<li><strong>本地/私有生态友好</strong>：#20621 反对 API Key 用户被挡在私有插件市场之外。</li>
<li><strong>安全收紧获肯定</strong>：远程执行网络策略、Guardian 隔离方向正确。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>/rewind 是分水岭功能</strong>：204👍 显示社区对「可撤销的编码动作」极强需求。</li>
<li><strong>Windows 平台治理复杂度高</strong>：从安装到运行时处处独立高赞 Issue。</li>
<li><strong>定时任务自禁用</strong>（#38350）暴露自动化可靠性的隐性风险。</li>
</ul>
</details>

<details>
<summary><strong>Gemini CLI</strong> — <a href="https://github.com/google-gemini/gemini-cli">google-gemini/gemini-cli</a></summary>

<h1>Gemini CLI 社区动态日报 — 2026-08-22</h1>
<h2>今日速览</h2>
<p>今日发布 v0.56.0-nightly.20260821 与 v0.57.0-preview.0（08-19）；PR 侧极静（仅 2 条 pr-generation 相关）。社区焦点集中在许可校验（#28912「无有效许可证」）、subagent 信任（#22323 误报 GOAL 成功、#21409 generalist 挂起）与「未充分利用 skills/sub-agents」（#21968）。</p>
<h2>版本发布</h2>
<ul>
<li><strong>v0.56.0-nightly.20260821</strong>（2026-08-21，nightly）</li>
<li><strong>v0.57.0-preview.0</strong>（2026-08-19，preview）</li>
<li><strong>v0.56.0</strong>（2026-08-19，稳定）</li>
</ul>
<h2>社区热点 Issues（近 24h 活跃）</h2>
<ol>
<li><strong>#21409 Generalist agent 挂起</strong>（8👍/8💬，开放）— 代理可靠性。</li>
<li><strong>#28912 提示「You do not have a valid license of this product.」</strong>（6👍/9💬，开放）— 许可校验误报。</li>
<li><strong>#22323 Subagent 在 MAX_TURNS 后被恢复为 GOAL 成功，隐藏中断</strong>（2👍/13💬，开放）— 信任机制。</li>
<li><strong>#19873 通过零依赖 OS 沙箱化与执行后意图路由利用模型的 bash 亲和</strong>（1👍/8💬，开放）。</li>
<li><strong>#22745 评估 AST 感知文件读取/搜索/映射的影响</strong>（1👍/7💬，开放）。</li>
<li><strong>#15269 缺少 Subagent Hook 事件</strong>（8💬，开放）。</li>
<li><strong>#25166 Shell 命令执行在完成后卡在「Waiting input」</strong>（3👍/4💬，开放）。</li>
<li><strong>#24353 鲁棒的组件级评估</strong>（7💬，开放）。</li>
<li><strong>#21968 Gemini 未充分利用 skills 与 sub-agents</strong>（6💬，开放）。</li>
<li><strong>#26522 停止 Auto Memory 对低信号会话无限重试</strong>（5💬，开放）。</li>
</ol>
<h2>重要 PR 进展（近 24h）</h2>
<ol>
<li><strong>#28951 feat(pr-generation)：新增 Cloud Run job、Workflow 编排与部署流水线</strong></li>
<li><strong>#28952 feat(pr-generation)：新增交互式 diff 对比可视化生成器</strong></li>
</ol>
<h2>功能需求趋势</h2>
<ul>
<li><strong>许可与信任</strong>：#28912 许可误报、#22323 subagent 误报成功，均削弱用户信任。</li>
<li><strong>代理可靠性</strong>：#21409 generalist 挂起、#25166 shell 卡死。</li>
<li><strong>能力利用率</strong>：#21968 呼吁更充分使用 skills/sub-agents；#26522 反对无界自动重试。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>subagent 行为不可预测</strong>仍是信任短板（误报成功 + 挂起）。</li>
<li><strong>PR 侧极静</strong>：今日仅 2 条 pr-generation 相关，进入功能深化前的信任建设期。</li>
<li><strong>许可校验需更精准</strong>：#28912 误报影响开箱体验。</li>
</ul>
</details>

<details>
<summary><strong>GitHub Copilot CLI</strong> — <a href="https://github.com/github/copilot-cli">github/copilot-cli</a></summary>

<h1>GitHub Copilot CLI 社区动态日报 — 2026-08-22</h1>
<h2>今日速览</h2>
<p>近期无新版本（最新 v1.0.81-6 为 08-14），近 24h PR 侧为 0。社区最高频诉求是 <strong>多 BYOK 模型与单会话内模型切换</strong>（#3282、#3709，各 26👍）与 <strong>沙箱无法禁用</strong>（#4521）。企业受管语境仍是核心定位。</p>
<h2>版本发布</h2>
<ul>
<li>最新仍为 <a href="https://github.com/github/copilot-cli/releases/tag/v1.0.81-6">v1.0.81-6</a>（2026-08-14，prerelease），今日无新发。</li>
</ul>
<h2>社区热点 Issues（近 24h 活跃）</h2>
<ol>
<li><strong>#3282 在 Copilot CLI 中添加多 BYOK 模型能力</strong>（26👍/8💬，开放）— 最高赞功能诉求。</li>
<li><strong>#3709 允许 /model 在单会话内切换多个模型（含 BYOK/本地 provider）</strong>（26👍/4💬，开放）— 与 #3282 同源诉求。</li>
<li><strong>#1313 Session Branching</strong>（13👍/7💬，开放）— 会话分支管理。</li>
<li><strong>#4345 reasoning effort &#39;medium&#39; 不支持模型 &#39;claude-haiku-4.5&#39;</strong>（4👍/8💬，开放）。</li>
<li><strong>#4521 沙箱无法禁用</strong>（4👍/3💬，开放）— 企业治理痛点。</li>
<li><strong>#4422 所有 Claude 模型在 CLI 模型选择下被禁用</strong>（3👍/4💬，已关闭）。</li>
<li><strong>#4485 主题在夜间变为浅色</strong>（2👍/2💬，开放）。</li>
<li><strong>#4038 非交互模式：晚连接的 MCP server 注入空用户消息</strong>（3💬，已关闭）。</li>
<li><strong>#4542 工作区 .mcp.json 被 &#39;mcp list&#39;/&#39;mcp get&#39; 识别但未在实际 agent 会话中连接</strong>（1👍/1💬，开放）。</li>
<li><strong>#4511 Session AIC 显示不可靠</strong>（2💬，开放）。</li>
</ol>
<h2>重要 PR 进展</h2>
<p>今日无新 PR 进入窗口。</p>
<h2>功能需求趋势</h2>
<ul>
<li><strong>多模型/BYOK 自由</strong>：#3282/#3709 高赞，单会话内切换模型是企业与个人共同诉求。</li>
<li><strong>沙箱可彻底关闭</strong>：#4521 显示托管环境策略过严。</li>
<li><strong>MCP 连接一致性</strong>：#4542 工作区配置被识别但未连接，需端到端校验。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>模型选择自由度不足</strong>：BYOK/本地 provider 的单会话切换是被反复呼吁的基线能力。</li>
<li><strong>沙箱策略仍偏强制</strong>：显式禁用无效，是企业用户核心痛点。</li>
<li><strong>近期无新发</strong>：主干进入稳定期，等待下一轮功能释放。</li>
</ul>
</details>

<details>
<summary><strong>Kimi Code CLI</strong> — <a href="https://github.com/MoonshotAI/kimi-cli">MoonshotAI/kimi-cli</a></summary>

<h1>Kimi Code CLI 社区动态日报 2026-08-22</h1>
<h2>今日速览</h2>
<p>今日社区近乎静默：仅 1 条 issue 进入窗口，PR 与 releases 均为 0（最新 1.49.0 为 07-16）。相较其他 CLI 的高活跃度，Kimi Code 生态仍处于早期静默期。</p>
<h2>版本发布</h2>
<p>今日无新版本发布（最新 1.49.0，2026-07-16）。</p>
<h2>社区热点 Issues</h2>
<ol>
<li><strong>#2615 后台 subagent 在 TaskStop/timeout 标记为终止后仍持续调用 LLM</strong>（开放）— 进程生命周期治理问题。</li>
</ol>
<h2>重要 PR 进展</h2>
<p>今日无更新。</p>
<h2>功能需求趋势</h2>
<p>基于连日低活跃度，社区当前重心可能在打通 ACP/IDE 基础链路与内部迭代，外部声量有限。</p>
<h2>开发者关注点</h2>
<ul>
<li>生态早期，活跃度在 7 个 CLI 中垫底；建议关注其 ACP runtime 工具能力边界的后续修复。</li>
</ul>
</details>

<details>
<summary><strong>OpenCode</strong> — <a href="https://github.com/anomalyco/opencode">anomalyco/opencode</a></summary>

<h1>OpenCode 社区动态日报 — 2026-08-22</h1>
<h2>今日速览</h2>
<p>发布 <strong>v1.18.21 / v1.18.20</strong>（2026-08-21），社区贡献极活跃——近 24h 78 个 PR 更新。高赞功能诉求 <strong>#785「能否关闭流式模式」</strong>（38👍/31💬）与 <strong>#24153「归档会话的 unarchive/restore」</strong>（11👍/9💬）。可靠性议题聚焦「空 LLM 响应导致会话静默停止」（#41469）与「随机停止响应」（#34473）。</p>
<h2>版本发布</h2>
<ul>
<li><a href="https://github.com/anomalyco/opencode/releases/tag/v1.18.21">v1.18.21</a>（2026-08-21）</li>
<li><a href="https://github.com/anomalyco/opencode/releases/tag/v1.18.20">v1.18.20</a>（2026-08-21）</li>
<li><a href="https://github.com/anomalyco/opencode/releases/tag/v1.18.19">v1.18.19</a>（2026-08-20）</li>
</ul>
<h2>社区热点 Issues（近 24h 活跃）</h2>
<ol>
<li><strong>#785 能否关闭流式模式？</strong>（38👍/31💬，开放）— 长期高赞体验诉求。</li>
<li><strong>#24153 新增归档会话的 unarchive/restore</strong>（11👍/9💬，开放）— 会话管理。</li>
<li><strong>#41469 空 LLM 响应导致会话静默停止（finish: unknown, 0 tokens）</strong>（10💬，开放）— 用量统计与评测失真。</li>
<li><strong>#34473 OpenCode 随机停止响应</strong>（3👍/6💬，开放）— 流式/中断语义不稳定。</li>
<li><strong>#37345 编辑项目：icon/color 变更未持久化到数据库</strong>（4💬，开放）。</li>
<li><strong>#33219 新增 FreeBSD 支持</strong>（2💬，已关闭）。</li>
<li><strong>#43882 muse-spark 流始终无 finish_reason 结束</strong>（2💬，开放）。</li>
<li><strong>#43907 TUI 复制失效</strong>（2💬，已关闭）。</li>
<li><strong>#41847 权限对话框未渲染，后端阻塞于不可见 prompt，应用假死</strong>（2💬，开放）。</li>
<li><strong>#36196 V2 改进工具搜索命名空间、减少 tool-context cache busts</strong>（2💬，已关闭）。</li>
</ol>
<h2>重要 PR 进展（近 24h 精选）</h2>
<ol>
<li><strong>#41936 fix(util)：用可配置超时约束 npm 安装</strong></li>
<li><strong>#43183 fix(tui)：使文件附件徽标在系统主题下可读</strong></li>
<li><strong>#42927 feat(tui)：在 token 用量计数与侧边栏显示上下文窗口上限</strong></li>
<li><strong>#42986 fix(shell)：扫描重定向目标以覆盖 external_directory</strong></li>
<li><strong>#42907 fix(tui)：按创建时间而非 session ID 排序子会话</strong></li>
<li><strong>#42819 fix(session)：按原始顺序边界删除回退消息并 tie-break id</strong></li>
<li><strong>#41723 fix(core)：将不支持的图片附件保留为文本而非丢弃</strong></li>
<li><strong>#42833 fix(session-ui)：防止移动端变体选择重叠</strong></li>
<li><strong>#42842 fix(i18n)：修正加泰罗尼亚语（ca）本地化并新增词汇表</strong></li>
<li><strong>#42936 feat(lsp)：为 Markdown 新增 Marksman 语言服务器</strong></li>
</ol>
<h2>功能需求趋势</h2>
<ul>
<li><strong>可靠性优先</strong>：#41469 空响应误判、#34473 随机停止，直接污染计费与评测。</li>
<li><strong>流式体验可控</strong>：#785 关闭流式模式是头号体验诉求。</li>
<li><strong>会话管理</strong>：#24153 归档恢复、#42907 子会话排序。</li>
<li><strong>provider 广度</strong>：llmgateway、QwenCloud、Vertex 等持续扩展。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>用量统计可信度</strong>：空响应被记为干净停止（finish: unknown, 0 tokens）直接污染计费与评测。</li>
<li><strong>贡献者生态活跃</strong>：78 个 PR 推动 TUI、session、core 多维修复。</li>
<li><strong>流式语义稳定</strong>：关闭流式的诉求反映流式/中断处理仍是体验短板。</li>
</ul>
</details>

<details>
<summary><strong>Qwen Code</strong> — <a href="https://github.com/QwenLM/qwen-code">QwenLM/qwen-code</a></summary>

<h1>Qwen Code 社区动态日报 — 2026-08-22</h1>
<h2>今日速览</h2>
<p>发布 <strong>v0.21.14-nightly.20260821</strong> 与 v0.21.15（08-20）；近 24h PR 侧 82 个更新，工业化 PR 体系成熟。焦点 PR：<strong>#8368 接入 Kimi 与小米 MiMo provider</strong>（68💬）、<strong>#8332 附件音频桥</strong>（67💬）、<strong>#8276 跨延迟工具发现保留 prompt cache</strong>（64💬）、<strong>#8992 MCP 2026 core + WebShell Apps host</strong>（32💬）。Issue 侧热度较低（18 条，最高仅 7💬）。</p>
<h2>版本发布</h2>
<ul>
<li><a href="https://github.com/QwenLM/qwen-code/releases/tag/v0.21.14-nightly.20260821">v0.21.14-nightly.20260821</a>（2026-08-21，nightly）</li>
<li><a href="https://github.com/QwenLM/qwen-code/releases/tag/v0.21.15">v0.21.15</a>（2026-08-20，稳定）</li>
</ul>
<h2>社区热点 Issues（近 24h 活跃）</h2>
<ol>
<li><strong>#5180 主会话作项目经理派发任务，subagent 执行到一半崩溃</strong>（7💬，开放）— 多 agent 编排稳定性。</li>
<li><strong>#8993 公共扩展安装需要 Git 2.37，但 Ubuntu 22.04 apt 仅提供 2.34.1</strong>（6💬，已关闭）— 安装门槛。</li>
<li><strong>#5966 0.19.3 UI 不定期错误，中文输入法完全无效</strong>（6💬，开放）— i18n/输入法。</li>
<li><strong>#7167 Fleet Shepherd Dashboard</strong>（3💬，开放）。</li>
<li><strong>#8094 Transport-continuation 恢复使续传 transcript 从中句开始</strong>（3💬，已关闭）。</li>
<li><strong>#9571 避免确认框默认被选中</strong>（3💬，已关闭）。</li>
<li><strong>#9494 流式响应时斜杠命令菜单选择重置到首项</strong>（3💬，已关闭）。</li>
<li><strong>#9487 Web shell 长任务中转译与会话加载指示中途丢失</strong>（3💬，已关闭）。</li>
<li><strong>#9675 会话间 MCP server 断开/不可用即使已配置</strong>（3💬，开放）。</li>
<li><strong>#9693 Qwen Desktop 在 Windows 上启动即报 MCP -32000 Connection closed</strong>（2💬，开放）。</li>
</ol>
<h2>重要 PR 进展（近 24h 精选）</h2>
<ol>
<li><strong>#8368 feat(auth)：新增 Kimi 与 Xiaomi MiMo provider</strong>（68💬，开放）</li>
<li><strong>#8332 feat(cli)：为附件新增音频桥</strong>（67💬，开放）</li>
<li><strong>#8276 fix(core)：跨延迟工具发现保留 prompt cache</strong>（64💬，开放）</li>
<li><strong>#8902 fix(cli)：从共享 option 定义派生 bootstrap --help</strong>（43💬，开放）</li>
<li><strong>#9513 fix(cli)：恢复 PR2A 会话行为</strong>（38💬，开放）</li>
<li><strong>#9273 feat(review)：capture-tui 渲染获取像素而非散文</strong>（32💬，开放）</li>
<li><strong>#8992 feat(mcp)：新增 MCP 2026 core 与 WebShell Apps host</strong>（32💬，开放）</li>
<li><strong>#9526 feat(review)：新增持续关键的收敛建议（land-with-residual-risk）</strong>（31💬，开放）</li>
<li><strong>#8927 feat(channels)：用 sessionRotation 约束会话生命周期</strong>（29💬，开放）</li>
<li><strong>#9350 feat(dingtalk)：支持出站文件投递</strong>（27💬，开放）</li>
</ol>
<h2>功能需求趋势</h2>
<ul>
<li><strong>provider 广度</strong>：Kimi、MiMo 接入（#8368），Volcengine/Mattermost 等外部生态同步扩展。</li>
<li><strong>成本与缓存透明</strong>：#8276 保留 prompt cache 直接关联账单可信度。</li>
<li><strong>多模态与通道</strong>：音频桥（#8332）、WebShell Apps host（#8992）、DingTalk 文件投递（#9350）。</li>
<li><strong>审查自动化</strong>：capture-tui、收敛建议、review 闭环。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>工业化发布门禁</strong>：82 个 PR 的密集合入显示高度自动化的 release/CI 体系。</li>
<li><strong>路由身份绑定用量</strong>：#8276 保留 prompt cache 提升计费可信度。</li>
<li><strong>多 agent 编排稳定性</strong>：#5180 subagent 中途崩溃需关注。</li>
</ul>
</details>

<hr>
<h2>Claude Code Skills 社区热点</h2>
<blockquote>
<p>数据来源: <a href="https://github.com/anthropics/skills">anthropics/skills</a> | 近 24h 活跃</p>
</blockquote>
<ul>
<li><strong>#1620 / #1625 Shell 命令注入：with_server.py 的 --server 参数使用 shell=True</strong>（#1620 已关闭，#1625 开放）— 技能元数据/示例脚本的安全隐患。</li>
<li><strong>#1624 claude-api 的 SKIP grep 未锚定——<code>cohere</code> 匹配 &quot;coherent&quot;，在含相关词的仓库中误禁用技能</strong>（开放）。</li>
<li><strong>#1622 claude-api skill 的 description 超过 1024 字符 frontmatter 上限（1077 字符）</strong>（开放）。</li>
<li><strong>#1621 / #1619 MCPConnectionSSE/HTTP 与 MCPConnectionStdio 接受调用方提供的任意 URL/headers/command</strong>（开放）— MCP 连接器的供应链安全风险。</li>
<li><strong>#1627 feat：新增 buffer-api Agent Skill（Buffer GraphQL 调度）</strong>（开放）。</li>
<li><strong>#1623 更新 claude-api skill：Python SDK 0.x → 1.x 升级指南</strong>（已关闭）。</li>
</ul>
<p>Skills 生态今日节奏聚焦<strong>安全审计</strong>（命令注入、MCP 任意命令执行）与单点修复，无大规模架构讨论。</p>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，所有内容基于 GitHub 公开 API 实时抓取并由执行代理人工撰写，未调用任何外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI CLI Tools Digest 2026-08-22</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-cli-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-cli-en</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
      <description>AI CLI Tools Community Daily — 2026-08-22 Generated: 2026-08-22 02:30 (GMT+8) | Coverage: 7 CLIs + Claude Code Skills This digest is produced by the agents-radar local automation. All summaries, comparisons, and writing are done by the executing agent — no external LLM API was called. Claude Code OpenAI Codex Gemini CLI GitHub Copilot CLI Kimi Code CLI OpenCode Qwen Code Claude Code Skills Cross-Tool Comparison AI CLI Tools Cross-Tool Comparison Report (2026-08-22) 1. Ecosystem Overview Today th...</description>
      <content:encoded><![CDATA[<h1>AI CLI Tools Community Daily — 2026-08-22</h1>
<blockquote>
<p>Generated: 2026-08-22 02:30 (GMT+8) | Coverage: 7 CLIs + Claude Code Skills
This digest is produced by the agents-radar local automation. All summaries, comparisons, and writing are done by the executing agent — no external LLM API was called.</p>
</blockquote>
<ul>
<li><a href="https://github.com/anthropics/claude-code">Claude Code</a></li>
<li><a href="https://github.com/openai/codex">OpenAI Codex</a></li>
<li><a href="https://github.com/google-gemini/gemini-cli">Gemini CLI</a></li>
<li><a href="https://github.com/github/copilot-cli">GitHub Copilot CLI</a></li>
<li><a href="https://github.com/MoonshotAI/kimi-cli">Kimi Code CLI</a></li>
<li><a href="https://github.com/anomalyco/opencode">OpenCode</a></li>
<li><a href="https://github.com/QwenLM/qwen-code">Qwen Code</a></li>
<li><a href="https://github.com/anthropics/skills">Claude Code Skills</a></li>
</ul>
<hr>
<h2>Cross-Tool Comparison</h2>
<h1>AI CLI Tools Cross-Tool Comparison Report (2026-08-22)</h1>
<h2>1. Ecosystem Overview</h2>
<p>Today the AI CLI track shows a clear &quot;two-speed&quot; split: on one end, <strong>OpenCode (78 PRs) and Qwen Code (82 PRs)</strong> ride a wave of community contributions; on the other, <strong>Claude Code and Kimi Code are nearly silent</strong> — Claude Code merged 0 PRs in the last 24h and Kimi Code logged a single issue. OpenAI Codex concentrated on a <strong>rapid alpha cadence</strong> (five pre-releases of rust-v0.150.0-alpha.x and v0.149.0-alpha.x on 08-21) alongside a highly-upvoted feature request.</p>
<p>Three cross-cutting themes converge: <strong>memory persistence</strong> (Claude #34556 cross-compaction memory, OpenCode #41469 &quot;empty response miscounted as clean stop&quot;), <strong>Windows / cross-platform quality</strong> (Codex #39136 plugin init failure, #27117 PSModulePath pollution, #37104 WSL terminal silent failure), and <strong>provider breadth &amp; cost transparency</strong> (Qwen #8368 adds Kimi/MiMo, #8276 preserves prompt cache across deferred tool discovery; CoPaw/NanoClaw/IronClaw all expanding provider matrices).</p>
<h2>2. Activity Comparison (last 24h)</h2>
<table>
<thead>
<tr>
<th>Tool</th>
<th>Active Issues</th>
<th>Notable PRs</th>
<th>Releases (recent)</th>
</tr>
</thead>
<tbody><tr>
<td>Claude Code</td>
<td>100 (mostly label/bot refreshes of historical issues)</td>
<td>0</td>
<td>v2.1.238 (08-20)</td>
</tr>
<tr>
<td>OpenAI Codex</td>
<td>84</td>
<td>16</td>
<td>rust-v0.150.0-alpha.5/.3/.2, v0.149.0-alpha.7.1/.4.1 (08-21)</td>
</tr>
<tr>
<td>Gemini CLI</td>
<td>98</td>
<td>2</td>
<td>v0.56.0-nightly.20260821, v0.57.0-preview.0</td>
</tr>
<tr>
<td>GitHub Copilot CLI</td>
<td>33</td>
<td>0</td>
<td>v1.0.81-6 (08-14, no new release)</td>
</tr>
<tr>
<td>Kimi Code CLI</td>
<td>1</td>
<td>0</td>
<td>1.49.0 (07-16, no new release)</td>
</tr>
<tr>
<td>OpenCode</td>
<td>22</td>
<td>78</td>
<td>v1.18.21 / v1.18.20 (08-21)</td>
</tr>
<tr>
<td>Qwen Code</td>
<td>18</td>
<td>82</td>
<td>v0.21.14-nightly.20260821, v0.21.15 (08-20)</td>
</tr>
</tbody></table>
<h2>3. Shared Functional Directions</h2>
<ul>
<li><strong>Memory &amp; context compaction</strong>: Claude #34556 &quot;persistent memory across context compactions&quot; stays top-of-mind (111 comments); OpenCode #41469 &quot;session silently stops on empty LLM response (finish: unknown, 0 tokens)&quot; is a quality black hole that pollutes evaluation and billing. Both point to the gap of &quot;compression-history replayable + failures diagnosable.&quot;</li>
<li><strong>Windows / cross-platform quality</strong>: Codex #39136 built-in browser plugin Trusted RPC not in trusted path (82 comments), #27117 Windows standalone update inherits PSModulePath into powershell.exe, #37104 WSL integrated terminal silently fails before PTY startup — Windows is the #1 pain platform. Copilot CLI #4521 &quot;sandbox cannot be disabled&quot; and Kimi #2615 background subagent keeps calling LLM after TaskStop reflect shared terminal/process-lifecycle governance pain.</li>
<li><strong>Provider breadth &amp; model routing</strong>: Qwen #8368 adds Kimi &amp; Xiaomi MiMo providers, #8276 preserves prompt cache across deferred tool discovery; NanoClaw adds Dial (SMS+voice) and Mattermost; CoPaw adds Volcengine Agent Plan &amp; MiMo V2.5; IronClaw pushes pluggable memory over MCP. Multi-model, multi-channel is now a differentiator axis.</li>
<li><strong>Agent reliability &amp; observability</strong>: Gemini #22323 subagent misreported as GOAL success after MAX_TURNS, #21409 generalist agent hangs; OpenCode #785 &quot;disable streaming mode&quot; (38👍/31💬) and #34473 &quot;randomly stops responding&quot; show unstable streaming/interrupt semantics.</li>
</ul>
<h2>4. Differentiated Positioning</h2>
<ul>
<li><strong>Claude Code</strong>: main branch in a polish phase — 0 PRs merged in 24h, issues dominated by bot/label refreshes of historical items; latest v2.1.238 (08-20) continues the &quot;cross-session memory&quot; and &quot;multi-session collaboration&quot; thread (#34556, #24798). Positioned as the daily driver terminal for professional developers; UX details scrutinized zero-tolerance.</li>
<li><strong>OpenAI Codex</strong>: Rust rewrite accelerating, daily alpha cadence; top community ask is #11626 &quot;/rewind checkpoint restore (revert both chat context and Codex-applied code)&quot; (204👍). Windows quality (freeze, plugin, installer) and &quot;local/private plugin marketplaces blocked for API-key users&quot; (#20621) are core tensions. Positioned as OpenAI&#39;s all-scenario entry point.</li>
<li><strong>Gemini CLI</strong>: PR side extremely quiet (only 2 pr-generation-related); issues cluster on license validation (#28912 &quot;no valid license&quot;), subagent trust (#22323 false GOAL success) and &quot;under-uses skills/sub-agents&quot; (#21968). Mid-maturity, entering a trust-building phase before feature deepening.</li>
<li><strong>GitHub Copilot CLI</strong>: most enterprise-managed context; #3282/#3709 &quot;multiple BYOK models, switch within a session&quot; (26👍 each) is the top ask; #4521 &quot;sandbox cannot be disabled&quot; remains a governance pain. No new release recently; positioned as the Copilot entry point for managed environments.</li>
<li><strong>Kimi Code CLI</strong>: only 1 issue today (#2615 background subagent keeps calling LLM after TaskStop/timeout); ecosystem in early silence, lowest external voice.</li>
<li><strong>OpenCode</strong>: highly active community (78 PRs), v1.18.21/20 (08-21) ongoing; top asks #785 &quot;disable streaming mode&quot;, #24153 &quot;unarchive/restore archived sessions&quot;. Positioned for developers chasing latest models and deep customization; provider breadth (llmgateway, QwenCloud, Vertex) keeps expanding.</li>
<li><strong>Qwen Code</strong>: mature industrial PR pipeline (82 PRs); #8368 adds Kimi/MiMo, #8332 audio bridge for attachments, #8276 preserves prompt cache, #8992 MCP 2026 core + WebShell Apps host. Positioned for verification rigor and China IM/cloud-ecosystem users.</li>
</ul>
<h2>5. Notable Trend Signals</h2>
<ul>
<li><strong>Contributor-driven vs main-branch silence divergence widens</strong>: OpenCode/Qwen propelled by a PR flood while Claude Code/Kimi main branch is near-silent — &quot;open contribution channel&quot; is becoming the watershed of ecosystem vibrancy.</li>
<li><strong>Memory persistence is the next watershed</strong>: cross-compaction memory (Claude), empty-response miscount (OpenCode), auto-memory infinite retry (Gemini #26522) all point to the unified命题 of &quot;failures diagnosable, history replayable.&quot;</li>
<li><strong>Windows remains an unsatisfied hard market</strong>: Codex plugin/installer/path, Copilot sandbox, Kimi process lifecycle — treating Windows quality as a first-class citizen is the opening for latecomers.</li>
<li><strong>Provider-matrix arms race</strong>: Kimi, MiMo, Volcengine, Dial, Mattermost successively integrated; multi-model/multi-channel is shifting from &quot;feature&quot; to &quot;baseline.&quot;</li>
</ul>
<hr>
<h2>Per-Tool Reports</h2>
<details>
<summary><strong>Claude Code</strong> — <a href="https://github.com/anthropics/claude-code">anthropics/claude-code</a></summary>

<h1>Claude Code Daily (2026-08-22)</h1>
<h2>Today at a glance</h2>
<ul>
<li>Latest release is <strong>v2.1.238</strong> (2026-08-20); v2.1.237 / v2.1.236 same-day. No new version and 0 merged PRs in 24h — main branch in a polish phase.</li>
<li>Top community themes continue: cross-compaction persistent memory (#34556, 111 comments) and cross-session communication for multi-Claude workflows (#24798, 83 comments).</li>
<li>Fresh bugs center on file encoding, git proxy, /rewind and Esc interaction details.</li>
</ul>
<h2>Releases</h2>
<ul>
<li><a href="https://github.com/anthropics/claude-code/releases/tag/v2.1.238">v2.1.238</a> (2026-08-20, latest stable)</li>
<li><a href="https://github.com/anthropics/claude-code/releases/tag/v2.1.237">v2.1.237</a> (2026-08-20)</li>
<li><a href="https://github.com/anthropics/claude-code/releases/tag/v2.1.236">v2.1.236</a> (2026-08-19)</li>
</ul>
<h2>Hot Issues (last 24h)</h2>
<ol>
<li><strong>#34556 Persistent memory across context compactions</strong> (111 comments, closed) — long-standing top resonance; user built a 59-compaction memory system.</li>
<li><strong>#24798 Inter-session communication for multi-Claude workflows</strong> (26👍/83💬, closed).</li>
<li><strong>#7134 Does not respect file encoding, corrupts Windows-1252 files</strong> (23👍/25💬, open) — cross-platform encoding regression.</li>
<li><strong>#76248 Cloud/Cowork sessions: git proxy now blocks all pushes</strong> (8👍/28💬, open) — &quot;not in this session&#39;s auth&quot; wrongly blocks legitimate pushes.</li>
<li><strong>#87575 Auto mode system prompt causes /rewind to silently fail on Bash-edited files</strong> (12👍/10💬, open).</li>
<li><strong>#64568 Pressing Esc to exit /btw mode rejects the pending tool-use prompt</strong> (9👍/11💬, open).</li>
<li><strong>#63092 Esc doesn&#39;t close /BTW conversation when main conversation is active</strong> (12👍/6💬, open).</li>
<li><strong>#77071 Dispatch tab missing from Claude Desktop sidebar (Windows 11 Pro)</strong> (1👍/14💬, open).</li>
<li><strong>#78264 Custom session title overridden by AI-generated title; /resume forks duplicate titles</strong> (3👍/9💬, closed).</li>
<li><strong>#66005 --resume drops the session&#39;s --effort level, invalidating the prompt cache</strong> (2👍/9💬, open).</li>
</ol>
<h2>Demand Trends</h2>
<table>
<thead>
<tr>
<th>Area</th>
<th>Issues</th>
<th>Ask</th>
</tr>
</thead>
<tbody><tr>
<td>Memory/session</td>
<td>#34556, #24798, #66005</td>
<td>cross-compaction memory, cross-session comms, resume fidelity</td>
</tr>
<tr>
<td>Encoding/cross-platform</td>
<td>#7134, #76248</td>
<td>Windows-1252 encoding, git proxy non-interference</td>
</tr>
<tr>
<td>TUI/interaction</td>
<td>#64568, #63092, #87575</td>
<td>Esc semantics, /rewind stability under Auto mode</td>
</tr>
</tbody></table>
<h2>Developer Notes</h2>
<ol>
<li><strong>Memory is core capital</strong>: #34556 leads with 111 comments; post-compression history un-replayable still drives user-built workarounds.</li>
<li><strong>Cross-platform encoding regression</strong>: #7134 affects Windows-1252 files — basic reliability.</li>
<li><strong>git proxy over-block</strong>: #76248 shows Cowork session proxy policy too strict, wrongly blocking push.</li>
</ol>
</details>

<details>
<summary><strong>OpenAI Codex</strong> — <a href="https://github.com/openai/codex">openai/codex</a></summary>

<h1>OpenAI Codex Daily — 2026-08-22</h1>
<h2>Today at a glance</h2>
<ul>
<li>08-21 shipped five pre-releases: rust-v0.150.0-alpha.5/.3/.2 and rust-v0.149.0-alpha.7.1/.4.1 — fast Rust-rewrite cadence.</li>
<li>Top community ask: <strong>#11626 &quot;/rewind checkpoint restore, reverting both chat context and Codex-applied code&quot;</strong> (204👍/39💬).</li>
<li>Windows quality remains the high-frequency pain (plugin init, PSModulePath pollution, WSL terminal silent failure).</li>
</ul>
<h2>Releases (recent)</h2>
<ul>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.5">rust-v0.150.0-alpha.5</a> (2026-08-21)</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.3">rust-v0.150.0-alpha.3</a> (2026-08-21)</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.150.0-alpha.2">rust-v0.150.0-alpha.2</a> (2026-08-21)</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.7.1">rust-v0.149.0-alpha.7.1</a> (2026-08-21)</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.4.1">rust-v0.149.0-alpha.4.1</a> (2026-08-21)</li>
</ul>
<h2>Hot Issues (last 24h)</h2>
<ol>
<li><strong>#11626 /rewind checkpoint restore</strong> (204👍/39💬, open) — top feature ask; revert context AND code.</li>
<li><strong>#39136 Built-in browser plugin init fails: Trusted RPC dependency not in trusted code path</strong> (42👍/82💬, open).</li>
<li><strong>#38455 ChatGPT desktop repeatedly spawns Computer Use workers, V8 OOM</strong> (14👍/34💬, open).</li>
<li><strong>#27117 Windows standalone update inherits PSModulePath into powershell.exe</strong> (13👍/20💬, open).</li>
<li><strong>#38350 Recurring scheduled tasks disable themselves after successful runs without user auth</strong> (31💬, open).</li>
<li><strong>#20621 Codex App blocks Local/Private Plugin Marketplaces for API-key users</strong> (28👍/3💬, open).</li>
<li><strong>#37475 Codex CLI 0.147.0 rejects Amazon Bedrock input, corrupts subagent handoff</strong> (22👍/6💬, open).</li>
<li><strong>#33493 Local compaction v2 retains unbounded input_image payloads, causing repeated auto-compaction</strong> (5👍/20💬, open).</li>
<li><strong>#37104 Windows/WSL integrated terminal silently fails before PTY/WSL startup</strong> (9👍/16💬, open).</li>
<li><strong>#39161 Could not archive conversation</strong> (14👍/10💬, open).</li>
</ol>
<h2>Notable PRs (last 24h)</h2>
<ol>
<li><strong>#39971 Fix elevated Windows sandbox setup activation</strong></li>
<li><strong>#39980 Enforce environment network policies for remote execution</strong></li>
<li><strong>#39976 Allow semaphore limit queries in the macOS sandbox</strong></li>
<li><strong>#39969 Consolidate code mode output helper tests</strong></li>
<li><strong>#39967 Upgrade pnpm to 10.34.5</strong></li>
<li><strong>#39962 Keep Guardian reviews isolated from executor MCP servers</strong></li>
<li><strong>#39961 Test browser MCP bearer tokens over executor WebSockets</strong></li>
<li><strong>#39958 Stop advertising shell snapshots from local exec servers</strong></li>
<li><strong>#39953 Support voice-aware configuration and version-skew builds</strong></li>
<li><strong>#39952 Honor required MCP servers from selected executors</strong></li>
</ol>
<h2>Demand Trends</h2>
<ul>
<li><strong>Rollback-able checkpoints</strong> (#11626) is the #1 ask: users want not just chat rollback but &quot;code + context&quot; consistent recovery.</li>
<li><strong>Windows stability</strong> is still the #1 pain platform: plugin, installer, PSModulePath, WSL terminal each independently highly-upvoted.</li>
<li><strong>Local/private ecosystem friendly</strong>: #20621 opposes API-key users being blocked from private plugin marketplaces.</li>
<li><strong>Security tightening endorsed</strong>: remote-exec network policy, Guardian isolation are right directions.</li>
</ul>
<h2>Developer Notes</h2>
<ul>
<li><strong>/rewind is a watershed feature</strong>: 204👍 shows strong demand for &quot;undoable coding actions.&quot;</li>
<li><strong>Windows governance complexity is high</strong>: independently highly-upvoted issues from installer to runtime.</li>
<li><strong>Scheduled tasks self-disable</strong> (#38350) exposes a hidden automation-reliability risk.</li>
</ul>
</details>

<details>
<summary><strong>Gemini CLI</strong> — <a href="https://github.com/google-gemini/gemini-cli">google-gemini/gemini-cli</a></summary>

<h1>Gemini CLI Daily — 2026-08-22</h1>
<h2>Today at a glance</h2>
<p>Shipped v0.56.0-nightly.20260821 and v0.57.0-preview.0 (08-19); PR side extremely quiet (only 2 pr-generation-related). Community focus: license validation (#28912 &quot;no valid license&quot;), subagent trust (#22323 false GOAL success, #21409 generalist hangs) and &quot;under-uses skills/sub-agents&quot; (#21968).</p>
<h2>Releases</h2>
<ul>
<li><strong>v0.56.0-nightly.20260821</strong> (2026-08-21, nightly)</li>
<li><strong>v0.57.0-preview.0</strong> (2026-08-19, preview)</li>
<li><strong>v0.56.0</strong> (2026-08-19, stable)</li>
</ul>
<h2>Hot Issues (last 24h)</h2>
<ol>
<li><strong>#21409 Generalist agent hangs</strong> (8👍/8💬, open).</li>
<li><strong>#28912 &quot;You do not have a valid license of this product.&quot;</strong> (6👍/9💬, open) — license false-positive.</li>
<li><strong>#22323 Subagent recovery after MAX_TURNS reported as GOAL success, hiding interruption</strong> (2👍/13💬, open).</li>
<li><strong>#19873 Leverage model&#39;s bash affinity via Zero-Dependency OS Sandboxing &amp; Post-Execution Intent Routing</strong> (1👍/8💬, open).</li>
<li><strong>#22745 Assess impact of AST-aware file reads, search, mapping</strong> (1👍/7💬, open).</li>
<li><strong>#15269 Missing Subagent Hook Events</strong> (8💬, open).</li>
<li><strong>#25166 Shell command execution stuck with &quot;Waiting input&quot; after completion</strong> (3👍/4💬, open).</li>
<li><strong>#24353 Robust component-level evaluations</strong> (7💬, open).</li>
<li><strong>#21968 Gemini does not use skills and sub-agents enough</strong> (6💬, open).</li>
<li><strong>#26522 Stop Auto Memory from retrying low-signal sessions indefinitely</strong> (5💬, open).</li>
</ol>
<h2>Notable PRs (last 24h)</h2>
<ol>
<li><strong>#28951 feat(pr-generation): add Cloud Run job, Workflow orchestration, deployment pipeline</strong></li>
<li><strong>#28952 feat(pr-generation): add interactive diff comparison visualizer generator</strong></li>
</ol>
<h2>Demand Trends</h2>
<ul>
<li><strong>License &amp; trust</strong>: #28912 license false-positive, #22323 false GOAL success both erode user trust.</li>
<li><strong>Agent reliability</strong>: #21409 generalist hangs, #25166 shell stuck.</li>
<li><strong>Capability utilization</strong>: #21968 urges fuller use of skills/sub-agents; #26522 opposes unbounded auto-retry.</li>
</ul>
<h2>Developer Notes</h2>
<ul>
<li><strong>Subagent behavior unpredictability</strong> remains the trust shortfall (false success + hangs).</li>
<li><strong>PR side extremely quiet</strong>: only 2 pr-generation-related today — trust-building phase before feature deepening.</li>
<li><strong>License validation needs precision</strong>: #28912 false-positive hurts out-of-box experience.</li>
</ul>
</details>

<details>
<summary><strong>GitHub Copilot CLI</strong> — <a href="https://github.com/github/copilot-cli">github/copilot-cli</a></summary>

<h1>GitHub Copilot CLI Daily — 2026-08-22</h1>
<h2>Today at a glance</h2>
<p>No new release recently (latest v1.0.81-6 is 08-14), 0 PRs in 24h. Top asks: <strong>multiple BYOK models &amp; in-session model switch</strong> (#3282, #3709, 26👍 each) and <strong>sandbox cannot be disabled</strong> (#4521). Enterprise-managed context remains the core positioning.</p>
<h2>Releases</h2>
<ul>
<li>Still <a href="https://github.com/github/copilot-cli/releases/tag/v1.0.81-6">v1.0.81-6</a> (2026-08-14, prerelease); no new release today.</li>
</ul>
<h2>Hot Issues (last 24h)</h2>
<ol>
<li><strong>#3282 Add multiple BYOK model capability in copilot cli</strong> (26👍/8💬, open).</li>
<li><strong>#3709 Allow /model to switch between multiple models, including BYOK/local providers, in one session</strong> (26👍/4💬, open).</li>
<li><strong>#1313 Session Branching</strong> (13👍/7💬, open).</li>
<li><strong>#4345 Reasoning effort &#39;medium&#39; not supported for model &#39;claude-haiku-4.5&#39;</strong> (4👍/8💬, open).</li>
<li><strong>#4521 Sandbox cannot be disabled</strong> (4👍/3💬, open).</li>
<li><strong>#4422 All Claude models disabled under CLI model selection</strong> (3👍/4💬, closed).</li>
<li><strong>#4485 Theme turns light over night</strong> (2👍/2💬, open).</li>
<li><strong>#4038 Non-interactive mode: late-connecting MCP server injects empty user message</strong> (3💬, closed).</li>
<li><strong>#4542 Workspace .mcp.json detected by &#39;mcp list&#39;/&#39;mcp get&#39; but not connected in actual agent session</strong> (1👍/1💬, open).</li>
<li><strong>#4511 Session AIC display is not reliable</strong> (2💬, open).</li>
</ol>
<h2>Notable PRs</h2>
<p>No new PR entered the window today.</p>
<h2>Demand Trends</h2>
<ul>
<li><strong>Multi-model / BYOK freedom</strong>: #3282/#3709 highly upvoted; in-session model switch is a shared ask for enterprise and individuals.</li>
<li><strong>Sandbox fully disablable</strong>: #4521 shows managed-environment policy too strict.</li>
<li><strong>MCP connection consistency</strong>: #4542 workspace config recognized but not connected — needs end-to-end validation.</li>
</ul>
<h2>Developer Notes</h2>
<ul>
<li><strong>Insufficient model-choice freedom</strong>: single-session BYOK/local switch is a repeatedly-urged baseline capability.</li>
<li><strong>Sandbox policy still too强制</strong>: explicit disable ineffective — core enterprise pain.</li>
<li><strong>No new release recently</strong>: main branch in a stable phase awaiting next feature drop.</li>
</ul>
</details>

<details>
<summary><strong>Kimi Code CLI</strong> — <a href="https://github.com/MoonshotAI/kimi-cli">MoonshotAI/kimi-cli</a></summary>

<h1>Kimi Code CLI Daily 2026-08-22</h1>
<h2>Today at a glance</h2>
<p>Near-silent today: only 1 issue entered the window, 0 PRs and 0 releases (latest 1.49.0 is 07-16). Versus the high activity of other CLIs, Kimi Code&#39;s ecosystem remains in an early silent phase.</p>
<h2>Releases</h2>
<p>No new release today (latest 1.49.0, 2026-07-16).</p>
<h2>Hot Issues</h2>
<ol>
<li><strong>#2615 Background subagent keeps making LLM calls after TaskStop/timeout marks it terminal</strong> (open) — process-lifecycle governance.</li>
</ol>
<h2>Notable PRs</h2>
<p>No updates today.</p>
<h2>Demand Trends</h2>
<p>Given the sustained low activity, the community&#39;s current focus is likely on internal ACP/IDE base-link iteration; external voice is limited.</p>
<h2>Developer Notes</h2>
<ul>
<li>Ecosystem early, lowest activity among the 7 CLIs; watch for follow-up fixes to its ACP runtime tool-capability boundaries.</li>
</ul>
</details>

<details>
<summary><strong>OpenCode</strong> — <a href="https://github.com/anomalyco/opencode">anomalyco/opencode</a></summary>

<h1>OpenCode Daily — 2026-08-22</h1>
<h2>Today at a glance</h2>
<p>Shipped <strong>v1.18.21 / v1.18.20</strong> (2026-08-21); highly active community — 78 PR updates in 24h. Top asks: <strong>#785 &quot;disable streaming mode?&quot;</strong> (38👍/31💬) and <strong>#24153 &quot;unarchive/restore for archived sessions&quot;</strong> (11👍/9💬). Reliability centers on &quot;session silently stops on empty LLM response&quot; (#41469) and &quot;randomly stops responding&quot; (#34473).</p>
<h2>Releases</h2>
<ul>
<li><a href="https://github.com/anomalyco/opencode/releases/tag/v1.18.21">v1.18.21</a> (2026-08-21)</li>
<li><a href="https://github.com/anomalyco/opencode/releases/tag/v1.18.20">v1.18.20</a> (2026-08-21)</li>
<li><a href="https://github.com/anomalyco/opencode/releases/tag/v1.18.19">v1.18.19</a> (2026-08-20)</li>
</ul>
<h2>Hot Issues (last 24h)</h2>
<ol>
<li><strong>#785 Is there a way to disable streaming mode?</strong> (38👍/31💬, open).</li>
<li><strong>#24153 Add unarchive/restore for archived sessions</strong> (11👍/9💬, open).</li>
<li><strong>#41469 Session silently stops on empty LLM response (finish: unknown, 0 tokens)</strong> (10💬, open) — pollutes billing &amp; evaluation.</li>
<li><strong>#34473 Opencode randomly stops responses</strong> (3👍/6💬, open).</li>
<li><strong>#37345 Edit Project: icon/color changes not persisted to database</strong> (4💬, open).</li>
<li><strong>#33219 Add FreeBSD support</strong> (2💬, closed).</li>
<li><strong>#43882 muse-spark stream always ends without finish_reason</strong> (2💬, open).</li>
<li><strong>#43907 TUI: copying doesn&#39;t work</strong> (2💬, closed).</li>
<li><strong>#41847 Permission dialogs not rendered; backend blocks on invisible prompts, app appears frozen</strong> (2💬, open).</li>
<li><strong>#36196 V2: improve tool search namespaces, reduce tool-context cache busts</strong> (2💬, closed).</li>
</ol>
<h2>Notable PRs (last 24h selected)</h2>
<ol>
<li><strong>#41936 fix(util): bound npm installs with a configurable timeout</strong></li>
<li><strong>#43183 fix(tui): keep file attachment badge readable with the system theme</strong></li>
<li><strong>#42927 feat(tui): display context window limit in token usage counter and sidebar</strong></li>
<li><strong>#42986 fix(shell): scan redirection targets for external_directory</strong></li>
<li><strong>#42907 fix(tui): sort child sessions by created time, not session ID</strong></li>
<li><strong>#42819 fix(session): delete reverted messages boundary-last, tie-break ids by raw order</strong></li>
<li><strong>#41723 fix(core): preserve unsupported image attachments as text instead of dropping</strong></li>
<li><strong>#42833 fix(session-ui): prevent variant select overlap on mobile</strong></li>
<li><strong>#42842 fix(i18n): correct Catalan (ca) locale, add ca glossary</strong></li>
<li><strong>#42936 feat(lsp): add Marksman language server for Markdown</strong></li>
</ol>
<h2>Demand Trends</h2>
<ul>
<li><strong>Reliability first</strong>: #41469 empty-response miscount, #34473 random stop directly pollute billing &amp; evaluation.</li>
<li><strong>Streaming controllability</strong>: #785 disable streaming is the top UX ask.</li>
<li><strong>Session management</strong>: #24153 archive restore, #42907 child-session sort.</li>
<li><strong>Provider breadth</strong>: llmgateway, QwenCloud, Vertex keep expanding.</li>
</ul>
<h2>Developer Notes</h2>
<ul>
<li><strong>Billing credibility</strong>: empty response miscounted as clean stop (finish: unknown, 0 tokens) pollutes billing &amp; evaluation.</li>
<li><strong>Active contributor ecosystem</strong>: 78 PRs push TUI/session/core multi-dimensional fixes.</li>
<li><strong>Streaming semantics stability</strong>: disable-streaming ask reflects streaming/interrupt handling still a UX shortfall.</li>
</ul>
</details>

<details>
<summary><strong>Qwen Code</strong> — <a href="https://github.com/QwenLM/qwen-code">QwenLM/qwen-code</a></summary>

<h1>Qwen Code Daily — 2026-08-22</h1>
<h2>Today at a glance</h2>
<p>Shipped <strong>v0.21.14-nightly.20260821</strong> and v0.21.15 (08-20); 82 PR updates in 24h — mature industrial PR pipeline. Focus PRs: <strong>#8368 adds Kimi &amp; Xiaomi MiMo providers</strong> (68💬), <strong>#8332 audio bridge for attachments</strong> (67💬), <strong>#8276 preserves prompt cache across deferred tool discovery</strong> (64💬), <strong>#8992 MCP 2026 core + WebShell Apps host</strong> (32💬). Issue side lower heat (18 items, highest only 7 comments).</p>
<h2>Releases</h2>
<ul>
<li><a href="https://github.com/QwenLM/qwen-code/releases/tag/v0.21.14-nightly.20260821">v0.21.14-nightly.20260821</a> (2026-08-21, nightly)</li>
<li><a href="https://github.com/QwenLM/qwen-code/releases/tag/v0.21.15">v0.21.15</a> (2026-08-20, stable)</li>
</ul>
<h2>Hot Issues (last 24h)</h2>
<ol>
<li><strong>#5180 Main session as PM dispatching tasks; subagent crashes halfway</strong> (7💬, open) — multi-agent orchestration stability.</li>
<li><strong>#8993 Public extension installs require Git 2.37, but Ubuntu 22.04 apt provides only 2.34.1</strong> (6💬, closed) — install门槛.</li>
<li><strong>#5966 0.19.3 UI intermittent error, Chinese IME completely invalid</strong> (6💬, open) — i18n/IME.</li>
<li><strong>#7167 Fleet Shepherd Dashboard</strong> (3💬, open).</li>
<li><strong>#8094 Transport-continuation recovery leaves resumed transcript starting mid-sentence</strong> (3💬, closed).</li>
<li><strong>#9571 Avoid confirmation boxes being selected by default</strong> (3💬, closed).</li>
<li><strong>#9494 Slash command menu selection resets to first item while streaming</strong> (3💬, closed).</li>
<li><strong>#9487 Web shell loading indicators drop mid-turn on long tasks</strong> (3💬, closed).</li>
<li><strong>#9675 MCP server disconnected between sessions even though configured</strong> (3💬, open).</li>
<li><strong>#9693 Qwen Desktop reports MCP -32000 Connection closed on Windows at startup</strong> (2💬, open).</li>
</ol>
<h2>Notable PRs (last 24h selected)</h2>
<ol>
<li><strong>#8368 feat(auth): add Kimi and Xiaomi MiMo providers</strong> (68💬, open)</li>
<li><strong>#8332 feat(cli): add audio bridge for attachments</strong> (67💬, open)</li>
<li><strong>#8276 fix(core): preserve prompt cache across deferred tool discovery</strong> (64💬, open)</li>
<li><strong>#8902 fix(cli): derive bootstrap --help from shared option definitions</strong> (43💬, open)</li>
<li><strong>#9513 fix(cli): Restore PR2A session behaviors</strong> (38💬, open)</li>
<li><strong>#9273 feat(review): capture-tui — rendering claims get pixels, not prose</strong> (32💬, open)</li>
<li><strong>#8992 feat(mcp): add MCP 2026 core and WebShell Apps host</strong> (32💬, open)</li>
<li><strong>#9526 feat(review): add persistently-critical convergence advisory (land-with-residual-risk)</strong> (31💬, open)</li>
<li><strong>#8927 feat(channels): bound session lifetime with sessionRotation</strong> (29💬, open)</li>
<li><strong>#9350 feat(dingtalk): support outbound file delivery</strong> (27💬, open)</li>
</ol>
<h2>Demand Trends</h2>
<ul>
<li><strong>Provider breadth</strong>: Kimi, MiMo onboarding (#8368); Volcengine/Mattermost etc. sync-expanding externally.</li>
<li><strong>Cost &amp; cache transparency</strong>: #8276 preserves prompt cache directly ties to billing credibility.</li>
<li><strong>Multimodal &amp; channels</strong>: audio bridge (#8332), WebShell Apps host (#8992), DingTalk file delivery (#9350).</li>
<li><strong>Review automation</strong>: capture-tui, convergence advisory, review loop.</li>
</ul>
<h2>Developer Notes</h2>
<ul>
<li><strong>Industrial release gate</strong>: 82 PRs densely merged show a highly automated release/CI system.</li>
<li><strong>Route-identity-bound usage</strong>: #8276 preserves prompt cache improves billing credibility.</li>
<li><strong>Multi-agent orchestration stability</strong>: #5180 subagent mid-crash needs attention.</li>
</ul>
</details>

<hr>
<h2>Claude Code Skills Hot Topics</h2>
<blockquote>
<p>Source: <a href="https://github.com/anthropics/skills">anthropics/skills</a> | last 24h</p>
</blockquote>
<ul>
<li><strong>#1620 / #1625 Shell command injection: with_server.py --server uses shell=True</strong> (#1620 closed, #1625 open) — security hazard in skill metadata/example scripts.</li>
<li><strong>#1624 claude-api SKIP grep unanchored — <code>cohere</code> matches &quot;coherent&quot;, disabling the skill in repos containing the word</strong> (open).</li>
<li><strong>#1622 claude-api skill description exceeds the 1024-char frontmatter cap (1077 chars)</strong> (open).</li>
<li><strong>#1621 / #1619 MCPConnectionSSE/HTTP and MCPConnectionStdio accept caller-supplied arbitrary URL/headers/command</strong> (open) — supply-chain security risk in MCP connectors.</li>
<li><strong>#1627 feat: add buffer-api Agent Skill (Buffer GraphQL scheduling)</strong> (open).</li>
<li><strong>#1623 Update claude-api skill: Python SDK 0.x → 1.x upgrade guide</strong> (closed).</li>
</ul>
<p>The Skills ecosystem today focuses on <strong>security auditing</strong> (command injection, MCP arbitrary command exec) and point fixes; no large architectural discussion.</p>
<hr>
<p><em>This digest is generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. All content is fetched live from GitHub&#39;s public API and written by the executing agent — no external LLM was called.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Agents 生态日报 2026-08-22</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-agents</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-agents</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
      <description>OpenClaw 生态社区动态日报 2026-08-22 生成时间: 2026-08-22 02:30 (GMT+8) | 覆盖: OpenClaw + 12 个 peer 项目 本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。 OpenClaw NanoBot Zeroclaw PicoClaw NanoClaw NullClaw IronClaw LobsterAI TinyClaw CoPaw Moltis ZeptoClaw EasyClaw 跨生态对比 OpenClaw 跨生态对比分析报告（2026-08-22） 1. 生态全景 OpenClaw 本体今日 41 条 issue、59 个 PR 更新，主干聚焦会话目录刷新风暴治理、诊断恢复、安装策略告警、UI 决策回执；12 个 peer 中，IronClaw（31 PR）、CoPaw（36 PR）、Zeroclaw（95 PR）、NanoClaw（14 PR）、LobsterAI（13 PR）、Moltis（6 PR）贡献活跃，NullClaw / ...</description>
      <content:encoded><![CDATA[<h1>OpenClaw 生态社区动态日报 2026-08-22</h1>
<blockquote>
<p>生成时间: 2026-08-22 02:30 (GMT+8) | 覆盖: OpenClaw + 12 个 peer 项目
本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。</p>
</blockquote>
<ul>
<li><a href="https://github.com/openclaw/openclaw">OpenClaw</a></li>
<li><a href="https://github.com/HKUDS/nanobot">NanoBot</a></li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw">Zeroclaw</a></li>
<li><a href="https://github.com/sipeed/picoclaw">PicoClaw</a></li>
<li><a href="https://github.com/qwibitai/nanoclaw">NanoClaw</a></li>
<li><a href="https://github.com/nullclaw/nullclaw">NullClaw</a></li>
<li><a href="https://github.com/nearai/ironclaw">IronClaw</a></li>
<li><a href="https://github.com/netease-youdao/LobsterAI">LobsterAI</a></li>
<li><a href="https://github.com/TinyAGI/tinyclaw">TinyClaw</a></li>
<li><a href="https://github.com/agentscope-ai/CoPaw">CoPaw</a></li>
<li><a href="https://github.com/moltis-org/moltis">Moltis</a></li>
<li><a href="https://github.com/qhkm/zeptoclaw">ZeptoClaw</a></li>
<li><a href="https://github.com/gaoyangz77/easyclaw">EasyClaw</a></li>
</ul>
<hr>
<h2>跨生态对比</h2>
<h1>OpenClaw 跨生态对比分析报告（2026-08-22）</h1>
<h2>1. 生态全景</h2>
<p>OpenClaw 本体今日 41 条 issue、59 个 PR 更新，主干聚焦<strong>会话目录刷新风暴治理、诊断恢复、安装策略告警、UI 决策回执</strong>；12 个 peer 中，IronClaw（31 PR）、CoPaw（36 PR）、Zeroclaw（95 PR）、NanoClaw（14 PR）、LobsterAI（13 PR）、Moltis（6 PR）贡献活跃，<strong>NullClaw / TinyClaw / ZeptoClaw 完全静默</strong>，EasyClaw 仅有版本发布无 issue/PR。整体趋势从「单 agent 聊天」走向<strong>多渠道 + 持久化记忆 + 自动化（automations/run-now）+ 企业级沙箱/鉴权</strong>。</p>
<h2>2. 各项目活跃度对比（近 24h）</h2>
<table>
<thead>
<tr>
<th>项目</th>
<th>Issues</th>
<th>PRs</th>
<th>Releases</th>
</tr>
</thead>
<tbody><tr>
<td>OpenClaw</td>
<td>41</td>
<td>59</td>
<td>v2026.8.1-beta.2（08-15）</td>
</tr>
<tr>
<td>NanoBot</td>
<td>5</td>
<td>34</td>
<td>v0.3.0（07-25）</td>
</tr>
<tr>
<td>Zeroclaw</td>
<td>5</td>
<td>95</td>
<td>v0.8.4（08-02）</td>
</tr>
<tr>
<td>PicoClaw</td>
<td>1</td>
<td>4</td>
<td>nightly（07-02）</td>
</tr>
<tr>
<td>NanoClaw</td>
<td>1</td>
<td>14</td>
<td>v2.2.0（08-13）</td>
</tr>
<tr>
<td>NullClaw</td>
<td>0</td>
<td>1</td>
<td>v2026.5.29</td>
</tr>
<tr>
<td>IronClaw</td>
<td>12</td>
<td>31</td>
<td>ironclaw-v1.3.0（08-19）</td>
</tr>
<tr>
<td>LobsterAI</td>
<td>2</td>
<td>13</td>
<td>2026.8.18</td>
</tr>
<tr>
<td>TinyClaw</td>
<td>0</td>
<td>0</td>
<td>v0.0.20（03-26）</td>
</tr>
<tr>
<td>CoPaw</td>
<td>34</td>
<td>36</td>
<td>v2.1.1-beta.1（08-20）</td>
</tr>
<tr>
<td>Moltis</td>
<td>2</td>
<td>6</td>
<td>20260820.01（08-20）</td>
</tr>
<tr>
<td>ZeptoClaw</td>
<td>0</td>
<td>0</td>
<td>v0.9.2（04-07）</td>
</tr>
<tr>
<td>EasyClaw</td>
<td>0</td>
<td>0</td>
<td>v1.8.109（08-21）</td>
</tr>
</tbody></table>
<h2>3. 共同关注方向</h2>
<ul>
<li><strong>多渠道接入与消息可靠性</strong>：NanoBot（DingTalk 不观测/不排空后台任务 #5463、流式 provider 中段 server_error 跳过重试 #5454、Notion MCP 连接失败 #1168）；NanoClaw（send_card 文档承诺的回调按钮被 bridge 丢弃 #3426、Dial 短信+语音 #3041、Mattermost #3202）；Moltis（共享 Slack 频道工具失效 #1224、WhatsApp Markdown 渲染 #1220）。</li>
<li><strong>记忆与上下文治理</strong>：OpenClaw 会话目录刷新风暴治理（#123535，154💬）、诊断恢复重叠工具调用（#124025，46💬）；IronClaw 可插拔 memory over MCP（#7664）；CoPaw ReMeLightMemoryCard reranker 面板（#6399）、embedding 健康检查超时硬编码（#7156）；Zeroclaw 上下文压缩锚定模型窗口比（#9535）。</li>
<li><strong>自动化与企业级</strong>：IronClaw 从运行时证据派生 run 结果（#7650，45💬）、benchmark QA 预览（#7749，39💬）、omp core-tool 契约（#7491，37💬）、可插拔 memory（#7664）；CoPaw 每会话模型覆盖（#5992，9💬）；Moltis cron 尊重 heartbeat active_hours（#1208）。</li>
<li><strong>安全与稳定性</strong>：OpenClaw 安装策略告警确认（#116489，49💬）、typecheck 挂死修复（#123975，45💬）、SSH 沙箱不暂存入站媒体（#112160）；Moltis 修复 WhatsApp/沙箱镜像校验（#1222、#1220）；CoPaw MCP 后端重启无法自动恢复（#6524）。</li>
<li><strong>开发者体验 / 设计系统</strong>：IronClaw WebUI 设计系统（#7257，#7750 Storybook）；OpenClaw UI 决策回执说明（#126007）、新聊天 worktree 从干净默认启动（#126056）。</li>
</ul>
<h2>4. 差异化定位</h2>
<ul>
<li><strong>OpenClaw</strong>：生态中枢，主攻会话/目录治理、诊断恢复、安装策略与 UI 决策透明，企业受管语境。</li>
<li><strong>NanoBot</strong>：渠道广（Telegram/Matrix/Slack/WebUI），重 Dream 恢复游标与轨迹统一 provider 用量后端（#5479）。</li>
<li><strong>Zeroclaw</strong>：Rust 核心，RFC/ADR 驱动「更轻核心 + 外部集成」，wire protocol 一等公民（#8396）、canonical 沙箱策略 schema（#7821，20💬）。</li>
<li><strong>NanoClaw</strong>：多 provider 接入（Dial/WhatsApp/Mattermost/Matrix），强调模板创建 agent（#3396）与刷新安全的 ESM 补丁（#3403）。</li>
<li><strong>IronClaw</strong>：每用户沙箱 + 结构化 automations + 设计系统 + Telegram 关联，企业/团队向，CI 提速专题（T1-T4）。</li>
<li><strong>LobsterAI</strong>：cowork 文件卡片/分屏、设置面板搜索、i18n 硬编码修复，体验向。</li>
<li><strong>CoPaw (QwenPaw)</strong>：记忆 ReMe、自托管多用户、Volcengine Agent Plan &amp; MiMo V2.5 provider（#6515），社区活跃度最高之一。</li>
<li><strong>Moltis</strong>：WhatsApp 为中心，重渠道安全（Vault/沙箱镜像校验）与 cron 调度。</li>
<li><strong>EasyClaw (rivonclaw)</strong>：高频小版本（每日多版 v1.8.109/108），商务开发筛选等垂直功能。</li>
<li><strong>PicoClaw / NullClaw / TinyClaw / ZeptoClaw</strong>：低活跃或静默。</li>
</ul>
<h2>5. 趋势信号</h2>
<ul>
<li><strong>静默项目需关注</strong>：NullClaw / TinyClaw / ZeptoClaw 连续多日 0 动态，EasyClaw 仅发版无交互，生态健康度分化明显。</li>
<li><strong>自动化成为一等公民</strong>：IronClaw/CoPaw 的 automations/run-now/Hub 标志 agent 从「对话」走向「可编排任务」。</li>
<li><strong>安全与稳定性从可选到必需</strong>：安装策略告警确认（CWE 类风险）、typecheck 挂死、MCP 重启恢复成为高频修复。</li>
<li><strong>记忆是跨项目主线</strong>：从 OpenClaw 会话治理到 IronClaw/CoPaw 记忆系统，持久化记忆仍是 2026 年 agent 框架竞争焦点。</li>
</ul>
<hr>
<h2>OpenClaw 详细动态</h2>
<blockquote>
<p>数据来源: <a href="https://github.com/openclaw/openclaw">openclaw/openclaw</a> | 近 24h（issue 41 / PR 59）</p>
</blockquote>
<h3>热点 Issues</h3>
<ol>
<li><strong>#125626 Release validation: v2026.8.1-beta.2</strong>（18💬，开放）— 新版发布校验跟踪。</li>
<li><strong>#124751 iOS app 在底部重复助手回复且不自动滚动到最新</strong>（6💬，开放）— 移动端渲染。</li>
<li><strong>#113014 Webchat：原始 MEDIA: 指令泄漏到可见回复文本</strong>（5💬，开放）— 指令注入可见化。</li>
<li><strong>#90243 feat(llm/google-vertex)：支持物理模型映射/别名以对接 Google Prior</strong>（3💬，开放）— 模型路由。</li>
<li><strong>#124689 Model picker 仅对新会话生效；Ollama Cloud 请求登录</strong>（4💬，开放）。</li>
<li><strong>#112160 SSH 沙箱不将入站媒体暂存到已有远程工作区</strong>（4💬，开放）。</li>
<li><strong>#10944 Telegram 频道 parseMode 配置需求</strong>（4💬，开放）。</li>
<li><strong>#126231 handler-timeout ingress 事件 attempts=0 静默丢消息</strong>（3💬，已关闭）。</li>
<li><strong>#126813 排队的 peer 消息以 answer-expected 提示重唤 agent 且无确认</strong>（3💬，开放）。</li>
<li><strong>#100911 Tasks 页面 / tasks.list 边界加固</strong>（2💬，开放）。</li>
</ol>
<h3>重要 PR 进展（按讨论热度）</h3>
<ol>
<li><strong>#123535 fix(ui)：避免会话目录刷新风暴</strong>（154💬，开放）</li>
<li><strong>#123979 fix(scripts)：build heap 忽略 systemd 内存预算而占满默认</strong>（56💬，开放）</li>
<li><strong>#116489 feat(security)：安装策略告警需显式确认</strong>（49💬，已关闭）</li>
<li><strong>#123975 fix(scripts)：tsgo 卡死时 typecheck 永久挂起</strong>（45💬，开放）</li>
<li><strong>#124025 fix(diagnostics)：恢复过期重叠工具调用</strong>（46💬，开放）</li>
<li><strong>#120900 feat(ui)：审查安装策略告警</strong>（44💬，已关闭）</li>
<li><strong>#125815 fix(sessions)：保持 owner 分配稳定、回复可用</strong>（38💬，开放）</li>
<li><strong>#126618 fix：Tool Search 目录/tools 用 tool_call 包裹原生 read/exec</strong>（26💬，开放）</li>
<li><strong>#126007 feat(ui)：在 Activity 中解释决策回执</strong>（25💬，开放）</li>
<li><strong>#126056 fix(ui)：新聊天 worktree 从干净默认启动</strong>（21💬，开放）</li>
</ol>
<hr>
<h2>Peer 项目动态精选</h2>
<h3>NanoBot（HKUDS/nanobot）— I5 / P34</h3>
<ul>
<li>Issues：#5198 特定会话改模型需重配（已关闭）、#1168 Notion MCP 连接失败（已关闭）、#5441 单点恢复的工具错误永久阻塞（已关闭）、#5463 DingTalk 不观测/不排空后台任务（开放）、#5454 流式 provider 中段 server_error 跳过重试（已关闭）。</li>
<li>PRs：#5442 fix(dream) 恢复游标、#5379 fix(memory) 保留完整合并输入（开放）、#5476 渲染 LaTeX 为 Unicode（已关闭）、#2063 Tauri 桌面端（已关闭）、#5455 重试 Codex server_error（已关闭）、#5479 feat(trajectory) 统一 provider 用量后端（开放）。</li>
</ul>
<h3>Zeroclaw（zeroclaw-labs/zeroclaw）— I5 / P95</h3>
<ul>
<li>Issues：#8396 RFC 使 wire protocol 成为 provider 构造一等公民（开放）、#8691 ADR 清单与已接受 RFC 决策记录（开放）、#10167 终端 agent 多路复用的 vendor-neutral 生命周期导出（开放）、#8288 SOP 里程碑 daemon 控制面 5/5（开放）、#10212 文档 switch 路由优先级（开放）。</li>
<li>PRs：#8561 feat(channels/telegram) 多消息流式（33💬）、#7821 feat(security) canonical 沙箱策略 schema（20💬）、#9447 fix(anthropic) 分类不完整终端响应（19💬）、#9196 feat(mcp) 聚合预算预检 materialize 资源 blob（19💬）、#9772 feat(telegram) 共享群聊每用户会话开关（18💬）、#9535 feat(runtime) 上下文压缩锚定模型窗口比（17💬）。</li>
</ul>
<h3>NanoClaw（qwibitai/nanoclaw）— I1 / P14</h3>
<ul>
<li>Issue：#3426 send_card 文档承诺的回调按钮被 bridge 自 #2265 起丢弃。</li>
<li>PRs：#3041 feat(channels) 新增 Dial 通道（SMS+AI 语音，已关闭）、#3202 新增 Mattermost 集成（已关闭）、#3050 Dial 通道选择器（已关闭）、#3396 feat 从模板在聊天中创建 agent（开放）、#3424 ci 测试 registry-backed skills（已关闭）、#3403 fix(matrix) 刷新安全 ESM 补丁（已关闭）。</li>
</ul>
<h3>NullClaw（nullclaw/nullclaw）— I0 / P1</h3>
<ul>
<li>PR：#990 feat(providers) 新增 Eden AI 作为 OpenAI 兼容网关（开放）。</li>
</ul>
<h3>IronClaw（nearai/ironclaw）— I12 / P31</h3>
<ul>
<li>Issues：#7801 CI 提速 T4 规范预检（开放）、#7799 T2 nextest 流水线（开放）、#7800 T3 PR/队列收敛（开放）、#7798 T1 setup-rust 复合（开放）、#7664 可插拔 memory over MCP（开放）、#7783 LLM 超时策略 finalization 无法测 TTFT（已关闭）。</li>
<li>PRs：#7650 feat(automations) 从运行时证据派生 run 结果（45💬）、#7749 benchmark QA 预览触发（39💬）、#7491 feat(coding) omp core-tool 契约+引擎+benchmark（37💬）、#7456 fix(reborn) 持久存储 profile 无关（12💬）、#7257 docs(design-system) WebUI 设计系统（11💬）、#7750 chore(webui) 集成 Storybook+设计系统目录（10💬）。</li>
</ul>
<h3>LobsterAI（netease-youdao/LobsterAI）— I2 / P13</h3>
<ul>
<li>Issues：#1217 运行中偶发启动网关（已关闭）、#1223 CoworkPromptInput 硬编码中文标签导致英文提示词混入（已关闭）。</li>
<li>PRs：#1218 重构定时任务排序（已关闭）、#1215 始终重建 chat handler（已关闭）、#1219 消除会话列表/详情无效重渲染（已关闭）、#1220 消除 recentChats 的 N+1 查询（已关闭）、#1224 修复 i18n 硬编码与 Escape 键（已关闭）、#1550 fix(scheduledTask) 投递模式「不通知」时去除 channel/to 字段（开放）。</li>
</ul>
<h3>TinyClaw（TinyAGI/tinyclaw）— I0 / P0</h3>
<ul>
<li>无近 24h 动态（最新 v0.0.20，03-26）。</li>
</ul>
<h3>CoPaw（agentscope-ai/CoPaw）— I34 / P36</h3>
<ul>
<li>Issues：#6524 MCP 后端重启后客户端无法自动恢复（开放）、#6780 2.0.1 不使用时会卡死（已关闭）、#7016 工具调用 404（开放）、#7156 embedding 健康检查在已预热时仍超时且硬编码（开放）、#7206 v2.1.1-beta.1 /compact 因 pydantic ValidationError 失败（开放）、#7204 qwenpaw 如何增加自定义 tool（开放）。</li>
<li>PRs：#5992 每会话模型覆盖（9💬）、#6515 feat(providers) 新增 Volcengine Agent Plan &amp; MiMo V2.5（9💬）、#6845 保留 assistant 完成时间（已关闭）、#6581 ReMeLightMemoryCard reranker UI 面板（开放）、#6399 新增 reranker UI 配置（开放）、#6586 fix(mcp) 恢复过期 server 会话（已关闭）。</li>
</ul>
<h3>Moltis（moltis-org/moltis）— I2 / P6</h3>
<ul>
<li>Issues：#1224 共享 Slack 频道工具停止工作（开放）、#1223 heartbeat active_hours 对默认配置无效（开放）。</li>
<li>PRs：#1220 渲染 WhatsApp 出站 Markdown（8💬，已关闭）、#1208 修复 cron 尊重 heartbeat active_hours（4💬，开放）、#468 Windows 用 cmd.exe 执行 shell hooks（开放）、#1226 定时输出投递到源聊天（开放）、#1225 改进 zh-TW 繁体中文（开放）、#1222 校验沙箱镜像请求（开放）。</li>
</ul>
<h3>ZeptoClaw（qhkm/zeptoclaw）— I0 / P0</h3>
<ul>
<li>无近 24h 动态（最新 v0.9.2，04-07）。</li>
</ul>
<h3>EasyClaw（gaoyangz77/easyclaw）— I0 / P0 / 发版 v1.8.109、v1.8.108（08-21）</h3>
<ul>
<li>今日仅发版，无 issue/PR 交互。</li>
</ul>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，所有内容基于 GitHub 公开 API 实时抓取并由执行代理人工撰写，未调用任何外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Agents Ecosystem Digest 2026-08-22</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-agents-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-agents-en</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
      <description>OpenClaw Ecosystem Community Daily — 2026-08-22 Generated: 2026-08-22 02:30 (GMT+8) | Coverage: OpenClaw + 12 peer projects This digest is produced by the agents-radar local automation. All summaries, comparisons, and writing are done by the executing agent — no external LLM API was called. OpenClaw NanoBot Zeroclaw PicoClaw NanoClaw NullClaw IronClaw LobsterAI TinyClaw CoPaw Moltis ZeptoClaw EasyClaw Cross-Ecosystem Comparison OpenClaw Cross-Ecosystem Comparison Report (2026-08-22) 1. Ecosystem...</description>
      <content:encoded><![CDATA[<h1>OpenClaw Ecosystem Community Daily — 2026-08-22</h1>
<blockquote>
<p>Generated: 2026-08-22 02:30 (GMT+8) | Coverage: OpenClaw + 12 peer projects
This digest is produced by the agents-radar local automation. All summaries, comparisons, and writing are done by the executing agent — no external LLM API was called.</p>
</blockquote>
<ul>
<li><a href="https://github.com/openclaw/openclaw">OpenClaw</a></li>
<li><a href="https://github.com/HKUDS/nanobot">NanoBot</a></li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw">Zeroclaw</a></li>
<li><a href="https://github.com/sipeed/picoclaw">PicoClaw</a></li>
<li><a href="https://github.com/qwibitai/nanoclaw">NanoClaw</a></li>
<li><a href="https://github.com/nullclaw/nullclaw">NullClaw</a></li>
<li><a href="https://github.com/nearai/ironclaw">IronClaw</a></li>
<li><a href="https://github.com/netease-youdao/LobsterAI">LobsterAI</a></li>
<li><a href="https://github.com/TinyAGI/tinyclaw">TinyClaw</a></li>
<li><a href="https://github.com/agentscope-ai/CoPaw">CoPaw</a></li>
<li><a href="https://github.com/moltis-org/moltis">Moltis</a></li>
<li><a href="https://github.com/qhkm/zeptoclaw">ZeptoClaw</a></li>
<li><a href="https://github.com/gaoyangz77/easyclaw">EasyClaw</a></li>
</ul>
<hr>
<h2>Cross-Ecosystem Comparison</h2>
<h1>OpenClaw Cross-Ecosystem Comparison Report (2026-08-22)</h1>
<h2>1. Ecosystem Overview</h2>
<p>OpenClaw core shows 41 issues and 59 PR updates today, with the main branch focused on <strong>session-catalog refresh-storm governance, diagnostics recovery, install-policy warnings, and UI decision receipts</strong>. Among the 12 peers, IronClaw (31 PRs), CoPaw (36 PRs), Zeroclaw (95 PRs), NanoClaw (14 PRs), LobsterAI (13 PRs), and Moltis (6 PRs) are active, while <strong>NullClaw / TinyClaw / ZeptoClaw are completely silent</strong> and EasyClaw only ships releases with no issue/PR interaction. The overall trend moves from &quot;single-agent chat&quot; toward <strong>multi-channel + persistent memory + automation (automations/run-now) + enterprise-grade sandbox/auth</strong>.</p>
<h2>2. Activity Comparison (last 24h)</h2>
<table>
<thead>
<tr>
<th>Project</th>
<th>Issues</th>
<th>PRs</th>
<th>Releases</th>
</tr>
</thead>
<tbody><tr>
<td>OpenClaw</td>
<td>41</td>
<td>59</td>
<td>v2026.8.1-beta.2 (08-15)</td>
</tr>
<tr>
<td>NanoBot</td>
<td>5</td>
<td>34</td>
<td>v0.3.0 (07-25)</td>
</tr>
<tr>
<td>Zeroclaw</td>
<td>5</td>
<td>95</td>
<td>v0.8.4 (08-02)</td>
</tr>
<tr>
<td>PicoClaw</td>
<td>1</td>
<td>4</td>
<td>nightly (07-02)</td>
</tr>
<tr>
<td>NanoClaw</td>
<td>1</td>
<td>14</td>
<td>v2.2.0 (08-13)</td>
</tr>
<tr>
<td>NullClaw</td>
<td>0</td>
<td>1</td>
<td>v2026.5.29</td>
</tr>
<tr>
<td>IronClaw</td>
<td>12</td>
<td>31</td>
<td>ironclaw-v1.3.0 (08-19)</td>
</tr>
<tr>
<td>LobsterAI</td>
<td>2</td>
<td>13</td>
<td>2026.8.18</td>
</tr>
<tr>
<td>TinyClaw</td>
<td>0</td>
<td>0</td>
<td>v0.0.20 (03-26)</td>
</tr>
<tr>
<td>CoPaw</td>
<td>34</td>
<td>36</td>
<td>v2.1.1-beta.1 (08-20)</td>
</tr>
<tr>
<td>Moltis</td>
<td>2</td>
<td>6</td>
<td>20260820.01 (08-20)</td>
</tr>
<tr>
<td>ZeptoClaw</td>
<td>0</td>
<td>0</td>
<td>v0.9.2 (04-07)</td>
</tr>
<tr>
<td>EasyClaw</td>
<td>0</td>
<td>0</td>
<td>v1.8.109 (08-21)</td>
</tr>
</tbody></table>
<h2>3. Shared Directions</h2>
<ul>
<li><strong>Multi-channel access &amp; message reliability</strong>: NanoBot (DingTalk doesn&#39;t observe/drain background tasks #5463, streaming provider mid-stream server_error skips retry #5454, Notion MCP failure #1168); NanoClaw (send_card doc-promised callback buttons dropped by bridge #3426, Dial SMS+voice #3041, Mattermost #3202); Moltis (shared Slack channel tools fail #1224, WhatsApp Markdown render #1220).</li>
<li><strong>Memory &amp; context governance</strong>: OpenClaw session-catalog refresh-storm governance (#123535, 154💬), diagnostics recovery of overlapping tool calls (#124025, 46💬); IronClaw pluggable memory over MCP (#7664); CoPaw ReMeLightMemoryCard reranker panel (#6399), embedding health-check hardcoded timeout (#7156); Zeroclaw context-compaction anchored to model-window ratio (#9535).</li>
<li><strong>Automation &amp; enterprise</strong>: IronClaw derive run outcomes from runtime evidence (#7650, 45💬), benchmark QA preview (#7749, 39💬), omp core-tool contract (#7491, 37💬), pluggable memory (#7664); CoPaw per-session model override (#5992, 9💬); Moltis cron honors heartbeat active_hours (#1208).</li>
<li><strong>Security &amp; stability</strong>: OpenClaw install-policy warning acknowledgement (#116489, 49💬), typecheck hang fix (#123975, 45💬), SSH sandbox doesn&#39;t stage inbound media (#112160); Moltis WhatsApp/sandbox-image validation (#1222, #1220); CoPaw MCP backend restart can&#39;t auto-recover (#6524).</li>
<li><strong>Developer experience / design system</strong>: IronClaw WebUI design system (#7257, #7750 Storybook); OpenClaw UI decision-receipt explanation (#126007), new-chat worktree from clean defaults (#126056).</li>
</ul>
<h2>4. Differentiated Positioning</h2>
<ul>
<li><strong>OpenClaw</strong>: ecosystem hub — session/catalog governance, diagnostics recovery, install policy &amp; UI decision transparency; enterprise-managed context.</li>
<li><strong>NanoBot</strong>: widest channels (Telegram/Matrix/Slack/WebUI); Dream recovery cursor &amp; unified trajectory provider-usage backend (#5479).</li>
<li><strong>Zeroclaw</strong>: Rust core, RFC/ADR-driven &quot;lighter core + external integrations&quot;; wire protocol first-class (#8396), canonical sandbox-policy schema (#7821, 20💬).</li>
<li><strong>NanoClaw</strong>: multi-provider (Dial/WhatsApp/Mattermost/Matrix); template-based agent creation (#3396) &amp; refresh-safe ESM patch (#3403).</li>
<li><strong>IronClaw</strong>: per-user sandbox + structured automations + design system + Telegram linkage; enterprise/team-oriented; CI-speedup track (T1–T4).</li>
<li><strong>LobsterAI</strong>: cowork file cards/split preview, settings search, i18n hardcoded-fix; UX-oriented.</li>
<li><strong>CoPaw (QwenPaw)</strong>: memory ReMe, self-hosted multi-user, Volcengine Agent Plan &amp; MiMo V2.5 provider (#6515); among the most active communities.</li>
<li><strong>Moltis</strong>: WhatsApp-centric, channel security (Vault/sandbox-image validation) &amp; cron scheduling.</li>
<li><strong>EasyClaw (rivonclaw)</strong>: high-frequency small releases (daily v1.8.109/108), vertical features like business-dev filtering.</li>
<li><strong>PicoClaw / NullClaw / TinyClaw / ZeptoClaw</strong>: low-activity or silent.</li>
</ul>
<h2>5. Trend Signals</h2>
<ul>
<li><strong>Silent projects need attention</strong>: NullClaw / TinyClaw / ZeptoClaw have had 0 activity for multiple days; EasyClaw ships only — ecosystem health is diverging.</li>
<li><strong>Automation becomes first-class</strong>: IronClaw/CoPaw automations/run-now/Hub mark agents moving from &quot;conversation&quot; to &quot;orchestrated tasks.&quot;</li>
<li><strong>Security &amp; stability from optional to mandatory</strong>: install-policy warning acknowledgement (CWE-class risk), typecheck hang, MCP restart recovery are now frequent fixes.</li>
<li><strong>Memory is the cross-project主线</strong>: from OpenClaw session governance to IronClaw/CoPaw memory systems, persistent memory remains the 2026 agent-framework battleground.</li>
</ul>
<hr>
<h2>OpenClaw Detailed Activity</h2>
<blockquote>
<p>Source: <a href="https://github.com/openclaw/openclaw">openclaw/openclaw</a> | last 24h (issue 41 / PR 59)</p>
</blockquote>
<h3>Hot Issues</h3>
<ol>
<li><strong>#125626 Release validation: v2026.8.1-beta.2</strong> (18💬, open) — new-version release validation tracker.</li>
<li><strong>#124751 iOS app duplicates assistant replies at bottom and doesn&#39;t auto-scroll to latest</strong> (6💬, open) — mobile rendering.</li>
<li><strong>#113014 Webchat: raw MEDIA: directive leaks into visible reply text</strong> (5💬, open) — instruction injection surfaced.</li>
<li><strong>#90243 feat(llm/google-vertex): physical model mapping/aliasing for Google&#39;s Prior</strong> (3💬, open) — model routing.</li>
<li><strong>#124689 Model picker only applies to new sessions; Ollama Cloud requests sign-in</strong> (4💬, open).</li>
<li><strong>#112160 SSH sandbox doesn&#39;t stage inbound media into an existing remote workspace</strong> (4💬, open).</li>
<li><strong>#10944 parseMode config for Telegram channels</strong> (4💬, open).</li>
<li><strong>#126231 handler-timeout ingress events die with attempts=0 — silently lost messages</strong> (3💬, closed).</li>
<li><strong>#126813 Queued peer message re-invokes an agent with answer-expected hint and no acknowledgement</strong> (3💬, open).</li>
<li><strong>#100911 Tasks page / tasks.list edge-case hardening</strong> (2💬, open).</li>
</ol>
<h3>Notable PRs (by discussion heat)</h3>
<ol>
<li><strong>#123535 fix(ui): avoid session catalog refresh storms</strong> (154💬, open)</li>
<li><strong>#123979 fix(scripts): build heap ignores its systemd memory budget and takes the full default</strong> (56💬, open)</li>
<li><strong>#116489 feat(security): require acknowledgement for install policy warnings</strong> (49💬, closed)</li>
<li><strong>#123975 fix(scripts): typecheck hangs forever when tsgo wedges instead of failing</strong> (45💬, open)</li>
<li><strong>#124025 fix(diagnostics): recover stale overlapping tool calls</strong> (46💬, open)</li>
<li><strong>#120900 feat(ui): review install policy warnings</strong> (44💬, closed)</li>
<li><strong>#125815 fix(sessions): keep owner assignment stable and replies working</strong> (38💬, open)</li>
<li><strong>#126618 fix: Tool Search directory/tools wrap native read/exec in tool_call</strong> (26💬, open)</li>
<li><strong>#126007 feat(ui): explain decision receipts in Activity</strong> (25💬, open)</li>
<li><strong>#126056 fix(ui): start new chat worktrees from fresh defaults</strong> (21💬, open)</li>
</ol>
<hr>
<h2>Peer Project Highlights</h2>
<h3>NanoBot (HKUDS/nanobot) — I5 / P34</h3>
<ul>
<li>Issues: #5198 change models in a specific session requires reconfig (closed), #1168 Notion MCP connection fails (closed), #5441 a single recovered tool error permanently blocks (closed), #5463 DingTalk doesn&#39;t observe/drain inbound background tasks (open), #5454 streaming providers skip retry once content streamed mid server_error (closed).</li>
<li>PRs: #5442 fix(dream) advance cursor when tool errors recovered, #5379 fix(memory) preserve full consolidation input (open), #5476 render LaTeX as Unicode (closed), #2063 Tauri desktop app (closed), #5455 retry Codex server_error (closed), #5479 feat(trajectory) unified provider usage backend (open).</li>
</ul>
<h3>Zeroclaw (zeroclaw-labs/zeroclaw) — I5 / P95</h3>
<ul>
<li>Issues: #8396 RFC make wire protocol first-class in provider construction, #8691 ADR inventory and accepted RFC decision records, #10167 vendor-neutral lifecycle export for terminal agent multiplexers, #8288 SOP milestone daemon-owned SOP control plane to 5/5, #10212 document <code>switch</code> and its routing precedence.</li>
<li>PRs: #8561 feat(channels/telegram) multi_message streaming mode (33💬), #7821 feat(security) canonical sandbox_policy schema with app-layer enforcement (20💬), #9447 fix(anthropic) classify incomplete terminal responses (19💬), #9196 feat(mcp) materialize resource blob with aggregate budget preflight (19💬), #9772 feat(telegram) per_user_session toggle for shared group-chat (18💬), #9535 feat(runtime) anchor context compaction to model window ratio (17💬).</li>
</ul>
<h3>NanoClaw (qwibitai/nanoclaw) — I1 / P14</h3>
<ul>
<li>Issue: #3426 send_card docs promise callback buttons that the bridge drops since #2265.</li>
<li>PRs: #3041 feat(channels) Dial channel adapter (SMS + AI voice, closed), #3202 Mattermost integration (closed), #3050 Dial channel picker (closed), #3396 feat create agents from templates in chat (open), #3424 ci test registry-backed skills (closed), #3403 fix(matrix) refresh-safe ESM patch (closed).</li>
</ul>
<h3>NullClaw (nullclaw/nullclaw) — I0 / P1</h3>
<ul>
<li>PR: #990 feat(providers) add Eden AI as an OpenAI-compatible gateway (open).</li>
</ul>
<h3>IronClaw (nearai/ironclaw) — I12 / P31</h3>
<ul>
<li>Issues: #7801 CI expedite T4 canonical preflight, #7799 T2 nextest pipeline, #7800 T3 PR/queue convergence, #7798 T1 setup-rust composite, #7664 pluggable memory over MCP, #7783 LLM timeout policy can&#39;t measure TTFT.</li>
<li>PRs: #7650 feat(automations) derive run outcomes from runtime evidence (45💬), #7749 benchmark QA-preview trigger (39💬), #7491 feat(coding) omp core-tool contract + engines + benchmark arm (37💬), #7456 fix(reborn) make durable storage profile-agnostic (12💬), #7257 docs(design-system) WebUI design system (11💬), #7750 chore(webui) integrate Storybook + design-system catalog (10💬).</li>
</ul>
<h3>LobsterAI (netease-youdao/LobsterAI) — I2 / P13</h3>
<ul>
<li>Issues: #1217 occasional gateway startup during run (closed), #1223 CoworkPromptInput hardcoded Chinese labels leak into English prompts (closed).</li>
<li>PRs: #1218 refactor scheduled-task sort (closed), #1215 always rebuild chat handler (closed), #1219 eliminate invalid re-renders (closed), #1220 eliminate N+1 queries (closed), #1224 fix i18n hardcoded &amp; Escape key (closed), #1550 fix(scheduledTask) drop channel/to when delivery mode is &quot;no-notify&quot; (open).</li>
</ul>
<h3>TinyClaw (TinyAGI/tinyclaw) — I0 / P0</h3>
<ul>
<li>No activity in last 24h (latest v0.0.20, 03-26).</li>
</ul>
<h3>CoPaw (agentscope-ai/CoPaw) — I34 / P36</h3>
<ul>
<li>Issues: #6524 MCP backend restart can&#39;t auto-recover (open), #6780 2.0.1 self-freezes when idle (closed), #7016 tool call 404 (open), #7156 embedding health-check times out when already warm, timeout hardcoded (open), #7206 v2.1.1-beta.1 /compact fails with pydantic ValidationError (open), #7204 how to add custom tool in qwenpaw (open).</li>
<li>PRs: #5992 per-session model overrides (9💬), #6515 feat(providers) Volcengine Agent Plan &amp; MiMo V2.5 (9💬), #6845 preserve assistant completion time (closed), #6581 ReMeLightMemoryCard reranker UI panel (open), #6399 reranker UI config (open), #6586 fix(mcp) recover stale server sessions (closed).</li>
</ul>
<h3>Moltis (moltis-org/moltis) — I2 / P6</h3>
<ul>
<li>Issues: #1224 tools stop working in shared Slack channels (open), #1223 heartbeat active_hours has no effect on default config (open).</li>
<li>PRs: #1220 render Markdown in outbound WhatsApp (8💬, closed), #1208 fix(cron) honor heartbeat active hours (4💬, open), #468 use cmd.exe on Windows for shell hooks (open), #1226 deliver scheduled output to originating chat (open), #1225 improve zh-TW Traditional Chinese (open), #1222 validate sandbox image requests (open).</li>
</ul>
<h3>ZeptoClaw (qhkm/zeptoclaw) — I0 / P0</h3>
<ul>
<li>No activity in last 24h (latest v0.9.2, 04-07).</li>
</ul>
<h3>EasyClaw (gaoyangz77/easyclaw) — I0 / P0 / releases v1.8.109, v1.8.108 (08-21)</h3>
<ul>
<li>Only releases today, no issue/PR interaction.</li>
</ul>
<hr>
<p><em>This digest is generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. All content is fetched live from GitHub&#39;s public API and written by the executing agent — no external LLM was called.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI 开源趋势日报 2026-08-22</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-trending</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-trending</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
      <description>开源 AI 趋势日报 2026-08-22 生成时间: 2026-08-22 02:30 (GMT+8) 数据来源：GitHub Trending（每日榜）+ gh search repos 6 个 AI 主题（按 stars 排序） 本日报由 agents-radar 本地自动化生成，所有撰写由执行代理人工完成，未调用任何外部大模型 API。 一、GitHub Trending 每日飙升榜（2026-08-22） 说明：本次抓取时 GitHub Trending 页面未对外暴露「当日新增 Star」数值（疑似未登录视图/版式变更），故下表仅列出入榜项目与简介，不含 star 增量。 项目 简介 modular/modular Modular 平台（含 MAX 与 Mojo），面向高性能 AI 推理与系统编程 mattpocock/skills 真实工程师的 Skills 合集，直接取自作者 .agents 目录 AprilNEA/OpenLogi 原生、本地优先的 Logitech Options+ 替代，Rust 编写 obra/superpowers Agentic Skills...</description>
      <content:encoded><![CDATA[<h1>开源 AI 趋势日报 2026-08-22</h1>
<blockquote>
<p>生成时间: 2026-08-22 02:30 (GMT+8)
数据来源：GitHub Trending（每日榜）+ <code>gh search repos</code> 6 个 AI 主题（按 stars 排序）
本日报由 agents-radar 本地自动化生成，所有撰写由执行代理人工完成，未调用任何外部大模型 API。</p>
</blockquote>
<hr>
<h2>一、GitHub Trending 每日飙升榜（2026-08-22）</h2>
<blockquote>
<p>说明：本次抓取时 GitHub Trending 页面未对外暴露「当日新增 Star」数值（疑似未登录视图/版式变更），故下表仅列出入榜项目与简介，不含 star 增量。</p>
</blockquote>
<table>
<thead>
<tr>
<th>项目</th>
<th>简介</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/modular/modular">modular/modular</a></td>
<td>Modular 平台（含 MAX 与 Mojo），面向高性能 AI 推理与系统编程</td>
</tr>
<tr>
<td><a href="https://github.com/mattpocock/skills">mattpocock/skills</a></td>
<td>真实工程师的 Skills 合集，直接取自作者 <code>.agents</code> 目录</td>
</tr>
<tr>
<td><a href="https://github.com/AprilNEA/OpenLogi">AprilNEA/OpenLogi</a></td>
<td>原生、本地优先的 Logitech Options+ 替代，Rust 编写</td>
</tr>
<tr>
<td><a href="https://github.com/obra/superpowers">obra/superpowers</a></td>
<td>Agentic Skills 框架与软件开发方法论</td>
</tr>
<tr>
<td><a href="https://github.com/cursor/plugins">cursor/plugins</a></td>
<td>Cursor 插件规范与官方插件</td>
</tr>
<tr>
<td><a href="https://github.com/santifer/career-ops">santifer/career-ops</a></td>
<td>开源 AI 求职：扫描招聘站点，用结构化评估筛选岗位（可跑在 Claude Code/Codex/OpenCode 等 CLI）</td>
</tr>
<tr>
<td><a href="https://github.com/harry0703/MoneyPrinterTurbo">harry0703/MoneyPrinterTurbo</a></td>
<td>用 AI 大模型与自动化工作流一键生成高清短视频</td>
</tr>
<tr>
<td><a href="https://github.com/agent-substrate/substrate">agent-substrate/substrate</a></td>
<td>Agent Substrate：核心系统</td>
</tr>
<tr>
<td><a href="https://github.com/chaitanyagiri/munder-difflin">chaitanyagiri/munder-difflin</a></td>
<td>本地多 agent 编排框架（harness）</td>
</tr>
<tr>
<td><a href="https://github.com/PostHog/posthog">PostHog/posthog</a></td>
<td>构建自驱动产品的领先平台（AI 可观测、分析、会话回放、特性开关等）</td>
</tr>
<tr>
<td><a href="https://github.com/mahlernim/google-timeline-visualizer">mahlernim/google-timeline-visualizer</a></td>
<td>用 Google 位置历史可视化全年旅行轨迹</td>
</tr>
<tr>
<td><a href="https://github.com/volcengine/OpenViking">volcengine/OpenViking</a></td>
<td>面向 AI Agent 的自进化上下文数据库，统一 Agent 记忆、知识与 RAG、Skills</td>
</tr>
<tr>
<td><a href="https://github.com/JuliusBrussee/caveman">JuliusBrussee/caveman</a></td>
<td>Claude Code skill：用「穴居人」式表达削减 65% token</td>
</tr>
<tr>
<td><a href="https://github.com/makeplane/plane">makeplane/plane</a></td>
<td>开源 Jira / Linear / Monday / ClickUp 替代</td>
</tr>
<tr>
<td><a href="https://github.com/Tencent/AI-Infra-Guard">Tencent/AI-Infra-Guard</a></td>
<td>全栈 AI 红队平台，通过 Agent Scan / Skills Scan / MCP scan / AI Infra scan 守护 AI 生态</td>
</tr>
<tr>
<td><a href="https://github.com/RyanCodrai/turbovec">RyanCodrai/turbovec</a></td>
<td>基于 TurboQuant 的 Rust 向量索引，带 Python 绑定</td>
</tr>
</tbody></table>
<p><strong>观察</strong>：今日 Trending 高度向「Agent 工具链 + 个人效率 + 安全」收口——Skills 框架（mattpocock/skills、obra/superpowers、JuliusBrussee/caveman）、Agent 基础设施（agent-substrate/substrate、chaitanyagiri/munder-difflin、volcengine/OpenViking、Tencent）、以及 AI 红队（Tencent/AI-Infra-Guard）同屏出现，反映社区对「可复用 agent 能力 + 安全治理」的双重关注。</p>
<h2>二、六大 AI 主题搜索热度（按 stars）</h2>
<h3>1. AI Agent 框架</h3>
<ul>
<li><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a> ⭐233,911 — The agent that grows with you</li>
<li><a href="https://github.com/shareAI-lab/learn-claude-code">shareAI-lab/learn-claude-code</a> ⭐74,900 — 从 0 到 1 构建类 claude code 的 agent harness</li>
<li><a href="https://github.com/Panniantong/Agent-Reach">Panniantong/Agent-Reach</a> ⭐73,818 — 给 AI agent 全网的眼睛（Twitter/Reddit/YouTube/GitHub/Bilibili/小红书）</li>
<li><a href="https://github.com/thedaviddias/Front-End-Checklist">thedaviddias/Front-End-Checklist</a> ⭐73,602 — 现代 Web 开发必备清单（人类与 AI agent 通用）</li>
<li><a href="https://github.com/santifer/career-ops">santifer/career-ops</a> ⭐67,306 — 开源 AI 求职，可跑在各 AI 编码 CLI</li>
<li><a href="https://github.com/ZhuLinsen/daily_stock_analysis">ZhuLinsen/daily_stock_analysis</a> ⭐63,578 — LLM 驱动的多市场股票智能分析</li>
<li><a href="https://github.com/CherryHQ/cherry-studio">CherryHQ/cherry-studio</a> ⭐50,885 — AI 生产力工作室，统一前沿 LLM</li>
<li><a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a> ⭐47,258 — 超轻量、自托管的个人 AI agent 平台</li>
<li><a href="https://github.com/zhayujie/CowAgent">zhayujie/CowAgent</a> ⭐46,623 — 开源超级 AI 助手与 Agent Harness</li>
<li><a href="https://github.com/siyuan-note/siyuan">siyuan-note/siyuan</a> ⭐45,917 — 开源、隐私优先、自托管的知识工作空间</li>
</ul>
<h3>2. 大模型（LLM）</h3>
<ul>
<li><a href="https://github.com/affaan-m/ECC">affaan-m/ECC</a> ⭐241,701 — agent harness 性能优化系统（Skills/instincts/memory/security）</li>
<li><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a> ⭐233,911 — The agent that grows with you</li>
<li><a href="https://github.com/Significant-Gravitas/AutoGPT">Significant-Gravitas/AutoGPT</a> ⭐186,719 — 人人可用的自主 AI</li>
<li><a href="https://github.com/ollama/ollama">ollama/ollama</a> ⭐179,115 — 一键跑起 Kimi-K2.6/GLM-5.2/MiniMax/DeepSeek/gpt-oss/Qwen/Gemma</li>
<li><a href="https://github.com/firecrawl/firecrawl">firecrawl/firecrawl</a> ⭐170,460 — 大规模搜索/抓取/交互 Web 的上下文 API</li>
<li><a href="https://github.com/f/prompts.chat">f/prompts.chat</a> ⭐167,704 — Awesome ChatGPT Prompts 社区共享</li>
<li><a href="https://github.com/huggingface/transformers">huggingface/transformers</a> ⭐164,310 — 文本/视觉/音频/多模态 SOTA 模型框架</li>
<li><a href="https://github.com/langgenius/dify">langgenius/dify</a> ⭐153,134 — Agentic 工作流与 RAG 管线协作平台</li>
<li><a href="https://github.com/open-webui/open-webui">open-webui/open-webui</a> ⭐149,491 — 用户友好的 AI 界面</li>
<li><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a> ⭐144,726 — agent 工程平台</li>
</ul>
<h3>3. RAG 检索增强生成</h3>
<ul>
<li><a href="https://github.com/langgenius/dify">langgenius/dify</a> ⭐153,134 — Agentic 工作流与 RAG 管线</li>
<li><a href="https://github.com/open-webui/open-webui">open-webui/open-webui</a> ⭐149,491 — 用户友好的 AI 界面</li>
<li><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a> ⭐144,726 — agent 工程平台</li>
<li><a href="https://github.com/Shubhamsaboo/awesome-llm-apps">Shubhamsaboo/awesome-llm-apps</a> ⭐133,487 — 100+ AI Agents/Skills/RAG 应用</li>
<li><a href="https://github.com/Graphify-Labs/graphify">Graphify-Labs/graphify</a> ⭐109,096 — 把代码库变成可查询知识图谱（局部 AST 解析，无向量库）</li>
<li><a href="https://github.com/thedotmack/claude-mem">thedotmack/claude-mem</a> ⭐91,430 — 跨会话持久上下文（Claude Code/OpenClaw/Codex/Gemini 等）</li>
<li><a href="https://github.com/infiniflow/ragflow">infiniflow/ragflow</a> ⭐88,983 — 领先的开源 RAG 引擎</li>
<li><a href="https://github.com/PaddlePaddle/PaddleOCR">PaddlePaddle/PaddleOCR</a> ⭐88,065 — 轻量 OCR 工具包，桥接图像/PDF 与 LLM</li>
<li><a href="https://github.com/dair-ai/Prompt-Engineering-Guide">dair-ai/Prompt-Engineering-Guide</a> ⭐77,664 — 提示工程/上下文工程/RAG 指南</li>
<li><a href="https://github.com/datawhalechina/hello-agents">datawhalechina/hello-agents</a> ⭐74,116 — 从零构建智能体教程</li>
</ul>
<h3>4. 向量数据库</h3>
<ul>
<li><a href="https://github.com/Mintplex-Labs/anything-llm">Mintplex-Labs/anything-llm</a> ⭐65,017 — 本地优先的强力 agent 体验</li>
<li><a href="https://github.com/meilisearch/meilisearch">meilisearch/meilisearch</a> ⭐59,045 — 极速搜索 API，AI 混合搜索</li>
<li><a href="https://github.com/pathwaycom/llm-app">pathwaycom/llm-app</a> ⭐59,013 — RAG/AI 管线云模板</li>
<li><a href="https://github.com/run-llama/llama_index">run-llama/llama_index</a> ⭐51,790 — 文档 agent 与 OCR 平台</li>
<li><a href="https://github.com/milvus-io/milvus">milvus-io/milvus</a> ⭐45,728 — 高性能云原生向量数据库</li>
<li><a href="https://github.com/VectifyAI/PageIndex">VectifyAI/PageIndex</a> ⭐35,280 — 无向量的推理式 RAG 文档索引</li>
<li><a href="https://github.com/qdrant/qdrant">qdrant/qdrant</a> ⭐34,115 — 大规模向量数据库与向量搜索</li>
<li><a href="https://github.com/topoteretes/cognee">topoteretes/cognee</a> ⭐30,170 — 开源 AI 记忆平台（知识图谱引擎）</li>
<li><a href="https://github.com/NirDiamant/RAG_Techniques">NirDiamant/RAG_Techniques</a> ⭐29,168 — RAG 高级技术笔记本</li>
<li><a href="https://github.com/weaviate/weaviate">weaviate/weaviate</a> ⭐16,745 — 云原生向量数据库</li>
</ul>
<h3>5. LLM 模型</h3>
<ul>
<li><a href="https://github.com/jingyaogong/minimind">jingyaogong/minimind</a> ⭐54,909 — 2 小时从零训练 64M 参数 LLM</li>
<li><a href="https://github.com/ScrapeGraphAI/Scrapegraph-ai">ScrapeGraphAI/Scrapegraph-ai</a> ⭐29,794 — 基于 AI 的爬虫</li>
<li><a href="https://github.com/The-Pocket/PocketFlow-Tutorial-Codebase-Knowledge">The-Pocket/PocketFlow-Tutorial-Codebase-Knowledge</a> ⭐12,626 — Codebase to Tutorial</li>
<li><a href="https://github.com/The-Pocket/PocketFlow">The-Pocket/PocketFlow</a> ⭐11,120 — 100 行 LLM 框架，让 agent 构建 agent</li>
<li><a href="https://github.com/OpenSPG/KAG">OpenSPG/KAG</a> ⭐9,004 — 逻辑形式引导的推理与检索框架</li>
<li><a href="https://github.com/0xPlaygrounds/rig">0xPlaygrounds/rig</a> ⭐8,347 — Rust 构建模块化可扩展 LLM 应用</li>
<li><a href="https://github.com/open-compass/opencompass">open-compass/opencompass</a> ⭐7,325 — LLM 评测平台</li>
<li><a href="https://github.com/InternLM/InternLM">InternLM/InternLM</a> ⭐7,267 — InternLM 系列官方发布</li>
<li><a href="https://github.com/Eigenwise/atomic-agents">Eigenwise/atomic-agents</a> ⭐6,190 — 原子化构建 AI agent</li>
<li><a href="https://github.com/gluonfield/enchanted">gluonfield/enchanted</a> ⭐5,998 — iOS/macOS 私本地模型聊天</li>
</ul>
<h3>6. 机器学习</h3>
<ul>
<li><a href="https://github.com/tensorflow/tensorflow">tensorflow/tensorflow</a> ⭐197,220 — 人人可用的开源机器学习框架</li>
<li><a href="https://github.com/f/prompts.chat">f/prompts.chat</a> ⭐167,704 — Awesome ChatGPT Prompts</li>
<li><a href="https://github.com/huggingface/transformers">huggingface/transformers</a> ⭐164,310 — SOTA 机器学习模型框架</li>
<li><a href="https://github.com/rasbt/LLMs-from-scratch">rasbt/LLMs-from-scratch</a> ⭐103,171 — 从零逐步实现类 ChatGPT LLM</li>
<li><a href="https://github.com/pytorch/pytorch">pytorch/pytorch</a> ⭐102,517 — 带 GPU 加速的张量与动态神经网络</li>
<li><a href="https://github.com/microsoft/ML-For-Beginners">microsoft/ML-For-Beginners</a> ⭐89,653 — 12 周 26 课经典机器学习</li>
<li><a href="https://github.com/Developer-Y/cs-video-courses">Developer-Y/cs-video-courses</a> ⭐83,139 — 带视频讲座的 CS 课程清单</li>
<li><a href="https://github.com/mlabonne/llm-course">mlabonne/llm-course</a> ⭐81,893 — LLM 学习路线与 Colab 笔记本</li>
<li><a href="https://github.com/netdata/netdata">netdata/netdata</a> ⭐80,255 — 最快的 AI 驱动全栈可观测</li>
<li><a href="https://github.com/d2l-ai/d2l-zh">d2l-ai/d2l-zh</a> ⭐79,853 — 《动手学深度学习》中英文版</li>
</ul>
<h2>三、趋势小结</h2>
<ul>
<li><strong>Agent 工具链与个人效率同屏爆发</strong>：Skills 框架、agent harness、自托管 agent 平台、AI 求职/股票分析等「把 agent 用起来」的项目占据多榜头部。</li>
<li><strong>记忆与上下文成为基础设施赛道</strong>：volcengine/OpenViking、thedotmack/claude-mem、topoteretes/cognee、Graphify-Labs/graphify 等从不同角度切入「agent 记忆/知识」，与今日 CLI/OpenClaw 日报中「记忆持久化」主线呼应。</li>
<li><strong>安全治理升温</strong>：再叠加 Tencent/AI-Infra-Guard 红队平台，社区对 agent 安全的关注从可选走向必需。</li>
<li><strong>轻量/本地优先受捧</strong>：Rust 编写的 OpenLogi、本地优先的 anything-llm/siyuan，反映对「自托管、隐私、低依赖」的偏好。</li>
</ul>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，所有内容基于 GitHub 公开数据实时抓取并由执行代理人工撰写，未调用任何外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Open Source Trends 2026-08-22</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-trending-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-trending-en</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
      <description>Open-Source AI Trends Daily — 2026-08-22 Generated: 2026-08-22 02:30 (GMT+8) Sources: GitHub Trending (daily board) + gh search repos across 6 AI topics (sorted by stars) This digest is produced by the agents-radar local automation. All writing is done by the executing agent — no external LLM API was called. 1. GitHub Trending Daily Board (2026-08-22) Note: During this fetch the GitHub Trending page did not expose per-day &amp;quot;stars gained&amp;quot; figures (likely an unauthenticated view / layout ...</description>
      <content:encoded><![CDATA[<h1>Open-Source AI Trends Daily — 2026-08-22</h1>
<blockquote>
<p>Generated: 2026-08-22 02:30 (GMT+8)
Sources: GitHub Trending (daily board) + <code>gh search repos</code> across 6 AI topics (sorted by stars)
This digest is produced by the agents-radar local automation. All writing is done by the executing agent — no external LLM API was called.</p>
</blockquote>
<hr>
<h2>1. GitHub Trending Daily Board (2026-08-22)</h2>
<blockquote>
<p>Note: During this fetch the GitHub Trending page did not expose per-day &quot;stars gained&quot; figures (likely an unauthenticated view / layout change), so the table lists trending repos with descriptions but without star deltas.</p>
</blockquote>
<table>
<thead>
<tr>
<th>Project</th>
<th>Description</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/modular/modular">modular/modular</a></td>
<td>The Modular Platform (MAX &amp; Mojo) — high-performance AI inference &amp; systems programming</td>
</tr>
<tr>
<td><a href="https://github.com/mattpocock/skills">mattpocock/skills</a></td>
<td>Skills for Real Engineers, straight from the author&#39;s <code>.agents</code> directory</td>
</tr>
<tr>
<td><a href="https://github.com/AprilNEA/OpenLogi">AprilNEA/OpenLogi</a></td>
<td>Native, local-first Logitech Options+ alternative, written in Rust</td>
</tr>
<tr>
<td><a href="https://github.com/obra/superpowers">obra/superpowers</a></td>
<td>An agentic skills framework &amp; software development methodology</td>
</tr>
<tr>
<td><a href="https://github.com/cursor/plugins">cursor/plugins</a></td>
<td>Cursor plugin specification and official plugins</td>
</tr>
<tr>
<td><a href="https://github.com/santifer/career-ops">santifer/career-ops</a></td>
<td>Open-source AI job search: scan portals, score listings, runs in Claude Code/Codex/OpenCode CLIs</td>
</tr>
<tr>
<td><a href="https://github.com/harry0703/MoneyPrinterTurbo">harry0703/MoneyPrinterTurbo</a></td>
<td>Generate HD short videos from a topic/keyword with an automated AI workflow</td>
</tr>
<tr>
<td><a href="https://github.com/agent-substrate/substrate">agent-substrate/substrate</a></td>
<td>Agent Substrate: the core system</td>
</tr>
<tr>
<td><a href="https://github.com/chaitanyagiri/munder-difflin">chaitanyagiri/munder-difflin</a></td>
<td>Local multi-agent harness</td>
</tr>
<tr>
<td><a href="https://github.com/PostHog/posthog">PostHog/posthog</a></td>
<td>Platform for self-driving products (AI observability, analytics, session replay, flags)</td>
</tr>
<tr>
<td><a href="https://github.com/mahlernim/google-timeline-visualizer">mahlernim/google-timeline-visualizer</a></td>
<td>Visualize your year in travel using Google Location History</td>
</tr>
<tr>
<td><a href="https://github.com/volcengine/OpenViking">volcengine/OpenViking</a></td>
<td>Self-evolving Context Database for AI Agents — memory, knowledge RAG &amp; skills</td>
</tr>
<tr>
<td><a href="https://github.com/JuliusBrussee/caveman">JuliusBrussee/caveman</a></td>
<td>Claude Code skill that cuts 65% of tokens by talking like a caveman</td>
</tr>
<tr>
<td><a href="https://github.com/makeplane/plane">makeplane/plane</a></td>
<td>Open-source Jira / Linear / Monday / ClickUp alternative</td>
</tr>
<tr>
<td><a href="https://github.com/Tencent/AI-Infra-Guard">Tencent/AI-Infra-Guard</a></td>
<td>Full-stack AI Red Teaming platform (Agent/Skills/MCP/AI-Infra scan, LLM jailbreak eval)</td>
</tr>
<tr>
<td><a href="https://github.com/RyanCodrai/turbovec">RyanCodrai/turbovec</a></td>
<td>A vector index built on TurboQuant, in Rust with Python bindings</td>
</tr>
</tbody></table>
<p><strong>Observation</strong>: Today&#39;s Trending converges on &quot;agent toolchain + personal productivity + security&quot; — Skills frameworks (mattpocock/skills, obra/superpowers, JuliusBrussee/caveman), agent infrastructure (agent-substrate/substrate, chaitanyagiri/munder-difflin, volcengine/OpenViking, Tencent), and AI red-teaming (Tencent/AI-Infra-Guard) appear together, reflecting dual community focus on reusable agent capability and security governance.</p>
<h2>2. Six AI Topic Search Heat (by stars)</h2>
<h3>1. AI Agent Frameworks</h3>
<ul>
<li><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a> ⭐233,911 — The agent that grows with you</li>
<li><a href="https://github.com/shareAI-lab/learn-claude-code">shareAI-lab/learn-claude-code</a> ⭐74,900 — Build a claude-code-like agent harness from 0 to 1</li>
<li><a href="https://github.com/Panniantong/Agent-Reach">Panniantong/Agent-Reach</a> ⭐73,818 — Give your AI agent eyes to see the entire internet</li>
<li><a href="https://github.com/thedaviddias/Front-End-Checklist">thedaviddias/Front-End-Checklist</a> ⭐73,602 — Essential checklist for modern web dev (humans &amp; AI agents)</li>
<li><a href="https://github.com/santifer/career-ops">santifer/career-ops</a> ⭐67,306 — Open-source AI job search, runs in AI coding CLIs</li>
<li><a href="https://github.com/ZhuLinsen/daily_stock_analysis">ZhuLinsen/daily_stock_analysis</a> ⭐63,578 — LLM-powered multi-market stock analysis</li>
<li><a href="https://github.com/CherryHQ/cherry-studio">CherryHQ/cherry-studio</a> ⭐50,885 — AI productivity studio with 300+ assistants</li>
<li><a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a> ⭐47,258 — Ultra-lightweight, self-hosted personal AI agent platform</li>
<li><a href="https://github.com/zhayujie/CowAgent">zhayujie/CowAgent</a> ⭐46,623 — Open-source super AI assistant &amp; Agent Harness</li>
<li><a href="https://github.com/siyuan-note/siyuan">siyuan-note/siyuan</a> ⭐45,917 — Open-source, privacy-first, self-hosted knowledge workspace</li>
</ul>
<h3>2. LLM (Large Language Models)</h3>
<ul>
<li><a href="https://github.com/affaan-m/ECC">affaan-m/ECC</a> ⭐241,701 — Agent harness performance optimization system</li>
<li><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a> ⭐233,911 — The agent that grows with you</li>
<li><a href="https://github.com/Significant-Gravitas/AutoGPT">Significant-Gravitas/AutoGPT</a> ⭐186,719 — Accessible AI for everyone</li>
<li><a href="https://github.com/ollama/ollama">ollama/ollama</a> ⭐179,115 — Run Kimi-K2.6/GLM-5.2/MiniMax/DeepSeek/gpt-oss/Qwen/Gemma locally</li>
<li><a href="https://github.com/firecrawl/firecrawl">firecrawl/firecrawl</a> ⭐170,460 — Context API to search, scrape, interact with the web at scale</li>
<li><a href="https://github.com/f/prompts.chat">f/prompts.chat</a> ⭐167,704 — Awesome ChatGPT Prompts community</li>
<li><a href="https://github.com/huggingface/transformers">huggingface/transformers</a> ⭐164,310 — SOTA ML model framework (text/vision/audio/multimodal)</li>
<li><a href="https://github.com/langgenius/dify">langgenius/dify</a> ⭐153,134 — Agentic workflows &amp; RAG pipelines platform</li>
<li><a href="https://github.com/open-webui/open-webui">open-webui/open-webui</a> ⭐149,491 — User-friendly AI interface</li>
<li><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a> ⭐144,726 — Agent engineering platform</li>
</ul>
<h3>3. RAG (Retrieval-Augmented Generation)</h3>
<ul>
<li><a href="https://github.com/langgenius/dify">langgenius/dify</a> ⭐153,134 — Agentic workflows &amp; RAG pipelines</li>
<li><a href="https://github.com/open-webui/open-webui">open-webui/open-webui</a> ⭐149,491 — User-friendly AI interface</li>
<li><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a> ⭐144,726 — Agent engineering platform</li>
<li><a href="https://github.com/Shubhamsaboo/awesome-llm-apps">Shubhamsaboo/awesome-llm-apps</a> ⭐133,487 — 100+ AI Agents, Skills and RAG Apps</li>
<li><a href="https://github.com/Graphify-Labs/graphify">Graphify-Labs/graphify</a> ⭐109,096 — Turn any codebase into a queryable knowledge graph (local AST, no vector store)</li>
<li><a href="https://github.com/thedotmack/claude-mem">thedotmack/claude-mem</a> ⭐91,430 — Persistent context across sessions (Claude Code/OpenClaw/Codex/Gemini…)</li>
<li><a href="https://github.com/infiniflow/ragflow">infiniflow/ragflow</a> ⭐88,983 — Leading open-source RAG engine</li>
<li><a href="https://github.com/PaddlePaddle/PaddleOCR">PaddlePaddle/PaddleOCR</a> ⭐88,065 — Lightweight OCR toolkit bridging images/PDFs and LLMs</li>
<li><a href="https://github.com/dair-ai/Prompt-Engineering-Guide">dair-ai/Prompt-Engineering-Guide</a> ⭐77,664 — Prompt/context engineering &amp; RAG guide</li>
<li><a href="https://github.com/datawhalechina/hello-agents">datawhalechina/hello-agents</a> ⭐74,116 — Build agents from scratch tutorial</li>
</ul>
<h3>4. Vector Databases</h3>
<ul>
<li><a href="https://github.com/Mintplex-Labs/anything-llm">Mintplex-Labs/anything-llm</a> ⭐65,017 — Powerful local-first agent experience</li>
<li><a href="https://github.com/meilisearch/meilisearch">meilisearch/meilisearch</a> ⭐59,045 — Lightning-fast search API with AI hybrid search</li>
<li><a href="https://github.com/pathwaycom/llm-app">pathwaycom/llm-app</a> ⭐59,013 — Cloud templates for RAG/AI pipelines</li>
<li><a href="https://github.com/run-llama/llama_index">run-llama/llama_index</a> ⭐51,790 — Document agent and OCR platform</li>
<li><a href="https://github.com/milvus-io/milvus">milvus-io/milvus</a> ⭐45,728 — High-performance cloud-native vector database</li>
<li><a href="https://github.com/VectifyAI/PageIndex">VectifyAI/PageIndex</a> ⭐35,280 — Vectorless, reasoning-based RAG document index</li>
<li><a href="https://github.com/qdrant/qdrant">qdrant/qdrant</a> ⭐34,115 — Massive-scale vector database &amp; search engine</li>
<li><a href="https://github.com/topoteretes/cognee">topoteretes/cognee</a> ⭐30,170 — Open-source AI memory platform (knowledge-graph engine)</li>
<li><a href="https://github.com/NirDiamant/RAG_Techniques">NirDiamant/RAG_Techniques</a> ⭐29,168 — Advanced RAG technique notebooks</li>
<li><a href="https://github.com/weaviate/weaviate">weaviate/weaviate</a> ⭐16,745 — Cloud-native vector database</li>
</ul>
<h3>5. LLM Models</h3>
<ul>
<li><a href="https://github.com/jingyaogong/minimind">jingyaogong/minimind</a> ⭐54,909 — Train a 64M-param LLM from scratch in 2h</li>
<li><a href="https://github.com/ScrapeGraphAI/Scrapegraph-ai">ScrapeGraphAI/Scrapegraph-ai</a> ⭐29,794 — AI-based scraper</li>
<li><a href="https://github.com/The-Pocket/PocketFlow-Tutorial-Codebase-Knowledge">The-Pocket/PocketFlow-Tutorial-Codebase-Knowledge</a> ⭐12,626 — Codebase to Tutorial</li>
<li><a href="https://github.com/The-Pocket/PocketFlow">The-Pocket/PocketFlow</a> ⭐11,120 — 100-line LLM framework; let Agents build Agents</li>
<li><a href="https://github.com/OpenSPG/KAG">OpenSPG/KAG</a> ⭐9,004 — Logic-form-guided reasoning &amp; retrieval framework</li>
<li><a href="https://github.com/0xPlaygrounds/rig">0xPlaygrounds/rig</a> ⭐8,347 — Build modular LLM apps in Rust</li>
<li><a href="https://github.com/open-compass/opencompass">open-compass/opencompass</a> ⭐7,325 — LLM evaluation platform</li>
<li><a href="https://github.com/InternLM/InternLM">InternLM/InternLM</a> ⭐7,267 — Official InternLM series releases</li>
<li><a href="https://github.com/Eigenwise/atomic-agents">Eigenwise/atomic-agents</a> ⭐6,190 — Build AI agents atomically</li>
<li><a href="https://github.com/gluonfield/enchanted">gluonfield/enchanted</a> ⭐5,998 — iOS/macOS app for private self-hosted LLMs</li>
</ul>
<h3>6. Machine Learning</h3>
<ul>
<li><a href="https://github.com/tensorflow/tensorflow">tensorflow/tensorflow</a> ⭐197,220 — Open-source ML framework for everyone</li>
<li><a href="https://github.com/f/prompts.chat">f/prompts.chat</a> ⭐167,704 — Awesome ChatGPT Prompts</li>
<li><a href="https://github.com/huggingface/transformers">huggingface/transformers</a> ⭐164,310 — SOTA ML model framework</li>
<li><a href="https://github.com/rasbt/LLMs-from-scratch">rasbt/LLMs-from-scratch</a> ⭐103,171 — Implement a ChatGPT-like LLM in PyTorch step by step</li>
<li><a href="https://github.com/pytorch/pytorch">pytorch/pytorch</a> ⭐102,517 — Tensors and dynamic neural networks with GPU acceleration</li>
<li><a href="https://github.com/microsoft/ML-For-Beginners">microsoft/ML-For-Beginners</a> ⭐89,653 — 12 weeks, 26 lessons, 52 quizzes</li>
<li><a href="https://github.com/Developer-Y/cs-video-courses">Developer-Y/cs-video-courses</a> ⭐83,139 — CS courses with video lectures</li>
<li><a href="https://github.com/mlabonne/llm-course">mlabonne/llm-course</a> ⭐81,893 — LLM course with roadmaps &amp; Colab notebooks</li>
<li><a href="https://github.com/netdata/netdata">netdata/netdata</a> ⭐80,255 — Fastest path to AI-powered full-stack observability</li>
<li><a href="https://github.com/d2l-ai/d2l-zh">d2l-ai/d2l-zh</a> ⭐79,853 — Dive into Deep Learning (Chinese/English)</li>
</ul>
<h2>3. Trend Takeaways</h2>
<ul>
<li><strong>Agent toolchain &amp; personal productivity surge together</strong>: Skills frameworks, agent harnesses, self-hosted agent platforms, and AI job-search/stock-analysis projects dominate multiple boards&#39; tops.</li>
<li><strong>Memory &amp; context become an infrastructure赛道</strong>: volcengine/OpenViking, thedotmack/claude-mem, topoteretes/cognee, Graphify-Labs/graphify each attack &quot;agent memory/knowledge&quot; from a different angle — echoing today&#39;s CLI/OpenClaw &quot;memory persistence&quot;主线.</li>
<li><strong>Security governance heats up</strong>: with Tencent/AI-Infra-Guard red-teaming platform, community attention to agent security shifts from optional to mandatory.</li>
<li><strong>Lightweight / local-first favored</strong>: Rust-written OpenLogi, local-first anything-llm/siyuan reflect preference for &quot;self-hosted, private, low-dependency.&quot;</li>
</ul>
<hr>
<p><em>This digest is generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. All content is fetched live from GitHub&#39;s public data and written by the executing agent — no external LLM was called.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>Hacker News AI 社区动态日报 2026-08-22</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-hn</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-hn</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
      <description>Hacker News AI 动态日报 2026-08-22 生成时间: 2026-08-22 02:30 (GMT+8) 数据来源：HN Algolia Search API（6 个查询：AI / LLM / Claude / OpenAI / Anthropic / machine learning，近 24h，去重后按 points 取 Top 30；本批共 104 条唯一故事） 本日报由 agents-radar 本地自动化生成，所有撰写由执行代理人工完成，未调用任何外部大模型 API。 一、AI 编码 Agent：成本、可靠性与自托管 Codex on AWS bedrock bug causing 10x charges（145👍 / 60💬）— 一条 AWS Bedrock 上的 Codex bug 导致费用暴涨 10 倍，引发对 agent 计费透明度的激烈讨论。最高赞，显示「成本可控」已成为社区头号焦虑。 Building an (almost) fully self-hosted, sandboxed, agentic software factory（25👍...</description>
      <content:encoded><![CDATA[<h1>Hacker News AI 动态日报 2026-08-22</h1>
<blockquote>
<p>生成时间: 2026-08-22 02:30 (GMT+8)
数据来源：HN Algolia Search API（6 个查询：AI / LLM / Claude / OpenAI / Anthropic / machine learning，近 24h，去重后按 points 取 Top 30；本批共 104 条唯一故事）
本日报由 agents-radar 本地自动化生成，所有撰写由执行代理人工完成，未调用任何外部大模型 API。</p>
</blockquote>
<hr>
<h2>一、AI 编码 Agent：成本、可靠性与自托管</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49383326">Codex on AWS bedrock bug causing 10x charges</a></strong>（145👍 / 60💬）— 一条 AWS Bedrock 上的 Codex bug 导致费用暴涨 10 倍，引发对 agent 计费透明度的激烈讨论。最高赞，显示「成本可控」已成为社区头号焦虑。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49390463">Building an (almost) fully self-hosted, sandboxed, agentic software factory</a></strong>（25👍 / 17💬）— 几乎全自托管、带沙箱的 agentic 软件工厂实践，呼应今日 CLI/OpenClaw 日报里的「沙箱/自托管」主线。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49390739">Show HN: Proliferate – open-source, self-hostable Codex for any coding agent</a></strong>（16👍 / 7💬）— 让任意编码 agent 用上自托管 Codex 的开源项目。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49390066">LLMs are proof that Unix won</a></strong>（10👍 / 3💬）— 从 Unix 哲学视角解读 LLM 的胜利。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49391392">Linus Torvalds Endures a Debug Session from Hell, &quot;Enormously Helped&quot; by AI</a></strong>（6👍 / 0💬）— Linus 自述 AI 在艰难调试中「极大帮助」，权威背书 agent 辅助开发。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49384957">Claude Opus 4.6 returned nothing 900/900 times. Should agents retry?</a></strong>（5👍 / 1💬）— 900 次调用 0 返回，引发「agent 是否该重试、如何界定失败」的讨论，与 OpenCode #41469 空响应误判同源。</li>
</ul>
<h2>二、Claude / Anthropic 生态</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49388752">Claudette: Make Claude Stop Talking Like a BuzzFeed Article</a></strong>（77👍 / 75💬）— 让 Claude 停止「 BuzzFeed 式」浮夸表达的技能，高赞高讨论，反映对模型输出风格的审美疲劳。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49378451">Anthropic Expects to Match SpaceX&#39;s Record IPO Size or Top It</a></strong>（8👍 / 0💬）— Bloomberg：Anthropic 预计 IPO 规模匹敌或超越 SpaceX 纪录。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49390345">Anthropic plans to change enterprise data retention policy</a></strong>（4👍 / 0💬）— Reuters：Anthropic 计划调整企业数据保留政策，企业治理相关。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49387028">Opus 5 feels, in a word, hostile</a></strong>（4👍 / 0💬）— 用户对 Opus 5 交互「敌对感」的吐槽（Reddit 镜像）。</li>
</ul>
<h2>三、OpenAI 动态与争议</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49379261">Introducing AI Futures</a></strong>（30👍 / 8💬）— OpenAI 发布「AI Futures」。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49386233">OpenAI is becoming a surveillance company</a></strong>（9👍 / 2💬）— 对 OpenAI  surveillance 化的批评。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49381996">If You Weren&#39;t Worried About A.I., You Should Be</a></strong>（9👍 / 5💬）— NYT 观点文，呼吁重视 AI 风险。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49390687">Why your infrastructure is more important than the next LLM release</a></strong>（6👍 / 1💬）— 论点：基础设施比下一个模型发布更重要。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49384270">OpenAI Is Backing Away from Reddit as Reddit Tries to Become OpenAI?</a></strong>（6👍 / 1💬）— OpenAI 与 Reddit 关系微妙变化。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49378686">OpenAI&#39;s Rogue AI Agent Hacked More Than Just Hugging Face</a></strong>（5👍 / 1💬）— Wired：OpenAI 失控 agent 不止黑了 Hugging Face。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49389602">Introducing ChatGPT for Teens</a></strong>（4👍 / 0💬）— OpenAI 推出青少年版 ChatGPT。</li>
</ul>
<h2>四、Show HN 与开发者项目</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49389466">Show HN: A desktop fly drawn to the scent of vibecode</a></strong>（19👍 / 8💬）— 趣味项目：被 vibecode「气味」吸引的桌面苍蝇。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49391007">Show HN: Visual way to understand things in parallel</a></strong>（5👍 / 3💬）— 可视化并行理解工具。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49380160">Show HN: Praxos – team messaging with built-in memory</a></strong>（5👍 / 2💬）— 内置记忆的团队消息工具（呼应「记忆」主线）。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49389972">Show HN: Gramola, a CoverFlow-style music dock for macOS</a></strong>（5👍 / 2💬）— macOS 音乐坞。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49389744">Show HN: Bounded GenAI metrics from Otel traces with O raw prompts</a></strong>（4👍 / 2💬）— 从 Otel trace 取 GenAI 有界指标、零原始 prompt 泄露，可观测性方向。</li>
</ul>
<h2>五、模型与训练</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49387684">Good Results when training Qwen 3 4B to learn a new domain</a></strong>（5👍 / 0💬）— Qwen 3 4B 迁移学习新领域的好结果。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49391959">Benchmarks of rumored Mythos level model from Zhipu AI</a></strong>（3👍 / 0💬）— 智谱传闻 Mythos 级别模型的基准。</li>
</ul>
<h2>六、其它/学术</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49388963">How I came to write that paper with Leslie Lamport</a></strong>（32👍 / 9💬）— 与 Lamport 合著论文的幕后。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49389339">Code Obfuscation via Local Mixing</a></strong>（24👍 / 1💬）— Vitalik 关于代码混淆的文章。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49391389">Rebuilding our Electron meeting-recording engine in Swift</a></strong>（18👍 / 1💬）— 用 Swift 重写 Electron 会议录制引擎。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49391453">The puzzling case of Britain&#39;s young people and what they think of AI</a></strong>（4👍 / 0💬）— 英国年轻人对 AI 的态度调查。</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49385089">Writing with AI Is Stupid</a></strong>（5👍 / 3💬）— 对「用 AI 写作」的批评，与 #2 Claudette 的审美疲劳呼应。</li>
</ul>
<h2>趋势小结</h2>
<ul>
<li><strong>成本与计费透明是头号议题</strong>：Codex Bedrock 10x 费用（145👍）与 OpenCode 空响应误判同源——agent 的「用量/失败可诊断」正成为信任底座。</li>
<li><strong>自托管 + 沙箱成共识</strong>：self-hosted agentic factory、Proliferate、Praxos 记忆、Otel 指标，均指向「可控、可观测、隐私优先」的部署取向。</li>
<li><strong>模型输出风格引发审美疲劳</strong>：Claudette（77👍）、Writing with AI Is Stupid，显示社区开始反感浮夸/套路化表达。</li>
<li><strong>巨头动态主导舆论场</strong>：Anthropic IPO、OpenAI surveillance/Reddit/青少年版，企业治理与伦理争议持续升温。</li>
</ul>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，所有内容基于 HN Algolia API 实时抓取并由执行代理人工撰写，未调用任何外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>Hacker News AI Community Digest 2026-08-22</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-hn-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-22/ai-hn-en</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
      <description>Hacker News AI Daily — 2026-08-22 Generated: 2026-08-22 02:30 (GMT+8) Source: HN Algolia Search API (6 queries: AI / LLM / Claude / OpenAI / Anthropic / machine learning, last 24h, deduped, Top 30 by points; 104 unique stories this batch) This digest is produced by the agents-radar local automation. All writing is done by the executing agent — no external LLM API was called. 1. AI Coding Agents: Cost, Reliability, Self-Hosting Codex on AWS bedrock bug causing 10x charges (145👍 / 60💬) — An AWS ...</description>
      <content:encoded><![CDATA[<h1>Hacker News AI Daily — 2026-08-22</h1>
<blockquote>
<p>Generated: 2026-08-22 02:30 (GMT+8)
Source: HN Algolia Search API (6 queries: AI / LLM / Claude / OpenAI / Anthropic / machine learning, last 24h, deduped, Top 30 by points; 104 unique stories this batch)
This digest is produced by the agents-radar local automation. All writing is done by the executing agent — no external LLM API was called.</p>
</blockquote>
<hr>
<h2>1. AI Coding Agents: Cost, Reliability, Self-Hosting</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49383326">Codex on AWS bedrock bug causing 10x charges</a></strong> (145👍 / 60💬) — An AWS Bedrock Codex bug inflated costs 10x, sparking heated debate on agent billing transparency. Top story — &quot;cost control&quot; is now the community&#39;s #1 anxiety.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49390463">Building an (almost) fully self-hosted, sandboxed, agentic software factory</a></strong> (25👍 / 17💬) — A near-fully self-hosted, sandboxed agentic software factory, echoing today&#39;s CLI/OpenClaw &quot;sandbox / self-host&quot;主线.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49390739">Show HN: Proliferate – open-source, self-hostable Codex for any coding agent</a></strong> (16👍 / 7💬) — OSS project bringing self-hostable Codex to any coding agent.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49390066">LLMs are proof that Unix won</a></strong> (10👍 / 3💬) — Reading LLM&#39;s victory through the Unix philosophy.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49391392">Linus Torvalds Endures a Debug Session from Hell, &quot;Enormously Helped&quot; by AI</a></strong> (6👍 / 0💬) — Linus says AI &quot;enormously helped&quot; in a brutal debug session — authoritative endorsement of agent-assisted dev.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49384957">Claude Opus 4.6 returned nothing 900/900 times. Should agents retry?</a></strong> (5👍 / 1💬) — 900 calls, 0 returns, raising &quot;should agents retry / how to define failure&quot; — same root as OpenCode #41469 empty-response miscount.</li>
</ul>
<h2>2. Claude / Anthropic Ecosystem</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49388752">Claudette: Make Claude Stop Talking Like a BuzzFeed Article</a></strong> (77👍 / 75💬) — A skill to stop Claude&#39;s BuzzFeed-style fluff; high votes + discussion, signaling aesthetic fatigue with model output style.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49378451">Anthropic Expects to Match SpaceX&#39;s Record IPO Size or Top It</a></strong> (8👍 / 0💬) — Bloomberg: Anthropic expects an IPO matching or surpassing SpaceX&#39;s record.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49390345">Anthropic plans to change enterprise data retention policy</a></strong> (4👍 / 0💬) — Reuters: Anthropic plans to change enterprise data-retention policy (enterprise governance).</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49387028">Opus 5 feels, in a word, hostile</a></strong> (4👍 / 0💬) — User gripe about Opus 5&#39;s &quot;hostile&quot; interaction (Reddit mirror).</li>
</ul>
<h2>3. OpenAI News &amp; Controversies</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49379261">Introducing AI Futures</a></strong> (30👍 / 8💬) — OpenAI launches &quot;AI Futures&quot;.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49386233">OpenAI is becoming a surveillance company</a></strong> (9👍 / 2💬) — Critique of OpenAI&#39;s surveillance trajectory.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49381996">If You Weren&#39;t Worried About A.I., You Should Be</a></strong> (9👍 / 5💬) — NYT op-ed urging attention to AI risk.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49390687">Why your infrastructure is more important than the next LLM release</a></strong> (6👍 / 1💬) — Thesis: infrastructure matters more than the next model.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49384270">OpenAI Is Backing Away from Reddit as Reddit Tries to Become OpenAI?</a></strong> (6👍 / 1💬) — Shifting OpenAI–Reddit relationship.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49378686">OpenAI&#39;s Rogue AI Agent Hacked More Than Just Hugging Face</a></strong> (5👍 / 1💬) — Wired: OpenAI&#39;s rogue agent hacked more than Hugging Face.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49389602">Introducing ChatGPT for Teens</a></strong> (4👍 / 0💬) — OpenAI launches a teen version of ChatGPT.</li>
</ul>
<h2>4. Show HN &amp; Developer Projects</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49389466">Show HN: A desktop fly drawn to the scent of vibecode</a></strong> (19👍 / 8💬) — Fun project: a desktop fly drawn to the &quot;scent&quot; of vibecode.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49391007">Show HN: Visual way to understand things in parallel</a></strong> (5👍 / 3💬) — Visual parallel-understanding tool.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49380160">Show HN: Praxos – team messaging with built-in memory</a></strong> (5👍 / 2💬) — Team messaging with built-in memory (echoes the &quot;memory&quot;主线).</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49389972">Show HN: Gramola, a CoverFlow-style music dock for macOS</a></strong> (5👍 / 2💬) — macOS music dock.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49389744">Show HN: Bounded GenAI metrics from Otel traces with O raw prompts</a></strong> (4👍 / 2💬) — Bounded GenAI metrics from Otel traces, zero raw-prompt leakage — observability direction.</li>
</ul>
<h2>5. Models &amp; Training</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49387684">Good Results when training Qwen 3 4B to learn a new domain</a></strong> (5👍 / 0💬) — Good transfer-learning results for Qwen 3 4B on a new domain.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49391959">Benchmarks of rumored Mythos level model from Zhipu AI</a></strong> (3👍 / 0💬) — Benchmarks of Zhipu AI&#39;s rumored Mythos-level model.</li>
</ul>
<h2>6. Other / Academic</h2>
<ul>
<li><strong><a href="https://news.ycombinator.com/item?id=49388963">How I came to write that paper with Leslie Lamport</a></strong> (32👍 / 9💬) — Behind the scenes of co-authoring a paper with Lamport.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49389339">Code Obfuscation via Local Mixing</a></strong> (24👍 / 1💬) — Vitalik on code obfuscation.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49391389">Rebuilding our Electron meeting-recording engine in Swift</a></strong> (18👍 / 1💬) — Rewriting an Electron meeting-recording engine in Swift.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49391453">The puzzling case of Britain&#39;s young people and what they think of AI</a></strong> (4👍 / 0💬) — Survey of British youth attitudes toward AI.</li>
<li><strong><a href="https://news.ycombinator.com/item?id=49385089">Writing with AI Is Stupid</a></strong> (5👍 / 3💬) — Critique of &quot;writing with AI&quot;, resonating with #2 Claudette&#39;s aesthetic fatigue.</li>
</ul>
<h2>Trend Takeaways</h2>
<ul>
<li><strong>Cost &amp; billing transparency is the #1 topic</strong>: Codex Bedrock 10x charges (145👍) shares a root with OpenCode&#39;s empty-response miscount — &quot;usage/failure diagnosable&quot; is becoming the trust bedrock for agents.</li>
<li><strong>Self-host + sandbox is consensus</strong>: self-hosted agentic factory, Proliferate, Praxos memory, Otel metrics — all point to &quot;controllable, observable, privacy-first&quot; deployment.</li>
<li><strong>Model output style triggers aesthetic fatigue</strong>: Claudette (77👍) and &quot;Writing with AI Is Stupid&quot; show the community tiring of fluff/boilerplate expression.</li>
<li><strong>Megacorp moves dominate the discourse</strong>: Anthropic IPO, OpenAI surveillance/Reddit/teen-version — enterprise governance and ethics controversies keep heating up.</li>
</ul>
<hr>
<p><em>This digest is generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. All content is fetched live from the HN Algolia API and written by the executing agent — no external LLM was called.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI CLI 工具社区动态日报 2026-08-21</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-cli</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-cli</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate>
      <description>AI CLI 工具社区动态日报 2026-08-21 生成时间: 2026-08-21 02:30 (GMT+8) | 覆盖工具: 7 个 CLI + Claude Code Skills 本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。 Claude Code OpenAI Codex Gemini CLI GitHub Copilot CLI Kimi Code CLI OpenCode Qwen Code Claude Code Skills 横向对比 AI CLI 工具社区动态横向对比分析报告（2026-08-21） 1. 生态全景 AI CLI 工具进入「日更竞争」阶段：今日 Claude Code、OpenAI Codex、Gemini CLI、GitHub Copilot CLI、OpenCode、Qwen Code 均有版本发布，IronClaw / EasyClaw / Moltis / CoPaw 等周边生态也同步出新。社区诉求的焦点从「模型能力」进一步转向「工程可信度与平台质量」——Win...</description>
      <content:encoded><![CDATA[<h1>AI CLI 工具社区动态日报 2026-08-21</h1>
<blockquote>
<p>生成时间: 2026-08-21 02:30 (GMT+8) | 覆盖工具: 7 个 CLI + Claude Code Skills
本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。</p>
</blockquote>
<ul>
<li><a href="https://github.com/anthropics/claude-code">Claude Code</a></li>
<li><a href="https://github.com/openai/codex">OpenAI Codex</a></li>
<li><a href="https://github.com/google-gemini/gemini-cli">Gemini CLI</a></li>
<li><a href="https://github.com/github/copilot-cli">GitHub Copilot CLI</a></li>
<li><a href="https://github.com/MoonshotAI/kimi-cli">Kimi Code CLI</a></li>
<li><a href="https://github.com/anomalyco/opencode">OpenCode</a></li>
<li><a href="https://github.com/QwenLM/qwen-code">Qwen Code</a></li>
<li><a href="https://github.com/anthropics/skills">Claude Code Skills</a></li>
</ul>
<hr>
<h2>横向对比</h2>
<h1>AI CLI 工具社区动态横向对比分析报告（2026-08-21）</h1>
<h2>1. 生态全景</h2>
<p>AI CLI 工具进入「日更竞争」阶段：今日 Claude Code、OpenAI Codex、Gemini CLI、GitHub Copilot CLI、OpenCode、Qwen Code 均有版本发布，IronClaw / EasyClaw / Moltis / CoPaw 等周边生态也同步出新。社区诉求的焦点从「模型能力」进一步转向「工程可信度与平台质量」——Windows 平台问题（Codex 尤为突出）、TUI 终端交互细节、上下文压缩后的记忆持久化、以及沙箱/权限的最小信任边界，成为跨工具共通的痛点。一个明显趋势是：<strong>自动化 bot 正在深度参与各工具的发布质量门禁</strong>（Codex 的 <code>copyberry[bot]</code>、Qwen 的 <code>qwen-code-review-bot</code>、OpenCode 的 <code>opencode-agent</code> 等），修复与发布的频次被显著拉高，但外部人类社区的声量分化加剧。</p>
<h2>2. 各工具活跃度对比（近 24h）</h2>
<table>
<thead>
<tr>
<th>工具</th>
<th>活跃 Issues</th>
<th>重要 PR</th>
<th>Releases（今日）</th>
</tr>
</thead>
<tbody><tr>
<td>Claude Code</td>
<td>12+（高赞集中）</td>
<td>0</td>
<td>v2.1.236 / v2.1.237</td>
</tr>
<tr>
<td>OpenAI Codex</td>
<td>12（Windows 主导）</td>
<td>12+（bot 驱动）</td>
<td>rust-v0.149.0-alpha.4 / .3 / .2 / .1</td>
</tr>
<tr>
<td>Gemini CLI</td>
<td>16</td>
<td>12+</td>
<td>v0.56.0（稳定）/ v0.57.0-preview.0</td>
</tr>
<tr>
<td>GitHub Copilot CLI</td>
<td>14+</td>
<td>1</td>
<td>v1.0.81-6 / -5 / -4 / -3 / -2</td>
</tr>
<tr>
<td>Kimi Code CLI</td>
<td>0</td>
<td>0</td>
<td>无</td>
</tr>
<tr>
<td>OpenCode</td>
<td>14</td>
<td>12+</td>
<td>v1.18.19</td>
</tr>
<tr>
<td>Qwen Code</td>
<td>0（issue）</td>
<td>12+</td>
<td>v0.21.15</td>
</tr>
</tbody></table>
<h2>3. 共同关注的功能方向</h2>
<ul>
<li><strong>Windows / 跨平台质量</strong>：OpenAI Codex 的 Windows 冻结（#20214，86👍/107💬）、独立安装包诉求（#13993，242👍）、Trusted RPC 浏览器插件失败（#39136）持续高赞；Copilot CLI 的 <code>wta.exe</code> 路径引号错误（#4540）与沙箱阻断 git（#4524）；OpenCode 此前暴露的 <code>/tmp</code> 泄漏、Sidecar 超时等仍被社区引用。Windows 是第一大痛点平台。</li>
<li><strong>TUI / 终端交互稳定性</strong>：Claude Code 复制粘贴缩进污染（#18170，287👍/134💬）仍是社区最高频诉求；OpenCode 的剪贴板写入静默失败修复（#41924）仍在开放；Gemini CLI 的滚动/渲染（#13107、#10673）与拖拽图片（#27855）被持续提出。</li>
<li><strong>上下文与跨压缩记忆</strong>：Claude Code 用户自建跨压缩记忆系统（#34556，98💬）热度不减；OpenCode 的「中断流被记为干净停止」（#37852，56👍）暴露 subagent 用量统计失真；Gemini 的 subagent 误报成功（#22323）仍在讨论。</li>
<li><strong>权限 / 沙箱最小信任</strong>：Copilot CLI 沙箱策略过度强制（#4524）、<code>store_memory</code> 在 1.0.81 失败（#4535）、非交互模式绕过 managed settings（#4103）构成企业治理语境的核心争议；Codex 收紧 Git 命令信任、隔离插件 Git 操作等安全 PR 方向清晰。</li>
<li><strong>模型兼容性与成本透明</strong>：Codex GPT-5.6 串行化导致 27–45% 额外用量（#35050，72👍）；OpenCode 的 gpt-5.6 系列参数注入/空响应问题（昨日 #43367/#43565）仍在被引用；Qwen Code 路由切换后 token 计数失效（#9506）已修复并绑定路由身份。</li>
<li><strong>自动化发布质量门禁</strong>：Codex <code>copyberry[bot]</code> 今日批量合入 12+ PR（模型定义刷新、shell 统一执行、MCP 事件流等）；Qwen <code>qwen-code-review-bot</code> 发布 v0.21.15；OpenCode <code>opencode-agent</code> 持续提交。AI 已深度参与自身软件工程。</li>
</ul>
<h2>4. 差异化定位</h2>
<ul>
<li><strong>Claude Code</strong>：社区期望最高、反馈最尖锐，复制粘贴/快捷键/输出展开等体验细节被零容忍审视；v2.1.237 新增「Concise」输出风格与 prompt caching 修复，定位专业开发者日常主力终端。PR 侧近 24h 静默，意味着主干进入稳定打磨期。</li>
<li><strong>OpenAI Codex</strong>：Rust 重写持续推进，bot 驱动发布节奏快；Windows 质量与桌面端集成（Computer Use、浏览器插件）是最突出短板。安全方向（Git 信任收紧、插件隔离）获社区肯定，定位 OpenAI 全场景入口。</li>
<li><strong>Gemini CLI</strong>：稳定版/预览版分轨清晰，PR 以安全加固（Cloud Workstations OAuth、IDE 连接、环境变更同意）与模型接入（Gemini 3.6/3.7 Flash）为主，成熟度中上。</li>
<li><strong>GitHub Copilot CLI</strong>：企业受管语境最明确，managed settings 强制、沙箱、数据驻留、审计是核心；今日 v1.0.81-6 新增 <code>defaultMode</code>/<code>defaultPermissionMode</code> 与 <code>--with-token</code> 登录，ACP 客户端获得 subagent ID 等能力。定位企业受管环境的 Copilot 入口。</li>
<li><strong>Kimi Code CLI</strong>：今日零动态（issues/PRs/releases 全空），生态处于早期静默期。</li>
<li><strong>OpenCode</strong>：社区贡献极活跃，v1.18.19 新增 Cloudflare AI Gateway 原生透传、对齐 Codex 速率限制、Go provider 启用 web 搜索；问题集中在 TUI 数据丢失级缺陷与 gpt-5.6 兼容性。定位追求最新模型与高度可定制的开发者。</li>
<li><strong>Qwen Code</strong>：v0.21.15 强化 Web Shell 文件附件、混合模型 Thinking 开关、<code>/review --resume</code>、鉴权 HTTPS Git 扩展安装，工业化的 release/CI bot 体系成熟，定位验证严谨性与中国 IM/云生态用户。</li>
</ul>
<h2>5. 值得关注的趋势信号</h2>
<ul>
<li><strong>Windows 是未被充分满足的硬市场</strong>：Codex 冻结/安装包/插件、Copilot 路径引号、Gemini Browser agent 跨显示协议失败——后来者若把 Windows 质量当作一等公民，是差异化切口。</li>
<li><strong>TUI 基础体验成为选型硬指标</strong>：复制粘贴、滚动、拖拽图片等「小问题」占据各工具高赞榜，真实终端环境（WSL、Ghostty、Windows Terminal）可用性测试应优先于模型能力对比。</li>
<li><strong>记忆持久化是下一轮分水岭</strong>：压缩后历史可回溯 + 隐私安全 + 可控，三件事同时做好的工具有望建立长期粘性。</li>
<li><strong>自动化发布门禁双刃剑</strong>：bot 提速修复，但也让外部人类贡献者声量被稀释，对人工审查机制提出新要求。</li>
<li><strong>模型行为变更直接关联账单</strong>：GPT-5.6 串行化带来额外用量（#35050），开发者应「先小规模验证成本再大规模切换」，并要求工具提供路由身份绑定的用量统计。</li>
</ul>
<hr>
<h2>各工具详细报告</h2>
<details>
<summary><strong>Claude Code</strong> — <a href="https://github.com/anthropics/claude-code">anthropics/claude-code</a></summary>

<h1>Claude Code 社区动态日报（2026-08-21）</h1>
<h2>今日速览</h2>
<ul>
<li>发布 v2.1.237 与 v2.1.236：v2.1.237 带来内置「Concise」输出风格并修复自定义 base URL 下的 prompt caching；v2.1.236 新增 <code>ANTHROPIC_DEFAULT_MODEL</code>、跨会话 <code>notify_when_idle</code>、macOS 沙箱通配读拒绝规则强化及多项渲染/会话修复。</li>
<li>社区高赞问题持续集中在终端复制粘贴（#18170，287👍/134💬）、多账号切换（#36151，847👍）、跨压缩记忆（#34556，98💬）。</li>
<li>PR 侧近 24h 静默（0 条合并/更新），主干进入稳定打磨期。</li>
</ul>
<h2>版本发布</h2>
<p><strong>v2.1.237</strong></p>
<ul>
<li>修复：使用 LLM 网关或自定义 base URL 的会话中 prompt caching 失效。</li>
<li>新增：内置「Concise」输出风格——Claude 直接给结果、跳过开场白与叙述，同时保持同等的执行深度，可在 <code>/config</code> 的 Output style 下选择。</li>
</ul>
<p><strong>v2.1.236</strong></p>
<ul>
<li>新增 <code>ANTHROPIC_DEFAULT_MODEL</code> 环境变量（设定新会话起始模型，<code>/model</code> 可覆盖且重启保持，区别于 <code>ANTHROPIC_MODEL</code>）。</li>
<li>新增跨会话 <code>SendMessage</code> 的 <code>notify_when_idle</code>（macOS/Linux，opt-in 一次性通知）。</li>
<li>沙箱（macOS）：通配读拒绝规则（如 <code>**/.env</code>）在允许读区域内优先、覆盖匹配目录内容且不可通过重命名绕过。</li>
<li>修复：切换目录被删除后剪贴板复制/后台会话/本地 MCP 日志损坏（自 2.1.229）；全屏渲染器单次启动失败后回退经典渲染器；<code>/model</code> 选择器超高时只显示适配行数；SendMessage 畸形闭合标签拒绝；WSL 下 <code>powershell.exe</code> 未启动时的未处理 promise 拒绝；全屏模式新消息不刷新等。</li>
</ul>
<h2>社区热点 Issues（近 24h 活跃）</h2>
<ol>
<li><strong>#6235 [FEATURE] 支持 AGENTS.md</strong>（6335👍）— 社区长期最高赞功能诉求，呼吁原生支持项目级 <code>AGENTS.md</code> 指令文件。</li>
<li><strong>#36151 多账号切换</strong>（847👍/开放）— 希望在 Claude Mobile 中无需共享邮箱即可切换多账号。</li>
<li><strong>#18170 终端复制粘贴混入缩进与行尾空格</strong>（287👍/134💬）— 社区最高频 TUI 痛点，影响将结果移入编辑器的工作流。</li>
<li><strong>#84352 CVP 已批准的组织仍被 cyber safeguard 拦截</strong>（21👍/130💬）— 企业合规场景的误杀问题。</li>
<li><strong>#60705 /goal Stop-hook 被当作越权授权</strong>（127💬）— hook 指令边界与安全的讨论。</li>
<li><strong>#10199 API Error 400 Thinking Block 修改错误</strong>（65👍/100💬）— 思考块相关 API 调用稳定性。</li>
<li><strong>#34556 跨压缩持久记忆</strong>（98💬）— 用户自建记忆系统，社区共鸣强烈。</li>
<li><strong>#4953 内存泄漏至 120GB 被 OOM 杀死</strong>（75👍/97💬）— 进程资源管理长期隐患。</li>
<li><strong>#32479 GitHub Connector 在 Desktop 已连但 CLI 不识别</strong>（140👍/89💬）— 连接器状态一致性。</li>
<li><strong>#22543 Cowork 创建 10GB VM 包拖慢性能</strong>（259👍/76💬）— 资源占用。</li>
<li><strong>#79337 Fable 5 提示需用量积分</strong>（26👍/75💬）— 计费/权益相关。</li>
<li><strong>#63875 模型工具调用无法解析（重试也失败）反复打断会话</strong>（116👍/75💬）— 解析稳定性。</li>
</ol>
<h2>功能需求趋势</h2>
<table>
<thead>
<tr>
<th>方向</th>
<th>代表 Issues</th>
<th>社区诉求</th>
</tr>
</thead>
<tbody><tr>
<td>项目级指令</td>
<td>#6235、#60705</td>
<td>原生 AGENTS.md、hook 指令边界清晰</td>
</tr>
<tr>
<td>TUI 交互</td>
<td>#18170、#4953</td>
<td>复制粘贴干净、内存可控</td>
</tr>
<tr>
<td>账户/组织</td>
<td>#36151、#84352、#32479</td>
<td>数据驻留、连接器一致性</td>
</tr>
<tr>
<td>资源/性能</td>
<td>#22543、#4953</td>
<td>VM 包瘦身、泄漏治理</td>
</tr>
</tbody></table>
<h2>开发者关注点</h2>
<ol>
<li><strong>复制粘贴仍是最大痛点</strong>：#18170 以 287👍居首，直接冲击核心工作流。</li>
<li><strong>跨压缩记忆成黑匣子</strong>：#34556 反映压缩后历史不可回看，用户被迫自建系统。</li>
<li><strong>资源与健康度</strong>：内存泄漏（#4953）、10GB VM（#22543）影响长时间使用信心。</li>
<li><strong>企业合规误杀</strong>：#84352 显示已批准组织仍被拦截，合规规则需更精细。</li>
</ol>
</details>

<details>
<summary><strong>OpenAI Codex</strong> — <a href="https://github.com/openai/codex">openai/codex</a></summary>

<h1>OpenAI Codex 社区动态日报 — 2026-08-21</h1>
<h2>今日速览</h2>
<ul>
<li>发布 rust-v0.149.0-alpha.4（及 .3/.2/.1 系列），release note 为占位格式，具体变更见对应 tag 的 commit。</li>
<li>社区 Windows 平台问题继续主导：App 冻结（#20214，86👍/107💬）、独立安装包诉求（#13993，242👍）、Trusted RPC 浏览器插件失败（#39136，82💬）。</li>
<li><code>copyberry[bot]</code> 批量合入 12+ PR，覆盖模型定义刷新、shell 统一执行、MCP 事件流、权限档案选择等。</li>
</ul>
<h2>版本发布</h2>
<ul>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.4">rust-v0.149.0-alpha.4</a> — 2026-08-20</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.3">rust-v0.149.0-alpha.3</a> — 2026-08-20</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.2">rust-v0.149.0-alpha.2</a> — 2026-08-19</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.1">rust-v0.149.0-alpha.1</a> — 2026-08-19</li>
</ul>
<h2>社区热点 Issues（近 24h 活跃）</h2>
<ol>
<li><strong>#20214 Windows 11 上频繁冻结/卡顿</strong>（86👍/107💬）— 资源充足仍卡顿，最高讨论度。</li>
<li><strong>#28969 增加关闭 60 秒自动 resolve 的设置</strong>（201👍/83💬）— 提问自动解决过激。</li>
<li><strong>#39136 内置浏览器插件初始化失败：Trusted RPC 依赖不在可信代码路径</strong>（42👍/82💬）— Windows 回归。</li>
<li><strong>#13993 支持独立 Windows 安装包 <code>codex-setup.exe</code></strong>（242👍/79💬）— 安装体验诉求。</li>
<li><strong>#39397 0.148 对 gpt-5.6-sol 发送 prompt_cache_retention 致每轮失败</strong>（37👍/41💬）— 模型参数注入。</li>
<li><strong>#30009 apply_patch 因 Windows 沙箱相关错误失败</strong>（11👍/34💬）。</li>
<li><strong>#28507 所选模型容量已满</strong>（33👍/33💬）— 容量与配额。</li>
<li><strong>#38455 ChatGPT 桌面端 Computer Use worker 反复 spawn 并 V8 OOM</strong>（13👍/32💬）。</li>
<li><strong>#25178 Windows 10 22H2 Computer Use 截图失败</strong>（15👍/28💬）。</li>
<li><strong>#39239 <code>thread/archive</code> 因 <code>\\?\</code> 路径失败</strong>（3👍/26💬）。</li>
<li><strong>#39162 macOS 打开旧会话使 ChatGPT 认证失效</strong>（18👍/25💬）。</li>
<li><strong>#35050 GPT-5.6 串行化工具调用，显式批处理降低 27–45% 加权用量</strong>（72👍/25💬）。</li>
</ol>
<h2>重要 PR 进展（近 24h，<code>copyberry[bot]</code> 主导）</h2>
<ol>
<li><strong>#39770 刷新内置模型定义</strong></li>
<li><strong>#39765 在插件安装元数据中包含 suggestion IDs</strong></li>
<li><strong>#39761 增加 app-server MCP 事件流</strong></li>
<li><strong>#39757 将 shell 执行统一到 unified exec</strong></li>
<li><strong>#39756 在 exec server 中缓存 shell 快照</strong></li>
<li><strong>#39755 将 managed developer instructions 加入 requirements</strong></li>
<li><strong>#39752 暴露未编译的权限档案选择</strong></li>
<li><strong>#39749 要求文件系统后端实现目录遍历</strong></li>
<li><strong>#39746 从 executors 刷新 resumed thread 的 capability roots</strong></li>
<li><strong>#39744 对短 composer 输入跳过后处理</strong></li>
<li><strong>#39741 使用模型特定的 auto-review 结果指令</strong></li>
<li><strong>#39738 遵从模型默认中的 Guardian runtime 设置</strong></li>
</ol>
<h2>功能需求趋势</h2>
<ul>
<li><strong>Windows 稳定性是第一诉求</strong>：冻结、安装包、Trusted RPC、沙箱、Computer Use 截图等问题密度最高。</li>
<li><strong>成本与用量可控</strong>：GPT-5.6 串行化（#35050）放大上下文与账单，社区希望更透明。</li>
<li><strong>交互尊重用户节奏</strong>：60 秒自动 resolve（#28969）被高赞反对，需可关闭。</li>
<li><strong>安全边界收紧获肯定</strong>：Git 命令不再默认安全、插件 Git 隔离方向正确。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>Windows 是最大痛点平台</strong>：从安装到运行时处处是独立高赞 Issue。</li>
<li><strong>容量/配额焦虑</strong>：模型满载（#28507）与额度（#39397 之外的计费讨论）并存。</li>
<li><strong>bot 提速发布但需人工审查</strong>：<code>copyberry[bot]</code> 高频合入，质量门禁依赖自动化测试覆盖。</li>
</ul>
</details>

<details>
<summary><strong>Gemini CLI</strong> — <a href="https://github.com/google-gemini/gemini-cli">google-gemini/gemini-cli</a></summary>

<h1>Gemini CLI 社区动态日报 — 2026-08-21</h1>
<h2>今日速览</h2>
<p>今日发布 v0.56.0 稳定版、v0.57.0-preview.0 预览版；PR 围绕 Cloud Workstations OAuth、IDE 连接修复、环境变更同意、Gemini 3.6/3.7 Flash 模型接入、subagent 误报修复等。社区高赞问题集中在公开路线图（#4191，173👍）、V1.0 后工作（#3132，150👍）与模型可用性（#28802，40👍）。</p>
<h2>版本发布</h2>
<ul>
<li><strong>v0.56.0（稳定版）</strong>：完整变更见 <a href="https://github.com/google-gemini/gemini-cli/compare/v0.55.1...v0.56.0">v0.55.1...v0.56.0</a>。</li>
<li><strong>v0.57.0-preview.0</strong>：动态解析 Cloud Workstations 代理重定向 URI 修复 OAuth（<a href="https://github.com/google-gemini/gemini-cli/pull/28688">#28688</a>）；修复 IDE 连接目录不匹配被静默吞掉（<a href="https://github.com/google-gemini/gemini-cli/pull/28729">#28729</a>）；eval 校验与工具调用格式化（<a href="https://github.com/google-gemini/gemini-cli/pull/28344">#28344</a>、<a href="https://github.com/google-gemini/gemini-cli/pull/28305">#28305</a>）；上下文感知静默重试与可用性 TTL（<a href="https://github.com/google-gemini/gemini-cli/pull/28790">#28790</a>）；取消/中止时回滚整个多轮请求（<a href="https://github.com/google-gemini/gemini-cli/pull/28801">#28801</a>）。</li>
</ul>
<h2>社区热点 Issues（近 24h 活跃）</h2>
<ol>
<li><strong>#4191 公开路线图</strong>（173👍）— 社区希望透明的产品规划。</li>
<li><strong>#3132 V1.0 之后工作</strong>（150👍/45💬）— 后发布路线图讨论。</li>
<li><strong>#28802 最新 Gemini 模型（Flash 3.5/3.6/3.7）已可用</strong>（40👍/10💬）— 模型接入反馈。</li>
<li><strong>#27393 命令替换块应可用户配置而非硬编码墙</strong>（19💬）。</li>
<li><strong>#28052 antigravity.google URL 末尾句点导致链接无法加载</strong>（14💬）。</li>
<li><strong>#22323 Subagent MAX_TURNS 后误报 GOAL 成功</strong>（12💬）— 信任机制。</li>
<li><strong>#21409 Generalist agent 挂起</strong>（8👍/8💬）。</li>
<li><strong>#27855 原生终端拖拽与图片拖放（多模态对齐）</strong>（8💬）。</li>
<li><strong>#19873 零依赖 OS 沙箱化与执行后意图路由</strong>（8💬）。</li>
<li><strong>#22745 AST 感知文件读取/搜索/映射的影响评估</strong>（7💬）。</li>
</ol>
<h2>重要 PR 进展（近 24h）</h2>
<ol>
<li><strong>#28932 Antigravity agent runner 与异步流解析（pr-generation）</strong></li>
<li><strong>#28915 修复 ignore 路径处理中 symlink 评估一致性</strong></li>
<li><strong>#28931 明确全局 npm 安装的默认稳定发布通道</strong></li>
<li><strong>#28863 环境变更需用户同意并清理影响运行时行为的环境变量</strong></li>
<li><strong>#28933 迭代式编排状态机（pr-generation）</strong></li>
<li><strong>#28867 防止 agents 模式禁用时 subagent 运行</strong></li>
<li><strong>#28910 新增 Gemini 3.7 Flash / 3.6 Flash 模型配置与选择</strong></li>
<li><strong>#28828 预览模型被静默替换时告警</strong></li>
<li><strong>#28926 Windows longpaths 设置说明</strong></li>
<li><strong>#28917 Whisper 模型原子下载与失败清理</strong></li>
</ol>
<h2>功能需求趋势</h2>
<ul>
<li><strong>路线图透明</strong>：#4191/#3132 高赞，社区要清晰规划。</li>
<li><strong>代理可靠性</strong>：subagent 误报成功（#22323）、generalist 挂起（#21409）。</li>
<li><strong>多模态终端体验</strong>：图片拖放（#27855）、AST 感知读取（#22745）。</li>
<li><strong>安全与一致性</strong>：环境变更同意（#28863）、symlink 评估（#28915）、预览模型替换告警（#28828）。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>subagent 行为不可预测</strong>仍是信任短板。</li>
<li><strong>多模态与本地化体验</strong>（拖拽图片、Windows longpaths）被持续提出。</li>
<li><strong>模型可用性反馈积极</strong>（#28802），Gemini 3.x Flash 系列接入预期高。</li>
</ul>
</details>

<details>
<summary><strong>GitHub Copilot CLI</strong> — <a href="https://github.com/github/copilot-cli">github/copilot-cli</a></summary>

<h1>GitHub Copilot CLI 社区动态日报 — 2026-08-21</h1>
<h2>今日速览</h2>
<p>今日连发 v1.0.81-2 至 v1.0.81-6 五个 prerelease。v1.0.81-6 新增 <code>defaultMode</code>/<code>defaultPermissionMode</code> 设置、<code>--with-token</code> 登录，ACP 客户端获得 subagent ID 与实时标题/模式/命令/计划更新，Canvas 窗口改为后台打开不抢焦点。社区层面，<code>store_memory</code> 在 1.0.81 失败（#4535）、沙箱阻断 git（#4524）等治理类问题仍被引用；PR 侧仅 1 条（<code>#4510</code> 移除 README 中的 Copilot CLI 文档，来自外部账户）。</p>
<h2>版本发布（今日）</h2>
<ul>
<li><strong><a href="https://github.com/github/copilot-cli/releases/tag/v1.0.81-6">v1.0.81-6</a></strong> — 新增 <code>defaultMode</code>/<code>defaultPermissionMode</code>（新交互会话的启动模式与审批行为）、<code>--with-token</code> 从 stdin 读取 auth token；ACP 客户端获得 subagent IDs、原始事件订阅、实时标题/模式/命令/计划更新；<code>/instructions</code> 分文件展示；managed settings 对 enabledPlugins/extraKnownMarketplaces 逐条胜出；Canvas 窗口后台打开刷新。</li>
<li>v1.0.81-5 / -4 / -3 / -2 — 官方标注 “Fixes and changes”。</li>
</ul>
<h2>社区热点 Issues（近 24h 活跃）</h2>
<ol>
<li><strong>#4535 <code>store_memory</code> 在 v1.0.81 prerelease 失败：<code>Instance id is required</code></strong>（开放）— 记忆持久化回归。</li>
<li><strong>#4524 沙箱禁止 copilot 使用 git</strong>（已关闭）— 沙箱策略误伤。</li>
<li><strong>#4103 插件 marketplace 克隆禁用 Git credential helpers，破坏私有 HTTPS 仓库</strong>（开放）— 非交互模式安全边界。</li>
<li><strong>#4540 <code>wta.exe</code> 启动失败 0x80070002：路径引号错位破坏 &quot;Program Files&quot;</strong>（开放）— Windows 路径处理。</li>
<li><strong>#4447 Backspace 一次删一个词</strong>（开放）— 终端输入体验。</li>
<li><strong>#4503 SDK server 未鉴权即报 ready，Slack 会话创建泛型失败</strong>（已关闭）。</li>
<li><strong>#4439 1.0.79 拒绝 GitLab MCP OAuth 元数据（RFC 8414 issuer 不匹配）</strong>（已关闭）。</li>
<li><strong>#4390 组织启用模型缺失（Claude Sonnet 5/Opus 5、Kimi K3）</strong>（已关闭，15💬）。</li>
<li><strong>#4096 第三方 MCP 显示 Connected 但工具缺失</strong>（已关闭）。</li>
<li><strong>#4206 内置 GitHub MCP 握手停滞时环境页卡在 Loading</strong>（已关闭）。</li>
</ol>
<h2>重要 PR 进展</h2>
<ul>
<li><strong>#4510 从 README 移除 GitHub Copilot CLI 文档</strong>（@prioritizedprotection086，开放）— 外部账户提交，疑似清理/更名动作。</li>
</ul>
<h2>功能需求趋势</h2>
<ul>
<li><strong>企业治理可控性</strong>：沙箱可彻底关闭、managed settings 生效范围、<code>store_memory</code> 可靠。</li>
<li><strong>MCP/ACP 稳定性</strong>：第三方 MCP 工具缺失、OAuth issuer 校验、SDK server 鉴权时序。</li>
<li><strong>Windows 路径与输入</strong>：<code>wta.exe</code> 引号、Backspace 行为。</li>
<li><strong>私有仓库友好</strong>：Git credential helpers 不被禁用。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>沙箱策略仍偏强制</strong>：显式禁用无效、误伤 git，是企业用户核心痛点。</li>
<li><strong><code>store_memory</code> 回归需尽快修复</strong>：记忆能力在 1.0.81 不可用。</li>
<li><strong>文档/命名清理</strong>：#4510 暗示文档或品牌调整。</li>
</ul>
</details>

<details>
<summary><strong>Kimi Code CLI</strong> — <a href="https://github.com/MoonshotAI/kimi-cli">MoonshotAI/kimi-cli</a></summary>

<h1>Kimi Code CLI 社区动态日报 2026-08-21</h1>
<h2>今日速览</h2>
<p>今日社区完全静默：issues、PRs、releases 均为 0。相较昨日仅有的 ACP Grep/Glob 限制问题（#2609，已关闭），今日无新增动态，生态仍处于早期静默期。</p>
<h2>版本发布</h2>
<p>今日无新版本发布。</p>
<h2>社区热点 Issues</h2>
<p>今日无更新。</p>
<h2>重要 PR 进展</h2>
<p>今日无更新。</p>
<h2>功能需求趋势</h2>
<p>基于连日低活跃度，社区当前重心可能在打通 ACP/IDE 基础链路与内部迭代，外部声量有限。</p>
<h2>开发者关注点</h2>
<ul>
<li>生态早期，活跃度在 7 个 CLI 中垫底；建议关注其 ACP runtime 工具能力边界的后续修复。</li>
</ul>
</details>

<details>
<summary><strong>OpenCode</strong> — <a href="https://github.com/anomalyco/opencode">anomalyco/opencode</a></summary>

<h1>OpenCode 社区动态日报 — 2026-08-21</h1>
<h2>今日速览</h2>
<p>发布 v1.18.19：新增 Cloudflare AI Gateway 的 OpenAI/Anthropic 原生透传、对齐 Codex 速率限制、移除会发送不支持设置的 Qwen 采样默认值、Go provider 启用 web 搜索等。社区侧 14 个 Issue 活跃，焦点延续 TUI 数据丢失级缺陷、subagent 中断流被记为干净停止（#37852，56👍）、gpt-5.6 兼容性、以及异步 sub-agent 委派（#5887，98👍）等长期诉求。PR 侧 12+ 更新，贡献者驱动特征明显。</p>
<h2>版本发布</h2>
<p><strong><a href="https://github.com/anomalyco/opencode/releases/tag/v1.18.19">v1.18.19</a></strong></p>
<ul>
<li>Core：新增 Cloudflare AI Gateway 模型的 OpenAI/Anthropic 原生透传；更贴近 ChatGPT 订阅限制地对齐 Codex 速率限制。</li>
<li>Bugfix：移除会发送不支持设置的 Qwen 采样默认值；<code>/connect</code> 正确展示已鉴权 provider；忽略畸形模型定价而非破坏用量计算；OpenAI websocket 超消息大小限制时回退；转发 ChatGPT workspace 计算驻留到 Codex 请求；更新账户连接默认 Console URL；Go provider 启用 web 搜索；兼容现有 v1 数据库。</li>
<li>Desktop：server 对话框中已保存的 server 详情可编辑。</li>
</ul>
<h2>社区热点 Issues（近 24h 活跃）</h2>
<ol>
<li><strong>#5887 真正的异步/后台 Sub-Agent 委派</strong>（98👍/26💬）— 长期高赞功能诉求。</li>
<li><strong>#37852 中断的 provider 流被记为干净停止（finish=unknown，零用量，无文本）</strong>（56👍/19💬）— subagent 用量统计失真。</li>
<li><strong>#11865 Codex/OpenAI 的 Tasks/Subagents 频繁卡死无超时/重试</strong>（19💬）— 可靠性。</li>
<li><strong>#27906 v1.15.1+ 破坏 Bun 安装</strong>（16💬）— 安装回归。</li>
<li><strong>#7006 <code>permission.ask</code> 插件 hook 已定义但不触发</strong>（23👬）— 权限钩子。</li>
<li><strong>#13626 Web UI 从 server 自动同步项目</strong>（26💬）— 项目同步。</li>
<li><strong>#11232 原生调度（Native Scheduling）</strong>（33💬，已关闭）— 已落地或被采纳。</li>
<li><strong>#10531 原生多模态上下文支持（视频/音频）</strong>（16💬，已关闭）。</li>
<li><strong>#25848 会话重命名</strong>（13💬）。</li>
<li><strong>#29462 Skills 工具无上限枚举所有 skill 进系统提示</strong>（12💬，已关闭）。</li>
</ol>
<h2>重要 PR 进展（近 24h）</h2>
<ol>
<li><strong>#40310 新增 llmgateway-providers provider</strong>（@smakosh）</li>
<li><strong>#43674 新增 QwenCloud International provider</strong>（@navegantesjr）</li>
<li><strong>#43574 配置的模型变体兜底</strong>（@rekram1-node）</li>
<li><strong>#43123 向模型暴露结构化内容（MCP）</strong>（@mcostasilva）</li>
<li><strong>#40857 实例查找前拒绝外部目录提示</strong>（@romanilyin）</li>
<li><strong>#43664 保留模型 ID 中斜杠以兼容 legacy server 解析</strong>（@StreamOfRon）</li>
<li><strong>#43665 从循环退出条件排除 &#39;unknown&#39; finish</strong>（@madebysaira）</li>
<li><strong>#41924 TUI 暴露剪贴板写入失败而非假成功</strong>（@aishangwuji）</li>
<li><strong>#43498 保留 Vertex Anthropic 工具续接</strong>（@major）</li>
<li><strong>#43695/#43690 Ox Alpha 免费模型 ID 文档对齐</strong>（@MrMushrooooom）</li>
</ol>
<h2>功能需求趋势</h2>
<ul>
<li><strong>可靠性优先</strong>：subagent 卡死/中断统计失真（#11865、#37852）是社区最高频痛点。</li>
<li><strong>provider 广度</strong>：llmgateway、QwenCloud、Vertex 等持续扩展。</li>
<li><strong>TUI 体验</strong>：剪贴板失败暴露（#41924）、项目自动同步（#13626）。</li>
<li><strong>多模态与调度</strong>：原生多模态（#10531）、原生调度（#11232）已被讨论并部分落地。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>用量统计可信度</strong>：中断流被记为干净停止直接污染计费与评测。</li>
<li><strong>安装与兼容性回归</strong>：Bun 安装（#27906）、模型 ID 斜杠解析（#43664）需谨慎。</li>
<li><strong>贡献者生态活跃</strong>：大量社区 PR 推动 provider 与 TUI 修复。</li>
</ul>
</details>

<details>
<summary><strong>Qwen Code</strong> — <a href="https://github.com/QwenLM/qwen-code">QwenLM/qwen-code</a></summary>

<h1>Qwen Code 社区动态日报 — 2026-08-21</h1>
<h2>今日速览</h2>
<p>发布 v0.21.15：Web Shell 支持文件附件插入、混合模型 Thinking 开关、<code>/review --resume</code>、鉴权 HTTPS Git 扩展安装、工具审批改为底部抽屉式。近 24h issue 侧无新增（0），但 PR 侧 12+ 更新，工业化 release/CI bot（<code>qwen-code-review-bot</code>）体系成熟。</p>
<h2>版本发布</h2>
<p><strong><a href="https://github.com/QwenLM/qwen-code/releases/tag/v0.21.15">v0.21.15</a></strong></p>
<ul>
<li>Web Shell 支持通过 composer 或 @ 选择插入文件附件，流式性能提升，侧边栏即时同步（<a href="https://github.com/QwenLM/qwen-code/pull/9405">#9405</a>、<a href="https://github.com/QwenLM/qwen-code/pull/9477">#9477</a>、<a href="https://github.com/QwenLM/qwen-code/pull/9570">#9570</a>、<a href="https://github.com/QwenLM/qwen-code/pull/9533">#9533</a>）。</li>
<li>Qwen 混合模型暴露简单 Thinking 开关，稳定版 qwen3.8-max 可在 <code>/model</code> 选择（<a href="https://github.com/QwenLM/qwen-code/pull/9574">#9574</a>、<a href="https://github.com/QwenLM/qwen-code/pull/9383">#9383</a>）。</li>
<li><code>--resume</code> 支持 <code>/review</code> 与 CI 重试，在 PR head 未移动时继续中断的审查（<a href="https://github.com/QwenLM/qwen-code/pull/9153">#9153</a>）。</li>
<li>支持鉴权 HTTPS Git 扩展安装，凭证持久化可配置（<a href="https://github.com/QwenLM/qwen-code/pull/9458">#9458</a>）。</li>
<li>工具审批/询问对话框改为与聊天宽度对齐的底部抽屉（<a href="https://github.com/QwenLM/qwen-code/pull/9351">#9351</a>）。</li>
<li>修复 <code>/rewind</code> 错误丢弃对话历史、重复 tool-call ID 导致执行错误（<a href="https://github.com/QwenLM/qwen-code/pull/9331">#9331</a>、<a href="https://github.com/QwenLM/qwen-code/pull/9436">#9436</a>）。</li>
</ul>
<h2>社区热点 Issues</h2>
<p>近 24h 无新 issue 进入窗口（stats 显示 0 条更新）。此前的活跃议题（Web Shell 剪贴板、ACP 多会话日志串扰、DingTalk 引用消息）已在昨日被修复 PR 跟进。</p>
<h2>重要 PR 进展（近 24h 精选）</h2>
<ol>
<li><strong>#9332 <code>/review</code> 一键导入扩宽合入 <code>fetch-pr --since</code></strong>（@wenshao）</li>
<li><strong>#9190 内容锚定的增量 review-fix 循环</strong>（@wenshao）</li>
<li><strong>#9513 恢复被 PR2A 身份收紧收窄的行为</strong>（@doudouOUC）</li>
<li><strong>#9500 同步已加载 skill 状态与历史驱逐</strong>（@ZijianZhang989）</li>
<li><strong>#9606 chore(release): v0.21.15</strong>（@qwen-code-review-bot）</li>
<li><strong>#9590 provider 感知的推理控制</strong>（@callmeYe）</li>
<li><strong>#7803 agent view roster UI</strong>（@ZijianZhang989）</li>
<li><strong>#9392 让 channel worker 可达 TLS 启用的 daemon</strong>（@qqqys）</li>
<li><strong>#9526 持续关键的收敛建议（land-with-residual-risk）</strong>（@wenshao）</li>
<li><strong>#9530 选择遗忘候选时不限扫描</strong>（@harjothkhara）</li>
<li><strong>#9577 release CI 禁用安装脚本并加固安全校验 workflow</strong>（@yiliang114）</li>
<li><strong>#9568 在 banner 标记预估压缩 token 数</strong>（@yiliang114）</li>
</ol>
<h2>功能需求趋势</h2>
<ul>
<li><strong>Web Shell 体验</strong>：文件附件、流式、侧边栏同步是前端主线。</li>
<li><strong>审查自动化</strong>：<code>/review</code> 增量循环、收敛建议、CI 重试。</li>
<li><strong>provider 与推理控制</strong>：混合模型 Thinking 开关、provider 感知推理。</li>
<li><strong>记忆与 skill 一致性</strong>：加载状态与历史驱逐同步（#9500）。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>工业化发布门禁</strong>：<code>qwen-code-review-bot</code> 驱动 v0.21.15，质量门禁高度自动化。</li>
<li><strong>路由身份绑定用量</strong>：此前 #9506 已落地，计费可信度提升。</li>
<li><strong>安全收紧后的行为补偿</strong>：#9513 恢复被身份收紧误伤的合法行为。</li>
</ul>
</details>

<hr>
<h2>Claude Code Skills 社区热点</h2>
<blockquote>
<p>数据来源: <a href="https://github.com/anthropics/skills">anthropics/skills</a> | 近 24h 活跃</p>
</blockquote>
<ul>
<li><strong>#1613 claude-api frontmatter description 超过 1024 字符限制</strong>（1💬，开放）— 技能元数据长度约束问题。</li>
<li><strong>#1616 修复 claude-api description 限制</strong>（@BRGOVIND，开放）— 对应 #1613 的修复 PR。</li>
<li><strong>#1615 新增 scnet-hpc skill</strong>（@lql341，开放）— HPC 场景技能。</li>
<li><strong>#1614 新增 web-security-audit skill</strong>（@cnbruce，开放）— Web 安全审计技能。</li>
<li><strong>#807 新增 x-twitter-scraper：X 数据 API 技能</strong>（@kriptoburak，已合并）— 社交媒体数据抓取技能。</li>
</ul>
<p>Skills 生态今日节奏平稳，以单点 bug 修复与新增技能为主，无大规模架构讨论。</p>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，所有内容基于 GitHub 公开 API 实时抓取并由执行代理人工撰写，未调用任何外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI CLI Tools Digest 2026-08-21</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-cli-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-cli-en</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate>
      <description>AI CLI Tools Community Daily Digest 2026-08-21 Generated: 2026-08-21 02:30 (GMT+8) | Coverage: 7 CLIs + Claude Code Skills This digest is produced by the agents-radar local automation. All summaries, comparisons and writing are done by the executing agent — no external LLM API is called. Claude Code OpenAI Codex Gemini CLI GitHub Copilot CLI Kimi Code CLI OpenCode Qwen Code Claude Code Skills Cross-Tool Comparison AI CLI Tools Cross-Tool Comparison Report (2026-08-21) 1. Ecosystem Overview AI CL...</description>
      <content:encoded><![CDATA[<h1>AI CLI Tools Community Daily Digest 2026-08-21</h1>
<blockquote>
<p>Generated: 2026-08-21 02:30 (GMT+8) | Coverage: 7 CLIs + Claude Code Skills
This digest is produced by the agents-radar local automation. All summaries, comparisons and writing are done by the executing agent — no external LLM API is called.</p>
</blockquote>
<ul>
<li><a href="https://github.com/anthropics/claude-code">Claude Code</a></li>
<li><a href="https://github.com/openai/codex">OpenAI Codex</a></li>
<li><a href="https://github.com/google-gemini/gemini-cli">Gemini CLI</a></li>
<li><a href="https://github.com/github/copilot-cli">GitHub Copilot CLI</a></li>
<li><a href="https://github.com/MoonshotAI/kimi-cli">Kimi Code CLI</a></li>
<li><a href="https://github.com/anomalyco/opencode">OpenCode</a></li>
<li><a href="https://github.com/QwenLM/qwen-code">Qwen Code</a></li>
<li><a href="https://github.com/anthropics/skills">Claude Code Skills</a></li>
</ul>
<hr>
<h2>Cross-Tool Comparison</h2>
<h1>AI CLI Tools Cross-Tool Comparison Report (2026-08-21)</h1>
<h2>1. Ecosystem Overview</h2>
<p>AI CLI tools have entered a &quot;daily-release&quot; competition: today Claude Code, OpenAI Codex, Gemini CLI, GitHub Copilot CLI, OpenCode and Qwen Code all shipped versions, with the surrounding ecosystem (IronClaw / EasyClaw / Moltis / CoPaw) releasing in sync. Community focus has shifted further from &quot;model capability&quot; to &quot;engineering trust and platform quality&quot; — Windows-quality issues (especially Codex), TUI interaction details, post-compaction memory persistence, and sandbox/permission least-trust boundaries are now common pain points across tools. A clear trend: <strong>automation bots are deeply involved in each tool&#39;s release quality gates</strong> (<code>copyberry[bot]</code> for Codex, <code>qwen-code-review-bot</code> for Qwen, <code>opencode-agent</code> for OpenCode), raising fix/release cadence while widening the voice gap between internal automation and external human contributors.</p>
<h2>2. Activity Comparison (last 24h)</h2>
<table>
<thead>
<tr>
<th>Tool</th>
<th>Active Issues</th>
<th>Notable PRs</th>
<th>Releases (today)</th>
</tr>
</thead>
<tbody><tr>
<td>Claude Code</td>
<td>12+ (high-upvote)</td>
<td>0</td>
<td>v2.1.236 / v2.1.237</td>
</tr>
<tr>
<td>OpenAI Codex</td>
<td>12 (Windows-led)</td>
<td>12+ (bot-driven)</td>
<td>rust-v0.149.0-alpha.4 / .3 / .2 / .1</td>
</tr>
<tr>
<td>Gemini CLI</td>
<td>16</td>
<td>12+</td>
<td>v0.56.0 (stable) / v0.57.0-preview.0</td>
</tr>
<tr>
<td>GitHub Copilot CLI</td>
<td>14+</td>
<td>1</td>
<td>v1.0.81-6 / -5 / -4 / -3 / -2</td>
</tr>
<tr>
<td>Kimi Code CLI</td>
<td>0</td>
<td>0</td>
<td>none</td>
</tr>
<tr>
<td>OpenCode</td>
<td>14</td>
<td>12+</td>
<td>v1.18.19</td>
</tr>
<tr>
<td>Qwen Code</td>
<td>0 (issues)</td>
<td>12+</td>
<td>v0.21.15</td>
</tr>
</tbody></table>
<h2>3. Shared Themes</h2>
<ul>
<li><strong>Windows / cross-platform quality</strong>: Codex Windows freeze (#20214, 86👍/107💬), standalone installer wish (#13993, 242👍), Trusted RPC browser-plugin failure (#39136); Copilot <code>wta.exe</code> quote bug (#4540) and sandbox blocking git (#4524); OpenCode <code>/tmp</code> leak and Sidecar timeout references. Windows is the #1 pain platform.</li>
<li><strong>TUI stability</strong>: Claude Code copy/paste indentation pollution (#18170, 287👍/134💬) remains the top complaint; OpenCode clipboard silent-failure fix (#41924) still open; Gemini scroll/render (#13107, #10673) and image drag-drop (#27855) recur.</li>
<li><strong>Context &amp; post-compaction memory</strong>: Claude Code user-built cross-compaction memory (#34556, 98💬); OpenCode &quot;aborted stream recorded as clean stop&quot; (#37852, 56👍) distorts subagent usage stats; Gemini subagent false GOAL success (#22323) still discussed.</li>
<li><strong>Permission / sandbox least-trust</strong>: Copilot over-aggressive sandbox (#4524), <code>store_memory</code> failure in 1.0.81 (#4535), non-interactive bypass of managed settings (#4103); Codex tightening Git-command trust and isolating plugin Git ops earn community approval.</li>
<li><strong>Model compatibility &amp; cost transparency</strong>: Codex GPT-5.6 serialization adds 27–45% weighted usage (#35050, 72👍); OpenCode gpt-5.6 param-injection/empty-response references persist; Qwen routing token-count fix (#9506) now binds routing identity.</li>
<li><strong>Automated release quality gates</strong>: Codex <code>copyberry[bot]</code> merged 12+ PRs today; Qwen <code>qwen-code-review-bot</code> shipped v0.21.15; OpenCode <code>opencode-agent</code> continuous — AI is deeply embedded in its own engineering.</li>
</ul>
<h2>4. Differentiation</h2>
<ul>
<li><strong>Claude Code</strong>: highest expectations, sharpest feedback; v2.1.237 adds &quot;Concise&quot; output style + prompt-caching fix; positions as the professional developer&#39;s daily terminal. PR side silent in 24h → stabilization phase.</li>
<li><strong>OpenAI Codex</strong>: Rust rewrite ongoing, bot-driven cadence; Windows quality &amp; desktop integration (Computer Use, browser plugin) are the biggest shortcomings; security direction (Git trust tightening, plugin isolation) approved.</li>
<li><strong>Gemini CLI</strong>: clean stable/preview split; PRs on security hardening (Cloud Workstations OAuth, IDE connection, env-change consent) and model onboarding (Gemini 3.6/3.7 Flash); mature-middle.</li>
<li><strong>GitHub Copilot CLI</strong>: strongest enterprise-governance context; v1.0.81-6 adds <code>defaultMode</code>/<code>defaultPermissionMode</code> and <code>--with-token</code>; positions as the managed Copilot entry point.</li>
<li><strong>Kimi Code CLI</strong>: zero activity today; early-silent stage.</li>
<li><strong>OpenCode</strong>: highly active community; v1.18.19 adds Cloudflare AI Gateway native passthrough, Codex rate-limit alignment, Go provider web search; pain in data-loss TUI defects and gpt-5.6 compat; positions for latest-model / customizable developers.</li>
<li><strong>Qwen Code</strong>: v0.21.15 strengthens Web Shell attachments, hybrid Thinking toggle, <code>/review --resume</code>, authenticated HTTPS Git extension installs; mature industrial release/CI bot system.</li>
</ul>
<h2>5. Notable Trend Signals</h2>
<ul>
<li><strong>Windows is an unsatisfied hard market</strong> — a differentiator for latecomers who treat Windows quality as first-class.</li>
<li><strong>TUI basics are a hard selection criterion</strong> — copy/paste, scroll, image drag-drop top the upvote charts; real-terminal testing should precede model-capability comparison.</li>
<li><strong>Memory persistence is the next watershed</strong> — retrievable + private + controllable history together builds long-term stickiness.</li>
<li><strong>Automated release gates are double-edged</strong> — faster fixes but diluted external human voice; demands stronger human-review mechanisms.</li>
<li><strong>Model behavior changes hit the bill directly</strong> — verify cost at small scale before large switches; require routing-identity-bound usage stats.</li>
</ul>
<hr>
<h2>Per-Tool Reports</h2>
<details>
<summary><strong>Claude Code</strong> — <a href="https://github.com/anthropics/claude-code">anthropics/claude-code</a></summary>

<h1>Claude Code Daily (2026-08-21)</h1>
<h2>Today</h2>
<ul>
<li>Shipped v2.1.237 and v2.1.236: v2.1.237 adds a built-in &quot;Concise&quot; output style and fixes prompt caching under custom base URLs; v2.1.236 adds <code>ANTHROPIC_DEFAULT_MODEL</code>, cross-session <code>notify_when_idle</code>, macOS sandbox wildcard read-deny hardening, and several render/session fixes.</li>
<li>Top community complaints: terminal copy/paste (#18170, 287👍/134💬), multi-account switching (#36151, 847👍), cross-compaction memory (#34556, 98💬).</li>
<li>PR side silent in 24h (0) — mainline in stabilization.</li>
</ul>
<h2>Releases</h2>
<p><strong>v2.1.237</strong> — Fixed prompt caching for sessions using an LLM gateway or custom base URL; added a built-in &quot;Concise&quot; output style (results-first, no preamble) selectable under <code>/config</code> → Output style.
<strong>v2.1.236</strong> — Added <code>ANTHROPIC_DEFAULT_MODEL</code> env var; <code>notify_when_idle</code> for cross-session <code>SendMessage</code>; macOS sandbox wildcard read-deny precedence; fixed clipboard/session/MCP breakage after dir removal, fullscreen renderer fallback, <code>/model</code> overflow, malformed tag rejection, WSL powershell unhandled rejections, fullscreen new-message refresh.</p>
<h2>Hot Issues (active 24h)</h2>
<ol>
<li>#6235 Support AGENTS.md (6335👍) 2. #36151 Multi-account switching (847👍) 3. #18170 Copy/paste indentation (287👍/134💬) 4. #84352 CVP-approved org still cyber-safeguard blocked (130💬) 5. #60705 /goal stop-hook as authorization (127💬) 6. #10199 API 400 thinking-block (65👍/100💬) 7. #34556 Persistent memory (98💬) 8. #4953 120GB memory leak OOM (75👍/97💬) 9. #32479 GitHub Connector not recognized (140👍/89💬) 10. #22543 Cowork 10GB VM (259👍/76💬) 11. #79337 Fable 5 usage-credit prompt (75💬) 12. #63875 Model tool-call unparseable (116👍/75💬).</li>
</ol>
</details>

<details>
<summary><strong>OpenAI Codex</strong> — <a href="https://github.com/openai/codex">openai/codex</a></summary>

<h1>OpenAI Codex Daily (2026-08-21)</h1>
<h2>Today</h2>
<ul>
<li>Released rust-v0.149.0-alpha.4 (+ .3/.2/.1), placeholder notes. Windows dominates community: App freeze (#20214, 86👍/107💬), standalone installer (#13993, 242👍), Trusted RPC browser-plugin failure (#39136, 82💬). <code>copyberry[bot]</code> merged 12+ PRs (model defs, unified exec, MCP event stream, permission-profile selection).</li>
</ul>
<h2>Releases</h2>
<p>rust-v0.149.0-alpha.4 / -alpha.3 / -alpha.2 / -alpha.1 (2026-08-19 ~ 08-20).</p>
<h2>Hot Issues</h2>
<ol>
<li>#20214 Windows freeze (86👍/107💬) 2. #28969 Disable 60s auto-resolve (201👍/83💬) 3. #39136 Trusted RPC browser-plugin fail (82💬) 4. #13993 Standalone Windows installer (242👍) 5. #39397 0.148 prompt_cache_retention on gpt-5.6-sol (41💬) 6. #30009 apply_patch windows sandbox (34💬) 7. #28507 Model at capacity (33💬) 8. #38455 Computer Use V8 OOM (32💬) 9. #25178 Windows Computer Use screenshot (28💬) 10. #39239 <code>\\?\</code> path archive fail (26💬) 11. #39162 macOS auth invalidation (25💬) 12. #35050 GPT-5.6 serialization +27–45% usage (72👍/25💬).</li>
</ol>
<h2>Recent PRs (<code>copyberry[bot]</code>-led)</h2>
<p>#39770 Refresh bundled model defs · #39765 suggestion IDs in plugin metadata · #39761 app-server MCP event streaming · #39757 unified exec · #39756 cache shell snapshots · #39755 managed dev instructions · #39752 uncompiled permission-profile selection · #39749 filesystem dir-walk backend · #39746 resumed thread capability roots · #39744 skip postprocessing short input · #39741 model-specific auto-review · #39738 Guardian runtime settings.</p>
</details>

<details>
<summary><strong>Gemini CLI</strong> — <a href="https://github.com/google-gemini/gemini-cli">google-gemini/gemini-cli</a></summary>

<h1>Gemini CLI Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>Shipped v0.56.0 (stable) and v0.57.0-preview.0. PRs on Cloud Workstations OAuth, IDE connection fix, env-change consent, Gemini 3.6/3.7 Flash onboarding, subagent false-success fix. Hot issues: public roadmap (#4191, 173👍), post-V1.0 work (#3132, 150👍), model availability (#28802, 40👍).</p>
<h2>Releases</h2>
<ul>
<li>v0.56.0 stable — <a href="https://github.com/google-gemini/gemini-cli/compare/v0.55.1...v0.56.0">compare v0.55.1...v0.56.0</a>.</li>
<li>v0.57.0-preview.0 — Cloud Workstations proxy redirect URI (#28688), IDE dir-mismatch fix (#28729), eval validation (#28344/#28305), context-aware silent retries (#28790), multi-turn rollback on cancel (#28801).</li>
</ul>
<h2>Hot Issues</h2>
<p>#4191 Roadmap (173👍) · #3132 Post-V1.0 (150👍/45💬) · #28802 Gemini 3.x Flash available (40👍/10💬) · #27393 configurable command-substitution wall (19💬) · #28052 trailing-dot URL load fail (14💬) · #22323 subagent false GOAL (12💬) · #21409 generalist hang (8💬) · #27855 terminal image drag-drop (8💬) · #19873 zero-dep OS sandbox (8💬) · #22745 AST-aware reads (7💬).</p>
<h2>Recent PRs</h2>
<p>#28932 Antigravity agent runner · #28915 symlink eval consistency · #28931 default stable channel docs · #28863 env-change consent · #28933 iterative orchestrator · #28867 block subagents when disabled · #28910 Gemini 3.7/3.6 Flash · #28828 preview-model substitution warning · #28926 Windows longpaths · #28917 Whisper atomic download.</p>
</details>

<details>
<summary><strong>GitHub Copilot CLI</strong> — <a href="https://github.com/github/copilot-cli">github/copilot-cli</a></summary>

<h1>GitHub Copilot CLI Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>Shipped v1.0.81-2 through -6. v1.0.81-6 adds <code>defaultMode</code>/<code>defaultPermissionMode</code>, <code>--with-token</code> login, ACP subagent IDs + live title/mode/command/plan updates, background Canvas. Community: <code>store_memory</code> fails in 1.0.81 (#4535), sandbox blocked git (#4524). Only 1 PR (#4510 removing Copilot CLI docs from README, external account).</p>
<h2>Releases</h2>
<p>v1.0.81-6 — <code>defaultMode</code>/<code>defaultPermissionMode</code>, <code>--with-token</code>; ACP client subagent IDs + event subscriptions + live metadata; <code>/instructions</code> per-file; managed settings win per-entry for enabledPlugins/extraKnownMarketplaces; Canvas opens in background. (-5/-4/-3/-2: &quot;Fixes and changes&quot;.)</p>
<h2>Hot Issues</h2>
<p>#4535 store_memory fails <code>Instance id required</code> · #4524 sandbox blocks git · #4103 marketplace clone disables Git credential helpers · #4540 wta.exe quote bug 0x80070002 · #4447 Backspace deletes words · #4503 SDK server ready-before-auth · #4439 GitLab MCP OAuth issuer mismatch · #4390 org models missing · #4096 third-party MCP tools missing · #4206 GitHub MCP handshake stall.</p>
<h2>Recent PRs</h2>
<p>#4510 Remove GitHub Copilot CLI docs from README (@prioritizedprotection086, open).</p>
</details>

<details>
<summary><strong>Kimi Code CLI</strong> — <a href="https://github.com/MoonshotAI/kimi-cli">MoonshotAI/kimi-cli</a></summary>

<h1>Kimi Code CLI Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>Completely silent: 0 issues, 0 PRs, 0 releases. Compared with yesterday&#39;s only ACP Grep/Glob limitation (#2609, closed), no new activity — ecosystem still in early silent stage.</p>
</details>

<details>
<summary><strong>OpenCode</strong> — <a href="https://github.com/anomalyco/opencode">anomalyco/opencode</a></summary>

<h1>OpenCode Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>Shipped v1.18.19: Cloudflare AI Gateway OpenAI/Anthropic native passthrough, Codex rate-limit alignment, removed Qwen sampling defaults that sent unsupported settings, Go provider web search. 14 active issues; focus on data-loss TUI defects, &quot;aborted stream recorded as clean stop&quot; (#37852, 56👍), gpt-5.6 compat, async sub-agent delegation (#5887, 98👍). 12+ PR updates.</p>
<h2>Release</h2>
<p>v1.18.19 — Gateway passthrough; rate-limit alignment; Qwen sampling default removal; <code>/connect</code> authed providers; malformed pricing ignored; OpenAI ws size fallback; ChatGPT workspace residency forwarded; Go provider web search; v1 DB compat. Desktop: editable saved server details.</p>
<h2>Hot Issues</h2>
<p>#5887 Async/background sub-agent delegation (98👍) · #37852 aborted stream as clean stop (56👍) · #11865 Tasks/Subagents stuck no timeout (19💬) · #27906 v1.15.1+ breaks Bun (16💬) · #7006 permission.ask hook not triggered (23👍) · #13626 auto-sync projects (26💬) · #11232 native scheduling (33💬) · #10531 native multimodal (16💬) · #25848 session rename · #29462 skills enumerated unbounded.</p>
<h2>Recent PRs</h2>
<p>#40310 llmgateway-providers · #43674 QwenCloud International · #43574 model variant fallbacks · #43123 structured content to models (MCP) · #40857 reject foreign dir hints · #43664 preserve slashes in model IDs · #43665 exclude &#39;unknown&#39; finish · #41924 surface clipboard failures · #43498 Vertex Anthropic continuations · #43695/#43690 Ox Alpha model docs.</p>
</details>

<details>
<summary><strong>Qwen Code</strong> — <a href="https://github.com/QwenLM/qwen-code">QwenLM/qwen-code</a></summary>

<h1>Qwen Code Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>Shipped v0.21.15: Web Shell file attachments, hybrid Thinking toggle, <code>/review --resume</code>, authenticated HTTPS Git extension installs, bottom-sheet tool approvals. 0 new issues in 24h window; 12+ PR updates; mature <code>qwen-code-review-bot</code> release system.</p>
<h2>Release</h2>
<p>v0.21.15 — Web Shell attachments + streaming + sidebar sync (#9405/#9477/#9570/#9533); hybrid Thinking toggle + qwen3.8-max in <code>/model</code> (#9574/#9383); <code>--resume</code> for <code>/review</code> &amp; CI retries (#9153); authenticated HTTPS Git extension installs (#9458); bottom-sheet approvals (#9351); <code>/rewind</code> history-drop &amp; duplicate tool-call ID fixes (#9331/#9436).</p>
<h2>Recent PRs</h2>
<p>#9332 fetch-pr --since widening · #9190 content-anchored review-fix loop · #9513 restore PR2A-narrowed behaviors · #9500 sync skill state with eviction · #9606 chore(release) v0.21.15 · #9590 provider-aware reasoning · #7803 agent view roster UI · #9392 TLS-enabled daemon reachability · #9526 convergence advisory · #9530 uncapped forget scan · #9577 release CI hardening · #9568 compression token banner.</p>
</details>

<hr>
<h2>Claude Code Skills Community Highlights</h2>
<blockquote>
<p>Source: <a href="https://github.com/anthropics/skills">anthropics/skills</a> | active 24h</p>
</blockquote>
<ul>
<li>#1613 claude-api frontmatter description exceeds 1024-char limit (open) — metadata length constraint.</li>
<li>#1616 Fix claude-api description limit (@BRGOVIND, open).</li>
<li>#1615 Add scnet-hpc skill (@lql341, open).</li>
<li>#1614 Add web-security-audit skill (@cnbruce, open).</li>
<li>#807 Add x-twitter-scraper skill (@kriptoburak, merged).</li>
</ul>
<p>Skills ecosystem calm today — single-point bug fixes and new skills, no large architectural debate.</p>
<hr>
<p><em>Generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. Data fetched live from GitHub public APIs and written by the executing agent — no external LLM used.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Agents 生态日报 2026-08-21</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-agents</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-agents</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate>
      <description>OpenClaw 生态社区动态日报 2026-08-21 生成时间: 2026-08-21 02:30 (GMT+8) | 覆盖: OpenClaw + 12 个 peer 项目 本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。 OpenClaw NanoBot Zeroclaw PicoClaw NanoClaw NullClaw IronClaw LobsterAI TinyClaw CoPaw Moltis ZeptoClaw EasyClaw 跨生态对比 OpenClaw 跨生态对比分析报告（2026-08-21） 1. 生态全景 OpenClaw 本体今日有 35 条 PR 更新、0 issue、0 release，主干聚焦鉴权一致性、记忆/wiki 上下文治理、Control UI 与 HTTP 边界；12 个 peer 中，NanoBot / Zeroclaw / IronClaw / CoPaw 贡献最活跃，NullClaw / TinyClaw / ZeptoClaw 完全静默。整体趋势从「单...</description>
      <content:encoded><![CDATA[<h1>OpenClaw 生态社区动态日报 2026-08-21</h1>
<blockquote>
<p>生成时间: 2026-08-21 02:30 (GMT+8) | 覆盖: OpenClaw + 12 个 peer 项目
本日报由 agents-radar 本地自动化生成，所有摘要/对比/撰写均由执行代理人工完成，未调用任何外部大模型 API。</p>
</blockquote>
<ul>
<li><a href="https://github.com/openclaw/openclaw">OpenClaw</a></li>
<li><a href="https://github.com/HKUDS/nanobot">NanoBot</a></li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw">Zeroclaw</a></li>
<li><a href="https://github.com/sipeed/picoclaw">PicoClaw</a></li>
<li><a href="https://github.com/nanocoai/nanoclaw">NanoClaw</a></li>
<li><a href="https://github.com/nullclaw/nullclaw">NullClaw</a></li>
<li><a href="https://github.com/nearai/ironclaw">IronClaw</a></li>
<li><a href="https://github.com/netease-youdao/LobsterAI">LobsterAI</a></li>
<li><a href="https://github.com/TinyAGI/tinyclaw">TinyClaw</a></li>
<li><a href="https://github.com/agentscope-ai/CoPaw">CoPaw</a></li>
<li><a href="https://github.com/moltis-org/moltis">Moltis</a></li>
<li><a href="https://github.com/qhkm/zeptoclaw">ZeptoClaw</a></li>
<li><a href="https://github.com/gaoyangz77/easyclaw">EasyClaw</a></li>
</ul>
<hr>
<h2>跨生态对比</h2>
<h1>OpenClaw 跨生态对比分析报告（2026-08-21）</h1>
<h2>1. 生态全景</h2>
<p>OpenClaw 本体今日有 35 条 PR 更新、0 issue、0 release，主干聚焦<strong>鉴权一致性、记忆/wiki 上下文治理、Control UI 与 HTTP 边界</strong>；12 个 peer 中，NanoBot / Zeroclaw / IronClaw / CoPaw 贡献最活跃，NullClaw / TinyClaw / ZeptoClaw 完全静默。整体趋势从「单 agent 聊天」走向<strong>多渠道（Telegram/Matrix/Slack/WhatsApp）+ 持久化记忆 + 自动化（automations/run-now）+ 企业级沙箱/鉴权</strong>。</p>
<h2>2. 各项目活跃度对比（近 24h）</h2>
<table>
<thead>
<tr>
<th>项目</th>
<th>Issues</th>
<th>PRs</th>
<th>Releases</th>
</tr>
</thead>
<tbody><tr>
<td>OpenClaw</td>
<td>0</td>
<td>35</td>
<td>—</td>
</tr>
<tr>
<td>NanoBot</td>
<td>4</td>
<td>29</td>
<td>—</td>
</tr>
<tr>
<td>Zeroclaw</td>
<td>3</td>
<td>35</td>
<td>—</td>
</tr>
<tr>
<td>PicoClaw</td>
<td>0</td>
<td>3</td>
<td>—</td>
</tr>
<tr>
<td>NanoClaw</td>
<td>1</td>
<td>35</td>
<td>—</td>
</tr>
<tr>
<td>NullClaw</td>
<td>0</td>
<td>0</td>
<td>—</td>
</tr>
<tr>
<td>IronClaw</td>
<td>1</td>
<td>35</td>
<td>v1.3.0</td>
</tr>
<tr>
<td>LobsterAI</td>
<td>2</td>
<td>7</td>
<td>—</td>
</tr>
<tr>
<td>TinyClaw</td>
<td>0</td>
<td>0</td>
<td>—</td>
</tr>
<tr>
<td>CoPaw</td>
<td>7</td>
<td>35</td>
<td>v2.1.1-beta.1</td>
</tr>
<tr>
<td>Moltis</td>
<td>1</td>
<td>6</td>
<td>20260820.01</td>
</tr>
<tr>
<td>ZeptoClaw</td>
<td>0</td>
<td>0</td>
<td>—</td>
</tr>
<tr>
<td>EasyClaw</td>
<td>0</td>
<td>0</td>
<td>v1.8.105~v1.8.101</td>
</tr>
</tbody></table>
<h2>3. 共同关注方向</h2>
<ul>
<li><strong>多渠道接入与消息可靠性</strong>：NanoBot（Telegram 贴纸回复 #5387、Matrix 错误日志 #5458、Slack 文件下载重定向 #5414）、NanoClaw（WhatsApp 媒体不可达 #2715、Slack agents #3421、Cursor SDK #3356）、Moltis（WhatsApp Markdown #1220、回复即寻址 #1217）。</li>
<li><strong>记忆与上下文治理</strong>：OpenClaw 防止超大 wiki 内容挤占上下文（#126779）、记忆导入失败暴露（#126738）；IronClaw AfterTurn 记忆策展（#7765）；CoPaw ReMe 记忆运行时看板（#6984）、PowerContext 长期记忆（#7080）。</li>
<li><strong>自动化与企业级</strong>：IronClaw 结构化 automations + 每用户沙箱代理（#7732/#7779）、可执行 run gate 通知（#7699）；CoPaw 自托管多用户 Hub（#7112）。</li>
<li><strong>安全加固</strong>：Moltis 修复 Vault 解锁/恢复缺失鉴权（#1216，CWE-306）、CoPaw master key 仅属主权限（#7119）。</li>
<li><strong>上下文压缩与配额</strong>：Zeroclaw 上下文压缩锚定模型窗口比（#9535）、运行时上下文耗尽终端提示（#9504）；NanoClaw token 用量（#3270）。</li>
</ul>
<h2>4. 差异化定位</h2>
<ul>
<li><strong>OpenClaw</strong>：生态中枢，主攻 Control UI / 鉴权 / 记忆 wiki / HTTP 边界，企业受管语境。</li>
<li><strong>NanoBot</strong>：渠道最广（Telegram/Matrix/Slack/WebUI），重渠道健壮性与网关日志。</li>
<li><strong>Zeroclaw</strong>：Rust 核心，RFC 驱动「更轻核心 + 外部集成」，上下文压缩与 telemetry 治理。</li>
<li><strong>NanoClaw</strong>：多 provider 接入（WhatsApp/Slack/Cursor/Codex），强调 token 用量与挂载。</li>
<li><strong>IronClaw</strong>：每用户沙箱 + 结构化 automations + 文档编辑 + Telegram 关联设备，企业/团队向。</li>
<li><strong>LobsterAI</strong>：cowork 文件卡片/分屏预览、设置面板搜索，体验向。</li>
<li><strong>CoPaw (QwenPaw)</strong>：记忆 ReMe、自托管 Hub、控制台性能，社区活跃度最高之一。</li>
<li><strong>Moltis</strong>：WhatsApp 为中心，重渠道安全（Vault 鉴权）。</li>
<li><strong>EasyClaw (rivonclaw)</strong>：高频小版本（每日多版），商务开发筛选等垂直功能。</li>
<li><strong>PicoClaw / NullClaw / TinyClaw / ZeptoClaw</strong>：低活跃或静默。</li>
</ul>
<h2>5. 趋势信号</h2>
<ul>
<li><strong>静默项目需关注</strong>：NullClaw / TinyClaw / ZeptoClaw 连续多日 0 动态，生态健康度分化。</li>
<li><strong>自动化 becoming first-class</strong>：IronClaw/CoPaw 的 automations/run-now/Hub 标志着 agent 从「对话」走向「可编排任务」。</li>
<li><strong>安全从可选到必需</strong>：Vault 鉴权缺失（CWE-306）、master key 权限、MCP 凭证保留成为高频修复。</li>
<li><strong>记忆是跨项目主线</strong>：从 OpenClaw wiki 到 IronClaw/CoPaw 记忆系统，持久化记忆是 2026 年 agent 框架的竞争焦点。</li>
</ul>
<hr>
<h2>各项目详细动态</h2>
<details>
<summary><strong>OpenClaw</strong> — <a href="https://github.com/openclaw/openclaw">openclaw/openclaw</a></summary>

<h1>OpenClaw 社区动态日报（2026-08-21）</h1>
<h2>今日速览</h2>
<p>35 条 PR 更新，0 issue，无 release。重点：Codex 鉴权身份跨重启保持（#126777）、记忆 wiki 防止超大内容挤占上下文（#126779）、UI 内存导入失败暴露（#126738）、HTTP 聊天在 tools.profile 最小时仍发全量系统提示的修正（#126619）、Control UI 模型 thinking 级别自动补全（#123507）。</p>
<h2>重要 PR（精选）</h2>
<ul>
<li>#126777 fix(qa): 跨重启保持 Codex 鉴权身份</li>
<li>#120301 fix(ui): Model Providers 用量卡片在 usage.status 失败后保持为空</li>
<li>#122431 fix(media): 理解前先缩放图片</li>
<li>#123507 fix(control-ui): 自动补全模型 thinking 级别</li>
<li>#126779 fix(memory-wiki): 防止超大 wiki 内容挤占模型上下文</li>
<li>#126738 fix(ui): 暴露 onboarding 记忆导入加载失败</li>
<li>#120900 feat(ui): 审查安装策略警告</li>
<li>#126619 fix: HTTP 聊天在 tools.profile 最小时仍发全量系统提示</li>
<li>#126782 fix(qa-lab): HTTP 边界接受直消息别名</li>
<li>#126783 fix(auth): 以规范共享鉴权所有权创建全新安装</li>
<li>#125471 fix(models): Control UI 保留 Claude CLI OAuth</li>
<li>#123535 fix(ui): 避免会话目录刷新风暴</li>
</ul>
</details>

<details>
<summary><strong>NanoBot</strong> — <a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a></summary>

<h1>NanoBot 社区动态日报（2026-08-21）</h1>
<h2>今日速览</h2>
<p>4 issue、29 PR。渠道健壮性是主线：Telegram 贴纸回复、Matrix 错误日志、Slack 文件下载重定向、网关子进程输出冲刷。</p>
<h2>社区热点 Issues</h2>
<ul>
<li>#5444 Docker 内通过 OAuth 登录 OpenAI 失败</li>
<li>#5425 支持 legacy socks:// 代理 URL（已关闭）</li>
<li>#5454 流式 provider 中段 server_error 在内容已流出后跳过重试</li>
<li>#5447 付费安全扫描 MCP 集成（nanobot + ScanPay x402）</li>
</ul>
<h2>重要 PR（精选）</h2>
<ul>
<li>#5387 feat(telegram): 可复用贴纸回复</li>
<li>#5379 fix(memory): 保留完整 consolidation 输入</li>
<li>#5420 feat(webui): 回合可观测性与安全恢复</li>
<li>#5458 fix(matrix): 插值错误日志上下文</li>
<li>#5456 chore(deps): 移除 websocket-client，加 certifi</li>
<li>#5414 fix(slack): 跨重定向校验文件下载</li>
<li>#5413 fix(providers): 对抛错应用 fallback 策略</li>
<li>#5412 fix(gateway): 冲刷后台子进程输出到日志</li>
<li>#5339 fix(webui): 拒绝丢弃的临时聊天消息</li>
<li>#5338 fix(mcp): 源失败保留凭证</li>
</ul>
</details>

<details>
<summary><strong>Zeroclaw</strong> — <a href="https://github.com/zeroclaw-labs/zeroclaw">zeroclaw-labs/zeroclaw</a></summary>

<h1>Zeroclaw 社区动态日报（2026-08-21）</h1>
<h2>今日速览</h2>
<p>3 issue（均为 RFC/tracker）、35 PR。RFC 指向「更轻核心 + 外部集成」与运行时会话/传输适配器；工程侧聚焦 web_fetch 解压、ACP 转录持久化、上下文压缩锚定窗口比、telemetry 退役。</p>
<h2>社区热点 Issues</h2>
<ul>
<li>#9487 RFC: 运行时拥有的会话与传输表面适配器（21💬）</li>
<li>#6165 RFC: 通过外部集成偏好更轻的 ZeroClaw 核心（18💬）</li>
<li>#10118 [Tracker]: Rust anti-slop 策略债清理（16💬）</li>
</ul>
<h2>重要 PR（精选）</h2>
<ul>
<li>#9283 fix(tools): web_fetch 响应 gzip/brotli/deflate 解压</li>
<li>#9378 fix(acp): 持久化失败/取消的回合转录</li>
<li>#9379 fix(runtime): 上下文 token 估算计入图片标记</li>
<li>#9447 fix(anthropic): 分类不完整的终端响应</li>
<li>#9451 refactor(observability)!: 退役休眠的 DORA telemetry</li>
<li>#9504 fix(runtime): 上下文耗尽时终端提示</li>
<li>#9535 feat(runtime): 上下文压缩锚定模型窗口比</li>
<li>#9557 feat(providers): ProviderErrorKind 分类</li>
<li>#9561 fix(personality): 渲染人格提示移除文件名标签</li>
</ul>
</details>

<details>
<summary><strong>NanoClaw</strong> — <a href="https://github.com/nanocoai/nanoclaw">nanocoai/nanoclaw</a></summary>

<h1>NanoClaw 社区动态日报（2026-08-21）</h1>
<h2>今日速览</h2>
<p>1 issue、35 PR。多渠道接入（WhatsApp/Slack/Cursor/Codex）与 token 用量是主线；#2715 报告 WhatsApp 入站媒体因挂载点不可达而无法被 agent 访问。</p>
<h2>社区热点 Issues</h2>
<ul>
<li>#2715 入站 WhatsApp 媒体（图片/文档/音频）agent 不可达，文件存到未挂载路径</li>
</ul>
<h2>重要 PR（精选）</h2>
<ul>
<li>#3270 Feat/ncl token usage</li>
<li>#3189 feat(skill): add-why — 解释某条消息发生了什么</li>
<li>#3196 Fix/add mount readonly</li>
<li>#3403 [main] fix(matrix): ESM patch 刷新时可执行</li>
<li>#3402 [main] fix(codex): 交付 provider 生成的文件</li>
<li>#3421 [channels] 宣布一键 Slack agents</li>
<li>#3401 fix(whatsapp-cloud): skill payload 兼容 main</li>
<li>#3356 feat(providers): Cursor Agent SDK payload</li>
<li>#3355 feat(setup): /add-cursor agent provider skill</li>
<li>#3420 fix(add-macos-statusbar): Swift 代码与 plist 标签 slug 感知</li>
<li>#3419 fix(add-anydoc): 安装作用域 ncl、可移植 skill 测试</li>
</ul>
</details>

<details>
<summary><strong>IronClaw</strong> — <a href="https://github.com/nearai/ironclaw">nearai/ironclaw</a></summary>

<h1>IronClaw 社区动态日报（2026-08-21）</h1>
<h2>今日速览</h2>
<p>发布 v1.3.0（稳定晋升 1.3.0-rc.2）。每用户沙箱 + 结构化 automations + 文档编辑 + Telegram 关联设备是核心新增。1 issue（#7732 持久每用户沙箱 epic，8💬）。</p>
<h2>版本发布</h2>
<p><strong><a href="https://github.com/nearai/ironclaw/releases/tag/ironclaw-v1.3.0">ironclaw-v1.3.0</a></strong> — 修复 1.2 升级崩溃循环、Reborn 运行时镜像可选公钥 SSH；新增每用户模型偏好、结构化 automations（失败关闭预检）、文档编辑（.docx/.xlsx/.pptx 结构编辑 + HTML 渲染 PDF）、Telegram 关联设备。</p>
<h2>社区热点 Issues</h2>
<ul>
<li>#7732 Epic: 持久每用户沙箱 + iron-proxy；延迟循环执行器（8💬）</li>
</ul>
<h2>重要 PR（精选）</h2>
<ul>
<li>#7765 feat(hooks): AfterTurn 生命周期点 + 记忆策展</li>
<li>#7779 feat(sandbox): 用户沙箱出口经受管每用户代理</li>
<li>#7491 feat(coding): omp core-tool 契约 + 引擎 + 基准臂</li>
<li>#7777 refactor(webui): 移除重复 Settings/Extensions 标签</li>
<li>#7763 refactor(subagent): 七份设计文档合并为一份 README</li>
<li>#7766 fix(telegram): 分离 bot 配对与个人账户关联</li>
<li>#7729 feat(automations): 跨触发域与 WebUI 的 run-now</li>
<li>#7699 feat(notifications): 发布可执行的 run gate</li>
<li>#7778 fix(lints): Rust 1.98 clippy 迁移</li>
</ul>
</details>

<details>
<summary><strong>LobsterAI</strong> — <a href="https://github.com/netease-youdao/LobsterAI">netease-youdao/LobsterAI</a></summary>

<h1>LobsterAI 社区动态日报（2026-08-21）</h1>
<h2>今日速览</h2>
<p>2 issue、7 PR。cowork 文件卡片/分屏预览、设置面板搜索、定时任务通知渠道修复是主线。</p>
<h2>社区热点 Issues</h2>
<ul>
<li>#1556 文档 bug：IM 机器人配置指南 404</li>
<li>#1552 feat: AI 产物 Markdown 预览及文件卡片支持</li>
</ul>
<h2>重要 PR（精选）</h2>
<ul>
<li>#1545 fix(agent): 更新当前 agent skills 时立即同步 activeSkillIds</li>
<li>#1546 feat(engine-overlay): 引擎启动超时后显示取消启动与查看日志按钮</li>
<li>#1547 fix(scheduledTask): 修复定时任务通知渠道选回&quot;不通知&quot;失败</li>
<li>#1553 feat(cowork): Write 工具文件卡片及分屏预览面板</li>
<li>#1555 fix: npm run dist:mac:x64 打包失败</li>
<li>#1557 feat(settings): 设置面板侧栏支持搜索筛选分类</li>
<li>#1560 fix: 修复 Agent 编辑后点击原 Agent 无法切回聊天界面</li>
</ul>
</details>

<details>
<summary><strong>CoPaw</strong> — <a href="https://github.com/agentscope-ai/CoPaw">agentscope-ai/CoPaw</a></summary>

<h1>CoPaw (QwenPaw) 社区动态日报（2026-08-21）</h1>
<h2>今日速览</h2>
<p>发布 v2.1.1-beta.1。7 issue、35 PR。记忆 ReMe 运行时看板、自托管多用户 Hub、控制台性能、统一工具面板是主线。</p>
<h2>版本发布</h2>
<p><strong><a href="https://github.com/agentscope-ai/QwenPaw/releases/tag/v2.1.1-beta.1">v2.1.1-beta.1</a></strong> — 编辑器标签溢出导航、provider 限流器日志级别、ReMe 运行时看板、插件渠道交互配置器、OneBot 入站媒体本地化、后台任务超时、插件重载工作区状态、历史消息 data-URL 图片渲染、DataPaw 原生运行时等。</p>
<h2>社区热点 Issues</h2>
<ul>
<li>#6921 常在「Now 2.1, 3.1, 3.2」类输出后无提示停止，需说&quot;继续&quot;才继续</li>
<li>#7102 冻结超过 10 分钟</li>
<li>#6643 任务产出物不要堆积在 media 目录，应按任务建目录</li>
<li>#6826 对话中助手消息结束时间显示异常</li>
<li>#6436 每消息自动模型路由</li>
<li>#7110 含不可下载图片链接的上下文使整个会话不可用</li>
<li>#7013 为 Chat 增加统一工具面板、Web 服务预览与交互式终端</li>
</ul>
<h2>重要 PR（精选）</h2>
<ul>
<li>#7119 fix(security): master key 文件仅属主权限</li>
<li>#7061 fix(video): OpenAI Responses API 交付工具结果视频</li>
<li>#7175 fix(console): 恢复完整免费模型列表</li>
<li>#7183 feat(skills): 工作区作用域常驻加载</li>
<li>#7167 feat(creator): 对话门控视频分发、项目复制与重建、效果库扩展</li>
<li>#7133 feat(memory): 更新 reme 0.4.1.8</li>
<li>#7112 feat(hub): 自托管多用户 Hub（本地与 Docker 运行时）</li>
<li>#7080 feat: 可选 PowerContext 可插拔长期记忆后端</li>
<li>#7161 feat(console): 助手响应卡片加 artifacts</li>
<li>#7176 perf(console): 长会话保持响应</li>
</ul>
</details>

<details>
<summary><strong>Moltis</strong> — <a href="https://github.com/moltis-org/moltis">moltis-org/moltis</a></summary>

<h1>Moltis 社区动态日报（2026-08-21）</h1>
<h2>今日速览</h2>
<p>发布 20260820.01。1 issue（Vault 解锁/恢复缺失鉴权，CWE-306）、6 PR。渠道安全与 WhatsApp 体验是主线。</p>
<h2>版本发布</h2>
<p><strong><a href="https://github.com/moltis-org/moltis/releases/tag/20260820.01">20260820.01</a></strong></p>
<h2>社区热点 Issues</h2>
<ul>
<li>#1177 [Bug]: Vault 解锁/恢复端点缺失鉴权（CWE-306）</li>
</ul>
<h2>重要 PR（精选）</h2>
<ul>
<li>#1220 fix(whatsapp): 出站消息渲染 Markdown</li>
<li>#468 fix(plugins): Windows 上 shell hooks 用 cmd.exe</li>
<li>#1218 fix(channels): 停止把 push name 硬编码为 &quot;Moltis&quot;</li>
<li>#1219 fix(channels): 不可信回合工具上限可配置</li>
<li>#1217 fix(whatsapp): 把对 bot 的回复视为寻址它</li>
<li>#1216 fix(httpd): Vault 解锁与恢复要求鉴权</li>
</ul>
</details>

<details>
<summary><strong>EasyClaw</strong> — <a href="https://github.com/gaoyangz77/easyclaw">gaoyangz77/easyclaw (rivonclaw)</a></summary>

<h1>EasyClaw (rivonclaw) 社区动态日报（2026-08-21）</h1>
<h2>今日速览</h2>
<p>0 issue、0 PR，但连续发布 v1.8.101~v1.8.105（每日多版）。v1.8.105 支持按商务开发人员筛选达人 Agent 的待审核与全部工作。</p>
<h2>版本发布</h2>
<ul>
<li><a href="https://github.com/gaoyangz77/rivonclaw/releases/tag/v1.8.105">v1.8.105</a> — 按商务开发人员筛选达人 Agent 工作</li>
<li>v1.8.104 / v1.8.103 / v1.8.102 / v1.8.101</li>
</ul>
</details>

<details>
<summary><strong>PicoClaw / NullClaw / TinyClaw / ZeptoClaw</strong></summary>

<h1>低活跃 / 静默项目（2026-08-21）</h1>
<ul>
<li><strong>PicoClaw</strong> (#3329 惰性 webhook_host/port 告警；#3316 routed-agent 上下文管理；#3315 私聊话题) — 3 PR，轻量更新。</li>
<li><strong>NullClaw</strong> — 0 issue / 0 PR / 0 release，完全静默。</li>
<li><strong>TinyClaw</strong> — 0 issue / 0 PR / 0 release，完全静默。</li>
<li><strong>ZeptoClaw</strong> — 0 issue / 0 PR / 0 release，完全静默。</li>
</ul>
<p>这四个项目今日无社区动态，生态活跃度分化明显。</p>
</details>

<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，数据来自 GitHub 公开 API，由执行代理人工撰写，未调用外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Agents Ecosystem Digest 2026-08-21</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-agents-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-agents-en</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate>
      <description>OpenClaw Ecosystem Community Daily Digest 2026-08-21 Generated: 2026-08-21 02:30 (GMT+8) | Coverage: OpenClaw + 12 peer projects This digest is produced by the agents-radar local automation. All summaries, comparisons and writing are done by the executing agent — no external LLM API is called. OpenClaw NanoBot Zeroclaw PicoClaw NanoClaw NullClaw IronClaw LobsterAI TinyClaw CoPaw Moltis ZeptoClaw EasyClaw Cross-Ecosystem Comparison OpenClaw Cross-Ecosystem Comparison (2026-08-21) 1. Ecosystem Ove...</description>
      <content:encoded><![CDATA[<h1>OpenClaw Ecosystem Community Daily Digest 2026-08-21</h1>
<blockquote>
<p>Generated: 2026-08-21 02:30 (GMT+8) | Coverage: OpenClaw + 12 peer projects
This digest is produced by the agents-radar local automation. All summaries, comparisons and writing are done by the executing agent — no external LLM API is called.</p>
</blockquote>
<ul>
<li><a href="https://github.com/openclaw/openclaw">OpenClaw</a></li>
<li><a href="https://github.com/HKUDS/nanobot">NanoBot</a></li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw">Zeroclaw</a></li>
<li><a href="https://github.com/sipeed/picoclaw">PicoClaw</a></li>
<li><a href="https://github.com/nanocoai/nanoclaw">NanoClaw</a></li>
<li><a href="https://github.com/nullclaw/nullclaw">NullClaw</a></li>
<li><a href="https://github.com/nearai/ironclaw">IronClaw</a></li>
<li><a href="https://github.com/netease-youdao/LobsterAI">LobsterAI</a></li>
<li><a href="https://github.com/TinyAGI/tinyclaw">TinyClaw</a></li>
<li><a href="https://github.com/agentscope-ai/CoPaw">CoPaw</a></li>
<li><a href="https://github.com/moltis-org/moltis">Moltis</a></li>
<li><a href="https://github.com/qhkm/zeptoclaw">ZeptoClaw</a></li>
<li><a href="https://github.com/gaoyangz77/easyclaw">EasyClaw</a></li>
</ul>
<hr>
<h2>Cross-Ecosystem Comparison</h2>
<h1>OpenClaw Cross-Ecosystem Comparison (2026-08-21)</h1>
<h2>1. Ecosystem Overview</h2>
<p>OpenClaw core shipped 35 PR updates, 0 issues, 0 release — mainline focuses on <strong>auth consistency, memory/wiki context governance, Control UI and HTTP boundaries</strong>. Among 12 peers, NanoBot / Zeroclaw / IronClaw / CoPaw are most active; NullClaw / TinyClaw / ZeptoClaw are completely silent. The overall trajectory moves from &quot;single-agent chat&quot; to <strong>multi-channel (Telegram/Matrix/Slack/WhatsApp) + persistent memory + automation (automations/run-now) + enterprise sandbox/auth</strong>.</p>
<h2>2. Activity Comparison (last 24h)</h2>
<table>
<thead>
<tr>
<th>Project</th>
<th>Issues</th>
<th>PRs</th>
<th>Releases</th>
</tr>
</thead>
<tbody><tr>
<td>OpenClaw</td>
<td>0</td>
<td>35</td>
<td>—</td>
</tr>
<tr>
<td>NanoBot</td>
<td>4</td>
<td>29</td>
<td>—</td>
</tr>
<tr>
<td>Zeroclaw</td>
<td>3</td>
<td>35</td>
<td>—</td>
</tr>
<tr>
<td>PicoClaw</td>
<td>0</td>
<td>3</td>
<td>—</td>
</tr>
<tr>
<td>NanoClaw</td>
<td>1</td>
<td>35</td>
<td>—</td>
</tr>
<tr>
<td>NullClaw</td>
<td>0</td>
<td>0</td>
<td>—</td>
</tr>
<tr>
<td>IronClaw</td>
<td>1</td>
<td>35</td>
<td>v1.3.0</td>
</tr>
<tr>
<td>LobsterAI</td>
<td>2</td>
<td>7</td>
<td>—</td>
</tr>
<tr>
<td>TinyClaw</td>
<td>0</td>
<td>0</td>
<td>—</td>
</tr>
<tr>
<td>CoPaw</td>
<td>7</td>
<td>35</td>
<td>v2.1.1-beta.1</td>
</tr>
<tr>
<td>Moltis</td>
<td>1</td>
<td>6</td>
<td>20260820.01</td>
</tr>
<tr>
<td>ZeptoClaw</td>
<td>0</td>
<td>0</td>
<td>—</td>
</tr>
<tr>
<td>EasyClaw</td>
<td>0</td>
<td>0</td>
<td>v1.8.105~v1.8.101</td>
</tr>
</tbody></table>
<h2>3. Shared Themes</h2>
<ul>
<li><strong>Multi-channel reliability</strong>: NanoBot (Telegram stickers #5387, Matrix error logs #5458, Slack redirect #5414), NanoClaw (WhatsApp media unreachable #2715, Slack agents #3421, Cursor SDK #3356), Moltis (WhatsApp Markdown #1220, reply-as-address #1217).</li>
<li><strong>Memory &amp; context governance</strong>: OpenClaw oversized-wiki crowding fix (#126779), import-failure surfacing (#126738); IronClaw AfterTurn memory curation (#7765); CoPaw ReMe runtime dashboard (#6984), PowerContext LTM (#7080).</li>
<li><strong>Automation &amp; enterprise</strong>: IronClaw structured automations + per-user sandbox proxy (#7732/#7779), executable run-gate notifications (#7699); CoPaw self-hosted multi-user Hub (#7112).</li>
<li><strong>Security hardening</strong>: Moltis Vault unlock/recovery auth fix (#1216, CWE-306); CoPaw master-key owner-only perms (#7119).</li>
<li><strong>Context compaction &amp; quota</strong>: Zeroclaw window-ratio anchoring (#9535), context-exhaustion terminal notice (#9504); NanoClaw token usage (#3270).</li>
</ul>
<h2>4. Differentiation</h2>
<ul>
<li><strong>OpenClaw</strong>: ecosystem hub — Control UI / auth / memory-wiki / HTTP boundary, enterprise-managed context.</li>
<li><strong>NanoBot</strong>: widest channels (Telegram/Matrix/Slack/WebUI), channel robustness &amp; gateway logs.</li>
<li><strong>Zeroclaw</strong>: Rust core, RFC-driven &quot;lighter core + external integrations&quot;, context compaction &amp; telemetry governance.</li>
<li><strong>NanoClaw</strong>: multi-provider onboarding (WhatsApp/Slack/Cursor/Codex), token usage &amp; mounts.</li>
<li><strong>IronClaw</strong>: per-user sandbox + structured automations + doc editing + Telegram linked devices, team/enterprise-leaning.</li>
<li><strong>LobsterAI</strong>: cowork file cards / split preview, settings search, experience-focused.</li>
<li><strong>CoPaw (QwenPaw)</strong>: ReMe memory, self-hosted Hub, console perf — among the most active communities.</li>
<li><strong>Moltis</strong>: WhatsApp-centric, channel security (Vault auth).</li>
<li><strong>EasyClaw (rivonclaw)</strong>: high-frequency point releases (multiple/day), vertical features (BD-agent filtering).</li>
<li><strong>PicoClaw / NullClaw / TinyClaw / ZeptoClaw</strong>: low-activity or silent.</li>
</ul>
<h2>5. Trend Signals</h2>
<ul>
<li><strong>Silent projects need attention</strong>: NullClaw / TinyClaw / ZeptoClaw at 0 activity for multiple days — ecosystem health is diverging.</li>
<li><strong>Automation becomes first-class</strong>: IronClaw/CoPaw automations/run-now/Hub signal agents moving from &quot;chat&quot; to &quot;orchestrated tasks&quot;.</li>
<li><strong>Security from optional to mandatory</strong>: Vault auth gaps (CWE-306), master-key perms, MCP credential retention are frequent fixes.</li>
<li><strong>Memory is the cross-project main line</strong>: from OpenClaw wiki to IronClaw/CoPaw memory systems, persistent memory is the 2026 agent-framework battleground.</li>
</ul>
<hr>
<h2>Per-Project Details</h2>
<details>
<summary><strong>OpenClaw</strong> — <a href="https://github.com/openclaw/openclaw">openclaw/openclaw</a></summary>

<h1>OpenClaw Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>35 PR updates, 0 issues, no release. Highlights: preserve Codex auth identity across restarts (#126777), prevent oversized wiki content crowding context (#126779), surface onboarding memory-import failures (#126738), and fix HTTP chat sending full system prompt when tools.profile is minimal (#126619); Control UI model thinking-level autocomplete (#123507).</p>
<h2>Notable PRs</h2>
<p>#126777 fix(qa): preserve Codex auth identity across restarts · #120301 fix(ui): Model Providers usage cards stay empty after failed usage.status · #122431 fix(media): resize images before understanding · #123507 fix(control-ui): autocomplete model thinking levels · #126779 fix(memory-wiki): prevent oversized wiki crowding context · #126738 fix(ui): surface onboarding memory import failures · #120900 feat(ui): review install policy warnings · #126619 fix: HTTP chat sends full system prompt when tools.profile minimal · #126782 fix(qa-lab): accept DM aliases at HTTP boundary · #126783 fix(auth): fresh install with canonical shared-auth ownership · #125471 fix(models): keep Claude CLI OAuth in Control UI · #123535 fix(ui): avoid session catalog refresh storms.</p>
</details>

<details>
<summary><strong>NanoBot</strong> — <a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a></summary>

<h1>NanoBot Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>4 issues, 29 PRs. Channel robustness is the main line: Telegram sticker replies, Matrix error logs, Slack file-download redirects, gateway child-output flushing.</p>
<h2>Hot Issues</h2>
<p>#5444 OAuth login to OpenAI fails in Docker · #5425 legacy socks:// proxy support (closed) · #5454 streaming mid-stream server_error skips retry after content streamed · #5447 paid security-scan MCP (nanobot + ScanPay x402).</p>
<h2>Notable PRs</h2>
<p>#5387 feat(telegram): reusable sticker replies · #5379 fix(memory): preserve full consolidation input · #5420 feat(webui): turn observability &amp; safe recovery · #5458 fix(matrix): interpolate error log context · #5456 chore(deps): drop websocket-client, add certifi · #5414 fix(slack): validate file downloads across redirects · #5413 fix(providers): apply fallback to raised errors · #5412 fix(gateway): flush background child output to logs · #5339 fix(webui): reject discarded temp messages · #5338 fix(mcp): preserve credentials when OAuth store read fails.</p>
</details>

<details>
<summary><strong>Zeroclaw</strong> — <a href="https://github.com/zeroclaw-labs/zeroclaw">zeroclaw-labs/zeroclaw</a></summary>

<h1>Zeroclaw Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>3 issues (all RFC/tracker), 35 PRs. RFCs point to &quot;lighter core + external integrations&quot; and runtime session/transport adapters; engineering focuses on web_fetch decompression, ACP transcript persistence, window-ratio compaction, telemetry retirement.</p>
<h2>Hot Issues</h2>
<p>#9487 RFC: Runtime-owned conversation sessions &amp; transport surface adapters (21💬) · #6165 RFC: prefer lighter core via external integrations (18💬) · #10118 [Tracker]: Rust anti-slop policy debt (16💬).</p>
<h2>Notable PRs</h2>
<p>#9283 fix(tools): decompress gzip/brotli/deflate web_fetch responses · #9378 fix(acp): persist failed/cancelled turn transcripts · #9379 fix(runtime): charge image markers in context-token estimate · #9447 fix(anthropic): classify incomplete terminal responses · #9451 refactor(observability)!: retire dormant DORA telemetry · #9504 fix(runtime): terminal notice on context exhaustion · #9535 feat(runtime): anchor compaction to model window ratio · #9557 feat(providers): ProviderErrorKind classification · #9561 fix(personality): remove filename labels from prompt.</p>
</details>

<details>
<summary><strong>NanoClaw</strong> — <a href="https://github.com/nanocoai/nanoclaw">nanocoai/nanoclaw</a></summary>

<h1>NanoClaw Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>1 issue, 35 PRs. Multi-channel onboarding (WhatsApp/Slack/Cursor/Codex) and token usage are the main line; #2715 reports inbound WhatsApp media unreachable because files land on an unmounted path.</p>
<h2>Hot Issues</h2>
<p>#2715 Inbound WhatsApp media (images/docs/audio) unreachable by agent — saved to unmounted path.</p>
<h2>Notable PRs</h2>
<p>#3270 Feat/ncl token usage · #3189 feat(skill): add-why — explain what happened to one message · #3196 Fix/add mount readonly · #3403 [main] fix(matrix): ESM patch executable on refresh · #3402 [main] fix(codex): deliver provider-generated files · #3421 [channels] announce one-click Slack agents · #3401 fix(whatsapp-cloud): skill payload compatible with main · #3356 feat(providers): Cursor Agent SDK payload · #3355 feat(setup): /add-cursor agent provider skill · #3420 fix(add-macos-statusbar): slug-aware Swift/plist · #3419 fix(add-anydoc): install-scoped ncl, portable skill test.</p>
</details>

<details>
<summary><strong>IronClaw</strong> — <a href="https://github.com/nearai/ironclaw">nearai/ironclaw</a></summary>

<h1>IronClaw Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>Shipped v1.3.0 (stable promotion of 1.3.0-rc.2). Per-user sandbox + structured automations + document editing + Telegram linked devices are the headline additions. 1 issue (#7732 persistent per-user sandbox epic, 8💬).</p>
<h2>Release</h2>
<p>ironclaw-v1.3.0 — fixed 1.2 upgrade crash-loop, Reborn image optional pubkey SSH; added per-user model preferences, structured automations (fail-closed preflight), document editing (.docx/.xlsx/.pptx structural edits + HTML→PDF), Telegram linked devices.</p>
<h2>Hot Issues</h2>
<p>#7732 Epic: Persistent per-user sandbox with iron-proxy; defer loop executors (8💬).</p>
<h2>Notable PRs</h2>
<p>#7765 feat(hooks): AfterTurn lifecycle + memory curation · #7779 feat(sandbox): route user-sandbox egress through managed per-user proxy · #7491 feat(coding): omp core-tool contract + engines + benchmark arm · #7777 refactor(webui): remove duplicate Settings/Extensions tabs · #7763 refactor(subagent): consolidate seven design docs into one README · #7766 fix(telegram): separate bot pairing from personal device linking · #7729 feat(automations): run-now across trigger domain &amp; WebUI · #7699 feat(notifications): publish actionable run gates · #7778 fix(lints): Rust 1.98 clippy migration.</p>
</details>

<details>
<summary><strong>LobsterAI</strong> — <a href="https://github.com/netease-youdao/LobsterAI">netease-youdao/LobsterAI</a></summary>

<h1>LobsterAI Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>2 issues, 7 PRs. cowork file cards / split preview, settings search, scheduled-task notification-channel fix.</p>
<h2>Hot Issues</h2>
<p>#1556 doc bug: IM bot config guide 404 · #1552 feat: AI artifact Markdown preview &amp; file cards.</p>
<h2>Notable PRs</h2>
<p>#1545 fix(agent): sync activeSkillIds immediately on update · #1546 feat(engine-overlay): cancel-launch + view-logs button after engine timeout · #1547 fix(scheduledTask): fix notification channel reverting to &quot;none&quot; · #1553 feat(cowork): Write tool file card &amp; split preview panel · #1555 fix: npm run dist:mac:x64 packaging failure · #1557 feat(settings): sidebar search/filter · #1560 fix: agent edit → click original agent can&#39;t switch back to chat.</p>
</details>

<details>
<summary><strong>CoPaw</strong> — <a href="https://github.com/agentscope-ai/CoPaw">agentscope-ai/CoPaw</a></summary></details>

<h1>CoPaw (QwenPaw) Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>Shipped v2.1.1-beta.1. 7 issues, 35 PRs. ReMe memory runtime dashboard, self-hosted multi-user Hub, console perf, unified tool panel.</p>
<h2>Release</h2>
<p>v2.1.1-beta.1 — editor tab overflow nav, provider rate-limiter log level, ReMe runtime dashboard, plugin-channel interactive configurators, OneBot inbound media localization, background-task timeout, plugin reload workspace state, historical data-URL image render, DataPaw native runtime.</p>
<h2>Hot Issues</h2>
<p>#6921 stops without notice after &quot;Now 2.1, 3.1, 3.2&quot; output, needs &quot;continue&quot; · #7102 freeze &gt;10 min · #6643 outputs shouldn&#39;t pile in media dir, per-task dirs · #6826 assistant message end-time anomaly · #6436 automatic per-message model routing · #7110 undownloadable image link breaks session · #7013 unified tool panel + web preview + interactive terminal.</p>
<h2>Notable PRs</h2>
<p>#7119 fix(security): master key file owner-only perms · #7061 fix(video): deliver tool-result videos on OpenAI Responses API · #7175 fix(console): restore full free model listings · #7183 feat(skills): workspace-scoped always-on loading · #7167 feat(creator): dialogue-gated video dispatch, project copy/recreate · #7133 feat(memory): update reme 0.4.1.8 · #7112 feat(hub): self-hosted multi-user Hub (local &amp; Docker) · #7080 feat: optional PowerContext pluggable LTM backend · #7161 feat(console): artifacts on assistant response card · #7176 perf(console): keep long chats responsive.</p>
</details>

<details>
<summary><strong>Moltis</strong> — <a href="https://github.com/moltis-org/moltis">moltis-org/moltis</a></summary>

<h1>Moltis Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>Shipped 20260820.01. 1 issue (Vault unlock/recovery missing auth, CWE-306), 6 PRs. Channel security &amp; WhatsApp experience.</p>
<h2>Release</h2>
<p>20260820.01</p>
<h2>Hot Issues</h2>
<p>#1177 [Bug]: Vault Unlock/Recovery Endpoints Missing Authentication (CWE-306).</p>
<h2>Notable PRs</h2>
<p>#1220 fix(whatsapp): render Markdown in outbound messages · #468 fix(plugins): use cmd.exe on Windows for shell hooks · #1218 fix(channels): stop hardcoding push name &quot;Moltis&quot; · #1219 fix(channels): configurable untrusted-turn tool ceiling · #1217 fix(whatsapp): treat reply to bot as addressing it · #1216 fix(httpd): require auth for vault unlock/recovery.</p>
</details>

<details>
<summary><strong>EasyClaw</strong> — <a href="https://github.com/gaoyangz77/easyclaw">gaoyangz77/easyclaw (rivonclaw)</a></summary>

<h1>EasyClaw (rivonclaw) Daily (2026-08-21)</h1>
<h2>Today</h2>
<p>0 issues, 0 PRs, but continuous releases v1.8.101~v1.8.105 (multiple/day). v1.8.105 filters Affiliate Agent work by Business Developer across pending &amp; complete work.</p>
<h2>Releases</h2>
<p>v1.8.105 (filter Affiliate Agent work by BD) · v1.8.104 · v1.8.103 · v1.8.102 · v1.8.101.</p>
</details>

<details>
<summary><strong>PicoClaw / NullClaw / TinyClaw / ZeptoClaw</strong></summary>

<h1>Low-activity / Silent Projects (2026-08-21)</h1>
<ul>
<li><strong>PicoClaw</strong> (#3329 warn on inert webhook_host/port; #3316 routed-agent context mgmt; #3315 private-chat topics) — 3 PRs, light updates.</li>
<li><strong>NullClaw</strong> — 0 issues / 0 PRs / 0 releases, completely silent.</li>
<li><strong>TinyClaw</strong> — 0 issues / 0 PRs / 0 releases, completely silent.</li>
<li><strong>ZeptoClaw</strong> — 0 issues / 0 PRs / 0 releases, completely silent.</li>
</ul>
<p>These four projects had no community activity today; ecosystem activity is clearly diverging.</p>
</details>

<hr>
<p><em>Generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. Data fetched live from GitHub public APIs and written by the executing agent — no external LLM used.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI 开源趋势日报 2026-08-21</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-trending</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-trending</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate>
      <description>开源 AI 趋势日报 2026-08-21 生成时间: 2026-08-21 02:30 (GMT+8) 数据来源：GitHub Trending（每日榜）+ gh search repos 6 个 AI 主题（按 stars 排序） 本日报由 agents-radar 本地自动化生成，所有撰写由执行代理人工完成，未调用任何外部大模型 API。 一、GitHub Trending 每日飙升榜（2026-08-21） 项目 今日新增 ★ 简介 harry0703/MoneyPrinterTurbo +2,774 用 AI 大模型与自动化工作流，按主题/关键词一键生成高清短视频 sponsors/mattpocock +2,267 真实工程师的 Skills 合集，直接取自作者的 .agents 目录 sponsors/AprilNEA +1,540 原生、本地优先的 Logitech Options+ 替代，Rust 编写 sponsors/santifer +855 开源 AI 求职：扫描招聘站点，用结构化评估筛选岗位 volcengine/OpenViking +955 面向 AI ...</description>
      <content:encoded><![CDATA[<h1>开源 AI 趋势日报 2026-08-21</h1>
<blockquote>
<p>生成时间: 2026-08-21 02:30 (GMT+8)
数据来源：GitHub Trending（每日榜）+ <code>gh search repos</code> 6 个 AI 主题（按 stars 排序）
本日报由 agents-radar 本地自动化生成，所有撰写由执行代理人工完成，未调用任何外部大模型 API。</p>
</blockquote>
<hr>
<h2>一、GitHub Trending 每日飙升榜（2026-08-21）</h2>
<table>
<thead>
<tr>
<th>项目</th>
<th>今日新增 ★</th>
<th>简介</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/harry0703/MoneyPrinterTurbo">harry0703/MoneyPrinterTurbo</a></td>
<td>+2,774</td>
<td>用 AI 大模型与自动化工作流，按主题/关键词一键生成高清短视频</td>
</tr>
<tr>
<td><a href="https://github.com/mattpocock/mattpocock">sponsors/mattpocock</a></td>
<td>+2,267</td>
<td>真实工程师的 Skills 合集，直接取自作者的 <code>.agents</code> 目录</td>
</tr>
<tr>
<td><a href="https://github.com/AprilNEA/AprilNEA">sponsors/AprilNEA</a></td>
<td>+1,540</td>
<td>原生、本地优先的 Logitech Options+ 替代，Rust 编写</td>
</tr>
<tr>
<td><a href="https://github.com/santifer/santifer">sponsors/santifer</a></td>
<td>+855</td>
<td>开源 AI 求职：扫描招聘站点，用结构化评估筛选岗位</td>
</tr>
<tr>
<td><a href="https://github.com/volcengine/OpenViking">volcengine/OpenViking</a></td>
<td>+955</td>
<td>面向 AI Agent 的自进化上下文数据库，统一 Agent 记忆与知识</td>
</tr>
<tr>
<td><a href="https://github.com/obra/obra">sponsors/obra</a></td>
<td>+749</td>
<td>Agentic Skills 框架与软件开发方法论</td>
</tr>
<tr>
<td><a href="https://github.com/akitaonrails/ai-memory">akitaonrails/ai-memory</a></td>
<td>+335</td>
<td>为 agent 编码 CLI 提供长期记忆、便于交接的方案</td>
</tr>
<tr>
<td><a href="https://github.com/modular/modular">modular/modular</a></td>
<td>+340</td>
<td>Modular 平台（含 MAX 与 Mojo）</td>
</tr>
<tr>
<td><a href="https://github.com/mahlernim/google-timeline-visualizer">mahlernim/google-timeline-visualizer</a></td>
<td>+575</td>
<td>用 Google 位置历史可视化全年旅行轨迹</td>
</tr>
<tr>
<td><a href="https://github.com/chaitanyagiri/munder-difflin">chaitanyagiri/munder-difflin</a></td>
<td>+517</td>
<td>本地多 agent 编排框架（harness）</td>
</tr>
<tr>
<td><a href="https://github.com/JuliusBrussee/JuliusBrussee">sponsors/JuliusBrussee</a></td>
<td>+309</td>
<td>Claude Code skill：用更少 token 完成同样任务</td>
</tr>
<tr>
<td><a href="https://github.com/RyanCodrai/turbovec">RyanCodrai/turbovec</a></td>
<td>+251</td>
<td>基于 TurboQuant 的 Rust 向量索引，带 Python 绑定</td>
</tr>
<tr>
<td><a href="https://github.com/makeplane/plane">makeplane/plane</a></td>
<td>+206</td>
<td>开源 Jira / Linear / Monday / ClickUp 替代</td>
</tr>
<tr>
<td><a href="https://github.com/agent-substrate/substrate">agent-substrate/substrate</a></td>
<td>+66</td>
<td>Agent Substrate：核心系统</td>
</tr>
<tr>
<td><a href="https://github.com/PostHog/posthog">PostHog/posthog</a></td>
<td>+100</td>
<td>构建自驱动产品的领先平台</td>
</tr>
<tr>
<td><a href="https://github.com/Tencent/AI-Infra-Guard">Tencent/AI-Infra-Guard</a></td>
<td>+28</td>
<td>全栈 AI 红队平台，通过 Agent Scan 守护 AI 生态</td>
</tr>
<tr>
<td><a href="https://github.com/cursor/plugins">cursor/plugins</a></td>
<td>+473</td>
<td>Cursor 插件规范与官方插件</td>
</tr>
</tbody></table>
<h2>二、六大 AI 主题搜索热度（按 stars）</h2>
<h3>1. AI Agent 框架</h3>
<ul>
<li><a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a> ⭐47,228 — 超轻量、自托管的个人 AI agent 平台</li>
<li><a href="https://github.com/TransformerOptimus/SuperAGI">TransformerOptimus/SuperAGI</a> ⭐17,660 — 开发者优先的开源自主 AI agent 框架</li>
<li><a href="https://github.com/VoltAgent/voltagent">VoltAgent/voltagent</a> ⭐10,386 — 基于开源 TypeScript 的 AI Agent 工程平台</li>
<li><a href="https://github.com/omnigent-ai/omnigent">omnigent-ai/omnigent</a> ⭐9,094 — 开源 AI agent 框架与元编排</li>
<li><a href="https://github.com/darrenhinde/OpenAgentsControl">darrenhinde/OpenAgentsControl</a> ⭐4,748 — 计划优先的开发工作流 agent 框架</li>
<li><a href="https://github.com/GH05TCREW/pentestagent">GH05TCREW/pentestagent</a> ⭐2,972 — 黑盒安全测试的 AI agent 框架</li>
<li><a href="https://github.com/espressif/esp-claw">espressif/esp-claw</a> ⭐2,025 — 面向 IoT 开发的「Chat Coding」agent 框架</li>
<li><a href="https://github.com/yomorun/yomo">yomorun/yomo</a> ⭐1,920 — 地理分布边缘的无服务器 AI Agent 框架</li>
</ul>
<h3>2. 大模型（LLM）</h3>
<ul>
<li><a href="https://github.com/u14app/deep-research">u14app/deep-research</a> ⭐4,680 — 用任意 LLM 做深度研究</li>
<li><a href="https://github.com/HuaizhengZhang/AI-Infra-from-Zero-to-Hero">HuaizhengZhang/AI-Infra-from-Zero-to-Hero</a> ⭐4,288 — AI 系统论文与工程宝典</li>
<li><a href="https://github.com/ModelTC/LightLLM">ModelTC/LightLLM</a> ⭐4,228 — 基于 Python 的 LLM 推理引擎</li>
<li><a href="https://github.com/llmgenai/LLMInterviewQuestions">llmgenai/LLMInterviewQuestions</a> ⭐1,918 — LLM 面试问题合集</li>
<li><a href="https://github.com/apirrone/Memento">apirrone/Memento</a> ⭐654 — 记录你在电脑上一切操作的 Python 应用</li>
<li><a href="https://github.com/rohan-paul/LLM-FineTuning-Large-Language-Models">rohan-paul/LLM-FineTuning-Large-Language-Models</a> ⭐577 — LLM 微调</li>
<li><a href="https://github.com/maquina-app/rails-mcp-server">maquina-app/rails-mcp-server</a> ⭐570 — Ruby 实现的 MCP 服务器</li>
<li><a href="https://github.com/gergap/vim-ollama">gergap/vim-ollama</a> ⭐334 — Vim 的 Ollama LLM 插件</li>
</ul>
<h3>3. RAG 检索增强生成</h3>
<ul>
<li><a href="https://github.com/truefoundry/cognita">truefoundry/cognita</a> ⭐4,416 — 构建 RAG 应用的框架</li>
<li><a href="https://github.com/rag-web-ui/rag-web-ui">rag-web-ui/rag-web-ui</a> ⭐3,265 — 基于 RAG 的智能对话系统</li>
<li><a href="https://github.com/Andrew-Jang/RAGHub">Andrew-Jang/RAGHub</a> ⭐1,984 — 社区驱动的 RAG 资源集合</li>
<li><a href="https://github.com/jerry-ai-dev/MODULAR-RAG-MCP-SERVER">jerry-ai-dev/MODULAR-RAG-MCP-SERVER</a> ⭐1,094 — 模块化 RAG 系统 + MCP 服务</li>
<li><a href="https://github.com/mrdbourke/simple-local-rag">mrdbourke/simple-local-rag</a> ⭐1,010 — 从零构建本地 RAG 管线</li>
<li><a href="https://github.com/RafalWilinski/cloudflare-rag">RafalWilinski/cloudflare-rag</a> ⭐603 — 全栈「与 PDF 对话」RAG</li>
<li><a href="https://github.com/tonykipkemboi/ollama_pdf_rag">tonykipkemboi/ollama_pdf_rag</a> ⭐540 — 本地 RAG 全栈 demo</li>
<li><a href="https://github.com/LightningRAG/LightningRAG">LightningRAG/LightningRAG</a> ⭐451 — Vue + Gin 全栈 RAG 启动器</li>
</ul>
<h3>4. MCP 模型上下文协议</h3>
<ul>
<li><a href="https://github.com/microsoft/mcp">microsoft/mcp</a> ⭐3,593 — 微软官方 MCP 目录</li>
<li><a href="https://github.com/neka-nat/freecad-mcp">neka-nat/freecad-mcp</a> ⭐1,860 — FreeCAD MCP 服务器</li>
<li><a href="https://github.com/GongRzhe/Office-PowerPoint-MCP-Server">GongRzhe/Office-PowerPoint-MCP-Server</a> ⭐1,854 — PowerPoint 操作的 MCP 服务器</li>
<li><a href="https://github.com/johnson7788/MultiAgentPPT">johnson7788/MultiAgentPPT</a> ⭐1,633 — 集成 A2A + MCP 的多 agent PPT 工具</li>
<li><a href="https://github.com/f/mcptools">f/mcptools</a> ⭐1,619 — 与 MCP 服务器交互的命令行工具</li>
<li><a href="https://github.com/todo-for-ai/todo-for-ai">todo-for-ai/todo-for-ai</a> ⭐1,176 — 专为 AI 设计的任务管理系统</li>
<li><a href="https://github.com/Puliczek/awesome-mcp-security">Puliczek/awesome-mcp-security</a> ⭐729 — MCP 安全资源精选</li>
<li><a href="https://github.com/innocommerce/innoshop">innocommerce/innoshop</a> ⭐651? — AI 驱动的开源电商系统</li>
</ul>
<h3>5. Agentic 工作流自动化</h3>
<ul>
<li><a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a> ⭐47,228 — 自托管个人 AI agent 平台</li>
<li><a href="https://github.com/pipeshub-ai/pipeshub-ai">pipeshub-ai/pipeshub-ai</a> ⭐3,657 — 开源、可完全扩展的 AI 上下文层</li>
<li><a href="https://github.com/vmDeshpande/ai-agent-automation">vmDeshpande/ai-agent-automation</a> ⭐175 — 带调度的模块化 AI agent 工作流平台</li>
<li><a href="https://github.com/code-forge-temple/agentic-signal">code-forge-temple/agentic-signal</a> ⭐162 — 本地可视化 AI agent 工作流平台</li>
<li><a href="https://github.com/idoforgod/Church-Admin-AgenticWorkflow">idoforgod/Church-Admin-AgenticWorkflow</a> ⭐45 — 教会管理 Agentic 工作流</li>
<li><a href="https://github.com/idoforgod/SaaS-AgenticWorkflow">idoforgod/SaaS-AgenticWorkflow</a> ⭐37 — SaaS 自动构建器</li>
<li><a href="https://github.com/hamr0/agentic-toolkit">hamr0/agentic-toolkit</a> ⭐21 — 开箱即用的 AI 开发工具套件</li>
<li><a href="https://github.com/GurYN/opencode-sdlc">GurYN/opencode-sdlc</a> ⭐3 — OpenCode 的 SDLC 管理系统</li>
</ul>
<h3>6. 多模态基础模型</h3>
<ul>
<li><a href="https://github.com/jd-opensource/JoyAI-Image">jd-opensource/JoyAI-Image</a> ⭐2,146 — 统一的图像多模态基础模型</li>
<li><a href="https://github.com/DAMO-NLP-SG/VideoLLaMA3">DAMO-NLP-SG/VideoLLaMA3</a> ⭐1,175 — 面向图像与视频的前沿多模态基础模型</li>
<li><a href="https://github.com/InternLM/Intern-S1">InternLM/Intern-S1</a> ⭐847 — 科学多模态基础模型</li>
<li><a href="https://github.com/weijiawu/Awesome-RL-for-Multimodal-Foundation-Models">weijiawu/Awesome-RL-for-Multimodal-Foundation-Models</a> ⭐453 — 多模态基础模型强化学习论文/代码集</li>
<li><a href="https://github.com/xid32/NAACL_2025_TWM">xid32/NAACL_2025_TWM</a> ⭐316 — 时序工作记忆（TWM）</li>
<li><a href="https://github.com/OpenSenseNova/SenseNova-SI">OpenSenseNova/SenseNova-SI</a> ⭐294 — [CVPR 2026] 多模态空间智能</li>
<li><a href="https://github.com/OpenBMB/AppCopilot">OpenBMB/AppCopilot</a> ⭐245 — 通用、精准、长程、高效的移动 Agent</li>
<li><a href="https://github.com/hzlab/Brain-Harmony">hzlab/Brain-Harmony</a> ⭐243 — 多模态基础模型代码库</li>
</ul>
<h2>三、趋势洞察（执行代理分析）</h2>
<ol>
<li><p><strong>「Skills / Agent 记忆」成为飙升主线</strong>：Trending 前排被 agent skills 与记忆类项目占据——mattpocock 的 Skills 合集（+2,267）、obra 的 agentic skills 框架（+749）、akitaonrails/ai-memory（+335）、JuliusBrussee 的 token 精简 skill（+309）、cursor/plugins（+473），加上 OpenViking 自进化上下文数据库（+955）。这印证了与 CLI/OpenClaw 日报一致的信号：<strong>工程重心正从「模型能力」转向「可复用技能与持久记忆」</strong>。</p>
</li>
<li><p><strong>短视频/AIGC 仍是流量引擎</strong>：MoneyPrinterTurbo 以 +2,774 居 Trending 与搜索双榜首，说明「主题→短视频」的自动化创作仍是大众最买账的 AI 落地形态。</p>
</li>
<li><p><strong>MCP 生态走向「安全 + 生产力」双轨</strong>：microsoft/mcp 目录、Office/FreeCAD MCP 服务器、mcptools 持续走高；awesome-mcp-security 上榜反映<strong>MCP 供应链安全</strong>已成为独立关注点（与 CLI 日报中 MCP fail-open 修复、凭证保留等议题呼应）。</p>
</li>
<li><p><strong>RAG 框架成熟化</strong>：cognita、rag-web-ui 等从 demo 走向生产框架，多模态 RAG（MODULAR-RAG-MCP-SERVER）开始出现。</p>
</li>
<li><p><strong>自主 agent 平台的「自托管」叙事强化</strong>：nanobot（47k★）、SuperAGI、voltagent 等强调自托管与个人 agent，与 OpenClaw 生态的 per-user sandbox、CoPaw 自托管 Hub 形成共振。</p>
</li>
<li><p><strong>多模态基础模型开源活跃</strong>：京东 JoyAI-Image、阿里 DAMO VideoLLaMA3、上海 AI Lab Intern-S1 等显示国内团队在多模态基础模型上的持续投入。</p>
</li>
<li><p><strong>本仓库相关</strong>：<a href="https://github.com/volcengine/OpenViking">volcengine/OpenViking</a> 今日 +955★，定位为面向 AI Agent 的自进化上下文数据库——与 agents-radar 关注的「Agent 记忆/知识管理」方向高度相关。</p>
</li>
</ol>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，数据来自 GitHub 公开页面与 API，由执行代理人工撰写，未调用外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Open Source Trends 2026-08-21</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-trending-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-trending-en</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate>
      <description>Open-Source AI Trending Daily Digest 2026-08-21 Generated: 2026-08-21 02:30 (GMT+8) Sources: GitHub Trending (daily) + gh search repos across 6 AI topics (sorted by stars) This digest is produced by the agents-radar local automation. All writing is done by the executing agent — no external LLM API is called. 1. GitHub Trending — Daily Movers (2026-08-21) Repo ★ Today Description harry0703/MoneyPrinterTurbo +2,774 Generate HD short videos from a topic/keyword via LLM + automation sponsors/mattpoc...</description>
      <content:encoded><![CDATA[<h1>Open-Source AI Trending Daily Digest 2026-08-21</h1>
<blockquote>
<p>Generated: 2026-08-21 02:30 (GMT+8)
Sources: GitHub Trending (daily) + <code>gh search repos</code> across 6 AI topics (sorted by stars)
This digest is produced by the agents-radar local automation. All writing is done by the executing agent — no external LLM API is called.</p>
</blockquote>
<hr>
<h2>1. GitHub Trending — Daily Movers (2026-08-21)</h2>
<table>
<thead>
<tr>
<th>Repo</th>
<th>★ Today</th>
<th>Description</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://github.com/harry0703/MoneyPrinterTurbo">harry0703/MoneyPrinterTurbo</a></td>
<td>+2,774</td>
<td>Generate HD short videos from a topic/keyword via LLM + automation</td>
</tr>
<tr>
<td><a href="https://github.com/mattpocock/mattpocock">sponsors/mattpocock</a></td>
<td>+2,267</td>
<td>Skills for Real Engineers, straight from the author&#39;s <code>.agents</code> directory</td>
</tr>
<tr>
<td><a href="https://github.com/AprilNEA/AprilNEA">sponsors/AprilNEA</a></td>
<td>+1,540</td>
<td>Native, local-first Logitech Options+ alternative in Rust</td>
</tr>
<tr>
<td><a href="https://github.com/santifer/santifer">sponsors/santifer</a></td>
<td>+855</td>
<td>Open-source AI job search: scan portals, evaluate with structured scoring</td>
</tr>
<tr>
<td><a href="https://github.com/volcengine/OpenViking">volcengine/OpenViking</a></td>
<td>+955</td>
<td>Self-evolving Context Database for AI Agents — unifies Agent memory &amp; knowledge</td>
</tr>
<tr>
<td><a href="https://github.com/obra/obra">sponsors/obra</a></td>
<td>+749</td>
<td>Agentic skills framework &amp; software-development methodology</td>
</tr>
<tr>
<td><a href="https://github.com/akitaonrails/ai-memory">akitaonrails/ai-memory</a></td>
<td>+335</td>
<td>Long-term memory for agent coding CLIs, eases handoff</td>
</tr>
<tr>
<td><a href="https://github.com/modular/modular">modular/modular</a></td>
<td>+340</td>
<td>The Modular Platform (includes MAX &amp; Mojo)</td>
</tr>
<tr>
<td><a href="https://github.com/mahlernim/google-timeline-visualizer">mahlernim/google-timeline-visualizer</a></td>
<td>+575</td>
<td>Visualize your year in travel via Google Location History</td>
</tr>
<tr>
<td><a href="https://github.com/chaitanyagiri/munder-difflin">chaitanyagiri/munder-difflin</a></td>
<td>+517</td>
<td>Local multi-agent harness</td>
</tr>
<tr>
<td><a href="https://github.com/JuliusBrussee/JuliusBrussee">sponsors/JuliusBrussee</a></td>
<td>+309</td>
<td>Claude Code skill that cuts tokens</td>
</tr>
<tr>
<td><a href="https://github.com/RyanCodrai/turbovec">RyanCodrai/turbovec</a></td>
<td>+251</td>
<td>Vector index on TurboQuant, Rust with Python bindings</td>
</tr>
<tr>
<td><a href="https://github.com/makeplane/plane">makeplane/plane</a></td>
<td>+206</td>
<td>Open-source Jira / Linear / Monday / ClickUp alternative</td>
</tr>
<tr>
<td><a href="https://github.com/agent-substrate/substrate">agent-substrate/substrate</a></td>
<td>+66</td>
<td>Agent Substrate: the core system</td>
</tr>
<tr>
<td><a href="https://github.com/PostHog/posthog">PostHog/posthog</a></td>
<td>+100</td>
<td>Platform for building self-driving products</td>
</tr>
<tr>
<td><a href="https://github.com/Tencent/AI-Infra-Guard">Tencent/AI-Infra-Guard</a></td>
<td>+28</td>
<td>Full-stack AI Red Teaming platform via Agent Scan</td>
</tr>
<tr>
<td><a href="https://github.com/cursor/plugins">cursor/plugins</a></td>
<td>+473</td>
<td>Cursor plugin specification &amp; official plugins</td>
</tr>
</tbody></table>
<h2>2. Six AI Topic Search Heat (by stars)</h2>
<h3>1. AI Agent Frameworks</h3>
<ul>
<li><a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a> ⭐47,228 · <a href="https://github.com/TransformerOptimus/SuperAGI">TransformerOptimus/SuperAGI</a> ⭐17,660 · <a href="https://github.com/VoltAgent/voltagent">VoltAgent/voltagent</a> ⭐10,386 · <a href="https://github.com/omnigent-ai/omnigent">omnigent-ai/omnigent</a> ⭐9,094 · <a href="https://github.com/darrenhinde/OpenAgentsControl">darrenhinde/OpenAgentsControl</a> ⭐4,748 · <a href="https://github.com/GH05TCREW/pentestagent">GH05TCREW/pentestagent</a> ⭐2,972 · <a href="https://github.com/espressif/esp-claw">espressif/esp-claw</a> ⭐2,025 · <a href="https://github.com/yomorun/yomo">yomorun/yomo</a> ⭐1,920</li>
</ul>
<h3>2. Large Language Models (LLM)</h3>
<ul>
<li><a href="https://github.com/u14app/deep-research">u14app/deep-research</a> ⭐4,680 · <a href="https://github.com/HuaizhengZhang/AI-Infra-from-Zero-to-Hero">HuaizhengZhang/AI-Infra-from-Zero-to-Hero</a> ⭐4,288 · <a href="https://github.com/ModelTC/LightLLM">ModelTC/LightLLM</a> ⭐4,228 · <a href="https://github.com/llmgenai/LLMInterviewQuestions">llmgenai/LLMInterviewQuestions</a> ⭐1,918 · <a href="https://github.com/apirrone/Memento">apirrone/Memento</a> ⭐654 · <a href="https://github.com/rohan-paul/LLM-FineTuning-Large-Language-Models">rohan-paul/LLM-FineTuning-Large-Language-Models</a> ⭐577 · <a href="https://github.com/maquina-app/rails-mcp-server">maquina-app/rails-mcp-server</a> ⭐570 · <a href="https://github.com/gergap/vim-ollama">gergap/vim-ollama</a> ⭐334</li>
</ul>
<h3>3. RAG (Retrieval-Augmented Generation)</h3>
<ul>
<li><a href="https://github.com/truefoundry/cognita">truefoundry/cognita</a> ⭐4,416 · <a href="https://github.com/rag-web-ui/rag-web-ui">rag-web-ui/rag-web-ui</a> ⭐3,265 · <a href="https://github.com/Andrew-Jang/RAGHub">Andrew-Jang/RAGHub</a> ⭐1,984 · <a href="https://github.com/jerry-ai-dev/MODULAR-RAG-MCP-SERVER">jerry-ai-dev/MODULAR-RAG-MCP-SERVER</a> ⭐1,094 · <a href="https://github.com/mrdbourke/simple-local-rag">mrdbourke/simple-local-rag</a> ⭐1,010 · <a href="https://github.com/RafalWilinski/cloudflare-rag">RafalWilinski/cloudflare-rag</a> ⭐603 · <a href="https://github.com/tonykipkemboi/ollama_pdf_rag">tonykipkemboi/ollama_pdf_rag</a> ⭐540 · <a href="https://github.com/LightningRAG/LightningRAG">LightningRAG/LightningRAG</a> ⭐451</li>
</ul>
<h3>4. MCP (Model Context Protocol)</h3>
<ul>
<li><a href="https://github.com/microsoft/mcp">microsoft/mcp</a> ⭐3,593 · <a href="https://github.com/neka-nat/freecad-mcp">neka-nat/freecad-mcp</a> ⭐1,860 · <a href="https://github.com/GongRzhe/Office-PowerPoint-MCP-Server">GongRzhe/Office-PowerPoint-MCP-Server</a> ⭐1,854 · <a href="https://github.com/johnson7788/MultiAgentPPT">johnson7788/MultiAgentPPT</a> ⭐1,633 · <a href="https://github.com/f/mcptools">f/mcptools</a> ⭐1,619 · <a href="https://github.com/todo-for-ai/todo-for-ai">todo-for-ai/todo-for-ai</a> ⭐1,176 · <a href="https://github.com/Puliczek/awesome-mcp-security">Puliczek/awesome-mcp-security</a> ⭐729 · <a href="https://github.com/innocommerce/innoshop">innocommerce/innoshop</a> ⭐651</li>
</ul>
<h3>5. Agentic Workflow Automation</h3>
<ul>
<li><a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a> ⭐47,228 · <a href="https://github.com/pipeshub-ai/pipeshub-ai">pipeshub-ai/pipeshub-ai</a> ⭐3,657 · <a href="https://github.com/vmDeshpande/ai-agent-automation">vmDeshpande/ai-agent-automation</a> ⭐175 · <a href="https://github.com/code-forge-temple/agentic-signal">code-forge-temple/agentic-signal</a> ⭐162 · <a href="https://github.com/idoforgod/Church-Admin-AgenticWorkflow">idoforgod/Church-Admin-AgenticWorkflow</a> ⭐45 · <a href="https://github.com/idoforgod/SaaS-AgenticWorkflow">idoforgod/SaaS-AgenticWorkflow</a> ⭐37 · <a href="https://github.com/hamr0/agentic-toolkit">hamr0/agentic-toolkit</a> ⭐21 · <a href="https://github.com/GurYN/opencode-sdlc">GurYN/opencode-sdlc</a> ⭐3</li>
</ul>
<h3>6. Multimodal Foundation Models</h3>
<ul>
<li><a href="https://github.com/jd-opensource/JoyAI-Image">jd-opensource/JoyAI-Image</a> ⭐2,146 · <a href="https://github.com/DAMO-NLP-SG/VideoLLaMA3">DAMO-NLP-SG/VideoLLaMA3</a> ⭐1,175 · <a href="https://github.com/InternLM/Intern-S1">InternLM/Intern-S1</a> ⭐847 · <a href="https://github.com/weijiawu/Awesome-RL-for-Multimodal-Foundation-Models">weijiawu/Awesome-RL-for-Multimodal-Foundation-Models</a> ⭐453 · <a href="https://github.com/xid32/NAACL_2025_TWM">xid32/NAACL_2025_TWM</a> ⭐316 · <a href="https://github.com/OpenSenseNova/SenseNova-SI">OpenSenseNova/SenseNova-SI</a> ⭐294 · <a href="https://github.com/OpenBMB/AppCopilot">OpenBMB/AppCopilot</a> ⭐245 · <a href="https://github.com/hzlab/Brain-Harmony">hzlab/Brain-Harmony</a> ⭐243</li>
</ul>
<h2>3. Trend Insights (agent analysis)</h2>
<ol>
<li><p><strong>&quot;Skills / Agent Memory&quot; is the breakout theme</strong>: The Trending front page is dominated by agent-skills and memory projects — mattocock&#39;s Skills collection (+2,267), obra&#39;s agentic skills framework (+749), akitaonrails/ai-memory (+335), JuliusBrussee&#39;s token-cutting skill (+309), cursor/plugins (+473), plus OpenViking&#39;s self-evolving context DB (+955). This echoes the CLI/OpenClaw dailies: <strong>engineering focus is shifting from &quot;model capability&quot; to &quot;reusable skills &amp; persistent memory.&quot;</strong></p>
</li>
<li><p><strong>Short-video / AIGC remains the traffic engine</strong>: MoneyPrinterTurbo leads both Trending and search at +2,774 — &quot;topic → short video&quot; automation is still the most mass-appealing AI use case.</p>
</li>
<li><p><strong>MCP ecosystem splits into &quot;security + productivity&quot;</strong>: microsoft/mcp catalog, Office/FreeCAD MCP servers and mcptools keep rising; awesome-mcp-security&#39;s appearance reflects <strong>MCP supply-chain security</strong> as a standalone concern (echoing the CLI dailies&#39; MCP fail-open fixes and credential retention).</p>
</li>
<li><p><strong>RAG frameworks are maturing</strong>: cognita and rag-web-ui move from demos to production frameworks; multimodal RAG (MODULAR-RAG-MCP-SERVER) is emerging.</p>
</li>
<li><p><strong>&quot;Self-hosted&quot; autonomous-agent narrative strengthens</strong>: nanobot (47k★), SuperAGI, voltagent emphasize self-hosted personal agents — resonating with OpenClaw&#39;s per-user sandbox and CoPaw&#39;s self-hosted Hub.</p>
</li>
<li><p><strong>Open multimodal foundation models stay active</strong>: JD JoyAI-Image, Alibaba DAMO VideoLLaMA3, Shanghai AI Lab Intern-S1 show continued domestic investment in multimodal foundations.</p>
</li>
<li><p><strong>Repo-relevant</strong>: <a href="https://github.com/volcengine/OpenViking">volcengine/OpenViking</a> gained +955★ today as a self-evolving context database for AI agents — highly relevant to agents-radar&#39;s &quot;agent memory / knowledge management&quot; focus.</p>
</li>
</ol>
<hr>
<p><em>Generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. Data from GitHub public pages/API, written by the executing agent — no external LLM used.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>Hacker News AI 社区动态日报 2026-08-21</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-hn</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-hn</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate>
      <description>Hacker News AI 动态日报 2026-08-21 生成时间: 2026-08-21 02:30 (GMT+8) 数据来源：Hacker News Algolia Search API（6 个查询：AI / LLM / agent / machine learning / Claude / GPT，近 24h，按 points 排序） 本日报由 agents-radar 本地自动化生成，所有撰写由执行代理人工完成，未调用任何外部大模型 API。 一、Top AI 故事（近 24h，按热度） 🔺 热度 💬 评论 主题 标题 953 513 AI Don&amp;#39;t paste the AI, please — 一篇反「无脑粘贴 AI 输出」的讽诫站 341 212 agent Feature Request: Support AGENTS.md — Claude Code 最热功能诉求（跨工具共振） 107 104 LLM Clean up Claude 5&amp;#39;s token vomit with a separate LLM — 用另一个 LLM 清理模型冗余输出 ...</description>
      <content:encoded><![CDATA[<h1>Hacker News AI 动态日报 2026-08-21</h1>
<blockquote>
<p>生成时间: 2026-08-21 02:30 (GMT+8)
数据来源：Hacker News Algolia Search API（6 个查询：AI / LLM / agent / machine learning / Claude / GPT，近 24h，按 points 排序）
本日报由 agents-radar 本地自动化生成，所有撰写由执行代理人工完成，未调用任何外部大模型 API。</p>
</blockquote>
<hr>
<h2>一、Top AI 故事（近 24h，按热度）</h2>
<table>
<thead>
<tr>
<th>🔺 热度</th>
<th>💬 评论</th>
<th>主题</th>
<th>标题</th>
</tr>
</thead>
<tbody><tr>
<td>953</td>
<td>513</td>
<td>AI</td>
<td><a href="https://dontpastetheai.com/">Don&#39;t paste the AI, please</a> — 一篇反「无脑粘贴 AI 输出」的讽诫站</td>
</tr>
<tr>
<td>341</td>
<td>212</td>
<td>agent</td>
<td><a href="https://github.com/anthropics/claude-code/issues/6235">Feature Request: Support AGENTS.md</a> — Claude Code 最热功能诉求（跨工具共振）</td>
</tr>
<tr>
<td>107</td>
<td>104</td>
<td>LLM</td>
<td><a href="https://github.com/zachahn/vomit">Clean up Claude 5&#39;s token vomit with a separate LLM</a> — 用另一个 LLM 清理模型冗余输出</td>
</tr>
<tr>
<td>63</td>
<td>121</td>
<td>AI</td>
<td><a href="https://franciscotrindade.me/blog/the-kids-are-really-alright/">AI didn&#39;t erase the junior engineer&#39;s value, it increased it</a> — 初级工程师价值论</td>
</tr>
<tr>
<td>59</td>
<td>48</td>
<td>AI</td>
<td><a href="https://blog.yaros.ae/anti-ai-fonts-are-useless-and-harmful/">Anti-AI fonts are useless and harmful</a> — 反 AI 字体的无用与危害</td>
</tr>
<tr>
<td>59</td>
<td>33</td>
<td>Claude</td>
<td><a href="https://www.mikekasberg.com/blog/2026/08/19/hacking-with-claude-on-a-27-smart-watch.html">Hacking with Claude on a $27 Smart Watch</a> — 在 $27 智能手表上跑 Claude</td>
</tr>
<tr>
<td>27</td>
<td>22</td>
<td>Claude</td>
<td><a href="https://alex-jacobs.com/posts/claudemd/">I Am Morally Opposed to Updating My Claude.md</a> — 对频繁改 Claude.md 的道德抵触</td>
</tr>
<tr>
<td>27</td>
<td>1</td>
<td>AI</td>
<td><a href="https://www.wired.com/story/flock-safety-os-investigate/">Flock Has a Powerful New AI Tool for Police. We Got Its Code</a> — 警方 AI 工具代码泄露调查</td>
</tr>
<tr>
<td>25</td>
<td>12</td>
<td>agent</td>
<td><a href="https://github.com/BrightbeamAI/chap">Collaborative Human Agent Protocol (CHAP)</a> — 协作式人-Agent 协议</td>
</tr>
<tr>
<td>20</td>
<td>0</td>
<td>agent</td>
<td><a href="https://www.lambda-symbolics.com/autolith">Autolith: A programming agent with a live runtime</a> — 带实时运行时的编程 agent</td>
</tr>
<tr>
<td>17</td>
<td>5</td>
<td>AI</td>
<td><a href="https://www.japantimes.co.jp/news/2026/08/19/japan/ai-training-data-disclosure/">Japan to require AI firms to disclose training data</a> — 日本要求披露训练数据</td>
</tr>
<tr>
<td>15</td>
<td>1</td>
<td>AI</td>
<td><a href="https://www.hackster.io/news/pine64-calls-time-on-the-linux-hardware-market-ceases-production-until-the-ai-bubble-bursts-a865c8345041">PINE64 halts open-source hardware manufacturing until the AI bubble bursts</a> — PINE64 暂停开源硬件生产</td>
</tr>
<tr>
<td>14</td>
<td>29</td>
<td>AI</td>
<td><a href="https://economist.com/leaders/2026/08/20/could-ais-become-conscious">Could AIs Become Conscious?</a> — AI 能否有意识</td>
</tr>
<tr>
<td>14</td>
<td>2</td>
<td>AI</td>
<td><a href="http://taubench.com/leaderboard/">Pine AI getting 75.4% (SoTA) on τ³-Voice Leaderboard</a> — 语音基准 SoTA</td>
</tr>
<tr>
<td>13</td>
<td>10</td>
<td>AI</td>
<td><a href="https://techcrunch.com/2026/08/19/ai-was-supposed-to-win-people-over-by-now-it-hasnt/">AI was supposed to win people over by now – it hasn&#39;t</a> — AI 尚未赢得人心</td>
</tr>
<tr>
<td>13</td>
<td>8</td>
<td>AI</td>
<td><a href="https://www.dexerto.com/entertainment/new-airpods-leak-reveals-built-in-cameras-and-visual-intelligence-3400062/">New AirPods leak reveals built-in cameras and Visual Intelligence</a> — AirPods 内置摄像头</td>
</tr>
<tr>
<td>13</td>
<td>6</td>
<td>AI</td>
<td><a href="https://www.unite.ai/ai-is-less-likely-to-launch-a-nuclear-strike-when-it-reasons-in-japanese/">AI is less likely to launch a nuclear strike when it reasons in Japanese</a> — 用日语推理降低核打击倾向</td>
</tr>
<tr>
<td>13</td>
<td>4</td>
<td>AI</td>
<td><a href="https://www.theguardian.com/society/2026/aug/20/yorkshire-rotherham-ai-gp-receptionist-cannot-understand-accent">Frustrated GP patients hang up as Yorkshire accent baffles AI receptionist</a> — 约克郡口音难倒 AI 前台</td>
</tr>
<tr>
<td>12</td>
<td>1</td>
<td>agent</td>
<td><a href="https://github.com/copilotkit/openbot">Show HN: Open Bot – open-source Grok Bot for any agent harness</a> — 开源 Grok Bot</td>
</tr>
<tr>
<td>12</td>
<td>0</td>
<td>AI</td>
<td><a href="https://www.autoriteitpersoonsgegevens.nl/en/current/ap-advises-twitch-users-opt-out-from-sharing-data-with-amazon-ai">Dutch DPA advises Twitch users to opt out from Amazon AI</a> — 荷兰数据保护局建议退出 Amazon AI</td>
</tr>
<tr>
<td>11</td>
<td>4</td>
<td>AI</td>
<td><a href="https://arxiv.org/abs/2603.27017">Google&#39;s AI photoscanner can determine body fat through selfies</a> — 自拍估体脂</td>
</tr>
<tr>
<td>11</td>
<td>0</td>
<td>Claude</td>
<td><a href="https://twitter.com/ClaudeDevs/status/2090245922685063634">Claude Code adds new &quot;concise&quot; output style setting</a> — Claude Code 新增 concise 输出风格</td>
</tr>
<tr>
<td>10</td>
<td>15</td>
<td>AI</td>
<td><a href="https://schipper.ai/posts/technical-leaders-should-have-the-largest-ai-exhaust/">Technical leaders should have the largest AI exhaust</a> — 技术 leader 应有最大 AI 痕迹</td>
</tr>
<tr>
<td>10</td>
<td>7</td>
<td>AI</td>
<td><a href="https://www.campaignindia.in/article/linkedin-cracks-down-on-automated-content-with-new-seems-like-ai-slop-detection-button/43e4tn3qyq543rpam874wksjn3">LinkedIn cracks down on automated content with AI detection button</a> — LinkedIn 上线 AI 检测按钮</td>
</tr>
<tr>
<td>10</td>
<td>4</td>
<td>AI</td>
<td><a href="https://illegal.solutions/posts/meta_future">Mark Zuckerberg&#39;s AI Manifesto Shows How Little the AI Future Offers</a> — 扎克伯格 AI 宣言批评</td>
</tr>
</tbody></table>
<h2>二、主题洞察（执行代理分析）</h2>
<h3>1. Agent / Claude 工程实践成为高黏讨论</h3>
<ul>
<li><strong>AGENTS.md 支持（#2，341👍/212💬）</strong> 与今日 CLI 日报中 Claude Code 最热 issue 完全共振——社区对「项目级指令文件」的诉求达到现象级，已跨出单一工具，成为 agent 生态的通用约定呼声。</li>
<li><strong>Claude.md 治理疲劳（#9，27💬；#27 Claude Code concise 风格，11👬）</strong> —— 开发者对频繁改动 <code>Claude.md</code> 产生抵触，同时欢迎「concise」这类减少噪声的输出开关，反映「提示词/配置文件维护成本」正成为真实痛点。</li>
<li><strong>新型 agent 协议与运行时（#11 CHAP、#12 Autolith、#23 Open Bot）</strong> —— 人-Agent 协作协议、带实时运行时的编程 agent、可插拔任意 harness 的 Bot，显示 agent 基础设施仍在快速摸索期。</li>
</ul>
<h3>2. 「AI 输出可信度与滥用」是头号公共议题</h3>
<ul>
<li><strong>#1 Don&#39;t paste the AI（953👍/513💬）</strong> 登顶，说明社区对「无脑复制 AI 内容」的警惕已形成广泛共识；与 #3「用另一个 LLM 清理 Claude 5 的 token 冗余」（107👍）共同指向<strong>模型输出质量/噪声</strong>问题。</li>
<li><strong>反 AI 字体（#5）、LinkedIn AI 检测（#29）、AI 尚未赢得人心（#18）</strong> 显示公众对 AI 生成内容的反感与甄别机制正在制度化。</li>
</ul>
<h3>3. 政策、隐私与监控</h3>
<ul>
<li><strong>日本强制披露训练数据（#13）、荷兰 DPA 建议退出 Amazon AI（#22）</strong> —— 监管在全球范围收紧。</li>
<li><strong>Flock 警方 AI 工具代码调查（#8）</strong> —— AI 执法监控的透明度争议。</li>
<li><strong>自拍估体脂（#25）、AirPods 摄像头（#19）</strong> —— 端侧/消费 AI 的隐私边界持续被追问。</li>
</ul>
<h3>4. 意识、偏见与荒诞</h3>
<ul>
<li><strong>AI 能否有意识（#15，29💬）、用日语推理降低核打击倾向（#20）、约克郡口音难倒 AI 前台（#21）</strong> —— 既有哲学追问，也有对模型文化/语言偏见的轻松解构，反映社区对 AI 行为可解释性与偏见的持续好奇。</li>
</ul>
<h3>5. 产业与硬件</h3>
<ul>
<li><strong>PINE64 暂停开源硬件生产（#14）</strong> 把「AI 泡沫」叙事带入硬件制造端；<strong>Epic Games 官方 Linux 版（#10）</strong> 等则属常规产业动向，被归入 GPT 查询下的讨论。</li>
</ul>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成，数据来自 HN Algolia API，由执行代理人工撰写，未调用外部大模型。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>Hacker News AI Community Digest 2026-08-21</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-hn-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-21/ai-hn-en</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate>
      <description>Hacker News AI Daily Digest 2026-08-21 Generated: 2026-08-21 02:30 (GMT+8) Source: Hacker News Algolia Search API (6 queries: AI / LLM / agent / machine learning / Claude / GPT, last 24h, sorted by points) This digest is produced locally by the agents-radar automation. All writing is done manually by the executing agent — no external LLM API was called. 1. Top AI Stories (last 24h, by popularity) 🔺 Points 💬 Comments Topic Title 953 513 AI Don&amp;#39;t paste the AI, please — a satirical plea again...</description>
      <content:encoded><![CDATA[<h1>Hacker News AI Daily Digest 2026-08-21</h1>
<blockquote>
<p>Generated: 2026-08-21 02:30 (GMT+8)
Source: Hacker News Algolia Search API (6 queries: AI / LLM / agent / machine learning / Claude / GPT, last 24h, sorted by points)
This digest is produced locally by the agents-radar automation. All writing is done manually by the executing agent — no external LLM API was called.</p>
</blockquote>
<hr>
<h2>1. Top AI Stories (last 24h, by popularity)</h2>
<table>
<thead>
<tr>
<th>🔺 Points</th>
<th>💬 Comments</th>
<th>Topic</th>
<th>Title</th>
</tr>
</thead>
<tbody><tr>
<td>953</td>
<td>513</td>
<td>AI</td>
<td><a href="https://dontpastetheai.com/">Don&#39;t paste the AI, please</a> — a satirical plea against mindlessly pasting AI output</td>
</tr>
<tr>
<td>341</td>
<td>212</td>
<td>agent</td>
<td><a href="https://github.com/anthropics/claude-code/issues/6235">Feature Request: Support AGENTS.md</a> — the most-wanted Claude Code feature (cross-tool resonance)</td>
</tr>
<tr>
<td>107</td>
<td>104</td>
<td>LLM</td>
<td><a href="https://github.com/zachahn/vomit">Clean up Claude 5&#39;s token vomit with a separate LLM</a> — using a second LLM to clean up redundant model output</td>
</tr>
<tr>
<td>63</td>
<td>121</td>
<td>AI</td>
<td><a href="https://franciscotrindade.me/blog/the-kids-are-really-alright/">AI didn&#39;t erase the junior engineer&#39;s value, it increased it</a> — on the value of junior engineers</td>
</tr>
<tr>
<td>59</td>
<td>48</td>
<td>AI</td>
<td><a href="https://blog.yaros.ae/anti-ai-fonts-are-useless-and-harmful/">Anti-AI fonts are useless and harmful</a> — why anti-AI fonts don&#39;t work</td>
</tr>
<tr>
<td>59</td>
<td>33</td>
<td>Claude</td>
<td><a href="https://www.mikekasberg.com/blog/2026/08/19/hacking-with-claude-on-a-27-smart-watch.html">Hacking with Claude on a $27 Smart Watch</a> — running Claude on a $27 smartwatch</td>
</tr>
<tr>
<td>27</td>
<td>22</td>
<td>Claude</td>
<td><a href="https://alex-jacobs.com/posts/claudemd/">I Am Morally Opposed to Updating My Claude.md</a> — a moral objection to constantly editing Claude.md</td>
</tr>
<tr>
<td>27</td>
<td>1</td>
<td>AI</td>
<td><a href="https://www.wired.com/story/flock-safety-os-investigate/">Flock Has a Powerful New AI Tool for Police. We Got Its Code</a> — investigation into leaked police AI tool code</td>
</tr>
<tr>
<td>25</td>
<td>12</td>
<td>agent</td>
<td><a href="https://github.com/BrightbeamAI/chap">Collaborative Human Agent Protocol (CHAP)</a> — a collaborative human–agent protocol</td>
</tr>
<tr>
<td>20</td>
<td>0</td>
<td>agent</td>
<td><a href="https://www.lambda-symbolics.com/autolith">Autolith: A programming agent with a live runtime</a> — a coding agent with a live runtime</td>
</tr>
<tr>
<td>17</td>
<td>5</td>
<td>AI</td>
<td><a href="https://www.japantimes.co.jp/news/2026/08/19/japan/ai-training-data-disclosure/">Japan to require AI firms to disclose training data</a> — Japan mandates training-data disclosure</td>
</tr>
<tr>
<td>15</td>
<td>1</td>
<td>AI</td>
<td><a href="https://www.hackster.io/news/pine64-calls-time-on-the-linux-hardware-market-ceases-production-until-the-ai-bubble-bursts-a865c8345041">PINE64 halts open-source hardware manufacturing until the AI bubble bursts</a> — PINE64 pauses open-source hardware</td>
</tr>
<tr>
<td>14</td>
<td>29</td>
<td>AI</td>
<td><a href="https://economist.com/leaders/2026/08/20/could-ais-become-conscious">Could AIs Become Conscious?</a> — can AIs become conscious?</td>
</tr>
<tr>
<td>14</td>
<td>2</td>
<td>AI</td>
<td><a href="http://taubench.com/leaderboard/">Pine AI getting 75.4% (SoTA) on τ³-Voice Leaderboard</a> — SoTA on a voice benchmark</td>
</tr>
<tr>
<td>13</td>
<td>10</td>
<td>AI</td>
<td><a href="https://techcrunch.com/2026/08/19/ai-was-supposed-to-win-people-over-by-now-it-hasnt/">AI was supposed to win people over by now – it hasn&#39;t</a> — AI hasn&#39;t won people over yet</td>
</tr>
<tr>
<td>13</td>
<td>8</td>
<td>AI</td>
<td><a href="https://www.dexerto.com/entertainment/new-airpods-leak-reveals-built-in-cameras-and-visual-intelligence-3400062/">New AirPods leak reveals built-in cameras and Visual Intelligence</a> — AirPods with built-in cameras</td>
</tr>
<tr>
<td>13</td>
<td>6</td>
<td>AI</td>
<td><a href="https://www.unite.ai/ai-is-less-likely-to-launch-a-nuclear-strike-when-it-reasons-in-japanese/">AI is less likely to launch a nuclear strike when it reasons in Japanese</a> — reasoning in Japanese lowers nuclear-strike tendency</td>
</tr>
<tr>
<td>13</td>
<td>4</td>
<td>AI</td>
<td><a href="https://www.theguardian.com/society/2026/aug/20/yorkshire-rotherham-ai-gp-receptionist-cannot-understand-accent">Frustrated GP patients hang up as Yorkshire accent baffles AI receptionist</a> — Yorkshire accent stumps AI receptionist</td>
</tr>
<tr>
<td>12</td>
<td>1</td>
<td>agent</td>
<td><a href="https://github.com/copilotkit/openbot">Show HN: Open Bot – open-source Grok Bot for any agent harness</a> — open-source Grok bot</td>
</tr>
<tr>
<td>12</td>
<td>0</td>
<td>AI</td>
<td><a href="https://www.autoriteitpersoonsgegevens.nl/en/current/ap-advises-twitch-users-opt-out-from-sharing-data-with-amazon-ai">Dutch DPA advises Twitch users to opt out from Amazon AI</a> — Dutch DPA advises opting out of Amazon AI</td>
</tr>
<tr>
<td>11</td>
<td>4</td>
<td>AI</td>
<td><a href="https://arxiv.org/abs/2603.27017">Google&#39;s AI photoscanner can determine body fat through selfies</a> — estimating body fat from selfies</td>
</tr>
<tr>
<td>11</td>
<td>0</td>
<td>Claude</td>
<td><a href="https://twitter.com/ClaudeDevs/status/2090245922685063634">Claude Code adds new &quot;concise&quot; output style setting</a> — Claude Code&#39;s new concise output style</td>
</tr>
<tr>
<td>10</td>
<td>15</td>
<td>AI</td>
<td><a href="https://schipper.ai/posts/technical-leaders-should-have-the-largest-ai-exhaust/">Technical leaders should have the largest AI exhaust</a> — technical leaders should leave the largest AI trail</td>
</tr>
<tr>
<td>10</td>
<td>7</td>
<td>AI</td>
<td><a href="https://www.campaignindia.in/article/linkedin-cracks-down-on-automated-content-with-new-seems-like-ai-slop-detection-button/43e4tn3qyq543rpam874wksjn3">LinkedIn cracks down on automated content with AI detection button</a> — LinkedIn adds an AI-slop detector</td>
</tr>
<tr>
<td>10</td>
<td>4</td>
<td>AI</td>
<td><a href="https://illegal.solutions/posts/meta_future">Mark Zuckerberg&#39;s AI Manifesto Shows How Little the AI Future Offers</a> — critique of Zuckerberg&#39;s AI manifesto</td>
</tr>
</tbody></table>
<h2>2. Trend Insights (analyst commentary)</h2>
<h3>1. Agent / Claude engineering practices dominate the high-engagement discussion</h3>
<ul>
<li><strong>AGENTS.md support (#2, 341↑/212💬)</strong> perfectly resonates with the hottest Claude Code issue in today&#39;s CLI digest — demand for a &quot;project-level instruction file&quot; has reached a phenomenon level; it has spilled beyond a single tool and become a rallying cry for a shared convention across the agent ecosystem.</li>
<li><strong>Claude.md maintenance fatigue (#9, 27💬; #27 Claude Code&#39;s &quot;concise&quot; style, 11💬)</strong> — developers are pushing back on constantly editing <code>Claude.md</code>, while welcoming noise-reducing output toggles like &quot;concise.&quot; This reflects a real pain point: the maintenance cost of prompts/config files.</li>
<li><strong>New agent protocols and runtimes (#11 CHAP, #12 Autolith, #23 Open Bot)</strong> — human–agent collaboration protocols, coding agents with live runtimes, and bots pluggable into any harness show agent infrastructure is still in a rapid exploratory phase.</li>
</ul>
<h3>2. &quot;AI output trustworthiness and abuse&quot; is the #1 public concern</h3>
<ul>
<li><strong>#1 Don&#39;t paste the AI (953↑/513💬)</strong> tops the chart, signaling a broad community consensus against mindlessly copying AI content. Together with #3 &quot;clean up Claude 5&#39;s token vomit with another LLM&quot; (107↑), both point at the <strong>model-output quality / noise</strong> problem.</li>
<li><strong>Anti-AI fonts (#5), LinkedIn AI detection (#29), AI hasn&#39;t won people over (#18)</strong> show public aversion to AI-generated content and the institutionalization of detection mechanisms.</li>
</ul>
<h3>3. Policy, privacy, and surveillance</h3>
<ul>
<li><strong>Japan mandates training-data disclosure (#13), Dutch DPA advises opting out of Amazon AI (#22)</strong> — regulation is tightening globally.</li>
<li><strong>Flock police AI tool code investigation (#8)</strong> — transparency disputes over AI-powered law-enforcement surveillance.</li>
<li><strong>Selfie body-fat estimation (#25), AirPods cameras (#19)</strong> — the privacy边界 of on-device / consumer AI keeps being questioned.</li>
</ul>
<h3>4. Consciousness, bias, and the absurd</h3>
<ul>
<li><strong>Can AIs become conscious (#15, 29💬), reasoning in Japanese lowers nuclear-strike tendency (#20), Yorkshire accent stumps AI receptionist (#21)</strong> — ranging from philosophical inquiry to lighthearted deconstruction of cultural/linguistic model bias, reflecting the community&#39;s ongoing curiosity about AI behavior explainability and bias.</li>
</ul>
<h3>5. Industry and hardware</h3>
<ul>
<li><strong>PINE64 pauses open-source hardware production (#14)</strong> brings the &quot;AI bubble&quot; narrative into hardware manufacturing; <strong>Epic Games&#39; official Linux build (#10)</strong> is a routine industry move, surfacing under the GPT query.</li>
</ul>
<hr>
<p><em>This digest is auto-generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>. Data is sourced from the HN Algolia API and written manually by the executing agent — no external LLM was called.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI CLI 工具社区动态日报 2026-08-20</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-cli</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-cli</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      <description>AI CLI 工具社区动态日报 2026-08-20 生成时间: 2026-08-20 04:55 UTC | 覆盖工具: 7 个 Claude Code OpenAI Codex Gemini CLI GitHub Copilot CLI Kimi Code CLI OpenCode Qwen Code Claude Code Skills 横向对比 AI CLI 工具社区动态横向对比分析报告（2026-08-20） 1. 生态全景 AI CLI 工具已进入高频迭代与精细化竞争阶段：Claude Code、OpenAI Codex、Gemini CLI、GitHub Copilot CLI、Qwen Code 在 24 小时内均有版本发布，OpenCode 与 Qwen Code 各有 50 条 PR 动态。社区反馈重心正从“模型能力”转向“工程可信度”——TUI 交互细节、权限沙箱边界、上下文压缩后的数据可访问性、MCP/ACP 协议稳定性成为跨工具共通的痛点。安全加固显著提速：Git 命令默认信任被移除、MCP 配置 fail-open 漏洞修复、插件 Git 操作隔离等在同日合...</description>
      <content:encoded><![CDATA[<h1>AI CLI 工具社区动态日报 2026-08-20</h1>
<blockquote>
<p>生成时间: 2026-08-20 04:55 UTC | 覆盖工具: 7 个</p>
</blockquote>
<ul>
<li><a href="https://github.com/anthropics/claude-code">Claude Code</a></li>
<li><a href="https://github.com/openai/codex">OpenAI Codex</a></li>
<li><a href="https://github.com/google-gemini/gemini-cli">Gemini CLI</a></li>
<li><a href="https://github.com/github/copilot-cli">GitHub Copilot CLI</a></li>
<li><a href="https://github.com/MoonshotAI/kimi-cli">Kimi Code CLI</a></li>
<li><a href="https://github.com/anomalyco/opencode">OpenCode</a></li>
<li><a href="https://github.com/QwenLM/qwen-code">Qwen Code</a></li>
<li><a href="https://github.com/anthropics/skills">Claude Code Skills</a></li>
</ul>
<hr>
<h2>横向对比</h2>
<h1>AI CLI 工具社区动态横向对比分析报告（2026-08-20）</h1>
<h2>1. 生态全景</h2>
<p>AI CLI 工具已进入高频迭代与精细化竞争阶段：Claude Code、OpenAI Codex、Gemini CLI、GitHub Copilot CLI、Qwen Code 在 24 小时内均有版本发布，OpenCode 与 Qwen Code 各有 50 条 PR 动态。社区反馈重心正从“模型能力”转向“工程可信度”——TUI 交互细节、权限沙箱边界、上下文压缩后的数据可访问性、MCP/ACP 协议稳定性成为跨工具共通的痛点。安全加固显著提速：Git 命令默认信任被移除、MCP 配置 fail-open 漏洞修复、插件 Git 操作隔离等在同日合入。与此同时，Windows 平台问题（尤其 OpenAI Codex）与 gpt-5.6 系列新模型的兼容性/成本问题，正在成为用户流失的高风险点。</p>
<h2>2. 各工具活跃度对比</h2>
<table>
<thead>
<tr>
<th>工具</th>
<th>热点/活跃 Issues</th>
<th>重要 PR 动态</th>
<th>Releases（今日）</th>
</tr>
</thead>
<tbody><tr>
<td>Claude Code</td>
<td>12（Top 10 + 2 补充）</td>
<td>1</td>
<td>v2.1.236 / v2.1.237</td>
</tr>
<tr>
<td>OpenAI Codex</td>
<td>10</td>
<td>10</td>
<td>rust-v0.149.0-alpha.2 / alpha.3</td>
</tr>
<tr>
<td>Gemini CLI</td>
<td>10</td>
<td>10</td>
<td>v0.56.0 稳定版、v0.57.0-preview.0、nightly</td>
</tr>
<tr>
<td>GitHub Copilot CLI</td>
<td>10</td>
<td>0</td>
<td>v1.0.81-3 / -4 / -5</td>
</tr>
<tr>
<td>Kimi Code CLI</td>
<td>1（已关闭）</td>
<td>0</td>
<td>无</td>
</tr>
<tr>
<td>OpenCode</td>
<td>18 更新</td>
<td>50 更新</td>
<td>无</td>
</tr>
<tr>
<td>Qwen Code</td>
<td>6 活跃</td>
<td>50 更新</td>
<td>v0.21.14（dsw-eas-full-20260820-r1）</td>
</tr>
</tbody></table>
<h2>3. 共同关注的功能方向</h2>
<ul>
<li><strong>TUI / 终端交互稳定性</strong>：Claude Code 复制粘贴混入缩进（#18170，286👍/134 评论）、输出截断不可展开（#26954）、Ghostty 快捷键失效（#18157）；OpenCode 输入内容被静默销毁（#43563）、标签页无法关闭（#43553）、/tmp 泄漏导致启动失败（#42700）；GitHub Copilot CLI TUI 死锁（#4533）；Qwen Code Web Shell 剪贴板在非 localhost HTTP 环境失效（#9485）。基础交互问题成为社区最高频诉求。</li>
<li><strong>权限与安全边界</strong>：GitHub Copilot CLI ACP 模式自动批准工具调用（#4537）、沙箱策略未决时强制启用（#4522）、非交互模式绕过 managed settings（#4528）；Gemini CLI 修复 MCP 配置损坏 fail-open（#28794）、扩展环境变量注入需用户同意（#28863）；OpenAI Codex 不再默认信任 Git 命令（#39524）、隔离自动插件 Git 操作（#39520）；Claude Code 引号命令权限误报（#27957）、会话级 acceptEdits 不持久（#12070）。</li>
<li><strong>上下文管理与跨压缩记忆</strong>：Claude Code 压缩后历史不可回看（#27242）、用户自建跨压缩记忆系统（#34556，95 评论）、上下文用量显示不准确（#6616）；Gemini CLI Auto Memory 脱敏前置化与日志隐私争议（#26525）、低信号 session 无限重试（#26522）；OpenAI Codex 本地压缩 v2 保留无界 input_image 导致重复压缩（#33493）；GitHub Copilot CLI 社区同样提出压缩后长期记忆需求。</li>
<li><strong>MCP/ACP 开放协议成熟度</strong>：GitHub Copilot CLI Atlassian MCP OAuth 连续两版本失败（#4480/#4490）、<code>server/discover</code> 与 legacy <code>initialize</code> 双协议握手破坏（#4525）；Claude Code Notion MCP JSON 参数被序列化为字符串（#25865）；OpenAI Codex Windows 下 stdio MCP server 反复启动不回收（#38754）；Kimi Code ACP 模式 Grep/Glob 被硬性限制（#2609）。</li>
<li><strong>模型兼容性与成本透明度</strong>：OpenAI Codex GPT-5.6 串行化工具调用导致 27–45% 额外加权用量（#35050）；OpenCode gpt-5.6-sol-fast 被注入不支持的 <code>prompt_cache_retention</code>（#43367）、gpt-5.6-luna 空响应/403（#43565）；Qwen Code 模型路由切换后 token 计数失效（#9506）。</li>
<li><strong>企业级配置与跨平台质量</strong>：GitHub Copilot CLI GHEC 数据驻留租户下 prompt 模式 401（#4527）、组织启用模型不同步（#4390）；OpenAI Codex Windows 平台问题集中爆发，包括 Trusted RPC 初始化失败（#39136，80 评论）、<code>\\?\</code> 路径归档失败（#39239）、WSL PTY 静默失败（#37104）。</li>
</ul>
<h2>4. 差异化定位分析</h2>
<ul>
<li><strong>Claude Code</strong>：在 TUI 交互精细度上用户期望最高，社区高赞问题集中于复制粘贴、快捷键、输出展开等日常体验。功能侧持续强化输出风格控制（Concise）、默认模型切换（<code>ANTHROPIC_DEFAULT_MODEL</code>）与跨会话通知。定位为专业开发者日常主力终端工具。</li>
<li><strong>OpenAI Codex</strong>：Rust 重写推进中且与桌面端同步迭代，全平台覆盖意图明显，但 Windows 质量问题（浏览器插件、路径处理、沙箱、PTY）构成最突出短板。安全 PR 方向清晰（Git 信任收紧、插件隔离），定位为 OpenAI 模型能力与桌面/IDE/移动端全场景入口。</li>
<li><strong>Gemini CLI</strong>：双轨道发布（稳定版 + 预览版）验证严谨，安全修复与 IDE/云端集成（Cloud Workstations OAuth、VS Code Companion）并重。特色功能包括本地 Whisper 语音输入、GCS 轨迹日志、前缀缓存优化。定位为 Google 生态开发者与 Gemini 模型深度绑定用户。</li>
<li><strong>GitHub Copilot CLI</strong>：企业治理导向最明确：managed policy、沙箱强制、数据驻留、审计合规是核心语境。当前社区争论集中在安全策略的过度强制与 ACP/沙箱绕过风险。定位为企业受管环境中的 Copilot 入口。</li>
<li><strong>Kimi Code CLI</strong>：社区规模最小，今日仅 1 条被关闭的 ACP 相关问题（Grep/Glob 在 ACP runtime 被限制）。反映其当前重点是打通 ACP/IDE 集成基础链路，生态尚处早期。</li>
<li><strong>OpenCode</strong>：社区贡献驱动的开源工具，PR 活跃度极高（50 条），插件系统扩展至 HTTP 路由/webhook，同时进行 Effect Latch 重构、模型能力限制移除等底层清理。问题则包括数据丢失级 TUI 缺陷与桌面端 Sidecar 启动超时。定位为追求最新模型与高度可定制性的开发者。</li>
<li><strong>Qwen Code</strong>：开发流程高度自动化（大量 bot 驱动的 autofix PR），强调端到端验证（SWE-bench Verified 500/500、Terminal-Bench 89 分）与沙箱镜像 digest 绑定。渠道集成侧重 IM（DingTalk 引用消息修复），并持续运营 CI/CD 机器人看板。定位为面向验证严谨性和中国 IM/云生态的用户。</li>
</ul>
<h2>5. 社区热度与成熟度</h2>
<ul>
<li><strong>高活跃、高期望</strong>：Claude Code 社区反馈强度最高（单 issue 286👍、134 评论），用户讨论深入且对体验缺陷零容忍；GitHub Copilot CLI 因安全回归（ACP 自动批准）引发激烈争论，企业用户与安全合规诉求碰撞明显。</li>
<li><strong>快速迭代、质量承压</strong>：OpenAI Codex 双 alpha 同日发布但 Windows 回归问题跨版本复现，社区对其发布节奏与质量门禁存在质疑；OpenCode 贡献者活跃但 issue 暴露数据丢失、OOM 等严重问题，呈现典型的高速演进期特征。</li>
<li><strong>稳健推进、安全优先</strong>：Gemini CLI 稳定版/预览版分轨清晰，PR 以安全加固与可靠性修复为主，社区讨论围绕 subagent 可信度与记忆隐私，成熟度中上。</li>
<li><strong>自动化主导、外部参与待观察</strong>：Qwen Code 50 条 PR 中大量来自 bot 自动修复/接管，issue 数量少且多由官方跟进，开发流程高度工业化但外部社区声量有限；Kimi Code 活跃度垫底，仍在补齐基础能力。</li>
</ul>
<h2>6. 值得关注的趋势信号</h2>
<ul>
<li><strong>安全边界从“默认信任”转向“默认隔离”</strong>：OpenAI Codex 不再将 Git 命令视为安全、Gemini CLI 修复 MCP fail-open、GitHub Copilot CLI 收紧 ACP/非交互模式的绕过路径——AI CLI 正在集体收敛对本地环境的最小信任原则。开发者为 CI 或编辑器接入时应重新审视权限授予范围。</li>
<li><strong>上下文压缩与记忆持久化是下一轮体验分水岭</strong>：Claude Code 用户因压缩后无法回看历史而自建记忆系统（#34556），Gemini 的 Auto Memory 又引发隐私争议。能在“可回溯、可控制、隐私安全”三方面同时给出方案的工具有望建立长期粘性。</li>
<li><strong>TUI 基础体验成为选型硬指标</strong>：复制粘贴缩进污染、快捷键终端兼容性、输出截断、输入静默丢失等“小问题”占据各工具高赞榜。对技术决策者而言，在真实终端环境（Ghostty、WSL、Wayland、Windows Terminal）中的可用性测试应优先于模型能力对比。</li>
<li><strong>Windows/Linux 桌面是未被充分满足的市场</strong>：OpenAI Codex 的 Windows 问题密度最高（Trusted RPC、路径前缀、沙箱 EPERM、WSL PTY），Gemini Browser agent 在 Wayland 下失败，OpenCode 桌面端 Sidecar 启动超时。跨平台质量正在成为后来者差异化切入的机会点。</li>
<li><strong>模型行为变更直接影响账单与兼容性</strong>：GPT-5.6 串行化带来 27–45% 额外加权用量（Codex #35050），gpt-5.6 系列在 OpenCode 上出现参数注入与空响应问题。开发者应对新模型保持“先小规模验证成本与行为，再大规模切换”的策略，并关注工具是否提供用量统计的路由身份绑定（如 Qwen #9506）。</li>
<li><strong>开放协议方向明确，但实现成熟度不足</strong>：MCP/ACP 在 OAuth 发现、双协议握手、工具能力边界、进程生命周期方面接连出问题，且部分回归跨版本未修复。依赖第三方 MCP/ACP 的团队应预留降级方案，并优先选择协议实现迭代快的工具。</li>
<li><strong>AI 工具自身开发流程已深度 AI 化</strong>：Qwen Code 的 autofix/takeover bot、OpenCode 的 opencode-agent bot 自动提交 PR，显示 AI 已参与自身软件工程与发布质量门禁。这一模式若被更多厂商采用，将加快问题修复速度，但对人工审查机制提出新要求。</li>
</ul>
<hr>
<h2>各工具详细报告</h2>
<details>
<summary><strong>Claude Code</strong> — <a href="https://github.com/anthropics/claude-code">anthropics/claude-code</a></summary>

<h2>Claude Code Skills 社区热点</h2>
<blockquote>
<p>数据来源: <a href="https://github.com/anthropics/skills">anthropics/skills</a></p>
</blockquote>
<h1>Claude Code Skills 社区热点报告</h1>
<p><strong>数据截止：2026-08-20</strong> | 数据来源：github.com/anthropics/skills</p>
<h2>一、热门 Skills 排行</h2>
<p>按社区关注度与讨论热度排序，当前最受关注的 5 个 Skill PR：</p>
<h3>1. skill-creator 评估系统修复（run_eval.py）</h3>
<ul>
<li><strong>PR</strong>: <a href="https://github.com/anthropics/skills/pull/1298">#1298</a> | 状态: <strong>OPEN</strong> | 作者: MartinCajiao</li>
<li><strong>功能</strong>: 修复 <code>run_eval.py</code> 始终报告 <code>recall=0%</code> 的严重缺陷，该问题导致 skill 描述优化循环在噪声数据上运行。</li>
<li><strong>社区焦点</strong>: 影响面大——直接关联 <a href="https://github.com/anthropics/skills/issues/556">#556</a>（12 条评论，7 个 👍，10+ 独立复现），且与 Windows 兼容性修复（<a href="https://github.com/anthropics/skills/pull/1099">#1099</a>、<a href="https://github.com/anthropics/skills/pull/1050">#1050</a>）形成修复集群，是当前生态最集中的技术债。</li>
</ul>
<h3>2. document-typography 文档排版质检 Skill</h3>
<ul>
<li><strong>PR</strong>: <a href="https://github.com/anthropics/skills/pull/514">#514</a> | 状态: <strong>OPEN</strong> | 作者: PGTBoos</li>
<li><strong>功能</strong>: 针对 AI 生成文档的排版质量控制——孤行文字（1-6 个词溢出到下一行）、页底孤立标题、编号错位。</li>
<li><strong>社区焦点</strong>: 直击 AI 生成文档的普遍痛点，属于&quot;用户不会主动要求但明显影响质量&quot;的隐性需求，讨论集中在触发词设计和质检规则的边界情况。</li>
</ul>
<h3>3. skill-quality-analyzer + skill-security-analyzer 元技能</h3>
<ul>
<li><strong>PR</strong>: <a href="https://github.com/anthropics/skills/pull/83">#83</a> | 状态: <strong>OPEN</strong> | 作者: eovidiu</li>
<li><strong>功能</strong>: 新增两个元技能——Skill 质量分析器（SKILL.md 结构、文档、示例、资源等五个维度评分）和安全分析器。</li>
<li><strong>社区焦点</strong>: 与 <a href="https://github.com/anthropics/skills/issues/492">#492</a>（43 条评论的安全信任边界问题）形成呼应，反映了社区对 Skill 质量和安全评估工具的需求。</li>
</ul>
<h3>4. ServiceNow 平台综合 Skill</h3>
<ul>
<li><strong>PR</strong>: <a href="https://github.com/anthropics/skills/pull/568">#568</a> | 状态: <strong>OPEN</strong> | 作者: Vanka07</li>
<li><strong>功能</strong>: 覆盖 ITSM、ITOM、ITAM/SAM Pro、FSM、HRSD、CSM、SPM/PPM、Vulnerability Response、Security Incident Response 和 IntegrationHub 的 ServiceNow 平台助手。</li>
<li><strong>社区焦点</strong>: 企业级平台集成需求，跨度大、覆盖面广，更新活跃（最近更新 2026-08-12），讨论围绕技能边界和平台版本适配。</li>
</ul>
<h3>5. Pyxel 复古游戏开发 Skill</h3>
<ul>
<li><strong>PR</strong>: <a href="https://github.com/anthropics/skills/pull/525">#525</a> | 状态: <strong>OPEN</strong> | 作者: kitao（pyxel-mcp 作者）</li>
<li><strong>功能</strong>: 基于 Pyxel 引擎的复古/像素风/8-bit 游戏开发 MCP skill，覆盖&quot;编写 → 运行截图 → 检查 → 迭代&quot;的完整工作流。</li>
<li><strong>社区焦点</strong>: 官方引擎作者亲自提交，具备完整生态支持，关注度随时间持续上升（创建 3 月，更新至 7 月）。</li>
</ul>
<h3>6. ODT 格式支持 Skill</h3>
<ul>
<li><strong>PR</strong>: <a href="https://github.com/anthropics/skills/pull/486">#486</a> | 状态: <strong>OPEN</strong> | 作者: GitHubNewbie0</li>
<li><strong>功能</strong>: OpenDocument 格式（.odt/.ods）的创建、填充、读取与转换为 HTML，触发词覆盖 ODT/ODS/ODF/OpenDocument/LibreOffice 等。</li>
<li><strong>社区焦点</strong>: 补充现有 docx/pdf 之外的开源文档格式支持，讨论集中在 LibreOffice 兼容性和模板填充的可靠性。</li>
</ul>
<h2>二、社区需求趋势</h2>
<p>从 Issues 数据提炼，社区最关注的方向呈以下五个趋势：</p>
<h3>1. 安全与信任边界管理（最高热度）</h3>
<ul>
<li><strong>Issue #492</strong>（43 条评论）: 社区制作 Skill 在 <code>anthropic/</code> 命名空间下分发，伪装官方 Anthropic Skill，构成信任边界滥用漏洞——用户可能向非官方 Skill 授予过高权限。</li>
<li>这表明社区对 Skill 供应链安全有强烈关注，预期将推动官方签名/认证机制。</li>
</ul>
<h3>2. 企业级 Skill 分发与共享</h3>
<ul>
<li><strong>Issue #228</strong>（16 条评论，8 个 👍，👍 数最高）: 要求支持组织内直接共享 Skill（目前需手动下载 .skill 文件并通过 Slack/Teams 传输），期望建立共享 Skill 库或直接分享链接。</li>
<li>结合 <a href="https://github.com/anthropics/skills/issues/189">#189</a>（插件重复安装问题），说明技能分发链路尚不成熟。</li>
</ul>
<h3>3. Skill 开发工具链的可靠性</h3>
<ul>
<li><strong>Issue #556</strong>: <code>run_eval.py</code> 0% 触发率 bug，7 个 👍，10+ 独立复现——Skill 自动化评估工具存在系统性缺陷，导致优化循环失效。</li>
<li><strong>Issue #202</strong>: skill-creator 应更新为最佳实践——当前更像开发者文档而非可操作 Skill，违反自身规范。</li>
</ul>
<h3>4. 上下文窗口管理</h3>
<ul>
<li><strong>Issue #1487</strong>（4 条评论）: <code>claude-api</code> Skill 一次工具调用即注入约 156k tokens，直接耗尽上下文窗口。</li>
<li><strong>Issue #1175</strong>: SharePoint Online 文档处理对安全与上下文窗口的顾虑。</li>
</ul>
<h3>5. 推理质量与治理</h3>
<ul>
<li><strong>Issue #1385</strong>（4 条评论）: 推理质量门控管线——预任务校准 → 对抗性审查 → 交付验证，代表社区对输出质量控制的进阶需求。</li>
<li><strong>Issue #412</strong>: agent-governance 安全模式提案——策略执行、威胁检测、信任评分与审计追踪。</li>
</ul>
<h2>三、高潜力待合并 Skills</h2>
<p>以下 PR 讨论活跃、价值明确，近期有较大概率落地：</p>
<table>
<thead>
<tr>
<th>Skill</th>
<th>PR</th>
<th>亮点</th>
<th>当前状态</th>
</tr>
</thead>
<tbody><tr>
<td><strong>ServiceNow 平台 Skill</strong></td>
<td><a href="https://github.com/anthropics/skills/pull/568">#568</a></td>
<td>企业级平台全覆盖，最近更新 8 月 12 日，讨论持续活跃</td>
<td>OPEN（4.5 个月）</td>
</tr>
<tr>
<td><strong>Pyxel 复古游戏开发</strong></td>
<td><a href="https://github.com/anthropics/skills/pull/525">#525</a></td>
<td>官方引擎作者提交，生态完整，7 月仍有更新</td>
<td>OPEN（4.5 个月）</td>
</tr>
<tr>
<td><strong>skill-quality-analyzer</strong></td>
<td><a href="https://github.com/anthropics/skills/pull/83">#83</a></td>
<td>直击社区对 Skill 质量评估的需求，与 #492 安全诉求形成协同</td>
<td>OPEN（9 个月）</td>
</tr>
<tr>
<td><strong>self-audit 推理质量门控</strong></td>
<td><a href="https://github.com/anthropics/skills/pull/1367">#1367</a></td>
<td>文件校验 + 四维推理审计，通用性强，与 #1385 提案配套</td>
<td>OPEN（1.5 个月）</td>
</tr>
<tr>
<td><strong>run_eval.py 修复集</strong></td>
<td><a href="https://github.com/anthropics/skills/pull/1298">#1298</a></td>
<td>修复可复现的系统性 bug，有 10+ 复现报告背书</td>
<td>OPEN（2.5 个月）</td>
</tr>
<tr>
<td><strong>ODT 文档处理</strong></td>
<td><a href="https://github.com/anthropics/skills/pull/486">#486</a></td>
<td>明确的功能空白，触发词设计完整</td>
<td>OPEN（5.5 个月）</td>
</tr>
</tbody></table>
<h2>四、Skills 生态洞察</h2>
<p><strong>当前社区最集中的诉求是：Skill 工程化的&quot;基础设施&quot;建设——评估工具的可信度（#556、#1298）、分发链路的安全与便捷（#492、#228）、以及上下文窗口的占用控制（#1487）——三者共同指向一个核心问题：Skill 生态正从&quot;能做什么&quot;转向&quot;如何安全、可靠、高效地规模化使用&quot;。</strong></p>
<hr>
<h1>Claude Code 社区动态日报（2026-08-20）</h1>
<h2>今日速览</h2>
<ul>
<li>发布 v2.1.236 与 v2.1.237，带来 <strong>Concise 输出风格</strong>、<code>ANTHROPIC_DEFAULT_MODEL</code> 环境变量与跨会话 SendMessage 通知能力，同时修复 LLM 网关/custom base URL 下的 prompt caching 问题。</li>
<li>社区热度集中在 TUI 复制粘贴缺陷（#18170，286👍/134评论）、上下文压缩后历史不可访问（#27242，80👍）、引号命令权限误报（#27957，74👍）三大问题上。</li>
<li>PR 侧较平静，过去 24 小时仅 1 条文档类更新。</li>
</ul>
<h2>版本发布</h2>
<p><strong>v2.1.237</strong></p>
<ul>
<li>修复：使用 LLM 网关或自定义 base URL 的会话中 prompt caching 失效的问题</li>
<li>新增：内置 <strong>&quot;Concise&quot; 输出风格</strong>——Claude 直接给出结果、跳过开场白和叙述，同时保持同等的执行深度。可在 <code>/config</code> 的 Output style 下选择</li>
</ul>
<p><strong>v2.1.236</strong></p>
<ul>
<li>新增：<code>ANTHROPIC_DEFAULT_MODEL</code> 环境变量，设定新会话的起始模型；<code>/model</code> 选择可覆盖它，且重启后保持（不同于 <code>ANTHROPIC_MODEL</code>）</li>
<li>新增：跨会话 <code>SendMessage</code> 的 <code>notify_when_idle</code> 参数，可请求另一个 Claude Code 会话空闲时通知</li>
</ul>
<h2>社区热点 Issues</h2>
<p><strong>1. #18170 [TUI] 终端复制粘贴混入多余缩进与行尾空格</strong>
评论: 134 | 👍: 286 | <a href="https://github.com/anthropics/claude-code/issues/18170">链接</a>
从终端输出复制段落或代码块时，每行会自动带上与提示符对齐的视觉缩进和行尾空格，粘贴到编辑器后需要手动清理。这是当前社区反馈最强烈的 TUI 问题，评论数远超其他 Issue，操作频率高、影响面广。</p>
<p><strong>2. #27242 [TUI] 上下文压缩/plan-mode 清理/分支切换后无法回看历史对话</strong>
评论: 17 | 👍: 80 | <a href="https://github.com/anthropics/claude-code/issues/27242">链接</a>
<code>transcript.jsonl</code> 中完整数据始终保留，但 TUI 没有任何可用入口翻查被清理的对话。涉及压缩后、plan-mode 清理、分支导航三种高频场景，用户对&quot;数据在本地却看不到&quot;的落差感强烈。</p>
<p><strong>3. #27957 [权限] 无法禁用 &#39;Command contains quoted characters in flag names&#39; 警告</strong>
评论: 26 | 👍: 74 | <a href="https://github.com/anthropics/claude-code/issues/27957">链接</a>
更新后所有含引号 flag 的命令（如 <code>git commit -m &quot;message&quot;</code>、<code>bun run build --outdir &quot;dist&quot;</code>）都会触发确认弹窗，完全正常的操作被误报拦截。开发者普遍认为该警告标准过宽，要求提供关闭开关，日常 git 工作流被强制打断。</p>
<p><strong>4. #26997 [Desktop] SSH 对话框无法处理加密的默认私钥</strong>
评论: 31 | 👍: 42 | <a href="https://github.com/anthropics/claude-code/issues/26997">链接</a>
当 <code>~/.ssh/id_ed25519</code> 存在且受 passphrase 保护时，桌面端 SSH 连接直接失败。内置 SSH 库没有 passphrase 输入入口，使用加密密钥这一常见安全实践反而成为硬阻塞。</p>
<p><strong>5. #18157 [TUI] Ghostty 终端下 Option+Backspace（删除单词）失效</strong>
评论: 13 | 👍: 38 | <a href="https://github.com/anthropics/claude-code/issues/18157">链接</a>
macOS 上使用 Ghostty 终端时，Option+Backspace 在 Claude Code 内无法删除前一个单词，终端内其他程序正常。关联 #5196、#9219，表明该系列快捷键问题持续未解决。</p>
<p><strong>6. #26996 [Tools] Edit 工具静默将 tab 转为空格，导致反复匹配失败</strong>
评论: 20 | 👍: 30 | <a href="https://github.com/anthropics/claude-code/issues/26996">链接</a>
编辑 tab 缩进的文件时，Edit 工具会静默改变缩进字符，后续 string match 因格式不一致而反复失败。对以 tab 为缩进规范的代码库影响明显，且问题隐蔽、难以排查。</p>
<p><strong>7. #26954 [TUI] Bash 输出截断后 Ctrl+O/Ctrl+E 无法完整展开</strong>
评论: 18 | 👍: 30 | <a href="https://github.com/anthropics/claude-code/issues/26954">链接</a>
约 30-40 行的命令输出在会话中即被截断，按下 ctrl+o/ctrl+e 后仍不显示完整内容。日志检索、grep 等场景下关键信息直接丢失，影响 Agent 对上下文的判断。</p>
<p><strong>8. #26572 [Agents] 提议 CustomPaneBackend 协议，解耦 agent teams 与 tmux CLI</strong>
评论: 8 | 👍: 28 | <a href="https://github.com/anthropics/claude-code/issues/26572">链接</a>
KILD 项目作者提出以自定义 Pane 后端协议替代对 tmux 的强依赖，以支持 Ghostty、WezTerm、Zellij、KILD 及远程部署。这是由独立工具作者提出的建设性架构方案，反映生态对更开放 agent 基础设施的诉求。</p>
<p><strong>9. #12070 [权限] 会话级 acceptEdits 权限模式未持久生效</strong>
评论: 12 | 👍: 26 | <a href="https://github.com/anthropics/claude-code/issues/12070">链接</a>
选择 &quot;Yes, and accept all for this session&quot; 后，后续 Edit 仍反复弹出权限请求。session 级权限承诺未兑现，阻塞长时间批量编辑任务。</p>
<p><strong>10. #25865 [MCP] Notion MCP 连接器将 JSON 对象参数序列化为字符串</strong>
评论: 14 | 👍: 23 | <a href="https://github.com/anthropics/claude-code/issues/25865">链接</a>
Notion 连接器在传递 JSON 对象参数时被转成字符串，导致 update/move/create 等操作失败。MCP 生态是官方主推方向，此问题影响第三方工具集成可信度。</p>
<p><strong>补充关注</strong>（未入 Top 10）：</p>
<ul>
<li>#34556 [closed] 用户经历 59 次上下文压缩后自建了完整记忆持久化系统，95 条评论讨论热烈，反映跨压缩记忆是真实痛点（<a href="https://github.com/anthropics/claude-code/issues/34556">链接</a>）</li>
<li>#6616 显示 86% 可用上下文却被误报 &quot;Context low&quot; 且 <code>/compact</code> 失败，上下文使用量计算问题再度浮现（<a href="https://github.com/anthropics/claude-code/issues/6616">链接</a>）</li>
</ul>
<h2>重要 PR 进展</h2>
<p>过去 24 小时 PR 活跃度低，仅 1 条：</p>
<p><strong>#77977 [docs] 文档：记录 plugin-dev 中 skipLfs marketplace 来源</strong>
作者: superdiaodiao | 创建: 2026-07-16 | 更新: 2026-08-19 | <a href="https://github.com/anthropics/claude-code/pull/77977">链接</a>
为 plugin-dev 的 marketplace 指南补充 <code>skipLfs</code> 选项说明，支持在 GitHub 简写与通用 Git URL 来源中跳过 Git LFS 下载，引用 #63035。文档类变更，无代码逻辑修改。</p>
<h2>功能需求趋势</h2>
<p>从今日活跃 Issues 可提炼 5 个主要方向：</p>
<table>
<thead>
<tr>
<th>方向</th>
<th>代表 Issues</th>
<th>社区诉求</th>
</tr>
</thead>
<tbody><tr>
<td>上下文管理</td>
<td>#27242、#34556、#6616</td>
<td>压缩后历史可回看、跨压缩持久记忆、上下文用量计算准确</td>
</tr>
<tr>
<td>TUI 交互体验</td>
<td>#18170、#18157、#26954</td>
<td>复制粘贴干净、快捷键兼容各终端、输出可完整展开</td>
</tr>
<tr>
<td>权限系统精细化</td>
<td>#27957、#12070、#10089</td>
<td>减少误报/可关闭规则、会话级权限真正持久、可强制拦截危险参数</td>
</tr>
<tr>
<td>Agent 基础设施</td>
<td>#26572、#26479</td>
<td>摆脱 tmux 强依赖、teammate 继承项目权限配置、支持更多终端/远程</td>
</tr>
<tr>
<td>MCP 生态稳定性</td>
<td>#25865、#27625</td>
<td>连接器参数保真、内置 MCP server 可靠连接</td>
</tr>
</tbody></table>
<h2>开发者关注点</h2>
<ol>
<li><strong>TUI 复制粘贴是当前最大痛点</strong>：#18170 以 286👍 居首，输出混入视觉缩进和行尾空格，直接影响将 Claude 结果移入编辑器或 IDE 的核心工作流。</li>
<li><strong>压缩后历史成了&quot;黑匣子&quot;</strong>：#27242 与 #34556 指向同一矛盾——完整数据保存在本地 <code>transcript.jsonl</code>，界面层却无任何途径访问。用户甚至因此自建了记忆持久化系统。</li>
<li><strong>权限确认误报损害自动化信心</strong>：引号命令告警（#27957）和 acceptEdits 不持久（#12070）共同导致高频重复确认，开发者对权限机制的可信度下降。</li>
<li><strong>SSH 远程场景仍显粗糙</strong>：#26997（加密密钥被阻塞）与 #25664（本地插件/MCP 路径被错误传递给远端导致挂起）表明远程连接的配置隔离和密钥处理未成熟。</li>
<li><strong>上下文用量显示可信度不足</strong>：#6616、#17959、#18159 等多条 Issue 指向 statusline 百分比与实际内部计算不一致，用户无法信任界面数据来做 compact 决策。</li>
<li><strong>终端生态兼容性欠账积累</strong>：Ghostty 快捷键（#18157）、macOS 全屏 TUI 下 Cmd+C 复制失效（#65844）、detached 窗口缩放问题（#62449）等多终端/桌面问题长期未闭环。</li>
</ol>
</details>

<details>
<summary><strong>OpenAI Codex</strong> — <a href="https://github.com/openai/codex">openai/codex</a></summary>

<h1>OpenAI Codex 社区动态日报 — 2026-08-20</h1>
<h2>今日速览</h2>
<ul>
<li>发布两个 Rust 新 alpha 版本（v0.149.0-alpha.2 / alpha.3），为 CLI 与桌面端持续迭代。</li>
<li>Windows 平台问题集中爆发：内置浏览器插件 Trusted RPC 初始化失败形成系列回归，涉及多个版本（#39136 评论已达 80 条）；<code>\\?\</code> 路径前缀导致会话归档失败也出现两个独立 Issue。</li>
<li>上游合入多项安全加固 PR：Git 命令不再被默认视为安全、自动插件 Git 操作将被隔离，降低供应链与仓库配置注入风险。</li>
</ul>
<h2>版本发布</h2>
<ul>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.2">rust-v0.149.0-alpha.2</a> — 2026-08-20 发布</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.3">rust-v0.149.0-alpha.3</a> — 2026-08-20 发布</li>
</ul>
<p>两个 alpha 的发布说明均为 <code>Release 0.149.0-alpha.x</code> 的占位格式，未附详细 changelog，具体变更需查看 tag 对应的 commit 记录。</p>
<h2>社区热点 Issues（10 条）</h2>
<ol>
<li><p><strong><a href="https://github.com/openai/codex/issues/39136">#39136 — Windows 内置浏览器插件初始化失败：Trusted RPC 依赖不在可信代码路径内</a></strong>
作者: Double-hhd | 评论: 80 | 👍: 42
影响范围极大：ChatGPT Plus 用户使用 26.814.41407 版本时，Codex 内置浏览器 UI 打开即失败，Trusted RPC 依赖路径校验不通过。同一问题在 #39399、#39387、#39486 中分别被不同用户复现，指向近期 Windows 浏览器插件回归。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/35050">#35050 — GPT-5.6 频繁序列化独立的 Code Mode 调用；显式批处理降低 27–45% 加权用量</a></strong>
作者: MakerOfToys | 评论: 25 | 👍: 40
用户通过对比测试发现 GPT-5.6 会把本可并行的工具调用改为串行执行，显式批处理能显著降低 token 消耗。社区高赞，属于模型行为 + 成本控制的核心关注。</p>
</li>
<li><p>**<a href="https://github.com/openai/codex/issues/39239">#39239 — Windows: <code>thread/archive</code> 在 <code>thread/resume</code> 后因 <code>\\?\</code> 路径失败</a>**
作者: shaded0 | 评论: 21 | 👍: 1
Resume 会话后续归档时报 <code>os error 2</code>。根因是 Windows verbatim path（<code>\\?\</code> 前缀）导致路径相等性判断失误，同一文件被排队两次。与 #39150 同源，属于 Windows 路径处理的系统性问题。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/33493">#33493 — 本地压缩 v2 保留无界 input_image 负载，导致反复自动压缩</a></strong>
作者: snrui | 评论: 18 | 👍: 4
长对话且图片较多的 Codex Desktop 线程陷入重复自动压缩循环，<code>gpt-5.6-sol</code> 下明显。影响重度多模态用户的上下文管理体验。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/27117">#27117 — Windows 独立更新从 pwsh 启动时继承 PSModulePath，导致 Get-FileHash 失败</a></strong>
作者: BlueOcean223 | 评论: 18 | 👍: 13
更新流程在 PowerShell 7 启动场景下错误继承 <code>PSModulePath</code>，使子进程 <code>powershell.exe</code> 中的 Get-FileHash 异常，最终更新失败。更新器健壮性问题的典型代表。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/39162">#39162 — macOS 打开已存在会话导致 ChatGPT 认证失效并跳转登录</a></strong>
作者: gaozhitw | 评论: 15 | 👍: 14
稳定复现路径：打开旧会话 → 登录态失效。用户确认 26.810.52044 正常、26.814.41407 触发，属桌面端回归问题，影响面广。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/23527">#23527 — Codex 移动端不显示连接 Mac 主机上的 SSH 远程项目</a></strong>
作者: jameBoy | 评论: 15 | 👍: 21
Mac 桌面端可正常使用 SSH 远程项目，但同一主机的移动端项目选择器中缺失这些项。远程开发链路在移动端不完整，iOS 用户诉求强烈。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/37104">#37104 — Windows WSL 集成终端在 PTY/WSL 启动前静默失败，侧边栏/底部面板无法打开</a></strong>
作者: cxzhong | 评论: 14 | 👍: 8
WSL 场景下集成终端完全不可用，且错误静默，应用层面没有提示。属于「Papercuts 2026」Windows 体验类问题。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/37029">#37029 — Windows Computer Use 在应用选择前因 EPERM lstat 失败</a></strong>
作者: Ahmedmabdallah484 | 评论: 13 | 👍: 4
Computer Use 在 Windows 上执行前即报 EPERM，沙箱与运行时文件访问权限存在冲突，无法进入应用选择界面。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/38754">#38754 — Windows Codex App 内本地 stdio MCP 服务被反复启动且不回收</a></strong>
作者: youngraison | 评论: 10 | 👍: 2
单个任务中每个新 turn 都会重新 spawn MCP server，进程不被正确 reap。对 MCP 生态开发者影响明显：资源消耗高、调试困难。</p>
</li>
</ol>
<h2>重要 PR 进展（10 条）</h2>
<ol>
<li><p><strong><a href="https://github.com/openai/codex/pull/31155">#31155 — 修复 shutdown 失败后释放 rollout writer</a></strong>
在 shutdown 后 rollout 持久化未完成时，终端会话与本地 store 之间的 live-writer lease 不再被错误保留，避免后续写入被阻塞。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39524">#39524 — 不再将 Git 命令视为固有安全</a></strong>
仓库配置可诱导只读 Git 命令执行 helper，因此移除 Unix/Windows 上 Git 命令的 known-safe 分类。安全边界收紧，降低供应链攻击面。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39520">#39520 — 隔离自动插件 Git 操作</a></strong>
后台 marketplace 与插件刷新不再继承项目级 Git 配置，防止配置重定向 remote 或在自动操作期间调用 Git helper。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39523">#39523 — 在首个 turn 之前持久化线程 section 移动</a></strong>
非临时线程在首个 turn 前没有持久化 rollout/preview，移动到 section 后会从 section 过滤列表中消失。该 PR 修复此数据一致性问题。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39514">#39514 — 物化 turn 摘要时使用存储的 item_type</a></strong>
改用持久化的 <code>item_type</code> 列选择 user/agent 摘要项，并在该列为空时回退到 <code>item_json</code> 类型，保证旧客户端写入的行仍可生成正确摘要。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39510">#39510 — 追踪内置控制工具的调用分析事件</a></strong>
为 <code>request_user_input</code>、<code>update_plan</code>、<code>view_image</code> 等内置控制工具新增 <code>codex_control_tool_call_event</code>，记录状态（完成/失败/拒绝/中断）与耗时元数据，提升可观测性。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39452">#39452 — 移除 async user messages 的 feature gate</a></strong>
当所选模型支持时，根代理直接开放 <code>send_user_message_async</code>；旧的 <code>send_async_message</code> 作为兼容 flag 保留，不再影响工具可用性。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39474">#39474 — 将 Guardian 扩展整合进 <code>codex-guardian-v2</code></a></strong>
统一 Guardian 线程生命周期与 subagent-spawn 上下文，通过单一扩展入口安装 lifecycle contributor 和异步风险评分器，减少冗余扩展点。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39493">#39493 — HeadTailBuffer 容量改为 const generic</a></strong>
将 <code>HeadTailBuffer</code> 参数化为 const <code>MAX_BYTES</code>，head/tail 预算从该值推导，生产环境默认容量保持一致，测试覆盖更聚焦。</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/31817">#31817 — 自动更新 models.json</a></strong>
GitHub Actions 自动提交模型清单更新，确保 CLI 与 App 能及时识别最新模型 ID 与能力元数据。</p>
</li>
</ol>
<h2>功能需求趋势</h2>
<ul>
<li><strong>Windows 平台稳定性成为最突出的社区诉求</strong>：Trusted RPC 路径校验、<code>\\?\</code> 路径前缀、沙箱 EPERM、WSL PTY、Schannel 凭据等系统性问题的反馈密度最高，大量 Issue 停留在 OPEN 状态且持续被复现。</li>
<li><strong>浏览器/Chrome 插件回归</strong>：多个 Windows 用户报告内置浏览器插件初始化失败，集中在 26.814.x 版本。Trusted code path 的同步与校验逻辑急需修复。</li>
<li><strong>成本与用量控制</strong>：GPT-5.6 的串行工具调用（#35050）与高频率 code-mode 轮询放大上下文（#32309）表明，社区希望 Codex 在模型行为变化时提供更透明的用量控制选项。</li>
<li><strong>MCP 生态稳定性</strong>：Windows 上 local stdio MCP server 的 spawn/reap 生命周期存在明显缺陷，限制重度 MCP 用户的使用。</li>
<li><strong>订阅与授权边界</strong>：围绕 auth 失效（#39162）、已购 credits 自动扣费（#28382）、banked resets 消失（#39577）的讨论说明用户对账户安全与配额控制高度敏感。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>Windows 是当前最大的痛点平台</strong>：浏览器插件、会话归档、沙箱执行、更新器、PTY 终端均有独立 Issue 且相互交叉，开发者建议官方设立 Windows 专项质量门禁。</li>
<li><strong>归档/会话恢复链路脆弱</strong>：<code>\\?\</code> 路径前缀导致归档失败（#39239/#39150）、压缩保留 input_image（#33493）、远程 compact 404（#38706）共同指向会话存储层需要更严格的跨平台测试。</li>
<li><strong>Trusted RPC 校验引发连锁回归</strong>：从浏览器插件到 bundled Browser service，多个组件在同一校验逻辑上失败，涉及 26.814.x 桌面版多个构建。</li>
<li><strong>Git 安全边界收紧受到肯定</strong>：社区对「Git 命令不再默认安全」和「隔离插件 Git 操作」的 PR 反应正面，认为这是对抗仓库配置投毒的正确方向。</li>
<li><strong>模型行为变化被直接关联到账单数字</strong>：#35050 中用户用加权用量对比证明 GPT-5.6 的串行化带来 27–45% 额外消耗，开发者希望官方发布模型行为变更说明与成本控制开关，而非让用户自行猜测。</li>
</ul>
</details>

<details>
<summary><strong>Gemini CLI</strong> — <a href="https://github.com/google-gemini/gemini-cli">google-gemini/gemini-cli</a></summary>

<h1>Gemini CLI 社区动态日报 — 2026-08-20</h1>
<h2>今日速览</h2>
<p>今日发布 v0.56.0 稳定版、v0.57.0-preview.0 预览版及一个 nightly 版本，重点修复 Cloud Workstations OAuth 流程与 IDE 连接目录匹配问题。社区讨论持续聚焦 subagent 状态误报、generalist agent 挂起等稳定性和信任机制问题；安全方面，多个 PR 集中修补 MCP 配置损坏时的 fail-open 漏洞。</p>
<h2>版本发布</h2>
<h3>v0.56.0（稳定版）</h3>
<p>正式稳定版发布，完整变更请见 <a href="https://github.com/google-gemini/gemini-cli/compare/v0.55.1...v0.56.0">v0.55.1...v0.56.0 对比</a>。</p>
<h3>v0.57.0-preview.0（预览版）</h3>
<ul>
<li><strong>Cloud Workstations OAuth 修复</strong>：动态解析代理重定向 URI，修复 OAuth 流程在 Cloud Workstations 环境下的失败问题（<a href="https://github.com/google-gemini/gemini-cli/pull/28688">#28688</a>）</li>
<li><strong>IDE 连接修复</strong>：解决 IDE 连接中目录不匹配被静默吞掉的问题，提升 VS Code 等 IDE 协作的可靠性</li>
</ul>
<h3>v0.56.0-nightly.20260820.ge90c63fa1（Nightly）</h3>
<ul>
<li>修复 core 层在工具调用或媒体内容后，空文本 turns 被丢弃的问题（<a href="https://github.com/google-gemini/gemini-cli/pull/28892">#28892</a>）</li>
</ul>
<h2>社区热点 Issues</h2>
<h3>1. [P1] Subagent MAX_TURNS 被误报为 GOAL 成功 — <a href="https://github.com/google-gemini/gemini-cli/issues/22323">#22323</a></h3>
<p><code>codebase_investigator</code> 子代理在达到最大轮次限制后仍然报告 <code>status: &quot;success&quot;</code> 和 <code>Termination Reason: &quot;GOAL&quot;</code>，而实际上它没有任何分析产出。12 条评论，2 👍。该 issue 处于 need-retesting，维护者正在关注此误导性问题。</p>
<h3>2. [P1] Generalist agent 无限挂起 — <a href="https://github.com/google-gemini/gemini-cli/issues/21409">#21409</a></h3>
<p>当 CLI 将任务 defer 给 generalist agent 时会无限期挂起，简单的文件夹创建操作也受影响，最长等待 1 小时仍未完成。8 条评论，8 👍。社区共鸣强烈，用户表示通过禁止模型使用子代理可绕过此问题。</p>
<h3>3. [P2] 零依赖 OS 沙箱化与 bash 意图路由 — <a href="https://github.com/google-gemini/gemini-cli/issues/19873">#19873</a></h3>
<p>利用 Gemini 3 模型天然的 bash 操作能力，希望通过零依赖沙箱化方式让模型安全地使用原生 POSIX 工具，在执行后增加意图路由。8 条评论，1 👍。这是涉及安全与能力释放的重要方向。</p>
<h3>4. [P2] Auto Memory 缺乏确定性脱敏与日志过重 — <a href="https://github.com/google-gemini/gemini-cli/issues/26525">#26525</a></h3>
<p>Auto Memory 将本地 transcript 原始内容发送给模型后才指示其脱敏，且服务端可能记录包含 skill 内容的高敏日志。4 条评论。引发对后台记忆提取隐私边界的讨论。</p>
<h3>5. [P1] Shell 命令执行后卡在 &quot;Waiting input&quot; — <a href="https://github.com/google-gemini/gemini-cli/issues/25166">#25166</a></h3>
<p>简单 CLI 命令执行完成后，终端仍显示该命令为活动状态并等待输入，必须手动中断。4 条评论，3 👍。该问题严重影响自动化工作流，涉及 core 层交互管理。</p>
<h3>6. [P2] AST-aware 文件读取与代码库映射评估 — <a href="https://github.com/google-gemini/gemini-cli/issues/22745">#22745</a></h3>
<p>EPIC 调研通过 AST 感知工具实现精确读取方法边界、导航代码，以减少 tokens 噪声和读取错位。7 条评论，1 👍。代表社区对上下文效率优化的强烈兴趣。</p>
<h3>7. [P2] 模型不主动使用自定义 skills 和 sub-agents — <a href="https://github.com/google-gemini/gemini-cli/issues/21968">#21968</a></h3>
<p>用户反馈 Gemini CLI 几乎不会主动使用已配置的 gradle、git 等自定义技能，即使任务高度相关，仍需显式指令。6 条评论。代理自主性问题引发维护者讨论。</p>
<h3>8. [P2] Auto Memory 对低信号 session 无限重试 — <a href="https://github.com/google-gemini/gemini-cli/issues/26522">#26522</a></h3>
<p>自动记忆系统对标记为低信号且未被读取的 session 永不标记为已处理，导致重复出现在待处理索引中并被反复重试。5 条评论。</p>
<h3>9. [P1] Browser 子代理在 Wayland 下失败 — <a href="https://github.com/google-gemini/gemini-cli/issues/21983">#21983</a></h3>
<p>浏览器子代理在 Wayland 会话中直接失败。4 条评论，1 👍。已标记 need-retesting，社区仍关注跨 Linux 显示协议的兼容性。</p>
<h3>10. [P2] Browser agent 需要自动 session 接管与锁恢复 — <a href="https://github.com/google-gemini/gemini-cli/issues/22232">#22232</a></h3>
<p>浏览器代理遇到持久化 profile 被锁时采用 fail-fast 策略，希望改为自动接管或恢复，提升长时任务的鲁棒性。4 条评论。</p>
<h2>重要 PR 进展</h2>
<h3>1. [P1] 修复 MCP enablement 配置损坏导致的 fail-open 漏洞 — <a href="https://github.com/google-gemini/gemini-cli/pull/28794">#28794</a></h3>
<p><code>mcp-server-enablement.json</code> 损坏时 <code>readConfig()</code> 返回空对象，导致所有 server 被默认启用并可能覆盖用户禁用配置，造成数据丢失风险。本 PR 修复该 fail-open 行为。相关修复见 <a href="https://github.com/google-gemini/gemini-cli/pull/28787">#28787</a>。</p>
<h3>2. [P1] VS Code IDE Companion stop() 挂起与 keep-alive 失败阈值修复 — <a href="https://github.com/google-gemini/gemini-cli/pull/28789">#28789</a></h3>
<p>修复 <code>IdeServer.stop()</code> 在存在活跃 MCP streaming 会话时无限挂起，以及 keep-alive 偶发失败导致的内存泄漏问题。</p>
<h3>3. 扩展环境变量注入需用户同意 — <a href="https://github.com/google-gemini/gemini-cli/pull/28863">#28863</a></h3>
<p>扩展更新可能绕过用户同意并向 MCP server 注入未授权环境变量。本 PR 将环境配置纳入同意字符串，并清理会影响运行时行为的环境变量。</p>
<h3>4. 子进程执行安全加固 — <a href="https://github.com/google-gemini/gemini-cli/pull/28898">#28898</a></h3>
<p>增强编排器子进程的安全与可靠性：阻止认证 token 泄漏至不可信工具环境，加固配置读取与 GitHub API 交互。</p>
<h3>5. 一致化 symlink 与 ignore 路径处理 — <a href="https://github.com/google-gemini/gemini-cli/pull/28915">#28915</a></h3>
<p>确保 <code>.geminiignore</code> 和 <code>.gitignore</code> 对字面路径与解析后的规范路径一致评估，消除工具因 symlink 产生的行为差异。</p>
<h3>6. Whisper 转写 stdout 分块缓冲修复 — <a href="https://github.com/google-gemini/gemini-cli/pull/28916">#28916</a></h3>
<p>修复 <code>WhisperTranscriptionProvider</code> 中时间戳行被 stdout <code>data</code> 事件切分后丢失的问题，保证本地语音模式转写完整。对应 issue <a href="https://github.com/google-gemini/gemini-cli/issues/28648">#28648</a>。</p>
<h3>7. Whisper 模型原子下载 — <a href="https://github.com/google-gemini/gemini-cli/pull/28917">#28917</a></h3>
<p><code>downloadModel()</code> 改为写入临时文件、校验长度、处理流错误，并在成功后原子重命名，避免中断下载导致模型文件损坏。对应 issue <a href="https://github.com/google-gemini/gemini-cli/issues/28644">#28644</a>。</p>
<h3>8. 重试 nudge 注入 conversation 以保留前缀缓存 — <a href="https://github.com/google-gemini/gemini-cli/pull/28914">#28914</a></h3>
<p>将 on-retry 提示信息从 <code>systemInstruction</code> 移至 <code>contents</code> 末尾，既保留静态 prompt 前缀缓存，又确保模型在生成前立即看到恢复提示。对应 issue <a href="https://github.com/google-gemini/gemini-cli/issues/28909">#28909</a>。</p>
<h3>9. GCS 轨迹日志与 artifact 保存 — <a href="https://github.com/google-gemini/gemini-cli/pull/28922">#28922</a></h3>
<p>为生产与评估运行实现 GCS 轨迹日志器和调试 artifact 存储，支持 coding、evaluation、repair loop 的流式分块与 diff 产物持久化。</p>
<h3>10. 行为评估扩展：skills 激活与 URL 抓取 — <a href="https://github.com/google-gemini/gemini-cli/pull/28788">#28788</a></h3>
<p>新增 <code>activate_skill</code> 与 <code>web_fetch</code> 行为评估，修复 EDK 报告聚合器对未执行用例的过滤逻辑，并增强本地评估环境的 Windows 兼容性。</p>
<h2>功能需求趋势</h2>
<ol>
<li><p><strong>代理（Agent）可靠性与自主性</strong></p>
<ul>
<li>Subagent 错误报告与恢复逻辑（<a href="https://github.com/google-gemini/gemini-cli/issues/22323">#22323</a>、<a href="https://github.com/google-gemini/gemini-cli/issues/21409">#21409</a>）</li>
<li>更主动地使用自定义 skills 和 sub-agents（<a href="https://github.com/google-gemini/gemini-cli/issues/21968">#21968</a>）</li>
<li>Browser agent 的 session 恢复能力（<a href="https://github.com/google-gemini/gemini-cli/issues/22232">#22232</a>）</li>
</ul>
</li>
<li><p><strong>上下文效率与 Token 优化</strong></p>
<ul>
<li>AST-aware 读取与代码库映射（<a href="https://github.com/google-gemini/gemini-cli/issues/22745">#22745</a>、<a href="https://github.com/google-gemini/gemini-cli/issues/22746">#22746</a>）</li>
<li>Tactful Extraction 实现手术式低 token 读取（<a href="https://github.com/google-gemini/gemini-cli/issues/19561">#19561</a>）</li>
<li>重试提示与前缀缓存协同优化（<a href="https://github.com/google-gemini/gemini-cli/pull/28914">#28914</a>）</li>
</ul>
</li>
<li><p><strong>安全与信任机制强化</strong></p>
<ul>
<li>MCP 配置损坏时的 fail-closed 行为（<a href="https://github.com/google-gemini/gemini-cli/pull/28787">#28787</a>、<a href="https://github.com/google-gemini/gemini-cli/pull/28794">#28794</a>）</li>
<li>子进程与扩展环境变量隔离（<a href="https://github.com/google-gemini/gemini-cli/pull/28863">#28863</a>、<a href="https://github.com/google-gemini/gemini-cli/pull/28898">#28898</a>）</li>
<li>抑制模型破坏性命令（<a href="https://github.com/google-gemini/gemini-cli/issues/22672">#22672</a>）</li>
</ul>
</li>
<li><p><strong>记忆系统健壮化与隐私</strong></p>
<ul>
<li>Auto Memory 脱敏前置化与日志收敛（<a href="https://github.com/google-gemini/gemini-cli/issues/26525">#26525</a>）</li>
<li>低信号 session 不无限重试（<a href="https://github.com/google-gemini/gemini-cli/issues/26522">#26522</a>）</li>
<li>无效 memory patch 隔离或暴露（<a href="https://github.com/google-gemini/gemini-cli/issues/26523">#26523</a>）</li>
</ul>
</li>
<li><p><strong>IDE 与云端环境集成</strong></p>
<ul>
<li>Cloud Workstations OAuth 支持（<a href="https://github.com/google-gemini/gemini-cli/pull/28688">#28688</a>）</li>
<li>IDE 目录匹配与连接稳定性（<a href="https://github.com/google-gemini/gemini-cli/pull/28789">#28789</a>、<a href="https://github.com/google-gemini/gemini-cli/pull/28922">#28922</a>）</li>
</ul>
</li>
</ol>
<h2>开发者关注点</h2>
<ul>
<li><strong>Subagent 行为不可预测</strong>：开发者反复反馈子代理要么挂起、要么谎报成功，且不主动使用已配置的 skills，严重削弱了对多代理工作流的信任。</li>
<li><strong>Shell 执行偶发卡死</strong>：命令完成但状态仍为 &quot;Waiting input&quot;（<a href="https://github.com/google-gemini/gemini-cli/issues/25166">#25166</a>），以及交互式 prompt（如 vite 创建）卡住（<a href="https://github.com/google-gemini/gemini-cli/issues/22465">#22465</a>），是自动化场景的主要障碍。</li>
<li><strong>配置损坏导致安全降级</strong>：MCP 配置 JSON 损坏后 fail-open 的默认行为引起安全担忧，开发者期待更稳妥的配置失效处理。</li>
<li><strong>记忆系统隐私与可靠性</strong>：后台 Auto Memory 在模型上下文脱敏前就读取全量 transcript 的做法受到质疑，且低信号 session 反复重试浪费资源。</li>
<li><strong>Browser agent 环境兼容性</strong>：Wayland 下的失败与持久化 profile 锁问题仍是高频痛点，影响浏览器自动化在 Linux 桌面端的落地。</li>
<li><strong>上下文管理与工具数量限制</strong>：超过 128/400 个工具时触发 400 错误（<a href="https://github.com/google-gemini/gemini-cli/issues/24246">#24246</a>），以及模型到处创建临时脚本导致工作区污染（<a href="https://github.com/google-gemini/gemini-cli/issues/23571">#23571</a>），是 token 控制之外另一层实操困扰。</li>
</ul>
</details>

<details>
<summary><strong>GitHub Copilot CLI</strong> — <a href="https://github.com/github/copilot-cli">github/copilot-cli</a></summary>

<h1>GitHub Copilot CLI 社区动态日报 — 2026-08-20</h1>
<h2>今日速览</h2>
<p>昨日连发三个 prerelease（1.0.81-3/4/5），其中 1.0.81-5 修复了 pending 行残留问题。社区层面，Sandbox 强制启用与权限绕过（ACP 模式、非交互模式）成为最激烈的争论点；MCP OAuth 认证问题连续两个版本未修复，且有新报障指向 1.0.81 协议初始化兼容性回归。</p>
<h2>版本发布（过去 24 小时）</h2>
<ul>
<li><strong><a href="https://github.com/github/copilot-cli/releases/tag/v1.0.81-5">v1.0.81-5</a></strong> — 修复 agent 工作期间发送 prompt 后，第二份 prompt 残留为 <code>(pending)</code> 且无法清除的问题。</li>
<li><strong>v1.0.81-4</strong> / <strong>v1.0.81-3</strong> — 官方仅标注 “Fixes and changes”，未提供详细变更说明。</li>
</ul>
<h2>社区热点 Issues（10 个）</h2>
<ol>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4537">#4537 ACP 模式自动批准工具调用（回归 #845）</a></strong>
1.0.81-1 起 <code>--acp</code> 模式不再发送 <code>session/request_permission</code>，shell 命令、文件编辑和删除全部无人值守执行。严重安全回归，今日新提交，暂无评论但风险极高。</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4480">#4480 Atlassian MCP OAuth 失败（1.0.79 回归）</a></strong>
连接 Atlassian 远程 MCP server 时 OAuth 发现阶段报 RFC 8414 §3.3 issuer 不匹配。6 👍 / 6 评论，大量用户受第三方 MCP 认证影响。</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4490">#4490 Atlassian MCP OAuth 在 1.0.80 仍失败</a></strong>
与 #4480 同根因，1.0.80 仍未修复，1.0.78 尚正常。说明该回归已跨两个版本。</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4522">#4522 1.0.81 在托管策略未决时强制启用沙箱</a></strong>
即使用户显式配置 <code>sandbox.enabled=false</code>，只要服务端 managed policy 暂时无法确定，本地沙箱仍被强制开启。7 👍，企业用户抱怨配置被无视。</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4524">#4524 Sandbox 导致 git 不可用（Windows）</a></strong>
enforced-sandbox 更新后即使放行整个工作目录，git 操作仍被阻断，agent 无法正常工作流。</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4390">#4390 组织启用的模型缺失（Claude Sonnet 5/Opus 5、Kimi K3）</a></strong>
Copilot Business 组织显式启用的 Anthropic 模型在 CLI 模型目录中不可用。7 👍 / 15 评论，已经关闭但影响面大。</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4525">#4525 1.0.81-1 先发 <code>server/discover</code> 再发 legacy <code>initialize</code> 导致 -32022</a></strong>
对 Python MCP SDK 2.0.0 双协议 runner 的 stdio server，CLI 发起现代 <code>server/discover</code> 后又发送旧版 <code>initialize</code>，破坏 MCP 协议协商流程。</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4527">#4527 GHEC 数据驻留租户下 <code>copilot -p</code> 401</a></strong>
1.0.81-1 起 prompt 模式模型目录请求错误打到 <code>api.githubcopilot.com</code> 而非租户端点；交互模式同凭据正常。企业数据驻留场景被完全阻断。</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4528">#4528 非交互模式绕过 <code>disableBypassPermissionsMode</code></a></strong>
<code>-p</code> 模式加 <code>--allow-all</code>/<code>--yolo</code> 可无视 managed settings 中的权限禁用策略直接放行，合规性风险明显。</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4533">#4533 TUI 在并行子代理启动后停止消费事件</a></strong>
1.0.81-4/5 上并行 subagent 一启动，终端 UI 即停止响应输入与滚动，Rust runtime 仍在后台运行。UI 死锁类问题会被用户直接感知。</p>
</li>
</ol>
<h2>重要 PR 进展</h2>
<p>过去 24 小时数据源显示无新增或合并的 Pull Requests，暂无进展可汇报。</p>
<h2>功能需求趋势</h2>
<ul>
<li><strong>MCP 生态兼容性</strong>：OAuth 认证（RFC 8414 issuer 校验）、协议版本协商（<code>server/discover</code> vs <code>initialize</code>）、图片内容块透传、第三方 MCP 服务器稳定性是当前最集中的议题。</li>
<li><strong>沙箱/权限体系可控性</strong>：社区强烈要求沙箱可彻底关闭、可按进程类型（JVM、git）精细授权，并且不被服务端策略覆盖。</li>
<li><strong>企业级配置与合规</strong>：模型目录正确同步、GHEC 数据驻留端点、managed settings 对非交互模式和 ACP 模式生效。</li>
<li><strong>状态持久化</strong>：跨会话保留 reasoning effort、压缩后上下文长期记忆、<code>store_memory</code> 可用性。</li>
<li><strong>终端交互稳定性</strong>：退格键行为、焦点事件丢失、pending 行累积、TUI 死锁等输入与渲染问题。</li>
<li><strong>更新机制可预测性</strong>：<code>autoUpdate:false</code> 应真正生效，prerelease 缓存不应覆盖 stable 安装。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>沙箱策略过于强制</strong>：显式禁用无效、策略未决时强制执行、误伤 git 和 JVM 子进程，是最近几天最集中的开发者痛点。</li>
<li><strong>MCP OAuth 连续版本回归</strong>：Atlassian 等第三方 MCP 用户在 1.0.79/1.0.80 连续受阻，信任成本上升。</li>
<li><strong>权限绕过安全风险</strong>：ACP 模式自动放行工具调用、非交互模式绕过 managed settings，企业管理员可能无法强制审计。</li>
<li><strong>更新机制混乱</strong>：npm stable 安装被 <code>~/.copilot</code> 下缓存的 prerelease 抢占，且无法通过配置关闭。</li>
<li><strong>企业数据驻留支持不完整</strong>：prompt 模式请求走错域名导致 401，与交互模式行为不一致。</li>
</ul>
</details>

<details>
<summary><strong>Kimi Code CLI</strong> — <a href="https://github.com/MoonshotAI/kimi-cli">MoonshotAI/kimi-cli</a></summary>

<h1>Kimi Code CLI 社区动态日报 2026-08-20</h1>
<h2>今日速览</h2>
<p>今日社区无新版本发布，PR 也无更新。唯一值得关注的动态是 Issue #2609 被关闭，该问题报告了 ACP（Agent Client Protocol）环境下 <code>Grep</code>/<code>Glob</code> 工具被限制，仅在允许交互式 Bash 的进程内可用，导致 Zed 等 ACP 客户端用户遇到工具调用失败。该问题从创建到关闭仅不到一天，可能已由官方快速响应或定位为设计行为。</p>
<h2>版本发布</h2>
<p>今日无新版本发布。</p>
<h2>社区热点 Issues</h2>
<h3>1. <a href="https://github.com/MoonshotAI/kimi-cli/issues/2609">#2609 [ACP] Grep/Glob blocked: “ACP runtime only supports interactive Bash tool processes”; Bash intermittently reports “ACP terminal capability is unavailable”</a></h3>
<ul>
<li><strong>作者</strong>：SolomonFang</li>
<li><strong>创建/更新</strong>：2026-08-19 / 2026-08-19</li>
<li><strong>状态</strong>：已关闭（CLOSED）</li>
<li><strong>评论/赞</strong>：0 / 0</li>
</ul>
<p><strong>为什么重要</strong><br>这是今日唯一更新的 Issue，直接暴露了 <code>kimi acp</code> 在 ACP 模式下的关键限制：<code>Grep</code> 和 <code>Glob</code> 工具几乎必然失败，提示“ACP runtime only supports interactive Bash tool processes”。而 <code>Read</code> 工具正常工作。该问题影响使用 Zed 等 ACP 客户端的用户，说明非交互式只读工具在受限运行环境中无法使用，可能打断了依赖代码搜索的自动化流程。</p>
<p><strong>社区反应</strong><br>目前无评论和点赞，但由于 issue 在 24 小时内即被关闭，社区尚未形成讨论。关闭原因可能是官方确认这是当前 ACP 运行时设计边界，或者是补丁快速合入前的临时关闭，需要后续进一步观察。</p>
<h2>重要 PR 进展</h2>
<p>今日无重要 PR 更新。</p>
<h2>功能需求趋势</h2>
<p>基于当前仅有的 Issue，可以观察到以下社区关注点：</p>
<ul>
<li><strong>ACP 模式工具能力边界</strong>：用户希望 <code>Grep</code>/<code>Glob</code> 这类无需交互的只读工具在 ACP runtime 中也能正常工作，而不是被强制要求使用交互式 Bash。</li>
<li><strong>IDE 集成场景的可靠性</strong>：问题出现在 macOS 上的 Zed 通过 <code>kimi acp</code> 调用的过程，反映社区对非 VS Code 编辑器的支持质量有期待，尤其需要保证基础搜索工具不因 runtime 模式而失效。</li>
<li><strong>错误信息可观测性</strong>：Bash 间歇性报告“ACP terminal capability is unavailable”，说明错误提示不够稳定和可解释，社区期望更明确的失败原因和应对指引。</li>
</ul>
<h2>开发者关注点</h2>
<ul>
<li><strong>ACP 模式下工具调用失败是当前最大痛点</strong>：内置 <code>Grep</code> 和 <code>Glob</code> 被硬性拒绝，对依赖只读搜索的编码辅助场景影响明显。</li>
<li><strong>希望提供配置开关或更精细的权限策略</strong>：让开发者能够选择是否允许在 ACP runtime 中执行非交互式 Bash 工具，而不是直接一刀切。</li>
<li><strong>错误处理与降级方案</strong>：出现“terminal capability unavailable”时，应该给出备用建议（例如使用 <code>Read</code> 还是修改客户端配置），而不是让用户自行排查。</li>
</ul>
</details>

<details>
<summary><strong>OpenCode</strong> — <a href="https://github.com/anomalyco/opencode">anomalyco/opencode</a></summary>

<h1>OpenCode 社区动态日报 — 2026-08-20</h1>
<h2>今日速览</h2>
<p>过去 24 小时无新版本发布，但社区提交活跃：18 个 Issue 更新、50 个 PR 更新。焦点集中在 TUI 稳定性（粘贴失效、文本丢失、资源泄漏）、AI 模型兼容性（gpt-5.6 系列在 OpenCode Go 上频发错误）、以及性能问题（30GB 数据库膨胀、/tmp 填充导致启动失败）。</p>
<h2>社区热点 Issues</h2>
<p><strong>1. [2.0] TUI：每次启动向 /tmp 泄漏约 21MB .so 文件，填满 tmpfs 后导致 TUI 无法启动</strong>
<code>#42700</code> | 作者: jsongalvez | 评论: 3
TUI 每次启动都会在临时目录写入一个约 21MB 的 .so 文件且从不清理，多次启动后直接填满 tmpfs，随后以 OpenTUI 库加载错误告终。对于长期使用 TUI 的开发者是一个确定性故障，且清理成本极高。
🔗 <a href="https://github.com/anomalyco/opencode/issues/42700">https://github.com/anomalyco/opencode/issues/42700</a></p>
<p><strong>2. [2.0] subagents: gpt-5.6-sol-fast 因注入 prompt_cache_retention 而失败</strong>
<code>#43367</code> | 作者: brandon-julio-t | 评论: 7 | 👍: 10（今日最高赞）
使用 <code>openai/gpt-5.6-sol-fast</code> 的 subagent 在工具执行后停止运行，原因是 OpenCode 发送了该模型不支持的 <code>prompt_cache_retention</code> 参数。三个独立 review subagent 在三分钟内陆续失败，影响面广且难以排查。
🔗 <a href="https://github.com/anomalyco/opencode/issues/43367">https://github.com/anomalyco/opencode/issues/43367</a></p>
<p><strong>3. OOM 与约 30GB 数据库：工作区大文件差异被完整序列化到每次 message.updated 事件</strong>
<code>#43551</code> | 作者: isHarryh | 评论: 1
当工作区内的文本文件在会话期间持续增长（作者场景中两个日志文件分别达 292MB 和 407MB），OpenCode 将完整文件差异嵌入消息摘要，且每次 <code>message.updated</code> 事件都重新序列化，最终导致 OOM 和数据库膨胀至约 30GB。属于极端但真实的性能陷阱。
🔗 <a href="https://github.com/anomalyco/opencode/issues/43551">https://github.com/anomalyco/opencode/issues/43551</a></p>
<p><strong>4. 自动更新器破坏全局 npm 安装：stub 二进制 + 缺失 shim，并遗留挂起的 npm 进程</strong>
<code>#42291</code> | 作者: hyp-type | 评论: 3
Windows 11 上通过 <code>npm install -g opencode-ai</code> 安装后，自动更新器在每次启动时可能将全局安装替换为 stub 二进制、丢失 shim，并留下无法终止的 npm 进程。对 npm 用户而言，一次更新即可永久破坏安装环境。
🔗 <a href="https://github.com/anomalyco/opencode/issues/42291">https://github.com/anomalyco/opencode/issues/42291</a></p>
<p><strong>5. OpenCode Go：gpt-5.6-luna 返回空响应 / 403 错误</strong>
<code>#43565</code> | 作者: misaka11033 | 评论: 1
通过 Claude Code CLI 接入 OpenCode Go 端点使用 <code>gpt-5.6-luna</code> 时返回空响应或 403。与该系列另一个模型问题（#43367）叠加，说明 gpt-5.6 系在 OpenCode Go 上的兼容性仍是短板。
🔗 <a href="https://github.com/anomalyco/opencode/issues/43565">https://github.com/anomalyco/opencode/issues/43565</a></p>
<p><strong>6. [2.0] TUI：提交 POST 进行中输入的内容被静默销毁</strong>
<code>#43563</code> | 作者: kitlangton | 评论: 0
通过种子化网络故障注入测试发现（seeds 1/7/99 均能复现）：当 <code>session.prompt</code> POST 尚未返回时，用户输入的内容会被静默清除，因为 composer 只在请求 resolve 后才清空。属于数据丢失级缺陷。
🔗 <a href="https://github.com/anomalyco/opencode/issues/43563">https://github.com/anomalyco/opencode/issues/43563</a></p>
<p><strong>7. [2.0] server: workspace=global 请求全部返回 HTTP 500</strong>
<code>#42532</code> | 作者: wujiachen0727 | 评论: 2
桌面客户端几乎所有与 workspace 相关的 API 在 workspace 为 <code>global</code> 时返回 <code>Path is not absolute: global</code>，导致界面不断弹出“无法重新加载 global”的 toast。核心用户路径（全局配置/对话管理）完全不可用。
🔗 <a href="https://github.com/anomalyco/opencode/issues/42532">https://github.com/anomalyco/opencode/issues/42532</a></p>
<p><strong>8. Sidecar 60 秒内未就绪（桌面端启动失败）</strong>
<code>#43568</code> / <code>#43559</code> | 作者: rpb24 / vilesupe | 评论: 各 1
两位用户在同一天报告相同错误：<code>Sidecar did not become ready within 60000ms</code>，涉及 <code>@opencode-aidesktop</code> 的 <code>app.asar</code> 侧车进程。桌面端存在启动可靠性问题，值得优先排查。
🔗 <a href="https://github.com/anomalyco/opencode/issues/43568">https://github.com/anomalyco/opencode/issues/43568</a> / <a href="https://github.com/anomalyco/opencode/issues/43559">https://github.com/anomalyco/opencode/issues/43559</a></p>
<p><strong>9. [2.0] TUI：无法关闭当前活跃会话的标签页</strong>
<code>#43553</code> | 作者: austin-thesing | 评论: 1
点击 X 后标签页短暂消失又立即恢复，重启后依然存在；同一项目内其他标签页可正常关闭。属于 TUI 会话管理的基础交互缺陷。
🔗 <a href="https://github.com/anomalyco/opencode/issues/43553">https://github.com/anomalyco/opencode/issues/43553</a></p>
<p><strong>10. [FEATURE] 桌面应用内实现消息搜索（Cmd+F / Ctrl+F）</strong>
<code>#19143</code> | 作者: mpiosik | 评论: 8 | 👍: 7
自 3 月提出至今仍在更新，是 Issue 列表中生命周期最长的功能请求。长会话中无法快速定位历史消息，用户迫切需要类似编辑器的搜索能力。
🔗 <a href="https://github.com/anomalyco/opencode/issues/19143">https://github.com/anomalyco/opencode/issues/19143</a></p>
<hr>
<h2>重要 PR 进展</h2>
<p><strong>1. fix(core): 正确处理外来类型工具调用失败（避免永久 pending）</strong>
<code>#43576</code> | 作者: kitlangton | 状态: OPEN
插件工具抛出非 <code>Tool.Error</code> 的外来类型错误时，工具调用会永远处于 running 状态，spinner 不消失而步骤继续执行。该 PR 将此类失败正式结算为失败而不是丢弃。
🔗 <a href="https://github.com/anomalyco/opencode/pull/43576">https://github.com/anomalyco/opencode/pull/43576</a></p>
<p><strong>2. feat(core): 为已配置模型添加保守的变体后备方案</strong>
<code>#43574</code> | 作者: rekram1-node | 状态: OPEN
当用户配置新模型而未指定 <code>variants</code> 时，自动生成包感知的保守 variants；同时保留 <code>variants: []</code> 作为显式退出机制。覆盖 AI SDK、OpenAI、Azure、Google、Vertex、Anthropic 等提供方。
🔗 <a href="https://github.com/anomalyco/opencode/pull/43574">https://github.com/anomalyco/opencode/pull/43574</a></p>
<p><strong>3. fix(tui): 停止为每条 transcript 行注册一个 resize 监听器</strong>
<code>#43562</code> | 作者: kitlangton | 状态: OPEN
监听器数量随 transcript 长度线性增长，触发 Bun 的 <code>MaxListeners</code> 警告——大约 4 条 prompt 后就会出现，长会话中可达数十甚至更多。这是 TUI 长期会话内存/事件泄漏的重要修复。
🔗 <a href="https://github.com/anomalyco/opencode/pull/43562">https://github.com/anomalyco/opencode/pull/43562</a></p>
<p><strong>4. fix(ai): 结算 pending 的 Responses 工具调用</strong>
<code>#43575</code> | 作者: rekram1-node | 状态: CLOSED
当 Responses 流在未发出 <code>response.output_item.done</code> 的情况下成功结束时，现在会先结算挂起的函数调用，再走既有工具输入路径完成步骤，避免会话卡死。
🔗 <a href="https://github.com/anomalyco/opencode/pull/43575">https://github.com/anomalyco/opencode/pull/43575</a></p>
<p><strong>5. refactor(ai): 移除模型能力限制</strong>
<code>#43581</code> | 作者: rekram1-node | 状态: OPEN
从 AI 模型、路由和 provider-package 默认值中移除模型能力上限，停止将 Core catalog 限制投影到 AI provider 设置中；Anthropic Messages 默认 <code>max_tokens</code> 改为 32K。
🔗 <a href="https://github.com/anomalyco/opencode/pull/43581">https://github.com/anomalyco/opencode/pull/43581</a></p>
<p><strong>6. feat(plugin): 为插件添加 HTTP 路由（webhook 端点）支持</strong>
<code>#43499</code> | 作者: minderm | 状态: CLOSED
为 OpenCode server 插件新增 HTTP 路由能力，允许插件暴露 webhook 端点。关闭 #41362，是插件系统的重要扩展。
🔗 <a href="https://github.com/anomalyco/opencode/pull/43499">https://github.com/anomalyco/opencode/pull/43499</a></p>
<p><strong>7. fix(tui): 展示加密推理状态</strong>
<code>#43578</code> | 作者: opencode-agent[bot] | 状态: OPEN
当推理部分包含不透明 provider 元数据但没有可读文本时，不再渲染成空白；完成后展示为 <code>Thought · &lt;duration&gt; · encrypted</code>，保留交互性并如实反映加密推理的存在。
🔗 <a href="https://github.com/anomalyco/opencode/pull/43578">https://github.com/anomalyco/opencode/pull/43578</a></p>
<p><strong>8. feat(desktop): 优化冷启动开发流程（17.4s → 6.4s）</strong>
<code>#42722</code> | 作者: Hona | 状态: OPEN
将 desktop 冷启动中位数从 17,422ms 降至约 6.4s，经过 rebase 到当前 V2 架构后仍保持约 2.7 倍加速。对桌面端开发者体验是一次显著改进。
🔗 <a href="https://github.com/anomalyco/opencode/pull/42722">https://github.com/anomalyco/opencode/pull/42722</a></p>
<p><strong>9. feat(ai): 将流式拒答（refusal）保留为可见文本</strong>
<code>#43343</code> | 作者: rekram1-node | 状态: OPEN
OpenAI Chat 的 <code>delta.refusal</code> 以及 Responses 的 <code>response.refusal.delta/done</code> 现在会作为普通助手文本展示，而不是静默丢弃。有利于用户感知模型拒绝行为。
🔗 <a href="https://github.com/anomalyco/opencode/pull/43343">https://github.com/anomalyco/opencode/pull/43343</a></p>
<p><strong>10. feat(stats): 合并 Free 与 Go 用量统计</strong>
<code>#43577</code> | 作者: opencode-agent[bot] | 状态: CLOSED（含后续 <code>#43580</code> 修正文案）
将 Free 数据行纳入现有 Go 作用域的统计查询，并经过同一聚合路径输出，应用数据结构和对外文案保持不变。
🔗 <a href="https://github.com/anomalyco/opencode/pull/43577">https://github.com/anomalyco/opencode/pull/43577</a></p>
<p><strong>其他值得关注的 PR 进展：</strong></p>
<ul>
<li><code>#43567</code> — 将 Effect 升级至 rc.110，统一 workspace 依赖。</li>
<li><code>#43569</code> ~ <code>#43573</code> — 系列重构（kitlangton）：使用 Effect <code>Latch</code> 替换手写的 <code>Deferred</code> 信号门，覆盖插件 supervisor、MCP 启动、server 关停、renderer 关停、shell 输出门等场景。</li>
<li><code>#43579</code> — 桌面端从活跃目录解析分支，对齐 V2 TUI 的 location-first 行为。</li>
<li><code>#32370</code> — Linux 主剪贴板支持仍在持续更新（<code>linux_clipboard_selection</code> 配置项）。</li>
</ul>
<p>🔗 <a href="https://github.com/anomalyco/opencode/pulls">https://github.com/anomalyco/opencode/pulls</a></p>
<hr>
<h2>功能需求趋势</h2>
<ol>
<li><strong>TUI/桌面端交互修复成为绝对主线</strong> — 今日 18 个 Issue 中超过半数指向 TUI/桌面端问题：粘贴失效（#43241、#43233）、文本静默丢失（#43563）、标签页无法关闭（#43553）、Sidecar 启动超时（#43568、#43559）等。2.0 版本的终端 UI 稳定性是社区当前最大的痛点。</li>
<li><strong>gpt-5.6 系列模型兼容性</strong> — <code>gpt-5.6-sol-fast</code> 与 <code>gpt-5.6-luna</code> 在 OpenCode 上分别出现参数注入错误和空响应/403（#43367、#43565、#43557），新模型支持节奏快但质量跟踪不足，社区反应强烈。</li>
<li><strong>资源管理与性能治理</strong> — 从 /tmp 泄漏（#42700）、30GB 数据库膨胀（#43551）、启动时间优化（#42722）、到 resize 监听器泄漏（#43562），性能问题是贯穿 Issue 与 PR 的共同主题。</li>
<li><strong>消息/会话检索能力</strong> — #19143 的桌面消息搜索请求持续获得关注（8 评论、7 👍），长会话场景下用户对内容可发现性的需求明确。</li>
<li><strong>插件系统能力扩展</strong> — #43499 为插件引入 HTTP 路由/webhook 支持，插件生态正在从“工具调用”向“服务端能力”延伸。</li>
</ol>
<hr>
<h2>开发者关注点</h2>
<ul>
<li><strong>桌面端 Sidecar 启动超时集中爆发</strong>：一天内两名独立用户报告完全相同的 <code>Sidecar did not become ready within 60000ms</code> 错误（#43568、#43559），且均被标记为 <code>needs:compliance</code>，桌面版发布质量需要复盘。</li>
<li><strong>AI 模型接入的“隐性破坏”</strong>：多个问题来自 OpenCode 自动注入模型不支持参数（如 <code>prompt_cache_retention</code>）或加密内容校验失败（#43557），开发者倾向于认为这是 OpenCode 的兼容层责任，而非模型问题。</li>
<li><strong>数据丢失的零容忍</strong>：TUI 中“请求发送中输入被静默抹掉”（#43563）虽然是网络故障注入测试发现的边缘场景，但开发者在反馈中认为这是“数据丢失级别”的严重缺陷，社区会以极高优先级看待。</li>
<li><strong>自动更新器的信任危机</strong>：npm 全局安装被 stub 二进制破坏并遗留挂起进程（#42291）一旦规模化触达用户，对更新机制的信任成本很高。</li>
<li><strong>结构性重构开始回归</strong>：多位贡献者（kitlangton、rekram1-node）正在推动将手写 <code>Deferred</code> 模式替换为 Effect <code>Latch</code>、移除模型能力限制等底层清理，说明社区在追赶功能的同时也在强调代码基础的可维护性。</li>
</ul>
<hr>
<p><em>本日报数据来自 GitHub: anomalyco/opencode，统计区间为 2026-08-19 至 2026-08-20。</em></p>
</details>

<details>
<summary><strong>Qwen Code</strong> — <a href="https://github.com/QwenLM/qwen-code">QwenLM/qwen-code</a></summary>

<h1>Qwen Code 社区动态日报 — 2026-08-20</h1>
<h2>今日速览</h2>
<p>今日 Qwen Code 完成 v0.21.14 的端到端验证发布（SWE-bench Verified 500/500 全数通过，Terminal-Bench 2.0 得分 89）。社区侧聚焦稳定性与渠道集成：Web Shell 剪贴板在非 localhost HTTP 场景失效的问题获得修复 PR，ACP 多会话日志串扰被报告为 P2 bug，DingTalk 引用消息静默丢失问题同步出现 issue 与修复 PR。</p>
<h2>版本发布</h2>
<p><strong>dsw-eas-full-20260820-r1</strong>（对应 v0.21.14）</p>
<ul>
<li>全链路端到端验证通过：SWE-bench Verified 500 条全部成功（500/500）、Release 回写、Terminal-Bench 2.0 共 89 项测试及最终回写。</li>
<li>前序验证版本 <code>dsw-eas-full-20260819-r1</code> 状态一致，均为 <strong>SUCCEEDED</strong>。</li>
<li>当前共梳理 6 条活跃 issue（其中 2 条为今日新增 P2 bug），50 条 PR 在过去 24 小时内有更新。</li>
</ul>
<h2>社区热点 Issues</h2>
<p>今日共 6 条更新，按关注度排列如下：</p>
<ol>
<li><p><strong>#9485 Web Shell 复制按钮在非 localhost HTTP 场景下失效</strong> <code>[P2/bug, category/ui]</code>
<a href="https://github.com/QwenLM/qwen-code/issues/9485">https://github.com/QwenLM/qwen-code/issues/9485</a></p>
<ul>
<li>daemon 在远程 Linux 机器上运行时，通过 <code>http://&lt;remote-ip&gt;:4170</code> 打开 Web Shell，所有复制按钮报 <code>Clipboard API is not available</code>。</li>
<li><strong>社区反应</strong>：4 条评论，为今日讨论最活跃的 issue，同一作者已于当日提交修复 PR #9540。</li>
</ul>
</li>
<li><p><strong>#9534 / #9535 ACP 多路复用进程调试日志串扰</strong> <code>[P2/bug, scope/session-management, scope/logging]</code></p>
<ul>
<li><a href="https://github.com/QwenLM/qwen-code/issues/9534">https://github.com/QwenLM/qwen-code/issues/9534</a></li>
<li><a href="https://github.com/QwenLM/qwen-code/issues/9535">https://github.com/QwenLM/qwen-code/issues/9535</a></li>
<li>同一作者提交的两条 issue，分别从文件日志与 daemon 进程级两个角度描述同一根因：多会话共存的 ACP 进程中，新 <code>Config</code> 通过 <code>setDebugLogSession(this)</code> 覆盖进程级日志会话，导致会话 A 的调试信息写入会话 B 的日志文件。各获 2 条评论。</li>
<li><strong>关键影响</strong>：在多会话排障场景下调试日志不可信，会直接误导问题定位。</li>
</ul>
</li>
<li><p><strong>#9536 DingTalk 渠道丢弃引用消息内容</strong> <code>[P2/bug, category/integration]</code>
<a href="https://github.com/QwenLM/qwen-code/issues/9536">https://github.com/QwenLM/qwen-code/issues/9536</a></p>
<ul>
<li>DingTalk 适配器在构建 agent prompt 前提取引用消息，但字段映射与实际 <code>text.repliedMsg</code> 负载不匹配，text/richText/interactiveCard 三类引用内容被静默丢弃。当日即有 PR #9537 跟进修复。</li>
<li><strong>社区反应</strong>：2 条评论，问题复现路径清晰，修复方向明确。</li>
</ul>
</li>
<li><p><strong>#7167 Fleet Shepherd Dashboard</strong> <code>[scope/ci-cd]</code>
<a href="https://github.com/QwenLM/qwen-code/issues/7167">https://github.com/QwenLM/qwen-code/issues/7167</a></p>
<ul>
<li>机器人自动维护的 CI/CD 状态看板，最近一次 tick 正常（scan-signal 年龄 4 分钟，0 syncs / 0 dispatches / 0 releases）。3 条评论。</li>
</ul>
</li>
<li><p><strong>#9032 暴露结构化 Workflow 执行状态</strong> <code>[P2/feature-request, roadmap/multi-agent, roadmap/background-automation]</code>
<a href="https://github.com/QwenLM/qwen-code/issues/9032">https://github.com/QwenLM/qwen-code/issues/9032</a></p>
<ul>
<li>请求将阶段转换、代理分发、依赖边、审批关联与有序事件历史暴露为稳定的 JSON-safe 状态，以支撑下游工作流编排。该 issue 今日已关闭，讨论仍值得参考。</li>
</ul>
</li>
</ol>
<h2>重要 PR 进展（精选 10 条）</h2>
<ol>
<li><p><strong>#9540 Web Shell/WebUI 剪贴板降级修复</strong> <code>[fix, review/self-reported]</code>
<a href="https://github.com/QwenLM/qwen-code/pull/9540">https://github.com/QwenLM/qwen-code/pull/9540</a></p>
<ul>
<li>新增 <code>writeClipboardText()</code> 统一复制入口：优先使用异步 Clipboard API，在非安全上下文降级为隐藏 textarea + <code>document.execCommand(&#39;copy&#39;)</code>，并在最终失败时给出可操作错误提示。直接解决 #9485。</li>
</ul>
</li>
<li><p><strong>#9518 CI Shepherd 僵尸队列修复</strong> <code>[fix, autofix/takeover]</code>
<a href="https://github.com/QwenLM/qwen-code/pull/9518">https://github.com/QwenLM/qwen-code/pull/9518</a></p>
<ul>
<li>GitHub 拒绝启动 workflow 时仍会创建 run（零 job 永久卡在 queued，且 cancel/delete 均被拒），此前被误计为 in-flight，现已修复计数逻辑。背景是 2026-08-19 超大 <code>qwen-autofix.yml</code> 触发的死锁。</li>
</ul>
</li>
<li><p><strong>#9537 DingTalk 引用消息提取修复</strong> <code>[fix, review/self-reported]</code>
<a href="https://github.com/QwenLM/qwen-code/pull/9537">https://github.com/QwenLM/qwen-code/pull/9537</a></p>
<ul>
<li>按钉钉实际交付的引用类型分支解析：纯文本从正确嵌套字段读取正文，富文本与卡片引用均得到修复。对应 issue #9536，当日提交当日跟进。</li>
</ul>
</li>
<li><p><strong>#9402 Agent Board — 跨 Agent 工作共享</strong> <code>[feat]</code>
<a href="https://github.com/QwenLM/qwen-code/pull/9402">https://github.com/QwenLM/qwen-code/pull/9402</a></p>
<ul>
<li>基于文件系统的 Agent Board MVP，使独立启动的多个 agent 可以共享工作成果。该 PR 说明此前删除 agent-view 基础代码的变更已废弃，仅保留新功能。</li>
</ul>
</li>
<li><p><strong>#9527 沙箱镜像绑定拉取 digest</strong> <code>[fix, autofix/takeover]</code>
<a href="https://github.com/QwenLM/qwen-code/pull/9527">https://github.com/QwenLM/qwen-code/pull/9527</a></p>
<ul>
<li>将导出的沙箱镜像绑定到 pull 阶段实际得到的 digest，确保镜像内容可复现、抗篡改。重新落地自冻结的 #9214，并修复了审查提出的两个 Critical（R11-1/R11-2）。</li>
</ul>
</li>
<li><p><strong>#9303 Web Shell transcript 保留上限，修复 renderer OOM</strong> <code>[fix, autofix/takeover]</code>
<a href="https://github.com/QwenLM/qwen-code/pull/9303">https://github.com/QwenLM/qwen-code/pull/9303</a></p>
<ul>
<li>限制浏览器端保留的 daemon 会话历史：原始回放快照注入 transcript store 后立即释放，回放重建与 live 增长共用块上限。</li>
</ul>
</li>
<li><p><strong>#9506 模型路由切换时 token 计数失效</strong> <code>[fix]</code>
<a href="https://github.com/QwenLM/qwen-code/pull/9506">https://github.com/QwenLM/qwen-code/pull/9506</a></p>
<ul>
<li>GeminiChat 的 API 报告 token 计数现在记录路由身份（模型 ID + 认证类型 + endpoint），活动路由切换后旧计数自动失效，避免计费用量数据失真。</li>
</ul>
</li>
<li><p><strong>#9441 PreToolUse hook 返回 ask 时展示编辑/执行 diff</strong> <code>[fix]</code>
<a href="https://github.com/QwenLM/qwen-code/pull/9441">https://github.com/QwenLM/qwen-code/pull/9441</a></p>
<ul>
<li>被 hook 拦截的工具调用弹出等待审批时，不再只给纯文本提示，而是展示实际的编辑/执行差异供用户确认。</li>
</ul>
</li>
<li><p><strong>#9533 Web Shell 侧边栏会话同步</strong> <code>[fix]</code>
<a href="https://github.com/QwenLM/qwen-code/pull/9533">https://github.com/QwenLM/qwen-code/pull/9533</a></p>
<ul>
<li>创建/重命名/删除/归档/固定/分组/改色后立即 reconcile 工作区；用户手动重试可绕过目录服务瞬时 backoff，后台刷新不受影响。</li>
</ul>
</li>
<li><p><strong>#9466 将 rewind 映射锚定到稳定提示词身份</strong> <code>[refactor, review/self-reported]</code>
<a href="https://github.com/QwenLM/qwen-code/pull/9466">https://github.com/QwenLM/qwen-code/pull/9466</a></p>
<ul>
<li>以提示词身份作为可见用户轮次、模型历史、持久化会话、ACP rewind 与 fork 历史的唯一权威锚点，统一符号键元数据，提升回放可靠性。</li>
</ul>
</li>
</ol>
<p><strong>其他值得关注的 PR</strong>：</p>
<ul>
<li>#9532 npm publish 全面启用 <code>--provenance</code> 与 <code>id-token</code> 权限（供应链签名）</li>
<li>#9361 计划任务支持绑定已有存活会话</li>
<li>#8927 渠道 sessionRotation 会话生命周期上限</li>
</ul>
<h2>功能需求趋势</h2>
<p>从今日 Issues 中可以提炼出社区最关注的 5 个方向：</p>
<ol>
<li><strong>Web Shell 浏览器端体验</strong>（#9485）— 远程非安全上下文下的能力降级与可用性是当前前端最高频诉求。</li>
<li><strong>ACP/daemon 多会话隔离</strong>（#9534/#9535）— 多路复用进程下的日志、状态等资源隔离要求提高，单条 issue 已不足以覆盖影响面。</li>
<li><strong>IM 渠道消息语义保真</strong>（#9536）— 引用/富文本内容必须按各平台真实负载映射，静默丢弃是不可接受的失败模式。</li>
<li><strong>CI/CD 自动化运维可观测性</strong>（#7167）— 机器人看板持续监控 bot fleet、同步与发布状态，社区对发布质量门禁的透明度有稳定需求。</li>
<li><strong>Workflow 状态结构化解耦</strong>（#9032）— 调用方需要稳定的 JSON-safe 执行状态（阶段、依赖、审批、事件历史）来接驳下游编排，而非依赖内部 task 快照。</li>
</ol>
<h2>开发者关注点</h2>
<ul>
<li><strong>非安全上下文浏览器 API 降级</strong>：HTTP 非 localhost 访问时 Clipboard API 不可用，开发者要求优雅降级（如 execCommand 回退）而非直接报错。</li>
<li><strong>调试日志的可信度</strong>：日志串扰直接破坏多会话排障链路，进程级 fallback 调试会话需要与显式会话参数强隔离。</li>
<li><strong>渠道字段映射静默失败</strong>：DingTalk 等 IM 回调字段嵌套复杂，解析错误时静默丢弃比显式报错更难发现，建议为各消息类型补充解析器单元测试。</li>
<li><strong>模型路由切换后的元数据一致性</strong>：token 计数等 API 元数据必须绑定到产生它的路由身份，否则计费与用量分析失真（#9506）。</li>
<li><strong>长会话内存膨胀</strong>：daemon 将完整回放快照推送给浏览器端会触发 renderer OOM，需统一 live/回放两条路径的内存上限并尽快释放快照（#9303）。</li>
</ul>
</details>

<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI CLI Tools Digest 2026-08-20</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-cli-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-cli-en</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      <description>AI CLI Tools Community Digest 2026-08-20 Generated: 2026-08-20 04:55 UTC | Tools covered: 7 Claude Code OpenAI Codex Gemini CLI GitHub Copilot CLI Kimi Code CLI OpenCode Qwen Code Claude Code Skills Cross-Tool Comparison Cross-Tool Comparison Report — AI CLI Developer Tools (2026-08-20) 1. Ecosystem Overview The AI CLI tool landscape is in a high-velocity stabilization phase: six major tools shipped at least ten releases combined this week, dominated by patch fixes for regressions introduced in ...</description>
      <content:encoded><![CDATA[<h1>AI CLI Tools Community Digest 2026-08-20</h1>
<blockquote>
<p>Generated: 2026-08-20 04:55 UTC | Tools covered: 7</p>
</blockquote>
<ul>
<li><a href="https://github.com/anthropics/claude-code">Claude Code</a></li>
<li><a href="https://github.com/openai/codex">OpenAI Codex</a></li>
<li><a href="https://github.com/google-gemini/gemini-cli">Gemini CLI</a></li>
<li><a href="https://github.com/github/copilot-cli">GitHub Copilot CLI</a></li>
<li><a href="https://github.com/MoonshotAI/kimi-cli">Kimi Code CLI</a></li>
<li><a href="https://github.com/anomalyco/opencode">OpenCode</a></li>
<li><a href="https://github.com/QwenLM/qwen-code">Qwen Code</a></li>
<li><a href="https://github.com/anthropics/skills">Claude Code Skills</a></li>
</ul>
<hr>
<h2>Cross-Tool Comparison</h2>
<h1>Cross-Tool Comparison Report — AI CLI Developer Tools (2026-08-20)</h1>
<h2>1. Ecosystem Overview</h2>
<p>The AI CLI tool landscape is in a high-velocity stabilization phase: six major tools shipped at least ten releases combined this week, dominated by patch fixes for regressions introduced in recent feature work. Two cross-cutting failure clusters dominate community attention: Windows-specific breakage (path handling, sandboxing, process lifecycle, security-software friction) and session-state reliability (memory loss across compactions, misleading agent status reporting, UI freezes). Security hardening is a rising investment area across nearly all tools, targeting MCP configuration fail-open behavior, Git-command trust boundaries, and authentication enforcement on agent servers. Meanwhile, persistent memory across context compactions remains the single most-demanded capability, with active or recently closed threads in four of the six communities.</p>
<h2>2. Activity Comparison</h2>
<p>Counts reflect issues/PRs surfaced as notable in each tool&#39;s 24-hour digest window, not total tracker volume.</p>
<table>
<thead>
<tr>
<th>Tool</th>
<th>Issues (featured)</th>
<th>PRs</th>
<th>Releases (last 24h)</th>
<th>Release Status</th>
</tr>
</thead>
<tbody><tr>
<td>Claude Code</td>
<td>10 (2 closed)</td>
<td>1</td>
<td>2 (v2.1.236, v2.1.237)</td>
<td>Stable patch cadence</td>
</tr>
<tr>
<td>OpenAI Codex</td>
<td>10</td>
<td>10</td>
<td>2 (rust-v0.149.0-alpha.2/3)</td>
<td>Alpha churn, no changelogs</td>
</tr>
<tr>
<td>Gemini CLI</td>
<td>10</td>
<td>10</td>
<td>3 (v0.56.0 stable, v0.57.0-preview.0, nightly)</td>
<td>Stable + preview parallel tracks</td>
</tr>
<tr>
<td>GitHub Copilot CLI</td>
<td>10 (3 closed)</td>
<td>0</td>
<td>3 (v1.0.81-3 → v1.0.81-5)</td>
<td>Rapid patches, regression-prone 1.0.81 line</td>
</tr>
<tr>
<td>Kimi Code CLI</td>
<td>1 (closed)</td>
<td>0</td>
<td>0</td>
<td>Dormant</td>
</tr>
<tr>
<td>OpenCode</td>
<td>10 (1 closed)</td>
<td>13</td>
<td>0</td>
<td>Heavy refactoring, no release in window</td>
</tr>
<tr>
<td>Qwen Code</td>
<td>7 (1 closed)</td>
<td>14</td>
<td>2 (benchmark builds)</td>
<td>Benchmark-validation-driven</td>
</tr>
</tbody></table>
<h2>3. Shared Feature Directions</h2>
<ul>
<li><strong>Durable memory and session state</strong> — The strongest cross-tool theme. Claude Code (#34556 persistent memory across compactions, closed after 95 comments; #27242 inaccessible post-compaction history; #11408 named sessions), Copilot CLI (#4441 durable context across repeated compactions), Codex (#33493 compaction loops retaining image payloads), Gemini (#26522 Auto Memory infinite retries, #26525 deterministic redaction), and OpenCode (#19143 in-session search) all point to demand for durable, navigable, searchable session state.</li>
<li><strong>Sandbox and permission control</strong> — Copilot CLI has the most acute pain: sandbox force-enabling over explicit <code>&quot;enabled&quot;: false</code> (#4521, #4522), git-blocking restrictions (#4524), and silent bypass in non-interactive <code>-p</code> mode (#4528). Claude Code echoes this with sticky permission modes (#12070) and spurious quoted-character warnings (#27957). Gemini is adding consent gates for environment changes (#28863) and proposing OS-level bash sandboxing (#19873).</li>
<li><strong>MCP/A2A protocol and authentication reliability</strong> — Copilot CLI&#39;s Atlassian OAuth failure (#4480, #4490) and dual-era <code>initialize</code>/<code>server/discover</code> conflict (#4525); Gemini&#39;s corrupt-MCP-config fail-open fixes (#28794, #28787) and A2A server auth enforcement (#28699); Codex&#39;s per-turn MCP server process leaks (#38754); and Kimi&#39;s ACP Grep/Glob blocking (#2609) form a broad reliability/security cluster around agent-to-tool wiring.</li>
<li><strong>Honest agent status reporting</strong> — Gemini&#39;s subagent <code>MAX_TURNS</code> misreported as GOAL success (#22323) and browser agent failing on Wayland yet reporting success (#21983), plus OpenCode&#39;s permanently-spinning unsettled tool calls (#43576), show a shared trust deficit: agents claiming success while failing.</li>
<li><strong>Cost and context transparency</strong> — Codex&#39;s data-driven finding that explicit batching cuts weighted usage 27–45% (#35050, 40👍) plus requests for credit-usage toggles (#28382); Claude Code&#39;s context-accounting confusion (#6616, #18159, #17959); and OpenCode&#39;s removal of hard model limits (#43581) all signal cost/context efficiency as a feature driver.</li>
<li><strong>Windows reliability and parity</strong> — Codex leads with browser-plugin RPC trust failures (#39136 cluster), <code>\\?\</code> path-prefix archive breakage (#39239), and updater <code>PSModulePath</code> leakage (#27117). OpenCode&#39;s npm auto-updater corruption (#42291) and sidecar timeouts (#43568), Copilot&#39;s GHEC data-residency 401 (#4527), and Claude Code&#39;s encrypted-SSH-key dialog failure (#26997) confirm Windows remains the weak flank across all tools.</li>
</ul>
<h2>4. Differentiation Analysis</h2>
<p><strong>Claude Code</strong> targets experienced developers with the most mature TUI and permission ecosystem (output styles, plugin marketplaces, agent teams). Its 286👍 copy/paste issue reflects polish expectations of a mainstream tool; concerns center on session memory depth rather than raw capability. <strong>OpenAI Codex</strong> is the most Windows-focused and security-hardening-heavy tool (Git-command trust removal, plugin Git isolation), with a Rust codebase and enterprise ChatGPT integration; its cost-optimization discourse is unmatched. <strong>Gemini CLI</strong> differentiates through Google Cloud ecosystem integration (Cloud Workstations OAuth, Vertex) and a formal evaluation culture (behavioral evals, GCS trajectory logging), while its open issues show the most interest in AST-aware code navigation and agent self-observability. <strong>Copilot CLI</strong> is enterprise-governance-first: managed-policy enforcement, GHEC data residency, and sandbox bypass prevention dominate — but the 1.0.81 line demonstrates how quickly governance machinery can regress into user-hostile behavior. <strong>OpenCode</strong> is the open-source innovation lab: aggressive architecture investment (Effect <code>Latch</code> refactors, model variant fallbacks, removing model limits, plugin HTTP routes) with corresponding 2.0-instability risk. <strong>Qwen Code</strong> validates through benchmarks (SWE-bench Verified 500/500, Terminal-Bench 89) and invests heavily in CI/fleet automation and integration channels (DingTalk, Aone Code review) rather than TUI polish. <strong>Kimi Code CLI</strong> shows no meaningful differentiation activity this window beyond its ACP/Zed integration, where it currently has a tool-parity gap.</p>
<h2>5. Community Momentum &amp; Maturity</h2>
<p><strong>Highest velocity:</strong> Qwen Code (14 PRs) and OpenCode (13 PRs) are iterating fastest, with OpenCode showing the most architectural ambition and Qwen the most disciplined benchmark-gated pipeline. <strong>High PR volume with release churn:</strong> Codex and Gemini each landed 10 PRs; Gemini shipped a stable release alongside preview work, while Codex&#39;s alpha releases lack changelogs, obscuring progress. <strong>Issue-driven but PR-quiet:</strong> Copilot CLI shipped three patches but no PRs in the window — its community is highly active in reporting regressions, but the maintainers are in firefighting mode. <strong>Mature but low-frequency:</strong> Claude Code shipped two solid patches with only one PR surfaced; its community engagement is the deepest (95-comment threads, 286👍 issues), reflecting a large installed base with high expectations. <strong>Dormant:</strong> Kimi Code CLI had a single closed issue and zero code activity, offering little signal for ecosystem watchers.</p>
<h2>6. Trend Signals</h2>
<ul>
<li><strong>Persistent memory is the next battleground.</strong> Four communities have active demand for cross-compaction memory, named sessions, and searchable history. Tools that ship a credible memory solution (not just transcript files) will capture significant mindshare.</li>
<li><strong>Sandbox/permission systems are at peak instability.</strong> Concurrent regressions in Copilot CLI&#39;s sandbox enforcement and continued friction in Claude Code&#39;s permission prompts indicate the industry has not yet solved safe-by-default execution without user-hostile interference.</li>
<li><strong>Agent honesty is becoming a trust differentiator.</strong> Misleading GOAL-success reports, stuck &quot;Thinking&quot; states, and permanently spinning tool calls erode confidence in autonomous operation; expect observability and truthful status propagation to be prioritized.</li>
<li><strong>Windows remains the ecosystem&#39;s weak flank.</strong> From <code>\\?\</code> path prefixes to PowerShell module leakage to RPC trust validation, Windows-specific bugs account for the largest single cluster of high-severity issues. Cross-platform parity is a retention risk for every vendor.</li>
<li><strong>Cost efficiency is rising as a product lever.</strong> Data-backed usage analysis (Codex #35050) and requests for credit-control toggles indicate power users will increasingly demand transparency and control over token consumption.</li>
<li><strong>Security hardening is moving down the stack.</strong> Git-command trust removal, MCP config fail-open prevention, A2A server authentication, and env-var injection consent gates show a shift from prompt-level safety to infrastructure-level security.</li>
<li><strong>Architectural flexibility is the new differentiator.</strong> Removing model capacity limits (OpenCode), adding model variant fallbacks, pluggable pane backends (Claude Code #26572), and AST-aware tools (Gemini) point to tools positioning for a multi-model, multi-terminal future rather than lock-in to a single runtime stack.</li>
</ul>
<hr>
<h2>Per-Tool Reports</h2>
<details>
<summary><strong>Claude Code</strong> — <a href="https://github.com/anthropics/claude-code">anthropics/claude-code</a></summary>

<h2>Claude Code Skills Highlights</h2>
<blockquote>
<p>Source: <a href="https://github.com/anthropics/skills">anthropics/skills</a></p>
</blockquote>
<h1>Claude Code Skills Community Highlights — 2026-08-20</h1>
<h2>1. Top Skills Ranking</h2>
<p><strong>#1298 — skill-creator eval-loop fix (open, top discussion activity)</strong><br><a href="https://github.com/anthropics/skills/pull/1298">anthropics/skills PR #1298</a><br>Fixes <code>run_eval.py</code> always reporting <code>recall=0%</code>, which renders the description-optimization loop useless (&quot;optimizing against noise&quot;). Also addresses Windows stream reading, trigger detection, and parallel workers. Discussion references issue #556 (12 comments, 7 👍) with 10+ independent reproductions.</p>
<p><strong>#514 — document-typography skill (open)</strong><br><a href="https://github.com/anthropics/skills/pull/514">anthropics/skills PR #514</a><br>Typographic quality control for AI-generated documents: orphan word wrap, widow paragraphs, and numbering misalignment — problems the author argues affect every document Claude produces.</p>
<p><strong>#538 — pdf skill case-sensitivity fixes (open)</strong><br><a href="https://github.com/anthropics/skills/pull/538">anthropics/skills PR #538</a><br>Corrects 8 mismatches in <code>skills/pdf/SKILL.md</code> (<code>REFERENCE.md</code> → <code>reference.md</code>, <code>FORMS.md</code> → <code>forms.md</code>) that break skill loading on case-sensitive filesystems.</p>
<p><strong>#486 — ODT skill (open)</strong><br><a href="https://github.com/anthropics/skills/pull/486">anthropics/skills PR #486</a><br>Adds OpenDocument support: create, fill, read, and convert <code>.odt</code>/<code>.ods</code>, plus ODT-to-HTML parsing; triggers on ODT/ODS/ODF/OpenDocument/LibreOffice mentions.</p>
<p><strong>#210 — frontend-design skill overhaul (open)</strong><br><a href="https://github.com/anthropics/skills/pull/210">anthropics/skills PR #210</a><br>Revises the frontend-design skill for clarity, actionability, and internal coherence, ensuring every instruction is executable within a single conversation.</p>
<p><strong>#83 — skill-quality-analyzer + skill-security-analyzer (open)</strong><br><a href="https://github.com/anthropics/skills/pull/83">anthropics/skills PR #83</a><br>Two meta-skills: a five-dimension quality analyzer (structure/documentation, examples, resources, etc.) and a security analyzer for Claude Skills.</p>
<p><strong>#541 — docx tracked-change ID collision fix (open)</strong><br><a href="https://github.com/anthropics/skills/pull/541">anthropics/skills PR #541</a><br>Prevents document corruption when adding tracked changes to files with existing bookmarks — hardcoded low <code>w:id</code> values collide with OOXML&#39;s shared ID space across bookmarks, comments, and move ranges.</p>
<p><strong>#1367 — self-audit skill v1.3.0 (open, recent momentum)</strong><br><a href="https://github.com/anthropics/skills/pull/1367">anthropics/skills PR #1367</a><br>Universal pre-delivery audit: mechanical file verification first, then a four-dimension reasoning audit in damage-severity order; claims compatibility with any project, stack, or model.</p>
<p>All listed PRs are <strong>open</strong>; none have merged as of the data snapshot.</p>
<h2>2. Community Demand Trends</h2>
<ul>
<li><strong>Trust-boundary security</strong> — Issue <a href="https://github.com/anthropics/skills/issues/492">#492</a> (43 comments, the most active issue) flags community skills distributed under the <code>anthropic/</code> namespace as impersonation risks that could trick users into granting elevated permissions. Issue <a href="https://github.com/anthropics/skills/issues/1175">#1175</a> raises related security/context-window concerns for embedding SharePoint access-control logic in SKILL.md.</li>
<li><strong>Skill distribution and sharing</strong> — <a href="https://github.com/anthropics/skills/issues/228">#228</a> (16 comments, 8 👍) requests org-wide skill sharing in Claude.ai; <a href="https://github.com/anthropics/skills/issues/62">#62</a> reports skills disappearing; <a href="https://github.com/anthropics/skills/issues/189">#189</a> (9 👍) reports duplicate skills from overlapping plugins.</li>
<li><strong>Skill-creator toolchain reliability</strong> — <a href="https://github.com/anthropics/skills/issues/556">#556</a>: <code>run_eval.py</code> triggers no skills across all queries; <a href="https://github.com/anthropics/skills/issues/202">#202</a> argues skill-creator reads like developer documentation rather than an operational skill.</li>
<li><strong>Context-window efficiency</strong> — <a href="https://github.com/anthropics/skills/issues/1487">#1487</a>: the <code>claude-api</code> skill injects ~156k tokens in a single tool call; <a href="https://github.com/anthropics/skills/issues/12">#12</a>: docx skill whitespace reformatting corrupts documents.</li>
<li><strong>New skill directions proposed</strong> — <a href="https://github.com/anthropics/skills/issues/1329">#1329</a> compact-memory (symbolic notation for compressing agent state), <a href="https://github.com/anthropics/skills/issues/412">#412</a> agent-governance (policy enforcement, threat detection, audit trails), <a href="https://github.com/anthropics/skills/issues/1385">#1385</a> reasoning-quality gate pipeline.</li>
<li><strong>Platform integration</strong> — <a href="https://github.com/anthropics/skills/issues/29">#29</a> Bedrock support; <a href="https://github.com/anthropics/skills/issues/16">#16</a> exposing Skills as MCPs.</li>
</ul>
<h2>3. High-Potential Pending Skills</h2>
<ul>
<li><strong><a href="https://github.com/anthropics/skills/pull/1298">#1298 skill-creator eval fix</a></strong> — Directly resolves the most-reported bug (#556); converging companion fixes <a href="https://github.com/anthropics/skills/pull/1099">#1099</a> and <a href="https://github.com/anthropics/skills/pull/1050">#1050</a> address the same Windows subprocess failures.</li>
<li><strong><a href="https://github.com/anthropics/skills/pull/514">#514 document-typography</a></strong> — Broad applicability to all generated documents; low-risk additive skill.</li>
<li><strong><a href="https://github.com/anthropics/skills/pull/486">#486 ODT skill</a></strong> — Completes document-format coverage alongside pdf/docx.</li>
<li><strong><a href="https://github.com/anthropics/skills/pull/723">#723 testing-patterns</a></strong> — Full testing-stack coverage: Testing Trophy model, unit testing, React Testing Library, and what-not-to-test guidance.</li>
<li><strong><a href="https://github.com/anthropics/skills/pull/568">#568 ServiceNow platform skill</a></strong> — Very broad enterprise scope: ITSM, ITOM, ITAM/SAM, FSM, HRSD, CSM, SPM, Vulnerability Response, SecOps, IntegrationHub.</li>
<li><strong><a href="https://github.com/anthropics/skills/pull/525">#525 pyxel skill</a></strong> — Retro/pixel-art game development with Python via pyxel-mcp; submitted by the Pyxel engine&#39;s creator.</li>
<li><strong><a href="https://github.com/anthropics/skills/pull/181">#181 SAP-RPT-1-OSS predictor</a></strong> — SAP&#39;s open-source tabular foundation model for predictive analytics on SAP business data.</li>
<li><strong><a href="https://github.com/anthropics/skills/pull/1367">#1367 self-audit</a></strong> — Universal mechanical + reasoning quality gate; paired with proposal <a href="https://github.com/anthropics/skills/issues/1385">#1385</a>.</li>
</ul>
<h2>4. Skills Ecosystem Insight</h2>
<p>The community&#39;s most concentrated demand is a dependable skill-development toolchain — three independent open PRs (#1298, #1099, #1050) plus issue #556 all target the same broken <code>run_eval.py</code> evaluation loop — followed by document-format breadth (PDF, DOCX, ODT, typography) and, most urgently voiced, trust-boundary safety in how community skills are named and distributed.</p>
<hr>
<h1>Claude Code Community Digest — 2026-08-20</h1>
<h2>Today&#39;s Highlights</h2>
<p>Two patch releases shipped: v2.1.237 fixes prompt caching for LLM gateways/custom base URLs and adds a built-in &quot;Concise&quot; output style, while v2.1.236 introduces <code>ANTHROPIC_DEFAULT_MODEL</code> plus idle notifications for cross-session messaging. On the community side, the long-running TUI copy/paste bug (#18170) remains the most-voted open issue at 286 👍, and the popular persistent-memory request (#34556) was closed after a 95-comment thread.</p>
<h2>Releases</h2>
<ul>
<li><strong>v2.1.237</strong> — Fixed prompt caching for sessions using an LLM gateway or custom base URL. Added a built-in <strong>&quot;Concise&quot; output style</strong> (selectable under Output style in <code>/config</code>) that leads with results and skips preamble/narration while doing the work just as thoroughly.</li>
<li><strong>v2.1.236</strong> — Added <code>ANTHROPIC_DEFAULT_MODEL</code> to set the starting model for new sessions; a <code>/model</code> pick overrides it and persists across restarts (unlike <code>ANTHROPIC_MODEL</code>). Added <code>notify_when_idle</code> to cross-session <code>SendMessage</code> for asking another Claude Code session.</li>
</ul>
<h2>Hot Issues</h2>
<ol>
<li><p><strong><a href="https://github.com/anthropics/claude-code/issues/18170">#18170 — Copy/paste from terminal includes unwanted indentation and trailing spaces</a></strong> — OPEN, 134 comments, 286 👍. Copied text retains leading tabs/spaces aligned to the <code>&gt;</code> prompt and trailing whitespace. The highest-engagement open issue and a daily annoyance for anyone extracting code from the TUI.</p>
</li>
<li><p><strong><a href="https://github.com/anthropics/claude-code/issues/34556">#34556 — Persistent Memory Across Context Compactions</a></strong> — CLOSED, 95 comments. A user documented 59 compactions over 26 days and built a custom memory persistence system after losing context state. The closure of this heavily-discussed feature request will draw community attention.</p>
</li>
<li><p><strong><a href="https://github.com/anthropics/claude-code/issues/27242">#27242 — No working mechanism to review previous context after compaction</a></strong> — OPEN, 17 comments, 80 👍. Transcript data is preserved in <code>transcript.jsonl</code>, but the TUI offers no way to access it after compaction, plan-mode clear, or branch navigation.</p>
</li>
<li><p><strong><a href="https://github.com/anthropics/claude-code/issues/27957">#27957 — Option to disable &#39;quoted characters in flag names&#39; warning</a></strong> — OPEN, 26 comments, 74 👍. Normal commands like <code>git commit -m &quot;message&quot;</code> trigger confirmation prompts after a recent update; widespread friction with the permission system.</p>
</li>
<li><p><strong><a href="https://github.com/anthropics/claude-code/issues/26997">#26997 — SSH dialog cannot connect when default key is encrypted</a></strong> — OPEN, 31 comments, 42 👍. The desktop SSH dialog fails on passphrase-protected <code>~/.ssh/id_ed25519</code> with no way to prompt for a passphrase.</p>
</li>
<li><p><strong><a href="https://github.com/anthropics/claude-code/issues/18157">#18157 — Option+Backspace (delete word) not working in Ghostty</a></strong> — OPEN, 13 comments, 38 👍. Works in the terminal outside Claude Code but not in the TUI on macOS; related to #5196 and #9219.</p>
</li>
<li><p><strong><a href="https://github.com/anthropics/claude-code/issues/11408">#11408 — Ability to name and organize conversation sessions</a></strong> — CLOSED (duplicate), 9 comments, 34 👍. Requests custom names/labels for sessions to organize and quickly identify conversations.</p>
</li>
<li><p><strong><a href="https://github.com/anthropics/claude-code/issues/26996">#26996 — Edit tool silently converts tabs to spaces</a></strong> — OPEN, 20 comments, 30 👍. Causes repeated match failures on tab-indented files; a correctness bug that undermines trust in automated edits.</p>
</li>
<li><p><strong><a href="https://github.com/anthropics/claude-code/issues/26572">#26572 — CustomPaneBackend protocol to decouple agent teams from tmux CLI</a></strong> — OPEN, 8 comments, 28 👍. Proposal from the KILD creator for a pluggable pane backend supporting Ghostty, WezTerm, Zellij, and remote deployments.</p>
</li>
<li><p><strong><a href="https://github.com/anthropics/claude-code/issues/12070">#12070 — Session permission mode &#39;acceptEdits&#39; not persisting</a></strong> — OPEN, 12 comments, 26 👍. &quot;Yes, and accept all for this session&quot; doesn&#39;t stick; users get prompted for every Edit on Linux.</p>
</li>
</ol>
<h2>Key PR Progress</h2>
<p>Only <strong>1 pull request</strong> was updated in the last 24 hours:</p>
<ul>
<li><strong><a href="https://github.com/anthropics/claude-code/pull/77977">#77977 — docs(plugin-dev): document skipLfs marketplace sources</a></strong> — OPEN. Documents the <code>skipLfs</code> option for <code>github</code> and <code>git</code> marketplace source objects in plugin-dev guidance, with examples for GitHub shorthand and generic Git URLs that skip Git LFS downloads. Refs #63035. Docs only.</li>
</ul>
<h2>Feature Request Trends</h2>
<ul>
<li><strong>Conversation memory and history navigation</strong> — The strongest theme. Persistent memory across compactions (#34556), accessible history after compaction (#27242), and named sessions (#11408) all point to demand for durable, navigable session state.</li>
<li><strong>Output style and UI verbosity controls</strong> — Users want to tame Claude&#39;s narration: the &quot;Concise&quot; output style landed in v2.1.237, while requests continue for spinner verb overrides (#41905, #64098) and disabling animated verb rotation.</li>
<li><strong>Permission system granularity</strong> — Opt-out for the quoted-character flag warning (#27957), a setting to block <code>dangerouslyOverrideSandbox</code> (#10089), and persistent per-session accept modes (#12070) show demand for precise, sticky permission controls.</li>
<li><strong>Terminal/agent infrastructure extensibility</strong> — The CustomPaneBackend proposal (#26572) signals interest in pluggable terminal multiplexing backends instead of a hard tmux dependency for agent teams.</li>
</ul>
<h2>Developer Pain Points</h2>
<ul>
<li><strong>TUI text handling</strong> — Copy/paste whitespace corruption (#18170), truncated bash output that won&#39;t expand (#26954), and broken word-delete in Ghostty (#18157) degrade the terminal experience across platforms.</li>
<li><strong>Context accounting confusion</strong> — False &quot;Context low&quot; warnings with plenty of free space (#6616), context-limit errors despite 32k free tokens (#18159), and a status-line percentage that doesn&#39;t match internal calculations (#17959).</li>
<li><strong>Permission prompt fatigue</strong> — Repeated prompts despite &quot;accept all&quot; (#12070), spurious quoted-character warnings (#27957), and &quot;Always Allow&quot; mismatches on compound Windows commands (#27688).</li>
<li><strong>Edit tool whitespace normalization</strong> — Silent tab-to-space conversion (#26996) breaks matching on tab-indented files and erodes trust in the Edit tool.</li>
<li><strong>SSH/remote configuration friction</strong> — Encrypted default keys block the desktop SSH dialog (#26997), and remote sessions inherit local plugin/MCP paths that don&#39;t exist remotely, causing hangs (#25664).</li>
<li><strong>Resource exhaustion risks</strong> — Bundled ugrep ballooning to 9–14 GB RSS on bounded regexes (#83342) and unbounded task output files filling a 278 GB disk (#41737) are serious stability concerns.</li>
</ul>
</details>

<details>
<summary><strong>OpenAI Codex</strong> — <a href="https://github.com/openai/codex">openai/codex</a></summary>

<h1>OpenAI Codex Community Digest — 2026-08-20</h1>
<h2>Today&#39;s Highlights</h2>
<p>Windows reliability dominates the conversation: the in-app Browser plugin&#39;s Trusted RPC path-validation failure (#39136) is the most active issue this week (80 comments, 42 👍), with several related reports filed in the last 24 hours. Separately, a detailed usage analysis (#35050) claims GPT-5.6 frequently serializes independent Code Mode calls, and that explicit batching cut weighted token usage by 27–45% — a finding that has resonated with users watching their spend. Two new <code>rust-v0.149.0-alpha</code> releases landed, though no detailed changelog was published.</p>
<h2>Releases</h2>
<ul>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.2">rust-v0.149.0-alpha.2</a> — version bump, no changelog details provided.</li>
<li><a href="https://github.com/openai/codex/releases/tag/rust-v0.149.0-alpha.3">rust-v0.149.0-alpha.3</a> — version bump, no changelog details provided.</li>
</ul>
<h2>Hot Issues</h2>
<ol>
<li><p><strong><a href="https://github.com/openai/codex/issues/39136">#39136 — Codex built-in browser plugin initialization fails: Trusted RPC dependency is not within a trusted code path</a></strong> — The top issue by engagement (80 comments, 42 👍). Windows users on app build 26.814.41407 report the in-app browser cannot start because the bundled browser runtime fails RPC trust-path validation. This is the center of a wider cluster: #39399, #39387, and #39486 describe the same failure on Windows 10/11 across multiple versions.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/35050">#35050 — GPT-5.6 often serializes independent Code Mode calls; explicit batching reduced weighted usage by 27–45%</a></strong> — A data-driven report from a Pro/Business user showing the model tends to execute independent tool calls sequentially, and that batching them explicitly produces substantial weighted-usage savings. 25 comments, 40 👍 — high community interest in cost optimization.</p>
</li>
<li><p>**<a href="https://github.com/openai/codex/issues/39239">#39239 — Windows: <code>thread/archive</code> fails with &quot;os error 2&quot; after <code>thread/resume</code> stores a <code>\\?\</code> rollout_path</a>** — Archiving a resumed thread fails because the verbatim Windows path prefix breaks path-equality checks, causing the same file to be queued twice. 21 comments; related to #39150, which reports the same <code>\\?\</code> archive failure in the Desktop UI.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/33493">#33493 — Local compaction v2 retains unbounded input_image payloads, causing repeated auto-compaction</a></strong> — Image-heavy threads enter a repeated auto-compaction loop because compacted context keeps unbounded image payloads. 18 comments, affects macOS Desktop with <code>gpt-5.6-sol</code>.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/27117">#27117 — Windows standalone update from pwsh inherits PSModulePath into powershell.exe, causing Get-FileHash to fail</a></strong> — The updater spawns Windows PowerShell from PowerShell 7 and inherits incompatible module paths, breaking update verification. 18 comments, 13 👍.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/39162">#39162 — macOS: Opening an existing conversation invalidates ChatGPT auth and redirects to sign-in</a></strong> — Regression on 26.814.41407: opening a saved conversation forces re-authentication. 15 comments, 14 👍.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/23527">#23527 — Codex mobile does not show SSH remote projects from connected Mac host</a></strong> — Remote projects visible in the Mac app never appear in the mobile project selector. 15 comments, 21 👍 — the most-reacted issue on the list relative to comment count.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/37104">#37104 — Windows/WSL integrated terminal silently fails before PTY/WSL startup</a></strong> — Bottom and side panels cannot open in the Store build; failure happens before PTY/WSL initialization. 14 comments.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/38754">#38754 — Windows: Local stdio MCP servers are repeatedly spawned and not reaped within a single task</a></strong> — Each new turn respawns MCP servers, leaking processes inside a task. 10 comments; a meaningful performance/reliability concern for MCP-heavy Windows workflows.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/issues/13919">#13919 — Conflict between Codex and Antivirus (Bitdefender)</a></strong> — Long-running issue (since March) where Bitdefender interferes with Codex&#39;s PowerShell actions; 16 👍, recently active again. Highlights a broader theme of Windows security-software friction.</p>
</li>
</ol>
<h2>Key PR Progress</h2>
<ol>
<li><p><strong><a href="https://github.com/openai/codex/pull/39524">#39524 — Stop treating Git commands as inherently safe</a></strong> — Security hardening: repository configuration can make even read-only Git commands execute helpers, so Git arguments alone can&#39;t establish trust. Removes Git from known-safe command classification.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39520">#39520 — Isolate automatic plugin Git operations</a></strong> — Prevents background marketplace/plugin refreshes from inheriting project-local Git configuration that could redirect remotes or invoke helpers during automatic operations.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39523">#39523 — Persist thread section moves before the first turn</a></strong> — Fixes non-ephemeral threads disappearing from section-filtered lists by materializing and flushing the thread before the first turn.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39514">#39514 — Use stored item types when materializing turn summaries</a></strong> — Selects summary items using the materialized <code>item_type</code> column, with a fallback for rows written by older clients — a compatibility fix for session history rendering.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39510">#39510 — Track built-in control tool calls in analytics</a></strong> — Adds <code>codex_control_tool_call_event</code> telemetry for <code>request_user_input</code>, <code>update_plan</code>, <code>view_image</code>, and goal tools, including correlation/timing metadata and terminal states.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39474">#39474 — Consolidate Guardian extensions into <code>codex-guardian-v2</code></a></strong> — Moves the Guardian thread lifecycle contributor and subagent-spawn context into a single extension entry point, removing redundant initialization paths.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39452">#39452 — Remove the feature gate for async user messages</a></strong> — Exposes <code>send_user_message_async</code> to root agents whenever the model advertises support; keeps <code>send_async_message</code> as an accepted-but-inert compatibility flag.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39493">#39493 — Make head-tail buffer capacity const generic</a></strong> — Refactors <code>HeadTailBuffer</code> to take capacity as a const generic, with <code>UNIFIED_EXEC_OUTPUT_MAX_BYTES</code> as the production default — groundwork for safer output-buffer handling.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/39480">#39480 — Move shell snapshot tests into shell-command</a></strong> — Co-locates Bash/zsh snapshot-script tests with <code>codex-shell-command</code> where the implementation lives, improving test locality.</p>
</li>
<li><p><strong><a href="https://github.com/openai/codex/pull/31155">#31155 — fix: release thread writer after failed shutdown</a></strong> — Fixes a terminal session reporting shutdown complete while the <code>RolloutRecorder</code> writer is still held for retry, which previously left a stale live-writer lease and caused later failures.</p>
</li>
</ol>
<p>Also notable: <a href="https://github.com/openai/codex/pull/31817">#31817 — Update models.json</a> remains open as an automated model-catalog refresh.</p>
<h2>Feature Request Trends</h2>
<ul>
<li><strong>Usage/credit control</strong> is the clearest recurring request: <a href="https://github.com/openai/codex/issues/28382">#28382</a> asks for a toggle to prevent automatic use of purchased Codex credits once included usage is exhausted; <a href="https://github.com/openai/codex/issues/6372">#6372</a> requests a config option to disable the &quot;switch models&quot; prompt near allowance limits; <a href="https://github.com/openai/codex/issues/39577">#39577</a> reports banked rate-limit resets disappearing after a brief subscription lapse and re-activation.</li>
<li><strong>Cost transparency and efficiency</strong> — users want leverage over how the model batches calls and consumes context, as evidenced by the strong reception of #35050 and the ongoing concern over compaction loops in #33493.</li>
<li><strong>Cross-platform parity for remote/mobile flows</strong> — surfaced by #23527 (SSH remotes missing on mobile) and the persistent Windows feature/parity gap across browser, sandbox, and terminal subsystems.</li>
</ul>
<h2>Developer Pain Points</h2>
<ul>
<li><strong>Windows path handling is the most widespread theme</strong>: <code>\\?\</code> extended-length prefixes break thread archiving (#39239, #39150), and stale verbatim paths cause duplicate queueing and <code>os error 2</code> failures.</li>
<li><strong>Windows trust/security friction</strong>: the Browser plugin&#39;s Trusted RPC validation fails across multiple app builds (#39136, #39399, #39387, #39486); Bitdefender blocks Codex actions (#13919); the sandbox fails with <code>CreateProcessAsUserW</code> error 5 (#26803) and Schannel <code>SEC_E_NO_CREDENTIALS</code> (#17459).</li>
<li><strong>Process lifecycle problems on Windows</strong>: stdio MCP servers are spawned per-turn without reaping (#38754), and the updater breaks because of <code>PSModulePath</code> leakage between PowerShell editions (#27117).</li>
<li><strong>Session/state reliability</strong> — users report stuck &quot;Thinking&quot; states (#24850, #34026), auth invalidations when reopening conversations (#39162), and compaction loops driven by retained image payloads (#33493).</li>
</ul>
</details>

<details>
<summary><strong>Gemini CLI</strong> — <a href="https://github.com/google-gemini/gemini-cli">google-gemini/gemini-cli</a></summary>

<h2>Gemini CLI Community Digest — 2026-08-20</h2>
<h3>Today&#39;s Highlights</h3>
<p>The project shipped <strong>v0.57.0-preview.0</strong> with fixes for Cloud Workstations OAuth flows and IDE connection directory mismatches, alongside the <strong>v0.56.0</strong> stable release. Security hardening is the dominant PR theme, with multiple contributions preventing fail-open behavior for corrupt MCP configs and enforcing authentication on the A2A server. Community attention remains focused on agent reliability, with top issues involving subagent MAX_TURNS being misreported as success and generalist agents hanging indefinitely.</p>
<h3>Releases</h3>
<ul>
<li><strong>v0.57.0-preview.0</strong> — Fixes dynamic resolution of Cloud Workstations proxy redirect URI for OAuth flows (<a href="https://github.com/google-gemini/gemini-cli/pull/28688">#28688</a>) and resolves a swallowed directory mismatch in IDE connections.</li>
<li><strong>v0.56.0</strong> — Stable release. <a href="https://github.com/google-gemini/gemini-cli/compare/v0.55.1...v0.56.0">Full changelog</a></li>
<li><strong>v0.56.0-nightly.20260820.ge90c63fa1</strong> — Preserves empty text turns when tools or media are present in the conversation (<a href="https://github.com/google-gemini/gemini-cli/pull/28892">#28892</a>).</li>
</ul>
<h3>Hot Issues</h3>
<ol>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/issues/22323">#22323 — Subagent MAX_TURNS reported as GOAL success</a></strong> — A <code>codebase_investigator</code> subagent that hits its turn limit before any analysis is still reported as <code>status: &quot;success&quot;</code> with <code>Termination Reason: &quot;GOAL&quot;</code>. This masks real interruptions and makes debugging failures significantly harder. 12 comments, community-driven.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/issues/21409">#21409 — Generalist agent hangs</a></strong> — Simple tasks like folder creation defer to the generalist agent and hang indefinitely (up to an hour). Workaround: instructing the model not to use subagents. 8 comments, 8 👍.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/issues/19873">#19873 — Zero-dependency OS sandboxing for bash</a></strong> — Proposal to leverage Gemini 3&#39;s native bash affinity with OS-level sandboxing plus post-execution intent routing, balancing capability against security/UX. 8 comments.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/issues/24353">#24353 — Robust component-level evaluations</a></strong> — Epic tracking expansion of the 76 behavioral eval tests across 6 supported Gemini models; community wants better regression coverage for agent components. 7 comments.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/issues/22745">#22745 — AST-aware file reads, search, and mapping</a></strong> — Suggests AST-aware tools for precise method-bound reads and context reduction. Paired with the &quot;Tactful Extraction&quot; issue (<a href="https://github.com/google-gemini/gemini-cli/issues/19561">#19561</a>) targeting surgical token-frugal code discovery. 7 comments.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/issues/21968">#21968 — Gemini doesn&#39;t use skills and sub-agents enough</a></strong> — Users report the model rarely activates custom skills/sub-agents unless explicitly instructed, even when descriptions clearly match the task. 6 comments.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/issues/26522">#26522 — Auto Memory retries low-signal sessions indefinitely</a></strong> — Sessions that the extraction agent skips as low-signal are never marked processed, causing them to be re-surfaced repeatedly. 5 comments.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/issues/25166">#25166 — Shell command stuck at &quot;Waiting input&quot; after completion</a></strong> — Simple CLI commands finish but the shell remains active awaiting input, forcing manual intervention. 4 comments, 3 👍.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/issues/26525">#26525 — Deterministic redaction and reduced Auto Memory logging</a></strong> — Auto Memory sends transcript content to a background model before redaction happens, and the service can log existing skills. Security-sensitive gap in the memory pipeline. 4 comments.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/issues/21983">#21983 — Browser subagent fails on Wayland</a></strong> — Browser agent reports <code>Termination Reason: GOAL</code> despite failing in Wayland environments. Consistent with a pattern of misleading success reporting. 4 comments.</p>
</li>
</ol>
<h3>Key PR Progress</h3>
<ol>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/pull/28701">#28701 — Fix TRUST_PARENT rule precedence in folder-trust resolution</a></strong> — Corrects &quot;longest match wins&quot; logic for <code>LoadedTrustedFolders.isPathTrusted()</code> so the most specific configured trust rule takes precedence. Closed.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/pull/28699">#28699 — Enforce authentication and stop checkpoint path traversal in A2A server</a></strong> — Custom REST routes (<code>/tasks</code>, <code>/executeCommand</code>) bypassed the configured <code>UserBuilder</code> and accepted unauthenticated requests; also closes a checkpoint path traversal hole. Closed.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/pull/28794">#28794 — Prevent fail-open and data loss on corrupt MCP enablement config</a></strong> — Fixes <a href="https://github.com/google-gemini/gemini-cli/issues/28786">##28786</a>: invalid <code>mcp-server-enablement.json</code> previously returned <code>{}</code>, silently re-enabling all servers. Now surfaces the corruption instead of failing open.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/pull/28787">#28787 — Don&#39;t treat corrupt MCP enablement config as empty</a></strong> — Companion fix: JSON parse failures in <code>readConfig()</code> were collapsed into the &quot;file does not exist&quot; empty-object path, causing every server to default to enabled.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/pull/28789">#28789 — Fix vscode-ide-companion stop() hang and keep-alive failure threshold</a></strong> — Resolves <code>IdeServer.stop()</code> hanging when active streaming MCP sessions are open, and fixes a resource leak where intermittent ping failures never triggered cleanup.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/pull/28788">#28788 — Behavioral evals for skill activation and URL fetching</a></strong> — Adds evaluations for <code>activate_skill</code> and <code>web_fetch</code>, improves Windows compatibility for local eval runs, and fixes EDK report aggregation for skipped tests.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/pull/28898">#28898 — Harden pr-generator-core subprocess execution security</a></strong> — Prevents sensitive authentication tokens from leaking into untrusted tool execution environments, plus hardening of config ingestion and GitHub API interactions.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/pull/28922">#28922 — GCS trajectory logging and artifact preservation for PR generation</a></strong> — Adds GCS stream/chunk persistence and debug artifact storage to support post-mortem inspection and evaluation of coding/repair loops.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/pull/28863">#28863 — Prompt for consent on environment changes and sanitize runtime-altering env vars</a></strong> — Closes a gap where extension updates could bypass consent checks and inject unauthorized environment variables into spawned MCP server processes.</p>
</li>
<li><p><strong><a href="https://github.com/google-gemini/gemini-cli/pull/28915">#28915 — Consistent symlink evaluation in ignore path handling</a></strong> — Ensures <code>.geminiignore</code> and <code>.gitignore</code> rules are evaluated against both literal and canonical (resolved symlink) paths, eliminating tool behavior inconsistencies.</p>
</li>
</ol>
<h3>Feature Request Trends</h3>
<ul>
<li><strong>AST-aware code navigation</strong>: Multiple issues (<a href="https://github.com/google-gemini/gemini-cli/issues/22745">#22745</a>, <a href="https://github.com/google-gemini/gemini-cli/issues/22746">#22746</a>, <a href="https://github.com/google-gemini/gemini-cli/issues/19561">#19561</a>) push for AST-powered reads, codebase mapping, and token-frugal &quot;tactful extraction&quot; to cut context bloat.</li>
<li><strong>Agent self-awareness and observability</strong>: Users want subagent trajectories visible via <code>/chat share</code> (<a href="https://github.com/google-gemini/gemini-cli/issues/22598">#22598</a>) and accurate self-knowledge of CLI flags/hotkeys (<a href="https://github.com/google-gemini/gemini-cli/issues/21432">#21432</a>).</li>
<li><strong>Stricter safety defaults</strong>: Requests for discouraging destructive git/DB commands (<a href="https://github.com/google-gemini/gemini-cli/issues/22672">#22672</a>), deterministic secret redaction in Auto Memory (<a href="https://github.com/google-gemini/gemini-cli/issues/26525">#26525</a>), and OS-level sandboxing (<a href="https://github.com/google-gemini/gemini-cli/issues/19873">#19873</a>).</li>
<li><strong>Agent resilience/recovery</strong>: Browser agent session takeover and lock recovery (<a href="https://github.com/google-gemini/gemini-cli/issues/22232">#22232</a>), plus robust component-level eval infrastructure (<a href="https://github.com/google-gemini/gemini-cli/issues/24353">#24353</a>).</li>
</ul>
<h3>Developer Pain Points</h3>
<ul>
<li><strong>Misleading success reporting</strong>: Subagents that hit MAX_TURNS or fail (browser/Wayland) are frequently reported as GOAL success, hiding real failures and eroding trust in agent diagnostics.</li>
<li><strong>Hangs and stuck prompts</strong>: Generalist agent hangs and post-completion &quot;Waiting input&quot; shell states require manual cancellation, disrupting long-running workflows.</li>
<li><strong>Symlink support gaps</strong>: Agent files in <code>~/.gemini/agents/</code> are not recognized when symlinked (<a href="https://github.com/google-gemini/gemini-cli/issues/20079">#20079</a>); ignores behave inconsistently across symlinked paths.</li>
<li><strong>Config corruption risks</strong>: Corrupt MCP enablement configs fail open, silently re-enabling servers — a security and data-loss concern (<a href="https://github.com/google-gemini/gemini-cli/issues/28786">#28786</a>).</li>
<li><strong>Context and tool limits</strong>: 400 errors with &gt;128 tools (<a href="https://github.com/google-gemini/gemini-cli/issues/24246">#24246</a>), large file-read &quot;firehosing&quot; of context, and model-generated temp script litter across workspaces (<a href="https://github.com/google-gemini/gemini-cli/issues/23571">#23571</a>).</li>
</ul>
</details>

<details>
<summary><strong>GitHub Copilot CLI</strong> — <a href="https://github.com/github/copilot-cli">github/copilot-cli</a></summary>

<h1>GitHub Copilot CLI Community Digest — 2026-08-20</h1>
<h2>1. Today&#39;s Highlights</h2>
<p>Three patch releases (v1.0.81-3 → v1.0.81-5) shipped in the last 24 hours, with v1.0.81-5 fixing a visible transcript bug where answered prompts left duplicate <code>(pending)</code> lines on screen. The issue tracker shows a spike in regressions tied to the 1.0.81 prerelease line — sandbox enforcement overriding explicit user config, terminal UI freezes during parallel subagent runs, and ACP mode auto-approving tool calls again. Meanwhile, the Atlassian MCP OAuth failure (<code>RFC 8414 §3.3</code>) continues to affect users across multiple versions. No pull requests were updated or merged during this window.</p>
<h2>2. Releases</h2>
<ul>
<li><a href="https://github.com/github/copilot-cli/releases/tag/v1.0.81-5">v1.0.81-5</a> — Fixes a prompt sent while the agent is working no longer leaving a second copy of itself stuck as <code>(pending)</code> at the bottom of the transcript after it has been answered.</li>
<li><a href="https://github.com/github/copilot-cli/releases/tag/v1.0.81-4">v1.0.81-4</a> — General fixes and changes.</li>
<li><a href="https://github.com/github/copilot-cli/releases/tag/v1.0.81-3">v1.0.81-3</a> — General fixes and changes.</li>
</ul>
<h2>3. Hot Issues</h2>
<ol>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4522">#4522 — Copilot CLI 1.0.81 forces sandbox while managed policy is undetermined, overriding <code>sandbox.enabled=false</code></a></strong> — The local sandbox engages even when the user explicitly disabled it and no MDM/managed settings exist. With 7 👍, this is the highest-reaction open issue today and a serious trust/config-override problem for enterprise users.</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4390">#4390 (CLOSED) — Enabled organization models missing from catalogue (Claude Sonnet 5/Opus 5, Kimi K3)</a></strong> — Org-enabled Anthropic models are reported as &quot;disabled by your organization&quot; in the CLI. The most-discussed issue in this window with 15 comments and 7 👍, now closed — worth verifying the resolution on your org.</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4480">#4480 — Atlassian MCP OAuth fails with &quot;Incompatible authorization server (RFC 8414 §3.3)&quot;</a></strong> — Regression from 1.0.71; remote MCP OAuth discovery breaks with issuer/metadata URL mismatch. 6 👍 and a companion report in <a href="https://github.com/github/copilot-cli/issues/4490">#4490</a> (broken in 1.0.80, worked in 1.0.78). Still open and affecting a popular production MCP server.</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4537">#4537 — ACP mode auto-approves tool calls again; <code>session/request_permission</code> not sent since 1.0.81-1</a></strong> — Shell commands, file edits, and deletions execute unattended with no permission prompt — a security regression of the previously fixed #845. High severity for anyone driving the CLI through ACP hosts.</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4521">#4521 — Sandbox cannot be disabled</a></strong> — Config reports sandbox &quot;disabled&quot; while runtime status still shows it enabled, and execution keeps applying it. 4 👍; directly related to the #4522 cluster.</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4524">#4524 (CLOSED) — Sandbox won&#39;t let copilot use git anymore</a></strong> — Enforced-sandbox builds are overly restrictive: even after enabling the entire working directory and <code>~/.copilot</code>, git operations fail. Closed, but indicative of the sandbox friction users are hitting in 1.0.81.</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4527">#4527 — <code>copilot -p</code> fails with 401 on GHEC data residency since 1.0.81-1</a></strong> — Non-interactive prompt mode fetches the model catalog from <code>api.githubcopilot.com</code> instead of the tenant endpoint, breaking all <code>-p</code> usage on data-residency tenants while interactive mode still works.</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4533">#4533 — Terminal UI stops consuming events (input + scroll dead) when a turn spawns parallel subagents</a></strong> — On 1.0.81-4/1.0.81-5 the UI freezes while the underlying Rust runtime keeps working, leaving subagents to run unattended and results invisible to the user.</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4525">#4525 — 1.0.81-1 sends legacy <code>initialize</code> after successful modern <code>server/discover</code>, causing -32022</a></strong> — MCP initialization fails against servers using the Python MCP SDK 2.0.0 dual-era runner. Protocol negotiation is mishandled, breaking stdio servers built on current SDKs.</p>
</li>
<li><p><strong><a href="https://github.com/github/copilot-cli/issues/4528">#4528 — Non-interactive sessions bypass <code>disableBypassPermissionsMode</code> managed setting</a></strong> — <code>-p</code> with <code>--allow-all</code>/<code>--yolo</code> grants full permissions even when managed settings require bypass mode to be disabled. Silent policy escape for enterprises.</p>
</li>
</ol>
<h2>4. Key PR Progress</h2>
<p>No pull requests were updated or merged in the last 24 hours.</p>
<h2>5. Feature Request Trends</h2>
<ul>
<li><strong>Durable agent memory:</strong> <a href="https://github.com/github/copilot-cli/issues/4441">#4441</a> asks for preserving durable context across repeated compactions, noting that each re-summarization is recursively lossy and degrades early decisions.</li>
<li><strong>Session preference persistence:</strong> <a href="https://github.com/github/copilot-cli/issues/4530">#4530</a> requests that reasoning effort (not just model) persist across restarts; today it resets to Medium.</li>
<li><strong>Plugin marketplace discoverability:</strong> <a href="https://github.com/github/copilot-cli/issues/4523">#4523</a> proposes interactive search/filtering for <code>copilot plugin marketplace browse</code> as the flat list becomes unusable.</li>
<li><strong>Model catalogue fidelity:</strong> The closed <a href="https://github.com/github/copilot-cli/issues/4390">#4390</a> highlights a broader enterprise need: the CLI&#39;s effective model list must match org-enabled models exactly, including new Anthropic and Kimi families.</li>
</ul>
<h2>6. Developer Pain Points</h2>
<ul>
<li><strong>Sandbox configuration chaos (highest-frequency cluster):</strong> Users report sandbox forcing itself on despite <code>&quot;enabled&quot;: false</code> (<a href="https://github.com/github/copilot-cli/issues/4521">#4521</a>, <a href="https://github.com/github/copilot-cli/issues/4522">#4522</a>), blocking git and everyday shell use (<a href="https://github.com/github/copilot-cli/issues/4524">#4524</a>), ignoring RW path grants for JVM/Java processes (<a href="https://github.com/github/copilot-cli/issues/4516">#4516</a>), and being bypassable in non-interactive mode (<a href="https://github.com/github/copilot-cli/issues/4528">#4528</a>).</li>
<li><strong>MCP authentication and protocol regressions:</strong> OAuth breakage against Atlassian MCP across 1.0.79/1.0.80 (<a href="https://github.com/github/copilot-cli/issues/4480">#4480</a>, <a href="https://github.com/github/copilot-cli/issues/4490">#4490</a>), forced re-auth sending <code>prompt=select_account</code> to non-Microsoft providers (<a href="https://github.com/github/copilot-cli/issues/4526">#4526</a>), dual-era <code>initialize</code>/<code>server/discover</code> conflicts (<a href="https://github.com/github/copilot-cli/issues/4525">#4525</a>), and image content blocks dropped from MCP tool results (<a href="https://github.com/github/copilot-cli/issues/4536">#4536</a>).</li>
<li><strong>Terminal UI regressions in the 1.0.81 line:</strong> duplicate pending lines filling the screen (<a href="https://github.com/github/copilot-cli/issues/4532">#4532</a>, fixed in v1.0.81-5), complete UI freeze during parallel subagents (<a href="https://github.com/github/copilot-cli/issues/4533">#4533</a>), backspace deleting whole words (<a href="https://github.com/github/copilot-cli/issues/4447">#4447</a>), and dropped enter/key events when panes are unfocused (<a href="https://github.com/github/copilot-cli/issues/4213">#4213</a>).</li>
<li><strong>Prerelease channel/version confusion:</strong> <code>autoUpdate: false</code> is ignored and a cached prerelease keeps re-exec-ing over the npm stable install (<a href="https://github.com/github/copilot-cli/issues/4534">#4534</a>); <code>store_memory</code> fails with <code>Instance id is required</code> in 1.0.81 prereleases (<a href="https://github.com/github/copilot-cli/issues/4535">#4535</a>); GHEC data-residency tenants break in prompt mode only (<a href="https://github.com/github/copilot-cli/issues/4527">#4527</a>).</li>
</ul>
</details>

<details>
<summary><strong>Kimi Code CLI</strong> — <a href="https://github.com/MoonshotAI/kimi-cli">MoonshotAI/kimi-cli</a></summary>

<h1>Kimi Code CLI Community Digest — 2026-08-20</h1>
<h2>Today&#39;s Highlights</h2>
<p>The MoonshotAI/kimi-cli project had a quiet 24 hours: no new releases and no pull request activity. The sole signal is a closed ACP issue (#2609) reporting that Grep and Glob tools are fully blocked in ACP runtime on kimi-code 0.37.1, underscoring incomplete tool parity for ACP clients like Zed.</p>
<h2>Hot Issues</h2>
<p>Only one issue was updated in the last 24 hours; it is already closed.</p>
<h3><a href="https://github.com/MoonshotAI/kimi-cli/issues/2609">#2609 — [ACP] Grep/Glob blocked: &quot;ACP runtime only supports interactive Bash tool processes&quot;; Bash intermittently reports &quot;ACP terminal capability is unavailable&quot;</a> — Closed</h3>
<ul>
<li><strong>Why it matters:</strong> On kimi-code 0.37.1 (macOS, ACP client: Zed via <code>kimi acp</code>), the built-in Grep and Glob tools fail on every invocation with &quot;ACP runtime only supports interactive Bash tool processes,&quot; while Read works correctly. This breaks core code-search and file-discovery workflows for ACP users and reveals a hard runtime restriction: non-interactive Bash-backed tools are disabled inside ACP sessions. The additional &quot;ACP terminal capability is unavailable&quot; error for Bash introduces intermittent flakiness in the fallback path.</li>
<li><strong>Community reaction:</strong> Zero comments and zero reactions. The issue was opened and closed within the same day with no public explanation, leaving affected users without a documented workaround or a clear timeline for a fix in a release.</li>
</ul>
<h2>Key PR Progress</h2>
<p>No pull requests were updated in the last 24 hours.</p>
<h2>Feature Request Trends</h2>
<ul>
<li><strong>Full ACP tool parity:</strong> The most recent issue reinforces a growing expectation that Grep, Glob, and Bash tools behave identically in ACP sessions as they do in interactive terminal mode. The current &quot;interactive Bash only&quot; constraint forces ACP clients (e.g., Zed) into a degraded experience where basic search and file-lookup tooling is unusable.</li>
</ul>
<h2>Developer Pain Points</h2>
<ul>
<li><strong>ACP runtime restrictions:</strong> Non-interactive tool processes (Grep/Glob) are blocked outright, breaking fundamental search and file-discovery operations for ACP-backed editors.</li>
<li><strong>Intermittent Bash capability failures:</strong> &quot;ACP terminal capability is unavailable&quot; appears sporadically, complicating error handling and retry logic for client-side implementers.</li>
<li><strong>Low-visibility issue resolution:</strong> The issue was closed without comments, so users lack insight into whether this was a duplicate, a deliberate limitation, or a silently shipped fix.</li>
</ul>
</details>

<details>
<summary><strong>OpenCode</strong> — <a href="https://github.com/anomalyco/opencode">anomalyco/opencode</a></summary>

<h1>OpenCode Community Digest — 2026-08-20</h1>
<h2>Today&#39;s Highlights</h2>
<p>A severe data-integrity bug surfaced today: growing workspace files cause OOM crashes and ~30 GB databases, the most critical issue in the tracker. On the fix side, the team landed a substantial hardening batch — five <code>Latch</code>-based concurrency refactors across core, server, and TUI, plus a model-limits removal and model variant fallback system. Model reliability around GPT-5.6 variants (Luna, sol-fast) remains the hottest operational theme, with several provider-side failures reported against OpenCode Go.</p>
<h2>Releases</h2>
<p>No new releases in the last 24 hours.</p>
<h2>Hot Issues</h2>
<ul>
<li><p><strong><a href="http://github.com/anomalyco/opencode/issues/43551">#43551 — OOM and ~30 GB database: huge workspace-file diffs re-serialized on every <code>message.updated</code> event</a></strong> — A session tracking growing log files (292 MB and 407 MB) embeds full diffs into message summaries, then re-serializes them on every update event. The result is memory exhaustion and database bloat. The most severe open issue; likely to drive a quick fix.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/issues/43367">#43367 — [2.0] subagents: gpt-5.6-sol-fast fails when <code>prompt_cache_retention</code> is injected (CLOSED)</a></strong> — Subagents using <code>gpt-5.6-sol-fast</code> with the <code>max</code> variant halted after tool execution because OpenCode sent an unsupported <code>prompt_cache_retention</code> option. Three review subagents failed within minutes. 10 👍 — the highest-reacted issue today; now closed.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/issues/42700">#42700 — [2.0] tui: leaks ~21MB <code>.so</code> per launch into /tmp; fills tmpfs and breaks TUI startup</a></strong> — Every TUI launch leaks a ~21 MB shared object into the temp directory. On Arch Linux with tmpfs, enough launches fill the filesystem and the TUI fails with an OpenTUI library load error.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/issues/42291">#42291 — Auto-updater breaks global npm install: stub binary + missing shims, hung npm processes</a></strong> — On Windows, the auto-updater can permanently break a global npm install, leaving a stub binary, missing shims, and orphaned <code>npm install</code> processes. Startup-triggered corruption is particularly nasty for users who rely on <code>opencode-ai</code> from npm.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/issues/19143">#19143 — [FEATURE] Implement message search (Cmd+F / Ctrl+F) in the Desktop App</a></strong> — Long-standing request (March) for quick in-session search, now with 8 comments and 7 👍. Users need to locate specific information inside long sessions without scrolling.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/issues/43565">#43565 — gpt-5.6-luna returns empty response / 403 error with OpenCode Go API</a></strong> — Model returned empty responses and 403 errors through the OpenCode Go endpoint when called from Claude Code CLI via <code>https://opencode.ai/zen/go/v1</code>.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/issues/43557">#43557 — OpenCode Go: existing GPT-5.6 Luna sessions fail with <code>invalid_encrypted_content</code></a></strong> — Multi-turn Luna sessions repeatedly fail with <code>invalid_encrypted_content</code> on continuation. When combined with #43565, this signals a pattern of server-side issues for new GPT-5.6 variants through OpenCode Go.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/issues/43563">#43563 — [2.0] TUI: text typed while a submit POST is in flight is silently destroyed</a></strong> — Found via seeded network-chaos property testing (seeds 1, 7, 99). The prompt component clears the composer only after the awaited <code>session.prompt</code> POST resolves, so any text typed during the in-flight request is lost. Silent data loss in the primary input path.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/issues/42532">#42532 — [2.0] server: workspace=global requests return 500 &#39;Path is not absolute: global&#39;</a></strong> — The Desktop client shows repeated &quot;failed to reload global&quot; toasts because almost every workspace-scoped API returns HTTP 500 when the workspace is <code>global</code>. Breaks core desktop functionality for users on the new server.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/issues/43553">#43553 — [2.0] tui: cannot close tab for active conversation — tab reappears after clicking X</a></strong> — The active conversation&#39;s tab cannot be closed; it briefly disappears then reappears, and persists across restarts. Other tabs close normally, isolating the bug to active-session handling.</p>
</li>
</ul>
<h2>Key PR Progress</h2>
<ul>
<li><p><strong><a href="http://github.com/anomalyco/opencode/pull/43581">#43581 — refactor(ai): remove model limits</a></strong> — Removes model capability limits from AI model, route, and provider-package defaults; stops projecting Core catalog limits into provider settings; defaults Anthropic Messages <code>max_tokens</code> to 32K while preserving explicit <code>generation.maxTokens</code>. A significant philosophical and architectural shift toward letting models self-limit.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/pull/43574">#43574 — feat(core): add configured model variant fallbacks</a></strong> — Generates conservative package-aware variants for newly configured models when <code>variants</code> is omitted; preserves explicit variant arrays and <code>variants: []</code> as opt-out across layered config. Supports AI SDK and native OpenAI, OpenAI-compatible, Azure, Google, Vertex, and Anthropic.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/pull/43576">#43576 — fix(core): settle foreign typed tool failures instead of dropping them</a></strong> — Plugin tools failing with non-<code>Tool.Error</code> errors leave their tool call permanently unsettled: the part stays <code>running</code> with a live spinner forever while execution reports success. Found by a drive gauntlet probe; this fix settles those failures properly.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/pull/43575">#43575 — fix(ai): settle pending Responses tool calls</a></strong> — Finalizes pending function calls when a Responses stream reaches successful completion without <code>response.output_item.done</code>, parsing accumulated arguments through the canonical tool-input path so the session can validate or execute the call.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/pull/43562">#43562 — fix(tui): stop registering one resize listener per transcript row</a></strong> — Listener count grew linearly with transcript length, tripping Bun&#39;s EventTarget max-listeners warning within ~4 prompts and climbing into dozens over long sessions. Root-cause fix for a memory-leak-adjacent degradation.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/pull/43567">#43567 — chore: upgrade Effect to rc.110</a></strong> — Upgrades the V2 workspace from Effect 4.0.0-beta.107 to 4.0.0-rc.110 across core, Node platform, OpenTelemetry, and Bun SQLite packages. Lockfile resolves a single Effect runtime version.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/pull/43360">#43360 — feat(ai): support Responses request options</a></strong> — Lowers canonical presence/frequency penalties into Responses requests; adds typed metadata, safety identifier, stream obfuscation, and top-logprob provider options for native OpenAI and Open Responses-compatible routes.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/pull/43499">#43499 — feat(plugin): add HTTP routes support for webhook endpoints</a></strong> — Closes #41362. Enables OpenCode server plugins to register HTTP routes, opening up webhook endpoints and custom server-side plugin behavior.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/pull/43578">#43578 — fix(tui): show encrypted reasoning status</a></strong> — Renders reasoning parts containing opaque provider metadata but no readable text. Completed opaque reasoning displays as <code>Thought · &lt;duration&gt; · encrypted</code>, preserving the <code>Thinking</code> treatment while active.</p>
</li>
<li><p><strong><a href="http://github.com/anomalyco/opencode/pull/43570">#43570–#43573 — refactor(core/server/tui): use <code>Latch</code> for shutdown/startup/output gates</a></strong> — A coordinated batch (MCP startup gate, plugin supervisor ready gate, server shutdown, renderer shutdown, shell output gate) replacing hand-rolled <code>Deferred</code> signals with Effect&#39;s <code>Latch</code> primitive. Expresses open-once, never-failing intent directly and eliminates subtle re-await/<code>isDone</code> logic.</p>
</li>
</ul>
<h2>Feature Request Trends</h2>
<ul>
<li><strong>Session search in the Desktop app</strong> — #19143 remains the most prominent UI feature request: users need Cmd+F/Ctrl+F to locate content within long sessions.</li>
<li><strong>Cloud profile sync</strong> — #43544 requests saving profiles (models and provider API keys) to the cloud, signaling demand for portable multi-machine setups.</li>
<li><strong>Model configuration flexibility</strong> — The PR momentum around removing model limits (#43581) and variant fallbacks (#43574) aligns with user friction around provider-specific model behavior.</li>
<li><strong>Plugin HTTP/webhook routes</strong> — #43499 (closing #41362) indicates growing demand for server-side plugin extensibility beyond tool calls.</li>
<li><strong>Linux clipboard primary buffer</strong> — #32370 adds a <code>linux_clipboard_selection</code> config for primary buffer support, a long-running request from Linux TUI users.</li>
</ul>
<h2>Developer Pain Points</h2>
<ul>
<li><strong>Windows desktop reliability</strong> — Two near-identical sidecar timeout reports (#43568, #43559: &quot;Sidecar did not become ready within 60000ms&quot;) plus the auto-updater npm corruption (#42291) paint a pattern of Windows-specific instability in installation and desktop startup.</li>
<li><strong>OpenCode Go + GPT-5.6 variant failures</strong> — Empty responses/403s (#43565), <code>invalid_encrypted_content</code> on existing sessions (#43557), and the <code>prompt_cache_retention</code> subagent breakage (#43367) show the newest model variants are causing provider-protocol friction.</li>
<li><strong>TUI input and paste regressions</strong> — Cmd+V/Ctrl+V not working in the question dialog&#39;s custom answer field was reported twice (#43241, #43233) before being closed, and #43563 shows typed text can be silently destroyed during in-flight submits.</li>
<li><strong>Resource leaks and unbounded growth</strong> — The 21 MB-per-launch <code>/tmp</code> leak (#42700), the OOM/30 GB database issue (#43551), and the linear resize-listener leak fixed in #43562 all indicate systematic cleanup gaps in TUI and session lifecycle management.</li>
<li><strong>Input loss and stuck states</strong> — Users face multiple failure modes where their work or control disappears: destroyed composer text, unclosable active tabs (#43553), agents continuing while trapped in a false location-unavailable modal (#43415), and permanently spinning tool calls (fixed in #43576).</li>
</ul>
</details>

<details>
<summary><strong>Qwen Code</strong> — <a href="https://github.com/QwenLM/qwen-code">QwenLM/qwen-code</a></summary>

<h1>Qwen Code Community Digest — 2026-08-20</h1>
<h2>Today&#39;s Highlights</h2>
<p>Release validation continued with two new benchmark builds (dsw-eas-full-20260819-r1 and dsw-eas-full-20260820-r1) passing SWE-bench Verified 500/500 and Terminal-Bench 2.0 (89). The community shipped targeted fixes for Web Shell clipboard failures over plain HTTP (#9540) and DingTalk quoted-message extraction (#9537), while new bug reports highlighted ACP debug-log session isolation gaps (#9534, #9535) and a Web Shell-sidebar synchronization issue (#9533).</p>
<h2>Releases</h2>
<ul>
<li><a href="https://github.com/QwenLM/qwen-code/releases/tag/dsw-eas-full-20260820-r1">dsw-eas-full-20260820-r1</a> · Benchmark-Qwen-Ref: v0.21.14 — Full end-to-end validation: SWE-bench Verified 500/500, release writeback, Terminal-Bench 2.0 89, final writeback.</li>
<li><a href="https://github.com/QwenLM/qwen-code/releases/tag/dsw-eas-full-20260819-r1">dsw-eas-full-20260819-r1</a> · Benchmark-Qwen-Ref: v0.21.14 — Same validation pipeline: SWE-bench Verified 500/500, Terminal-Bench 2.0 89, release and final writeback.</li>
</ul>
<h2>Hot Issues</h2>
<ul>
<li><a href="https://github.com/QwenLM/qwen-code/issues/9485">#9485 Web Shell copy buttons fail with &quot;Clipboard API is not available&quot; when opened over HTTP from a non-localhost address</a> — P2 bug in the Web Shell over remote daemon setups: every copy button fails in non-secure contexts. High impact for remote Linux workflows; 4 comments and a fix PR (#9540) landed within 24 hours.</li>
<li><a href="https://github.com/QwenLM/qwen-code/issues/9536">#9536 DingTalk channel drops quoted message content for text, richText, and interactiveCard replies</a> — The channel builds the agent prompt from <code>text.repliedMsg</code> but uses the wrong field mapping for the payloads DingTalk actually delivers, silently dropping most quoted content before it reaches the model. Quickly followed by fix PR #9537.</li>
<li><a href="https://github.com/QwenLM/qwen-code/issues/9535">#9535 bug(core): debug logs can cross session boundaries in ACP multiplexed processes</a> — In daemon/ACP mode, each new <code>Config</code> overwrites the process-wide debug-log session, so session A&#39;s logs can be written to session B&#39;s file. A privacy- and debuggability-relevant isolation bug in the daemon path.</li>
<li><a href="https://github.com/QwenLM/qwen-code/issues/9534">#9534 ACP debug logs can cross session boundaries in a multiplexed process</a> — Overlapping report of the same root cause: file debug logging in a single <code>qwen --acp</code> process can leak one session&#39;s messages into another session&#39;s log file.</li>
<li><a href="https://github.com/QwenLM/qwen-code/issues/7167">#7167 Fleet Shepherd Dashboard</a> — Auto-maintained CI/CD status issue tracking bot-fleet PRs, scan-signal age, syncs, dispatches, releases, and cleanups. The community&#39;s live window into fleet health.</li>
<li><a href="https://github.com/QwenLM/qwen-code/issues/9032">#9032 feat(core): expose structured Workflow execution state</a> — CLOSED: requested stable JSON-safe state for phase transitions, agent dispatches, dependency edges, approval associations, and event history for dynamic Workflows; closed, indicating the capability shipped or was resolved.</li>
</ul>
<h2>Key PR Progress</h2>
<ul>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9540">#9540 fix(web-shell,webui): fall back to execCommand copy in non-secure contexts</a> — Routes all copy entry points through a <code>writeClipboardText()</code> helper that tries the async Clipboard API, then falls back to the legacy hidden-textarea <code>execCommand(&#39;copy&#39;)</code> path, fixing #9485.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9537">#9537 fix(channels): extract quoted DingTalk text, richText, and card replies</a> — Branches on the quoted message type as DingTalk actually delivers it so plain-text, richText, and interactiveCard replies reach the agent.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9402">#9402 feat: agent board — share work across independently started agents</a> — Filesystem-backed Agent Board MVP for sharing work across independent agents; repurposed after the original agent-view deletion idea was abandoned.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9518">#9518 fix(ci): stop counting wedged queued runs as in-flight in the shepherd</a> — Fixes a deadlock where GitHub creates a run that stays <code>queued</code> forever with zero jobs, and <code>cancel</code>/<code>force-cancel</code>/<code>delete</code> all refuse it, wedging the shepherd.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9527">#9527 fix(autofix): bind the sandbox image to its pulled digest</a> — Re-lands the digest-binding piece from frozen PR #9214, with the two Criticals from review (R11-1, R11-2) fixed.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9303">#9303 fix(web-shell): bound daemon transcript retention to stop renderer OOM crashes</a> — Releases raw replay snapshots after injection into the transcript store and caps replay rebuilds, preventing renderer OOM from unbounded session history.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9297">#9297 fix(autofix): make the brake&#39;s BLOCKED handoff a first-class round outcome</a> — Rounds following the growth brake&#39;s stop-<code>BLOCKED</code> instruction previously died as &quot;finished without required output file(s)&quot;; now a valid round outcome.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9491">#9491 feat(review): post --comment reviews to Aone Code via the a1 CLI</a> — Implements the write path for the Aone Code review chain: authorized runs post composed reviews through the org-standard CLI.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9448">#9448 feat(review): rule on contract documentation, and matrix layered guards</a> — Adds a path-scoped checklist for consumer-facing contract documentation that verifies prose against the actual diff.</li>
<li><a href="https://github.com/QwenLM/qwen-code/pull/9260">#9260 fix(web-shell): keep a manual session name across /clear</a> — Persists the user-chosen session name into the successor session before attachment, so auto-titling can&#39;t overwrite it; title provenance survives reloads and live updates.</li>
</ul>
<p>Also notable: <a href="https://github.com/QwenLM/qwen-code/pull/9506">#9506</a> (invalidate token counts on model-route switch), <a href="https://github.com/QwenLM/qwen-code/pull/9361">#9361</a> (scheduled tasks can reuse an existing live session), <a href="https://github.com/QwenLM/qwen-code/pull/8927">#8927</a> (per-channel <code>sessionRotation</code> bounding session lifetime), and <a href="https://github.com/QwenLM/qwen-code/pull/9441">#9441</a> (show edit/exec diffs when a PreToolUse hook returns <code>ask</code>).</p>
<h2>Feature Request Trends</h2>
<ul>
<li><strong>Structured runtime state for Workflows</strong> — <a href="https://github.com/QwenLM/qwen-code/issues/9032">#9032</a> requested stable JSON-safe execution state (phase transitions, dispatches, dependency edges, approvals); now closed, signaling the direction is being adopted.</li>
<li><strong>Cross-agent collaboration</strong> — <a href="https://github.com/QwenLM/qwen-code/pull/9402">#9402</a> (Agent Board) reflects growing demand for sharing work and state across independently started agents.</li>
<li><strong>Session lifecycle control</strong> — <a href="https://github.com/QwenLM/qwen-code/pull/9361">#9361</a> (bind scheduled tasks to existing sessions) and <a href="https://github.com/QwenLM/qwen-code/pull/8927">#8927</a> (session rotation bounds) push toward explicit, configurable session ownership and rotation.</li>
<li><strong>Review automation depth</strong> — PRs <a href="https://github.com/QwenLM/qwen-code/pull/9491">#9491</a>, <a href="https://github.com/QwenLM/qwen-code/pull/9448">#9448</a>, and <a href="https://github.com/QwenLM/qwen-code/pull/9332">#9332</a> show the review skill evolving toward write-back comments, contract-doc validation, and better import scoping.</li>
</ul>
<h2>Developer Pain Points</h2>
<ul>
<li><strong>Non-secure-context clipboard failures</strong> — Web Shell over remote <code>http://&lt;server-ip&gt;:4170</code> breaks all copy actions (<a href="https://github.com/QwenLM/qwen-code/issues/9485">#9485</a>).</li>
<li><strong>Integration channel payload drift</strong> — DingTalk&#39;s actual delivery shape for quoted text/richText/cards doesn&#39;t match the adapter&#39;s mapping, silently dropping context (<a href="https://github.com/QwenLM/qwen-code/issues/9536">#9536</a>).</li>
<li><strong>Session isolation in multiplexed daemon/ACP mode</strong> — Process-wide debug-log session state leaks across sessions (<a href="https://github.com/QwenLM/qwen-code/issues/9534">#9534</a>, <a href="https://github.com/QwenLM/qwen-code/issues/9535">#9535</a>).</li>
<li><strong>Web Shell session-state fragility</strong> — Manual session names lost on <code>/clear</code> (<a href="https://github.com/QwenLM/qwen-code/pull/9260">#9260</a>), sidebar sessions desyncing after mutations (<a href="https://github.com/QwenLM/qwen-code/pull/9533">#9533</a>), and renderer OOM from unbounded transcript retention (<a href="https://github.com/QwenLM/qwen-code/pull/9303">#9303</a>).</li>
<li><strong>CI deadlocks from wedged workflow runs</strong> — GitHub can create runs that stay <code>queued</code> with zero jobs and refuse all cancellation attempts, blocking the fleet shepherd (<a href="https://github.com/QwenLM/qwen-code/pull/9518">#9518</a>).</li>
</ul>
</details>

<hr>
<p><em>This digest is auto-generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Agents 生态日报 2026-08-20</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-agents</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-agents</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      <description>OpenClaw 生态日报 2026-08-20 Issues: 307 | PRs: 500 | 覆盖项目: 13 个 | 生成时间: 2026-08-20 04:55 UTC OpenClaw NanoBot Zeroclaw PicoClaw NanoClaw NullClaw IronClaw LobsterAI TinyClaw Moltis CoPaw ZeptoClaw EasyClaw OpenClaw 项目深度报告 OpenClaw 项目动态日报 — 2026-08-20 今日速览 过去24小时内，OpenClaw 项目更新密集：共 307 条 Issue 动态（新开/活跃 254 条，关闭 53 条）和 500 条 PR 动态（待合并 428 条，已合并/关闭 72 条），显示社区参与度与维护工作均处于高位。今日无新版本发布，但合入了多项针对模型选择（Codex/Claude CLI/GPT-5.6）与安全策略确认的关键修复。值得关注的是，P0 级网关启动阻塞问题（#108435、#112395）仍处于开放状态，为当前最大的稳定性风险点。 项目进展 今日无新版本 R...</description>
      <content:encoded><![CDATA[<h1>OpenClaw 生态日报 2026-08-20</h1>
<blockquote>
<p>Issues: 307 | PRs: 500 | 覆盖项目: 13 个 | 生成时间: 2026-08-20 04:55 UTC</p>
</blockquote>
<ul>
<li><a href="https://github.com/openclaw/openclaw">OpenClaw</a></li>
<li><a href="https://github.com/HKUDS/nanobot">NanoBot</a></li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw">Zeroclaw</a></li>
<li><a href="https://github.com/sipeed/picoclaw">PicoClaw</a></li>
<li><a href="https://github.com/qwibitai/nanoclaw">NanoClaw</a></li>
<li><a href="https://github.com/nullclaw/nullclaw">NullClaw</a></li>
<li><a href="https://github.com/nearai/ironclaw">IronClaw</a></li>
<li><a href="https://github.com/netease-youdao/LobsterAI">LobsterAI</a></li>
<li><a href="https://github.com/TinyAGI/tinyclaw">TinyClaw</a></li>
<li><a href="https://github.com/moltis-org/moltis">Moltis</a></li>
<li><a href="https://github.com/agentscope-ai/CoPaw">CoPaw</a></li>
<li><a href="https://github.com/qhkm/zeptoclaw">ZeptoClaw</a></li>
<li><a href="https://github.com/gaoyangz77/easyclaw">EasyClaw</a></li>
</ul>
<hr>
<h2>OpenClaw 项目深度报告</h2>
<h1>OpenClaw 项目动态日报 — 2026-08-20</h1>
<h2>今日速览</h2>
<p>过去24小时内，OpenClaw 项目更新密集：共 307 条 Issue 动态（新开/活跃 254 条，关闭 53 条）和 500 条 PR 动态（待合并 428 条，已合并/关闭 72 条），显示社区参与度与维护工作均处于高位。今日无新版本发布，但合入了多项针对模型选择（Codex/Claude CLI/GPT-5.6）与安全策略确认的关键修复。值得关注的是，P0 级网关启动阻塞问题（<a href="https://github.com/openclaw/openclaw/issues/108435">#108435</a>、<a href="https://github.com/openclaw/openclaw/issues/112395">#112395</a>）仍处于开放状态，为当前最大的稳定性风险点。</p>
<h2>项目进展</h2>
<p>今日无新版本 Release，重点回顾已合并/关闭的 PR 及其对项目的推进：</p>
<ul>
<li><strong>模型选择与认证修复（合并）</strong>：<a href="https://github.com/openclaw/openclaw/pull/126531">PR #126531</a> 修复了用户显式选择 Codex harness 后仍被静默切换到 embed 路径的问题；<a href="https://github.com/openclaw/openclaw/pull/126492">PR #126492</a> 确保通过 Codex 选择 GPT-5.6 Max/Ultra 时推理强度不会被降级。两项合并直接回应了近期模型选择链路上的多个回归报告。</li>
<li><strong>安全策略确认机制落地（合并）</strong>：<a href="https://github.com/openclaw/openclaw/pull/116489">PR #116489</a> 与 <a href="https://github.com/openclaw/openclaw/pull/120900">PR #120900</a> 相继合入，为 <code>security.installPolicy</code> 引入 <code>warn</code> 返回值和 CLI/UI 双重确认界面，安装策略警告不再是一纸空文。这一系列改动可能成为后续安全审查类 Issue（如 <a href="https://github.com/openclaw/openclaw/issues/79168">#79168</a>）的基础设施铺垫。</li>
<li><strong>UI 细节修复（合并）</strong>：<a href="https://github.com/openclaw/openclaw/pull/126303">PR #126303</a> 修复了 Control UI 完成工作间距失衡的问题，属于小但高频的用户体验改进。</li>
</ul>
<p>整体来看，项目今日专注于模型选择正确性、安全策略确认与 UI 打磨，属于稳定性和体验优化导向的一天。</p>
<h2>社区热点</h2>
<p>今日讨论最活跃的 Issue 集中在<strong>消息/会话状态丢失</strong>与<strong>升级后启动失败</strong>两类问题上，反映了用户对数据可靠性和版本平滑升级的高关注度：</p>
<ul>
<li><strong><a href="https://github.com/openclaw/openclaw/issues/48003">#48003 — 评论 20 条</a></strong>：<code>steer</code> 模式未在主会话轮次中注入消息，导致用户消息被排队到轮次结束。该 Issue 已持续 5 个月，带有 <code>diamond lobster</code> 高评级和 <code>linked-pr-open</code> 标签，说明已有修复 PR 在途但尚未合入。用户群体的反复 +1 表明此问题对依赖实时干预的高级用户影响显著。</li>
<li><strong><a href="https://github.com/openclaw/openclaw/issues/38327">#38327 — 评论 14 条</a></strong>：2026.3.2 版本中 google-vertex/gemini-3.1-pro-preview 出现 &quot;Cannot convert undefined or null to object&quot; 回归错误。尽管创建于 3 月，今日仍有更新，可能与用户持续补充复现信息或维护者近期排查有关。</li>
<li><strong><a href="https://github.com/openclaw/openclaw/issues/108435">#108435 — 评论 14 条</a></strong>：升级至 2026.7.1 后 gateway 无法通过 systemd、ollama、手动三种方式启动。P0 级且为 <code>diamond lobster</code>，无关联 fix PR，是当前最严重的未解决回归之一。</li>
<li><strong><a href="https://github.com/openclaw/openclaw/issues/53628">#53628 — 评论 14 条</a></strong>：安装 skill 时 <code>${XDG_CONFIG_HOME}</code> 未被展开解释，Docker 部署用户受影响明显。</li>
<li><strong><a href="https://github.com/openclaw/openclaw/issues/113306">#113306 — 评论 13 条</a></strong>：SQLite snapshot 恢复缺乏端到端崩溃与身份保证，涉及数据丢失风险（<code>impact:data-loss</code>），处于 <code>needs-maintainer-review</code> 状态。</li>
</ul>
<p><strong>诉求分析</strong>：评论数居前的 Issue 呈现高度一致性——用户对消息丢失、会话状态错乱、升级后启动失败这三类&quot;伤筋动骨&quot;的问题最为敏感，且这些问题大多已存活数月，社区耐心正在消耗。</p>
<h2>Bug 与稳定性</h2>
<p>按严重程度排列今日活跃的 Bug/回归问题：</p>
<p><strong>P0 — 网关启动/升级阻塞（无 fix PR）</strong></p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/108435">#108435</a>：升级至 2026.7.1 后 gateway 完全无法启动（systemd/ollama/手动均失败），报错 <code>gateway did not start on 127.0...</code>。14 条评论，高活跃，带 <code>source-repro</code>。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/112395">#112395</a>：从 2026.6.11 升级至 2026.7.1 后启动迁移预检阻塞，迁移表与租约均为空，<code>diamond lobster</code> + <code>ux-release-blocker</code>。</li>
</ul>
<p><strong>P1 — 消息/会话状态损坏（部分已有 fix PR）</strong></p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/48003">#48003</a>：<code>steer</code> 模式消息未注入主会话轮次，20 条评论，已有 linked PR。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/90944">#90944</a>：<code>sessions_yield</code> 恢复回复被记录但未投递，用户收到的是子代理原始摘要而非父代理回复——消息丢失类问题。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/80498">#80498</a>：子代理完成公告在 tool-use 轮次后可能过早或重复触发。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/119454">#119454</a>：卡死会话恢复被 <code>active_embedded_run</code> 自抑制，循环记录 <code>observe_only</code> 直到重启。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/83598">#83598</a>：<code>anthropic:claude-cli</code> OAuth 刷新在 2026.5.12 上仍然失效，尽管 #73682 声称已修复。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/77249">#77249</a>：Slack socket-mode 重连管理器在僵尸 WebSocket 上挂起，无事件无日志，需手动重启。</li>
</ul>
<p><strong>P1 — 其他</strong></p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/38327">#38327</a>：google-vertex/gemini-3.1-pro-preview 对象转换回归，14 条评论。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/113306">#113306</a>：SQLite snapshot 恢复在父目录/身份守卫上缺乏持久化保证，<code>data-loss</code> 风险。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/124284">#124284</a>：v2026.8.1-beta.2 的流包装器导致 vLLM <code>openai-completions</code> 子代理生成畸形 XML 工具调用。</li>
</ul>
<p><strong>P2 — 值得关注</strong></p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/88657">#88657</a>：DeepSeek V4 Flash 在 2026.5.27/28 产生不完整轮次（<code>payloads=0, tools=2</code>），5.26 正常，指向回归。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/95610">#95610</a>：OpenAI 模型路径上逐轮动态注入破坏前缀缓存，增加延迟与成本。</li>
<li><a href="https://github.com/openclaw/openclaw/issues/95840">#95840</a>：<code>contextPruning</code> 的 <code>cache-ttl</code> 模式对 OpenAI 模型永远不会触发，因为 <code>isCacheTtlEligibleProvider</code> 直接排除了 OpenAI。</li>
</ul>
<h2>功能请求与路线图信号</h2>
<ul>
<li><strong>投递队列 TTL（<a href="https://github.com/openclaw/openclaw/issues/16555">#16555</a>）</strong>：要求为投递队列消息增加可配置 TTL，防止 gateway 重启后陈旧消息洪水式冲刷频道。已有 <code>linked-pr-open</code> 标签，且为 <code>diamond lobster</code> 级别，<strong>较可能进入下一版本</strong>。</li>
<li><strong>模型降级审批模式（<a href="https://github.com/openclaw/openclaw/issues/33975">#33975</a>）</strong>：用户要求主模型失败时可选需审批的降级模式，而非静默切换，同时要求消息中标注实际使用的模型。与今日合并的 <a href="https://github.com/openclaw/openclaw/pull/116489">PR #116489</a>（安装策略确认）在&quot;可审计的人工干预&quot;方向上同频，路线图信号积极。</li>
<li><strong>可配置会话启动消息（<a href="https://github.com/openclaw/openclaw/issues/45501">#45501</a>）</strong>：<code>session.resetPrompt</code> 让用户自定义 <code>/new</code> 或 <code>/reset</code> 后的注入文本，当前为硬编码。<code>needs-product-decision</code> 挂起，需产品侧拍板。</li>
<li><strong><code>maxTurns</code>/<code>maxToolCalls</code> 限制（<a href="https://github.com/openclaw/openclaw/issues/9912">#9912</a>）</strong>：限制 agent 工具迭代次数，防止模型忽略系统提示进入死循环。P2 级别，<code>diamond lobster</code>，价值明确但设计需要谨慎。</li>
<li><strong>工具输出提示注入扫描（<a href="https://github.com/openclaw/openclaw/issues/79168">#79168</a>）</strong>：在 XML 结构性隔离之外增加内容级扫描，当前处于 <code>needs-security-review</code>，属于安全路线图上的长期议题。</li>
<li><strong>消息内联合并（<a href="https://github.com/openclaw/openclaw/issues/15022">#15022</a>）</strong>：将交错的文本与工具调用块合并为单条出站消息，减少 Telegram 等渠道的消息轰炸。已有 <code>linked-pr-open</code>。</li>
<li><strong>WhatsApp 贴纸发送（<a href="https://github.com/openclaw/openclaw/issues/7476">#7476</a>）</strong>：当前 <code>message</code> 工具发送 <code>.webp</code> 时仅为普通图片而非贴纸。</li>
</ul>
<p>综合来看，投递队列 TTL、消息内联合并与模型降级审批是近期路线图上最有可能落地的三项。</p>
<h2>用户反馈摘要</h2>
<ul>
<li><strong>升级焦虑真实存在</strong>：<a href="https://github.com/openclaw/openclaw/issues/108435">#108435</a> 与 <a href="https://github.com/openclaw/openclaw/issues/112395">#112395</a> 的持续活跃证明用户对&quot;升级即破坏&quot;的容忍度正在下降。有生产用户在 <a href="https://github.com/openclaw/openclaw/issues/123799">#123799</a> 中明确请求：受 Codex 404 问题影响的生产环境需要<strong>安全升级/回退操作指南</strong>，而不是等待下个版本修复——这类&quot;运维指导&quot;诉求是社区声音中容易忽视的部分。</li>
<li><strong>OAuth/认证刷新问题反复</strong>：<a href="https://github.com/openclaw/openclaw/issues/83598">#83598</a> 用户反馈&quot;修复后仍无效&quot;并附详细环境，说明跨版本认证一致性测试需要加强。</li>
<li><strong>静默失败是最大的挫败感来源</strong>：<a href="https://github.com/openclaw/openclaw/issues/58957">#58957</a> 指出模型切换时上下文过大导致静默失败、无明确错误提示；<a href="https://github.com/openclaw/openclaw/issues/108215">#108215</a> 反映上下文用量从 57% 骤降至 13% 且无压缩记录——用户面对这些状态变化时完全无法判断系统是否正常。</li>
<li><strong>多智能体场景是高频痛点</strong>：<a href="https://github.com/openclaw/openclaw/issues/56692">#56692</a>（群聊上下文串扰）、<a href="https://github.com/openclaw/openclaw/issues/124926">#124926</a>（<code>infer image generate</code> 在多 agent fleet 中缺少 agent 选择器）、<a href="https://github.com/openclaw/openclaw/issues/122625">#122625</a>（Matrix 房间无法解析会话路由）——多 agent 功能的完成度直接影响采用信心。</li>
<li><strong>正面反馈</strong>：<a href="https://github.com/openclaw/openclaw/pull/126303">#126303</a> 与 <a href="https://github.com/openclaw/openclaw/pull/123535">#123535</a> 等 UI 打磨 PR 的及时合入，说明维护团队对小而明确的体验问题响应迅速，社区对此类&quot;听得见反馈&quot;的行为有积极评价。</li>
</ul>
<h2>待处理积压</h2>
<p>以下 Issue/PR 长期未获关键进展或维护者行动，建议重点关注：</p>
<ul>
<li><strong><a href="https://github.com/openclaw/openclaw/issues/48003">#48003 — 存活 157 天，评论 20 条</a></strong>：<code>diamond lobster</code> 级别的消息注入缺陷，已有 linked PR 但迟迟未合入。作为社区最活跃 Issue，长期挂起对信任度消耗很大。</li>
<li><strong><a href="https://github.com/openclaw/openclaw/issues/30381">#30381 — 存活 172 天，<code>recovery-stuck</code></a></strong>：<code>x-openclaw-agent-id</code> 头存在时仍校验 <code>model</code> 字段。<code>needs-maintainer-review</code> + <code>needs-product-decision</code> 双重挂起，5 个月无实质进展。</li>
<li><strong><a href="https://github.com/openclaw/openclaw/issues/77249">#77249 — 存活 108 天，<code>recovery-stuck</code></a></strong>：Slack 重连僵尸态导致需手动重启，<code>diamond lobster</code> 且无 fix PR。</li>
<li><strong><a href="https://github.com/openclaw/openclaw/issues/16555">#16555 — 存活 187 天，<code>recovery-stuck</code></a></strong>：投递队列 TTL 需求，<code>diamond lobster</code> + <code>linked-pr-open</code>，但 PR 与 Issue 均未合入/关闭。</li>
<li><strong><a href="https://github.com/openclaw/openclaw/issues/77733">#77733 — 存活 107 天，<code>recovery-stuck</code></a></strong>：裸 <code>/new</code> 与 <code>/reset</code> 不再触发人格问候的回归，社区 +1 较多，但多个标签（needs-maintainer-review、needs-product-decision）间循环。</li>
<li><strong><a href="https://github.com/openclaw/openclaw/issues/112395">#112395 — P0 存活 30 天</a></strong>：升级迁移阻塞为发布阻断级缺陷，无关联 PR 且 6 条评论后无维护者回应，升级链路风险在持续累积。</li>
<li><strong><a href="https://github.com/openclaw/openclaw/pull/96011">PR #96011 — 存活 58 天</a></strong>：Skill Workshop 防护修复，<code>waiting on author</code> 但长时间无更新，维护者可能需要介入或主动关闭。</li>
</ul>
<hr>
<h2>横向生态对比</h2>
<h1>AI 智能体开源生态横向对比分析日报 — 2026-08-20</h1>
<h2>1. 生态全景</h2>
<p>个人 AI 助手/自主智能体开源生态正处于<strong>高密度迭代期</strong>：以 OpenClaw 为首的平台型项目单日处理 807 条 Issue/PR 动态，NanoClaw、CoPaw、Zeroclaw 等中坚力量同步保持每日 30–50 条 PR 级更新量。各项目不约而同将资源投向<strong>安全加固</strong>（渠道授权、工具隔离、漏洞修复）、<strong>记忆/会话可靠性</strong>（防覆盖、防丢失、断点恢复）与<strong>模型降级透明度</strong>三条主线。生态内部已出现明确分工——通用平台、垂直场景（电商/教育/硬件）、本地优先、安全优先等差异化定位正在固化。值得注意的是，<strong>升级稳定性与数据可靠性</strong>已成为跨项目用户投诉最集中的共性痛点，直接影响社区信任度。</p>
<h2>2. 各项目活跃度对比</h2>
<table>
<thead>
<tr>
<th>项目</th>
<th>Issues 动态</th>
<th>PR 动态</th>
<th>Release</th>
<th>健康度评估</th>
</tr>
</thead>
<tbody><tr>
<td><strong>OpenClaw</strong></td>
<td>307（新开/活跃 254，关闭 53）</td>
<td>500（待合并 428，合并/关闭 72）</td>
<td>无</td>
<td>高活跃但承压：P0 网关启动阻塞未解，合并积压巨大</td>
</tr>
<tr>
<td><strong>NanoBot</strong></td>
<td>3 新开</td>
<td>20（合并/关闭 7，待合并 13）</td>
<td>无</td>
<td>良好：问题响应快（OAuth 数小时即有修复 PR），但 8 条 conflict 积压</td>
</tr>
<tr>
<td><strong>Zeroclaw</strong></td>
<td>26 条更新</td>
<td>50（合并/关闭 7，待合并 43）</td>
<td>无</td>
<td>高活跃：43 条待合并积压明显，RFC 决策阻塞风险升高</td>
</tr>
<tr>
<td><strong>PicoClaw</strong></td>
<td>1 关闭</td>
<td>5（关闭 2，待合并 3）</td>
<td>无</td>
<td>中低：stale PR 悬置，新功能输入有限</td>
</tr>
<tr>
<td><strong>NanoClaw</strong></td>
<td>3 新开</td>
<td>33（合并/关闭 23）</td>
<td>无</td>
<td>高活跃：Slack 重构密集推进，但新机安装/Node 26 兼容性薄弱</td>
</tr>
<tr>
<td><strong>NullClaw</strong></td>
<td>0</td>
<td>1 待合并</td>
<td>无</td>
<td>低：维护模式，仅文档修复</td>
</tr>
<tr>
<td><strong>IronClaw</strong></td>
<td>未披露总量（热点 #7732 等）</td>
<td>39（合并/关闭 18，待合并 21）</td>
<td><strong>v1.3.0</strong></td>
<td>健康：v1.4.0 功能密集落地，CI 超时根因已修复</td>
</tr>
<tr>
<td><strong>LobsterAI</strong></td>
<td>2 stale</td>
<td>9（合并/关闭 8，待合并 1）</td>
<td>无</td>
<td>中：安装器问题响应快，4 个月 PR 未合并需关注</td>
</tr>
<tr>
<td><strong>TinyClaw</strong></td>
<td>0</td>
<td>0</td>
<td>无</td>
<td>静默</td>
</tr>
<tr>
<td><strong>Moltis</strong></td>
<td>1 关闭</td>
<td>4 合并/关闭</td>
<td><strong>20260818.10</strong></td>
<td>健康：CWE-306 当日闭环，无积压</td>
</tr>
<tr>
<td><strong>CoPaw</strong></td>
<td>19（新开 3，关闭 16）</td>
<td>45（合并/关闭 26，待合并 19）</td>
<td>无</td>
<td>高活跃：稳定性修复效率高，但历史信任事件（#2884）亟待官方结论</td>
</tr>
<tr>
<td><strong>ZeptoClaw</strong></td>
<td>0</td>
<td>0</td>
<td>无</td>
<td>静默</td>
</tr>
<tr>
<td><strong>EasyClaw</strong></td>
<td>0</td>
<td>0</td>
<td><strong>v1.8.101–103</strong></td>
<td>发布驱动：24 小时 3 版迭代，但社区输入为零，反馈渠道存疑</td>
</tr>
</tbody></table>
<h2>3. OpenClaw 在生态中的定位</h2>
<ul>
<li><strong>生态核心参照系</strong>：OpenClaw 的单日动态量（307 Issues / 500 PRs）是第二名 CoPaw 的约 7 倍，是 NanoBot 的 25 倍，事实上定义了行业问题分类与严重度评估标准（如 <code>diamond lobster</code>、P0/P1 分级、<code>source-repro</code> 标签体系）。</li>
<li><strong>技术路线差异</strong>：OpenClaw 走&quot;全栈聚合&quot;路线——统一接入 Codex/Claude CLI/GPT-5.6 等模型 harness、多渠道消息网关、技能系统、安全策略与 Control UI，追求&quot;开箱即用的个人 AI 中控&quot;；而 Zeroclaw 倾向&quot;精简核心 + 外部集成&quot;，IronClaw 侧重&quot;本地沙箱 + 企业级能力规范&quot;，NanoBot 则聚焦&quot;轻量 TUI + 记忆压缩&quot;。OpenClaw 的覆盖面最广，但也因此承担了最大的回归面风险（今日 2 个 P0 网关启动问题即为例证）。</li>
<li><strong>社区规模优势</strong>：OpenClaw 拥有生态内最活跃的反馈回路——单 Issue 最高 20 条评论、PR 提出到合并响应以天计；但 428 条待合并 PR 与 157 天未合入的 <code>diamond lobster</code> Issue（#48003）也暴露了超大规模社区的治理瓶颈。这是其他中小项目尚未面临的结构性挑战。</li>
</ul>
<h2>4. 共同关注的技术方向</h2>
<table>
<thead>
<tr>
<th>方向</th>
<th>涉及项目</th>
<th>具体诉求</th>
</tr>
</thead>
<tbody><tr>
<td><strong>安全加固与权限确认</strong></td>
<td>OpenClaw、Zeroclaw、Moltis、NanoBot</td>
<td>安装策略需用户确认（OpenClaw #116489）；渠道发件人校验/Shell 子进程隔离/工具 allowlist 强制（Zeroclaw #9428/#9827/#9433）；Vault 接口未鉴权 CWE-306（Moltis #1177）；仅手动调用技能（NanoBot #5405）</td>
</tr>
<tr>
<td><strong>记忆/会话状态可靠性</strong></td>
<td>OpenClaw、NanoBot、Zeroclaw、CoPaw、PicoClaw</td>
<td>消息丢失与注入错位（OpenClaw #48003）；后台保存覆盖新会话（NanoBot #5271）；ACP 失败轮次消失（Zeroclaw #9333）；envs.json 损坏被静默覆写（CoPaw #7118）；路由 agent 不记忆历史（PicoClaw #3316）</td>
</tr>
<tr>
<td><strong>模型降级与可审计回退</strong></td>
<td>OpenClaw、PicoClaw</td>
<td>主模型失败时需审批而非静默切换，并标注实际模型（OpenClaw #33975）；可配置默认模型回退链（PicoClaw #3200）</td>
</tr>
<tr>
<td><strong>OAuth/凭据管理</strong></td>
<td>NanoBot、OpenClaw、Zeroclaw</td>
<td>Docker 环境 OAuth 存储权限（NanoBot #5444）；OAuth 刷新跨版本失效（OpenClaw #83598）；Anthropic stored OAuth profiles（Zeroclaw #9420）</td>
</tr>
<tr>
<td><strong>多智能体/多租户上下文隔离</strong></td>
<td>OpenClaw、CoPaw、NanoClaw</td>
<td>群聊上下文串扰（OpenClaw #56692）；钉钉群共享/隔离上下文可配置（CoPaw #7158）；Slack agents 按需安装以隔离复杂度（NanoClaw #3357/#3358）</td>
</tr>
<tr>
<td><strong>安装/升级健壮性</strong></td>
<td>NanoClaw、Zeroclaw、EasyClaw、CoPaw</td>
<td>Node 26 下 better-sqlite3 构建失败（NanoClaw #3359）；Windows <code>TaskDialogIndirect</code> 缺失启动失败（Zeroclaw #9290）；macOS Gatekeeper 拦截（EasyClaw）；打包后端 PATH 解析（CoPaw #5861）</td>
</tr>
<tr>
<td><strong>本地 MCP/工具链打通</strong></td>
<td>IronClaw</td>
<td>本机 MCP server 无法通过 stdio 或 loopback HTTP 接入（IronClaw #5998），外部贡献者已提交窄方案 PR #7757</td>
</tr>
<tr>
<td><strong>卡死/静默失败可恢复</strong></td>
<td>CoPaw、OpenClaw、NanoBot</td>
<td>LLM 流中断永久停在 Thinking 态（CoPaw #7102/#7150）；卡死会话被自抑制循环（OpenClaw #119454）；后台任务失败无日志（NanoBot #5431）</td>
</tr>
</tbody></table>
<h2>5. 差异化定位分析</h2>
<table>
<thead>
<tr>
<th>项目</th>
<th>功能侧重</th>
<th>目标用户</th>
<th>技术架构关键差异</th>
</tr>
</thead>
<tbody><tr>
<td><strong>OpenClaw</strong></td>
<td>通用智能体中控：多模型 harness、多渠道网关、技能/安全策略、Control UI</td>
<td>技术发烧友、高级个人用户、中小团队</td>
<td>聚合式架构，模型选择层（Codex/Claude CLI/GPT-5.6）与网关深度耦合</td>
</tr>
<tr>
<td><strong>NanoBot</strong></td>
<td>TUI/WebUI 优先的轻量助手，记忆压缩与澄清交互创新</td>
<td>开发者、本地优先用户</td>
<td>内存压缩复用对话前缀、<code>ask_clarification</code> 中断式交互</td>
</tr>
<tr>
<td><strong>Zeroclaw</strong></td>
<td>安全/权限契约驱动的模块化核心</td>
<td>安全敏感的自托管者、企业 PoC</td>
<td>RFC 主导治理，渠道授权/Shell 隔离/工具 allowlist 为一级公民</td>
</tr>
<tr>
<td><strong>PicoClaw</strong></td>
<td>嵌入式/轻量部署（Sipeed 硬件背景），Telegram 体验打磨</td>
<td>硬件玩家、轻量机器人场景</td>
<td>低资源占用，Telegram 私聊/forum/topic 深度适配</td>
</tr>
<tr>
<td><strong>NanoClaw</strong></td>
<td>Slack 优先的团队助手，provisioning 与安装体验工程化</td>
<td>团队协作场景、Slack 重度用户</td>
<td><code>--slack-agents</code> opt-in 产品边界设计</td>
</tr>
<tr>
<td><strong>IronClaw</strong></td>
<td>本地沙箱 + 企业级能力规范（MCP/Provider 错误统一、持久化 per-user sandbox）</td>
<td>开发者、本地/内网部署</td>
<td>容器复用（Docker Exec ~40ms）、能力响应规范化、CI 超时治理</td>
</tr>
<tr>
<td><strong>LobsterAI</strong></td>
<td>中文桌面应用，Agent 协作（Cowork）+ 文件预览，Windows/macOS 安装器</td>
<td>中文个人/教育用户</td>
<td>桌面壳 + 引擎分离，安装器两阶段上传</td>
</tr>
<tr>
<td><strong>Moltis</strong></td>
<td>安全优先的自托管助手，WhatsApp 深度适配</td>
<td>隐私敏感的自托管用户</td>
<td>Vault 凭据体系、严格鉴权审计、渠道语义（mention/reply）精细处理</td>
</tr>
<tr>
<td><strong>CoPaw</strong></td>
<td>中文生态 + Computer Use 视觉 Agent，远程媒体/PDF 处理</td>
<td>中文用户、视觉自动化场景</td>
<td>远程媒体冻结/SSRF 防护、Computer Use 窗口表面观察、记忆静默通知</td>
</tr>
<tr>
<td><strong>EasyClaw</strong></td>
<td>飞书集成 + 达人协作/WMS/多店铺运营自动化</td>
<td>电商运营团队</td>
<td>无社区 PR 流程，纯 Release 驱动，飞书连接器 + 审批流</td>
</tr>
</tbody></table>
<h2>6. 社区热度与成熟度</h2>
<p><strong>第一梯队——超大规模迭代（每日 30+ PR 级）：</strong> OpenClaw、CoPaw、Zeroclaw、NanoClaw。共同特征是合并吞吐高、Issue 响应快，但也都面临不同程度的积压或回归风险。OpenClaw 与 Zeroclaw 的 PR 积压（428/43 条）开始成为治理负担。</p>
<p><strong>第二梯队——质量巩固期（每日 7–20 PR 级）：</strong> IronClaw、NanoBot、LobsterAI、Moltis。合并节奏适中，修复闭环率高：Moltis 当日 4/4 PR 关闭且无积压；IronClaw 发布 v1.3.0 后正以模块化节奏推进 v1.4.0 系列 PR。</p>
<p><strong>第三梯队——缓慢/维护模式：</strong> PicoClaw（stale PR 悬置）、NullClaw（仅文档修复）、EasyClaw（有版本无社区）。</p>
<p><strong>第四梯队——静默：</strong> TinyClaw、ZeptoClaw，24 小时零动态。</p>
<p><strong>成熟度特征信号：</strong></p>
<ul>
<li>头部项目开始出现<strong>产品边界收缩</strong>：NanoClaw 将 Slack agents 改为 opt-in，Zeroclaw 讨论精简核心，均为早期&quot;大而全&quot;策略后的主动回调。</li>
<li>治理透明化成为新焦点：Zeroclaw 建立维护者决策队列（#8692），IronClaw 面临外部贡献 PR 40 天无官方回应，积压的 RFC 与 <code>do-not-merge</code> 标记正在考验社区耐心。</li>
<li>中文社区项目（CoPaw、LobsterAI、EasyClaw）在 UI 细节、本地化渠道（钉钉/飞书）与安装器层面的投入显著，但 CoPaw 的历史数据安全事件（#2884）提醒：信任修复比功能迭代更紧迫。</li>
</ul>
<h2>7. 值得关注的趋势信号</h2>
<ol>
<li><p><strong>安全默认值正在成为准入门槛</strong>：Moltis 的 Vault 未鉴权漏洞、Zeroclaw 的 Shell 逃逸/渠道发件人校验、OpenClaw 的安装策略确认——安全不再只是配置项，而是从架构层内嵌（权限契约、子进程隔离、原子写入）。新项目若未在设计初期考虑安全边界，将很快在社区审查中暴露。</p>
</li>
<li><p><strong>&quot;升级即破坏&quot;焦虑已跨项目蔓延</strong>：OpenClaw P0 网关启动失败（#108435/#112395）、Zeroclaw 新配置天生损坏（#9436）、NanoClaw Node 26 构建失败——用户对版本升级的容忍度显著下降，已有生产用户明确要求<strong>安全升级/回退操作指南</strong>而非等待补丁。提供迁移预检、回滚路径和升级前验证将成为项目的核心竞争力。</p>
</li>
<li><p><strong>静默失败是最大的体验杀手</strong>：CoPaw 的&quot;Thinking 无限挂起&quot;、OpenClaw 的&quot;上下文用量骤降无压缩记录&quot;、NanoBot 的&quot;后台失败无日志&quot;——用户能容忍功能缺失，但不能容忍系统无反馈。可观测性（turn 级轨迹、失败终态持久化、显式错误码）正从可选项变为必选项。</p>
</li>
<li><p><strong>模型降级必须可解释、可审批</strong>：OpenClaw 与 PicoClaw 同时收到&quot;模型回退链&quot;相关诉求，且用户明确反对静默切换。结合 CoPaw 的&quot;模型幻觉 URL 导致会话瘫痪&quot;，可以推断：<strong>模型的不可靠性需要由平台层兜底，且兜底行为必须对用户透明</strong>。</p>
</li>
<li><p><strong>多智能体场景进入深水区</strong>：上下文串扰、群聊共享/隔离语义、agent 选择器、持久化沙箱——各项目正从&quot;单 agent 对话&quot;向&quot;多 agent 协作/多租户隔离&quot;迁移，但完成度参差不齐。先解决隔离与路由正确性的项目将获得差异化优势。</p>
</li>
<li><p><strong>本地优先与轻量化回潮</strong>：NanoBot 的本地记忆压缩、IronClaw 的本地沙箱与环回 MCP 支持、Zeroclaw 的&quot;精简核心&quot;RFC——在 SaaS/PaaS 主导的背景下，一部分用户明确偏好数据不出本机的部署形态。本地 MCP 传输缺口（IronClaw #5998）是一个被验证但未满足的真实需求。</p>
</li>
<li><p><strong>治理效率决定生态位</strong>：Zeroclaw 的维护者决策队列、IronClaw 悬置 40 天的外部贡献、OpenClaw 157 天未合入的高评级 Issue——社区活跃度与治理效率之间的剪刀差正在扩大。能够建立快速决策机制（如定期 RFC 评审、P0 限时响应 SLA）的项目，将更有效地将社区热情转化为项目资产。</p>
</li>
</ol>
<hr>
<h2>同赛道项目详细报告</h2>
<details>
<summary><strong>NanoBot</strong> — <a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a></summary>

<h1>NanoBot 项目日报 — 2026-08-20</h1>
<h2>今日速览</h2>
<p>过去 24 小时 NanoBot 项目保持高度活跃：新增 3 个 Issue（全为开放状态），PR 活动密集，共 20 条，其中 7 条已合并/关闭，13 条待合并。无新版本发布。值得关注的是 TUI/WebUI 与 Docker OAuth 存储问题集中获得修复，同时多条 PR 已标记合并冲突等待处理。整体项目健康度良好，但积压 PR 的冲突解决与合并效率需维护者关注。</p>
<hr>
<h2>版本发布</h2>
<p>今日无新版本发布。</p>
<hr>
<h2>项目进展</h2>
<p>今日 7 条 PR 被合并/关闭，覆盖 TUI、WebUI、内存管理、技能系统等多个模块：</p>
<ul>
<li><strong>[PR #5449] fix(tui): keep navigation commands in Herdr panes</strong>（已合并）— 修复 Herdr 托管面板中 TUI 导航命令不可用的问题，明确 Herdr 管理终端布局、nanobot 管理会话/新聊天/分支的职责边界。→ <a href="https://github.com/HKUDS/nanobot/pull/5449">https://github.com/HKUDS/nanobot/pull/5449</a></li>
<li><strong>[PR #5448] feat(tui): start fresh chats in launch workspace</strong>（已合并）— TUI 每次启动默认创建全新 WebSocket 会话，以命令启动目录作为初始工作区，移除旧的 last-session 持久化逻辑。→ <a href="https://github.com/HKUDS/nanobot/pull/5448">https://github.com/HKUDS/nanobot/pull/5448</a></li>
<li><strong>[PR #5443] fix(tui): expose /exit in command menu</strong>（已合并）— 将 <code>/exit</code> 注册为 TUI 本地命令并加入斜杠命令菜单，统一退出路径。→ <a href="https://github.com/HKUDS/nanobot/pull/5443">https://github.com/HKUDS/nanobot/pull/5443</a></li>
<li><strong>[PR #5440] perf(memory): reuse conversation prefix for local compaction</strong>（已合并）— 内存压缩复用模型对话前缀构建请求，保留结构化工具调用，同时禁用工具执行，提升压缩效率。→ <a href="https://github.com/HKUDS/nanobot/pull/5440">https://github.com/HKUDS/nanobot/pull/5440</a></li>
<li><strong>[PR #4527] Add ask_clarification tool</strong>（已合并）— 新增内置 <code>ask_clarification</code> 工具，支持在智能体回合中中断并向用户提问，附带 context trimming 保留澄清上下文。→ <a href="https://github.com/HKUDS/nanobot/pull/4527">https://github.com/HKUDS/nanobot/pull/4527</a></li>
<li><strong>[PR #5438] fix(webui): return promptly after Ctrl-C</strong>（已合并）— 修复 WebUI 客户端按 Ctrl-C 后退出卡住的问题，释放租约并保留网关优雅关闭流程。→ <a href="https://github.com/HKUDS/nanobot/pull/5438">https://github.com/HKUDS/nanobot/pull/5438</a></li>
<li><strong>[PR #5341] fix(skills): make weather workflow Windows-safe</strong>（已合并）— 修复 Windows PowerShell 中 <code>curl</code> 被 <code>Invoke-WebRequest</code> 别名解析导致天气技能失败的问题。→ <a href="https://github.com/HKUDS/nanobot/pull/5341">https://github.com/HKUDS/nanobot/pull/5341</a></li>
</ul>
<p>整体来看，今日合并内容集中在终端体验与稳定性修复，<code>ask_clarification</code> 工具的合入为后续交互式 Agent 能力打下基础。</p>
<hr>
<h2>社区热点</h2>
<p>尽管今日 Issue/PR 评论数据未标注详细热度，但以下条目因主题集中、跨 PR 联动而成为社区关注焦点：</p>
<ul>
<li><p><strong>Docker OAuth 登录问题（Issue #5444 + PR #5446 + PR #5445）</strong> — Issue #5444 报告 Docker 中 OpenAI OAuth 登录失败（<code>PermissionError</code>），仅数小时内出现两条针对性修复 PR：PR #5446（CLI 路由 OAuth 存储至 nanobot 数据目录）、PR #5445（Docker 镜像持久化 OAuth 客户端数据）。这是今日最典型的&quot;问题-修复&quot;即时联动。→ <a href="https://github.com/HKUDS/nanobot/issues/5444">https://github.com/HKUDS/nanobot/issues/5444</a> ｜ <a href="https://github.com/HKUDS/nanobot/pull/5446">https://github.com/HKUDS/nanobot/pull/5446</a> ｜ <a href="https://github.com/HKUDS/nanobot/pull/5445">https://github.com/HKUDS/nanobot/pull/5445</a></p>
</li>
<li><p><strong>Dream 内存游标卡死（Issue #5441 + PR #5442）</strong> — Issue #5441 描述 Dream 运行中即使完成有效记忆编辑仍被判定为 &quot;did not complete&quot;，导致同一历史批次被重复处理、产生重复编辑。PR #5442 直接修复该问题并在提交信息中引用 issue。→ <a href="https://github.com/HKUDS/nanobot/issues/5441">https://github.com/HKUDS/nanobot/issues/5441</a> ｜ <a href="https://github.com/HKUDS/nanobot/pull/5442">https://github.com/HKUDS/nanobot/pull/5442</a></p>
</li>
<li><p><strong>带 conflict 标记的 PR 集群</strong> — 目前 8 条 PR 被标注 <code>conflict</code>，其中包含 P0/P1 级别的关键修复（见&quot;待处理积压&quot;部分），维护者需重点关注以避免功能延迟落地。</p>
</li>
</ul>
<hr>
<h2>Bug 与稳定性</h2>
<p>按严重程度排列：</p>
<table>
<thead>
<tr>
<th>严重程度</th>
<th>Issue/PR</th>
<th>描述</th>
<th>修复状态</th>
</tr>
</thead>
<tbody><tr>
<td><strong>高（P0）</strong></td>
<td>[PR #5271]</td>
<td>后台任务陈旧保存可能覆盖 <code>/new</code> 后的新会话数据，属数据竞争问题</td>
<td>PR 已开放，带 <code>conflict</code> 标记，需解决冲突后合并 → <a href="https://github.com/HKUDS/nanobot/pull/5271">https://github.com/HKUDS/nanobot/pull/5271</a></td>
</tr>
<tr>
<td><strong>中（P1）</strong></td>
<td>[Issue #5444]</td>
<td>Docker 中 OpenAI OAuth 登录失败，<code>oauth-cli-kit</code> 默认目录不可写，抛出 <code>PermissionError</code></td>
<td>已有 PR #5445、#5446 双线修复，均待合并 → <a href="https://github.com/HKUDS/nanobot/issues/5444">https://github.com/HKUDS/nanobot/issues/5444</a></td>
</tr>
<tr>
<td>中（P1）</td>
<td>[PR #5403]</td>
<td>tiktoken 估算 token 数比 API 实际值低 30-50%，导致上下文超限时内存整合不触发</td>
<td>PR 待合并，带 <code>conflict</code> 标记 → <a href="https://github.com/HKUDS/nanobot/pull/5403">https://github.com/HKUDS/nanobot/pull/5403</a></td>
</tr>
<tr>
<td>中</td>
<td>[Issue #5441]</td>
<td>Dream 恢复的工具错误导致内存游标永久阻塞，后续 Dream 运行重复处理同一历史批次</td>
<td>已有 PR #5442 修复，待合并 → <a href="https://github.com/HKUDS/nanobot/issues/5441">https://github.com/HKUDS/nanobot/issues/5441</a></td>
</tr>
<tr>
<td>低（P2）</td>
<td>[PR #5431]</td>
<td>后台任务失败异常未记录日志，难以排查问题</td>
<td>PR 待合并 → <a href="https://github.com/HKUDS/nanobot/pull/5431">https://github.com/HKUDS/nanobot/pull/5431</a></td>
</tr>
</tbody></table>
<hr>
<h2>功能请求与路线图信号</h2>
<ul>
<li><p><strong>付费安全扫描 MCP 集成（Issue #5447）</strong> — 用户提出将 nanobot 与 Solana x402 微支付安全扫描服务集成，作为付费 MCP 服务对外提供。这反映了社区对自主 Agent 变现与安全能力的交叉需求，可能引导项目在 MCP 生态和支付原语上的探索。→ <a href="https://github.com/HKUDS/nanobot/issues/5447">https://github.com/HKUDS/nanobot/issues/5447</a></p>
</li>
<li><p><strong>支持仅手动调用的技能（PR #5405）</strong> — 为技能增加 <code>disable-model-invocation: true</code> frontmatter，使部署/发布等副作用技能仅限用户显式触发。该 PR 已在开放队列中，符合 Agent 安全性的社区共识方向。→ <a href="https://github.com/HKUDS/nanobot/pull/5405">https://github.com/HKUDS/nanobot/pull/5405</a></p>
</li>
<li><p><strong>WebUI 后续追问建议（PR #5408）</strong> — 在 WebUI 回合结束后生成简短会话级联建议，对齐 DeerFlow 交互模式。→ <a href="https://github.com/HKUDS/nanobot/pull/5408">https://github.com/HKUDS/nanobot/pull/5408</a></p>
</li>
<li><p><strong>Turn 级可观测性与安全恢复（PR #5420）</strong> — 将每次用户回合投射为独立答案面，保留推理/工具/文件编辑轨迹，并在中断时显示恢复入口。→ <a href="https://github.com/HKUDS/nanobot/pull/5420">https://github.com/HKUDS/nanobot/pull/5420</a></p>
</li>
<li><p><strong>nano_timer 核心工具（PR #4853）</strong> — 新增强大但零依赖的计时器工具，自动处理时区/DST，已开放 1 月余，带 <code>p1</code> 与 <code>conflict</code> 标记，建议维护者优先处理。→ <a href="https://github.com/HKUDS/nanobot/pull/4853">https://github.com/HKUDS/nanobot/pull/4853</a></p>
</li>
</ul>
<hr>
<h2>用户反馈摘要</h2>
<ul>
<li><p><strong>Docker 部署是 OAuth 痛点的重灾区（Issue #5444）</strong>：用户 <code>Bennett-Yang</code> 在 Docker 环境执行 OAuth 登录时遭遇权限错误，说明容器内非 root 用户运行场景的凭证目录管理仍不完善。两个独立贡献者（<code>Shizoqua</code>、<code>dangzitou</code>）同时提交修复，反映该问题在社区中具有较高影响面。</p>
</li>
<li><p><strong>Dream 的重复编辑困扰用户（Issue #5441）</strong>：用户 <code>flobo3</code> 描述了 Dream 因单个可恢复工具错误（如 <code>edit_file</code> 旧文本不匹配）被整体判定失败，导致&quot;成功的编辑反而被重复执行&quot;的逆直觉行为。用户对&quot;结果正确但流程被误判&quot;的反馈说明了 Agent 任务完成判定不能过于刚性。</p>
</li>
<li><p><strong>自然语言&quot;永远跟进&quot;导致的持续目标失控（PR #5257）</strong>：用户指出携带循环节奏（如&quot;每天跟进我&quot;）的请求因缺少终止条件被记录为永久持续目标，内部资源可能被无限占用。这体现了 Agent 长期目标语义边界的设计缺口。</p>
</li>
</ul>
<hr>
<h2>待处理积压</h2>
<p>以下为长期未合并/未响应的重要 PR 与 Issue，按优先级提醒维护者：</p>
<ul>
<li><p><strong>[PR #5271] [P0, conflict]</strong> fix(session): prevent stale background task saves from overwriting session data — 8 月 6 日创建，已开放 2 周，属数据安全/一致性问题，务必尽快解决冲突完成合并。→ <a href="https://github.com/HKUDS/nanobot/pull/5271">https://github.com/HKUDS/nanobot/pull/5271</a></p>
</li>
<li><p><strong>[PR #4853] [P1, conflict]</strong> feat(tools): add nano_timer core tool — 7 月 8 日创建，开放超 6 周，功能本身已完整却迟迟未落地，需维护者评估冲突原因。→ <a href="https://github.com/HKUDS/nanobot/pull/4853">https://github.com/HKUDS/nanobot/pull/4853</a></p>
</li>
<li><p><strong>[PR #5403] [P1, conflict]</strong> fix(memory): use API-reported prompt tokens to trigger consolidation — 修复 token 估算严重偏低导致上下文整合永不触发的问题，建议优先合并。→ <a href="https://github.com/HKUDS/nanobot/pull/5403">https://github.com/HKUDS/nanobot/pull/5403</a></p>
</li>
<li><p><strong>[PR #5379] [P2, conflict]</strong> fix(memory): preserve full consolidation input — 将压缩截断改为无损分块，涉及数据完整性，且与 #5403 同属记忆子系统的关键修复。→ <a href="https://github.com/HKUDS/nanobot/pull/5379">https://github.com/HKUDS/nanobot/pull/5379</a></p>
</li>
<li><p><strong>[PR #5405] [P2, conflict]</strong> feat(skills): support manual-only invocation — 安全相关功能，长时间未合并可能降低社区对技能系统安全性的信心。→ <a href="https://github.com/HKUDS/nanobot/pull/5405">https://github.com/HKUDS/nanobot/pull/5405</a></p>
</li>
<li><p><strong>[PR #5257] [P2]</strong> fix(agent): bound sustained-goal continuation when the turn goes idle — 开放 2 周余，解决长期目标无限续期的资源问题，建议尽快安排 review。→ <a href="https://github.com/HKUDS/nanobot/pull/5257">https://github.com/HKUDS/nanobot/pull/5257</a></p>
</li>
</ul>
<hr>
<blockquote>
<p><strong>健康度总结</strong>：项目社区参与度高，Issue 响应迅速（OAuth 问题数小时内即有修复 PR），TUI/WebUI 稳定性持续改善。需关注 P0 PR #5271 的合并进度以及 8 条 PR 的冲突积压，控制技术债累积速度。</p>
</blockquote>
</details>

<details>
<summary><strong>Zeroclaw</strong> — <a href="https://github.com/zeroclaw-labs/zeroclaw">zeroclaw-labs/zeroclaw</a></summary>

<h1>Zeroclaw 项目动态日报 — 2026-08-20</h1>
<h2>1. 今日速览</h2>
<p>过去 24 小时项目活跃度极高：26 条 Issue 更新、50 条 PR 更新，其中 43 个 PR 待合并、7 个已合并/关闭，无新版本发布。当前主线集中在安全加固（渠道发件人授权、Shell 子进程隔离、工具 allowlist 强制）与稳定性修复（ACP 会话持久化、配置初始化损坏、工具结果截断）两大方向，多个高优先级 P1 修复已有对应 PR 进入待合并队列。架构层面，4 个 RFC 正在维护者评审中，讨论集中在核心精简与权限契约定义。合并积压明显（43 个待合并 PR），建议维护者优先处理带 <code>needs-maintainer-review</code> / <code>do-not-merge</code> 标记的关键路径变更。</p>
<h2>2. 版本发布</h2>
<p>今日无新版本发布。</p>
<h2>3. 项目进展</h2>
<p>今日 7 个 PR 已合并/关闭（列表未披露具体 PR），1 个 Issue 关闭：</p>
<ul>
<li><strong>[Task] Correct Reliable fallback telemetry attribution and stale notices (#9470，已关闭)</strong> — 修正了 Reliable 回退遥测归属错误和用户可见回退通知不准确的问题，由 vrurg 提交，关联 PR #9424 与 #9447 的评审反馈。链接：<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9470">https://github.com/zeroclaw-labs/zeroclaw/issues/9470</a></li>
</ul>
<p>项目整体推进情况：虽然无版本发布，但 43 个待合并 PR 中体现了显著的前进势头——渠道授权安全修复（#9428）、Shell 子进程逃逸修复（#9827）、Anthropic OAuth 支持（#9420）、插件类型化配置验证（#9126）等大型变更均处于待合并状态。这些 PR 若合并将同时推进安全性、渠道兼容性、可发布性三条线。</p>
<h2>4. 社区热点</h2>
<p>今日讨论最活跃的 Issue：</p>
<ul>
<li><strong>RFC: Prefer a lighter ZeroClaw core through external integrations (#6165)</strong> — 17 条评论。4 月底创建，讨论持续至今，社区对核心膨胀问题关注度高，主张将长尾集成外置。诉求：降低默认核心的配置、安全与兼容性负担。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/6165">https://github.com/zeroclaw-labs/zeroclaw/issues/6165</a></li>
<li><strong>[Tracker]: Maintainer decision queue for RFCs and design issues (#8692)</strong> — 13 条评论。维护者决策队列，收集需要 maintainer 或 code-owner 关注的 RFC、设计问题、发布策略问题。反映出社区对决策透明度和响应速度的期待。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8692">https://github.com/zeroclaw-labs/zeroclaw/issues/8692</a></li>
<li><strong>RFC: Define the SOP capability permission contract (#9598)</strong> — 8 条评论。SOP 能力权限契约定义，目标 v0.9.0，区分临时 owner/risk-profile 执行路径与完整共享权限系统。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9598">https://github.com/zeroclaw-labs/zeroclaw/issues/9598</a></li>
<li><strong>refactor(gateway): centralize webhook channel message dispatch (#8586)</strong> — 7 条评论。网关层统一 webhook 到渠道的消息分发，当前 7 个讨论集中在复用消息生命周期的边界划分。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8586">https://github.com/zeroclaw-labs/zeroclaw/issues/8586</a></li>
</ul>
<p>PR 侧评论数未披露，但 <code>size:XL</code> 与 <code>do-not-merge</code> 标记的大规模 PR（#9420、#9428、#9378、#9419）预计为社区讨论焦点。</p>
<h2>5. Bug 与稳定性</h2>
<p>按严重程度排列：</p>
<p><strong>S1 - 工作流阻塞</strong></p>
<ul>
<li><strong>failed ACP turns disappear after switching sessions (#9333)</strong> — ACP 轮次在 provider 错误后切换会话再返回，整个失败的轮次从实录中消失。已有对应修复 PR #9378（persist failed and cancelled turn transcripts，size:XL，需作者行动）。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9333">https://github.com/zeroclaw-labs/zeroclaw/issues/9333</a></li>
<li><strong>Windows desktop installer fails with missing TaskDialogIndirect (#9290)</strong> — Windows 桌面版安装后无法启动，缺少 TaskDialogIndirect 入口点。同为新提交的支持请求 #10111 确认此问题，暂无修复 PR。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9290">https://github.com/zeroclaw-labs/zeroclaw/issues/9290</a></li>
<li><strong>bug(ci): MSRV system dependency installation can consume job timeout (#10042)</strong> — MSRV 构建任务可能将完整 20 分钟超时消耗在系统依赖安装阶段，导致 Cargo 检查从未启动。已有修复 PR #10122（pinned release-tool installer，待验证）。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10042">https://github.com/zeroclaw-labs/zeroclaw/issues/10042</a></li>
</ul>
<p><strong>S2 - 降级行为</strong></p>
<ul>
<li><strong>headless SOP step turns never persisted (#9929)</strong> — headless SOP 步骤轮次分配了会话路径但未写入会话存储。状态：blocked、accepted，无修复 PR。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9929">https://github.com/zeroclaw-labs/zeroclaw/issues/9929</a></li>
<li><strong><code>config init</code> writes template sections that fail the strict loader (#9436)</strong> — 新生成的配置天生损坏，<code>config migrate</code> 退出码 1。状态：in-progress，影响 v0.8.3 及 master。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9436">https://github.com/zeroclaw-labs/zeroclaw/issues/9436</a></li>
<li><strong>工具结果截断三连（#10114 / #10115 / #10116）</strong> — ① <code>max_tool_result_chars</code> 固定 50,000 与模型上下文无关；② 截断在模型上下文之外不可见；③ 截断采用中间挖空方式（保留头 2/3 + 尾 1/3），建议改为溢出到文件句柄，类似 <code>web_fetch</code>。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10114">https://github.com/zeroclaw-labs/zeroclaw/issues/10114</a> / <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10115">https://github.com/zeroclaw-labs/zeroclaw/issues/10115</a> / <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10116">https://github.com/zeroclaw-labs/zeroclaw/issues/10116</a></li>
<li><strong>Exact proxy selectors reject supported transcription services (#10106)</strong> — 精确匹配的代理选择器拒绝了 <code>transcription.*</code> 服务键。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10106">https://github.com/zeroclaw-labs/zeroclaw/issues/10106</a></li>
<li><strong>ZeroCode ignores paste while an agent turn is running (#10089)</strong> — 代理轮次运行期间终端粘贴被忽略，协作场景受阻。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10089">https://github.com/zeroclaw-labs/zeroclaw/issues/10089</a></li>
<li><strong>install.sh selects generic Linux binary on Android/Termux (#7911)</strong> — 预编译二进制与本地编译均错误选用未知的 linux aarch64 版本。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/7911">https://github.com/zeroclaw-labs/zeroclaw/issues/7911</a></li>
</ul>
<p><strong>已有修复 PR 的 Bug 速查：</strong></p>
<table>
<thead>
<tr>
<th>Bug</th>
<th>Issue</th>
<th>Fix PR</th>
<th>状态</th>
</tr>
</thead>
<tbody><tr>
<td>ACP 失败轮次丢失</td>
<td>#9333</td>
<td>#9378</td>
<td>需作者行动</td>
</tr>
<tr>
<td>Bluesky/Reddit 未校验发件人</td>
<td>#9428 内嵌</td>
<td>#9428</td>
<td>需作者行动</td>
</tr>
<tr>
<td>LINE 群组消息未授权</td>
<td>#9427</td>
<td>#9427</td>
<td>依赖 #9428</td>
</tr>
<tr>
<td>Shell 子进程逃逸隔离</td>
<td>#9827 内嵌</td>
<td>#9827</td>
<td>需作者行动</td>
</tr>
<tr>
<td>工具 allowlist 未强制执行</td>
<td>#9433 内嵌</td>
<td>#9433</td>
<td>需作者行动</td>
</tr>
<tr>
<td>Reliable 遥测归属错误</td>
<td>#9470</td>
<td>#9424/#9447 已合入，本 Issue 已关闭</td>
<td>✅</td>
</tr>
</tbody></table>
<h2>6. 功能请求与路线图信号</h2>
<p><strong>维护者评审中的 RFC（可能进入 v0.9.0）：</strong></p>
<ul>
<li><strong>RFC: Prefer a lighter ZeroClaw core through external integrations (#6165)</strong> — 将长尾集成从核心移除，改为外部集成。风险高，讨论时间长（17 条评论），方向获社区认可但落地路径待定。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/6165">https://github.com/zeroclaw-labs/zeroclaw/issues/6165</a></li>
<li><strong>RFC: Define the SOP capability permission contract (#9598)</strong> — SOP 权限契约目标 v0.9.0，Rev 3 已分离出临时执行路径与完整共享权限路径。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9598">https://github.com/zeroclaw-labs/zeroclaw/issues/9598</a></li>
<li><strong>RFC: Goal mode v2 (#9702)</strong> — 持久化续跑 + 可信 Web 控制面，v1 限制为 Matrix 命令 + 重启暂停，v2 需要安全浏览器控制界面。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9702">https://github.com/zeroclaw-labs/zeroclaw/issues/9702</a></li>
<li><strong>RFC: Calibrate PR risk and security approval requirements (#9990)</strong> — 校准 PR 风险评估标准，基于 #9530 的先例扩展。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9990">https://github.com/zeroclaw-labs/zeroclaw/issues/9990</a></li>
</ul>
<p><strong>已接受 / in-progress 功能方向：</strong></p>
<ul>
<li><strong>[Feature]: Isolate interactive Blacksmith debugging from attesting CI (#10041，已接受)</strong> — 增加非见证的 Blacksmith 调试通道，不允许交互式 SSH 进入合并/发布/制品路径。风险高，影响 CI 架构。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10041">https://github.com/zeroclaw-labs/zeroclaw/issues/10041</a></li>
<li><strong>[Tracker]: crates.io publishing, packaging, and cargo-install follow-ups (#9381，已接受)</strong> — crates.io 发布跟进，首个待办为 Windows 仓库 symlink 问题。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9381">https://github.com/zeroclaw-labs/zeroclaw/issues/9381</a></li>
<li><strong>[Task]: Make provider-call accounting lifecycle-complete (#10143，in-progress)</strong> — 完善 provider 调用记账，每个物理 provider 叶子精确一次、按物理启动顺序。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10143">https://github.com/zeroclaw-labs/zeroclaw/issues/10143</a></li>
</ul>
<p><strong>版本路线图信号：</strong> v0.8.5 稳定线（#9459）至 8 月 30 日，Intake 已于 8 月 4 日冻结，周切版持续发布可用成果。SOP 权限契约、Goal mode v2 目标版本指向 v0.9.0。按当前节奏，上述 RFC 的决策可能在未来 2-4 周内落定。</p>
<h2>7. 用户反馈摘要</h2>
<ul>
<li><strong>Android/Termux 安装困扰（#7911）</strong> — 用户尝试在 Termux 安装，预编译二进制和本地编译都拉取到错误的 linux aarch64 通用二进制。反馈被标注 <code>help wanted</code>，且今日有配套文档 PR #10160 澄清 Android 二进制可能缺席的情况。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/7911">https://github.com/zeroclaw-labs/zeroclaw/issues/7911</a></li>
<li><strong>Windows 桌面端启动失败（#9290 与 #10111 双反馈）</strong> — 两个独立用户报告同一问题：安装后 <code>zeroclaw-desktop.exe</code> 报 <code>TaskDialogIndirect</code> 入口点找不到。安装包为 v0.8.3 官方 release，说明发布流程缺少 Windows 原生运行验证。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9290">https://github.com/zeroclaw-labs/zeroclaw/issues/9290</a> | <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10111">https://github.com/zeroclaw-labs/zeroclaw/issues/10111</a></li>
<li><strong>Fresh config 即损坏（#9436）</strong> — 用户反馈 <code>config init</code> 生成的模板配置无法通过严格加载器，新用户首次配置即遇挫。Issue 确认在 master 上仍可复现。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9436">https://github.com/zeroclaw-labs/zeroclaw/issues/9436</a></li>
<li><strong>ZeroCode 粘贴体验（#10089）</strong> — 代理轮次进行中无法使用终端括号粘贴，协作输入被吞。反馈明确描述&quot;Chat composer 空闲时粘贴正常、轮次开始后失效&quot;。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10089">https://github.com/zeroclaw-labs/zeroclaw/issues/10089</a></li>
</ul>
<h2>8. 待处理积压</h2>
<p><strong>长期未决、需维护者关注的重要 Issue：</strong></p>
<ul>
<li><strong>RFC: Prefer a lighter ZeroClaw core through external integrations (#6165)</strong> — 4 月 27 日创建，已活跃近 4 个月，17 条评论，标记 <code>needs-maintainer-review</code> + <code>risk:high</code>。长期未获维护者正式回应。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/6165">https://github.com/zeroclaw-labs/zeroclaw/issues/6165</a></li>
<li><strong>[Tracker]: Maintainer decision queue (#8692)</strong> — 7 月 4 日创建，13 条评论，持续累积待决策项。该 tracker 的存在本身说明决策积压问题。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8692">https://github.com/zeroclaw-labs/zeroclaw/issues/8692</a></li>
</ul>
<p><strong>长期未合并的 PR（需关注或关闭决策）：</strong></p>
<ul>
<li><strong>refactor(observability)!: retire dormant DORA telemetry (#9451)</strong> — 7 月 27 日创建，<code>do-not-merge</code> + <code>needs-maintainer-review</code>，break change 需维护者拍板。<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9451">https://github.com/zeroclaw-labs/zeroclaw/pull/9451</a></li>
<li><strong>fix(anthropic): support stored OAuth profiles (#9420)</strong> — 7 月 26 日创建，<code>do-not-merge</code> + <code>needs-maintainer-review</code>，size:XL 跨 22 个组件。<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9420">https://github.com/zeroclaw-labs/zeroclaw/pull/9420</a></li>
<li><strong>fix(providers): rotate live credentials after rate limits (#9419)</strong> — 7 月 26 日创建，<code>do-not-merge</code> + <code>needs-maintainer-review</code>，涉及可靠 provider 凭据轮换。<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9419">https://github.com/zeroclaw-labs/zeroclaw/pull/9419</a></li>
<li><strong>feat(plugins): validate typed instance config (#9126)</strong> — 7 月 18 日创建，size:XL，跨 14 个组件，无 <code>needs-maintainer-review</code> 但已积压一个月以上。<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9126">https://github.com/zeroclaw-labs/zeroclaw/pull/9126</a></li>
</ul>
<p><strong>今日新增、已标记为 blocked 的 Issue：</strong></p>
<ul>
<li><strong>headless SOP step turns never persisted (#9929)</strong> — <code>status:blocked</code> + <code>status:accepted</code>，P1 风险高但被阻塞，需维护者解除阻塞条件。<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9929">https://github.com/zeroclaw-labs/zeroclaw/issues/9929</a></li>
</ul>
</details>

<details>
<summary><strong>PicoClaw</strong> — <a href="https://github.com/sipeed/picoclaw">sipeed/picoclaw</a></summary>

<h1>PicoClaw 项目动态日报 2026-08-20</h1>
<p>统计区间：2026-08-19 ~ 2026-08-20</p>
<h2>今日速览</h2>
<ul>
<li>过去 24 小时无新版本发布；Issue 侧仅收尾 1 条存量 bug（#1305），无新开/活跃 issue。</li>
<li>PR 侧共有 5 条更新：2 条关闭、3 条待合并（其中 2 条已被标记为 stale），整体以存量审查和收尾为主。</li>
<li>社区讨论热度集中在 #1305（4 条评论），该 issue 最终关闭，说明维护者正在清理旧问题。</li>
<li>Telegram 相关改动是本轮重点：#3341 快速关闭、#3315 仍待合并，平台交互体验与适配性持续被关注。</li>
<li>总体活跃度中等偏低，新功能输入有限，但存在一个待合并的配置正确性修复（#3329）值得继续推进。</li>
</ul>
<h2>项目进展</h2>
<h3>已关闭/合并 PR（2 条）</h3>
<ul>
<li><p><a href="https://github.com/sipeed/picoclaw/pull/3341">PR #3341 feat(telegram): add interactive command UX and formatted ephemeral fallback</a><br>该 PR 在 8/19 创建并同日关闭。核心改进包括：降低 <code>/memory</code> 等命令的子命令语法认知负担、精简 <code>/help</code> 每行输出、在结构化内容不可用时提供格式化的临时回退。如已合并，Telegram 机器人的命令体验将获得直接提升。</p>
</li>
<li><p><a href="https://github.com/sipeed/picoclaw/pull/3200">PR #3200 feat(models): add configurable default fallback chain</a><br>该 PR 为 Web UI 增加了默认模型回退链配置能力，支持用户设置默认模型、添加回退模型、排序并保存整条链路。但本次被标记为 stale 后关闭，功能可能未合入主线，其需求信号（模型容错与降级）仍值得保留至路线图。</p>
</li>
</ul>
<h3>待合并 PR（3 条）</h3>
<ul>
<li><p><a href="https://github.com/sipeed/picoclaw/pull/3329">PR #3329 fix(line): warn on inert webhook_host / webhook_port</a><br>修复 LINE 渠道中 <code>webhook_host</code> / <code>webhook_port</code> 配置项虽然存在但从未被读取的问题，改为向用户发出警告而非静默播种默认值。这是针对配置陷阱的实际修复，等待维护者 review。</p>
</li>
<li><p><a href="https://github.com/sipeed/picoclaw/pull/3316">PR #3316 fix: routed-agent context management</a><br>修复路由 agent 在特定 Discord 频道中不记忆历史、不触发自动压缩等问题，涉及历史、摘要、压缩与 seahorse bootstrap。当前已 stale。</p>
</li>
<li><p><a href="https://github.com/sipeed/picoclaw/pull/3315">PR #3315 Support topics in private bot chats</a><br>修复 Telegram 私聊 bot 中 <code>Chat.IsForum</code> 判断不适用的问题，补全对 private chat topic 消息的支持。当前已 stale。</p>
</li>
</ul>
<p>整体而言，项目处于小步推进状态：Telegram 命令交互优化这一轮有实质进展，而模型回退链和 agent 上下文管理两个较重要功能则暂时受阻。</p>
<h2>社区热点</h2>
<ul>
<li><p><a href="https://github.com/sipeed/picoclaw/issues/1305">Issue #1305 [BUG] new banner print to STDOUT, break completion flow</a><br>该 issue 是过去 24 小时内评论数最高的条目（4 条讨论），现已被关闭。用户指出新版 banner 打印到 STDOUT，导致 <code>picoclaw completion zsh &gt; _picoclaw</code> 生成的补全脚本混入非补全内容。背后诉求非常明确：CLI 工具必须保持 STDOUT 纯净，以便脚本化重定向、管道和命令替换场景安全使用；诊断/欢迎信息应输出到 STDERR。</p>
</li>
<li><p><a href="https://github.com/sipeed/picoclaw/pull/3341">PR #3341</a> 当天创建当天关闭，说明 Telegram 交互体验改动有较快推进，但 PR 评论区未记录具体互动数据。</p>
</li>
</ul>
<h2>Bug 与稳定性</h2>
<h3>已关闭 Bug</h3>
<ul>
<li><a href="https://github.com/sipeed/picoclaw/issues/1305">Issue #1305</a>（严重程度：中）<br>影响 shell completion 生成流程，用户执行 <code>picoclaw completion zsh &gt; _picoclaw</code> 后文件开头出现 banner，导致补全脚本不可用。该问题由 PR #1008 引入的新 banner 导致，属于版本升级后出现的 stdout 污染回归。Issue 已关闭，但今日数据中未看到关联 fix PR。</li>
</ul>
<h3>待处理稳定性隐患</h3>
<ul>
<li><a href="https://github.com/sipeed/picoclaw/pull/3329">PR #3329</a>（严重程度：低-中）<br>LINE 渠道的 <code>webhook_host</code> / <code>webhook_port</code> 配置项声明了、设了默认值、绑定了环境变量，但实际没有任何代码读取。这会使用户误以为配置已生效。该 PR 将其改为显式警告，属于配置正确性修复，建议优先合入。</li>
</ul>
<h2>功能请求与路线图信号</h2>
<ul>
<li>今日无新建功能请求类 Issue。</li>
<li>从 PR 看，Telegram 平台完善是明确方向：<ul>
<li><a href="https://github.com/sipeed/picoclaw/pull/3341">PR #3341</a>：交互式命令 UX，降低权限指令的认知负担。</li>
<li><a href="https://github.com/sipeed/picoclaw/pull/3315">PR #3315</a>：Telegram 私聊 bot 的 topic 支持，补齐 forum topic 之外的消息场景。</li>
</ul>
</li>
<li><a href="https://github.com/sipeed/picoclaw/pull/3200">PR #3200</a> 提出的默认模型回退链虽未合入，但反映了用户对模型可用性和降级容错的需求，很可能在后续版本中以其他形式回归。</li>
<li><a href="https://github.com/sipeed/picoclaw/pull/3316">PR #3316</a> 若被推进，将改善路由 agent 的会话记忆、自动压缩和上下文连续性，是 agent 体验稳定性的关键能力。</li>
</ul>
<h2>用户反馈摘要</h2>
<ul>
<li><a href="https://github.com/sipeed/picoclaw/issues/1305">Issue #1305</a> 反馈了一个典型 CLI 使用场景：用户需要自动生成 zsh 补全文件，但新 banner 输出到 STDOUT 破坏了结果。用户明确关联到引入该问题的 PR #1008，并给出了可复现步骤，说明其具备清晰的 bug 定位能力。</li>
<li>该反馈揭示的深层问题是：项目在引入视觉 banner 时未遵循 CLI 输出通道约定（诊断信息应走 STDERR），导致升级后出现回归。这类问题容易影响脚本化使用者，建议维护者建立明确的 stdout/stderr 使用规范，并增加对 <code>completion</code> 等命令的输出回归测试。</li>
<li>评论正文未在本数据中展示，因此无法提炼更多用户的满意度或额外痛点。</li>
</ul>
<h2>待处理积压</h2>
<ul>
<li><p><a href="https://github.com/sipeed/picoclaw/pull/3316">PR #3316</a>（stale）<br>8/03 创建，已长期无实质推进。涉及 routed-agent 上下文管理，是整个 agent 记忆与自动压缩链路的关键修复，建议维护者尽快给出明确处理意见。</p>
</li>
<li><p><a href="https://github.com/sipeed/picoclaw/pull/3315">PR #3315</a>（stale）<br>8/03 创建，Telegram 私聊 topics 支持。与刚合并的 #3341 在 Telegram 体验上互补，建议纳入下一步迭代。</p>
</li>
<li><p><a href="https://github.com/sipeed/picoclaw/pull/3329">PR #3329</a>（open）<br>8/11 创建，尚未合并。该 PR 修复配置项静默失效问题，属于低风险、高收益的稳定性改进。</p>
</li>
<li><p>另外，Issue #1305 于 2026-03-10 创建，到 2026-08-19 才关闭，耗时约 5 个月，暴露了 issue 积压处理周期较长的问题。虽然最终已收尾，但值得维护者反思旧 issue 的清理节奏。</p>
</li>
</ul>
</details>

<details>
<summary><strong>NanoClaw</strong> — <a href="https://github.com/qwibitai/nanoclaw">qwibitai/nanoclaw</a></summary>

<h1>NanoClaw 项目动态日报（2026-08-20）</h1>
<h2>今日速览</h2>
<p>过去 24 小时项目保持高活跃度：33 条 PR 更新，23 条合并/关闭，新增 3 个 issue，无新版本发布。核心维护者集中在 Slack 体验拆分（<code>--slack-agents</code>）、Slack/provisioning 可靠性修复以及 Telegram 群组连接器上；社区侧则集中报告 Node 26 兼容性和 headless 安装问题。整体看，项目正处于渠道扩展与安装/配置健壮性并行的阶段，但新 issue 均指向 setup 与 Dial 状态上报，是当前明显的薄弱点。</p>
<h2>项目进展</h2>
<h3>已合并/关闭的重要 PR</h3>
<ul>
<li><p><strong>Slack agents 功能正式拆分</strong><br><a href="https://github.com/nanocoai/nanoclaw/pull/3357">#3357 [CLOSED] setup: --slack-agents installs the whole Slack agents feature</a> 与 <a href="https://github.com/nanocoai/nanoclaw/pull/3358">#3358 [CLOSED] slack: split the payload — base adapter in /add-slack, agents feature in /slack-agent-flow</a> 合并后，默认 Slack 安装变为「基础体验」（单 bot、DM/频道聊天），完整 agents 功能通过 <code>--slack-agents</code> 按需安装。这是一个有意的产品边界调整，让主流程更轻量。</p>
</li>
<li><p><strong>Slack 与 provisioning 可靠性批量修复</strong><br>多个 core-team PR 在同一天关闭，集中修整 Slack 安装和审批链路：  </p>
<ul>
<li><a href="https://github.com/nanocoai/nanoclaw/pull/3340">#3340 fix(approvals): record the delivering instance on pending_approvals</a>  </li>
<li><a href="https://github.com/nanocoai/nanoclaw/pull/3341">#3341 fix(provisioning): derive the Slack service from the credential&#39;s issuer</a>  </li>
<li><a href="https://github.com/nanocoai/nanoclaw/pull/3342">#3342 feat(slack): decline owner-absent channel invites instead of carding them</a>  </li>
<li><a href="https://github.com/nanocoai/nanoclaw/pull/3345">#3345 feat(setup): forward optional client metadata on Slack service requests</a>  </li>
<li><a href="https://github.com/nanocoai/nanoclaw/pull/3344">#3344 feat(provisioning): optional request-origin metadata on app creation</a>  </li>
<li><a href="https://github.com/nanocoai/nanoclaw/pull/3339">#3339 fix(setup): fail closed when a stored sign-in cannot be verified</a></li>
</ul>
<p>这些改动提升了 Slack 安装的身份配对正确性、凭证失败处理的安全性，以及审批记录的可追溯性。</p>
</li>
<li><p><strong>Telegram 群组连接器</strong><br><a href="https://github.com/nanocoai/nanoclaw/pull/3351">#3351 [CLOSED] feat(telegram): add approved group connection picker</a> 为 Telegram 增加 <code>/connect_group</code> 管理命令，接入原生群组选择器，并复用现有 unknown-channel 审批链路。</p>
</li>
<li><p><strong>容器输出 token 上限调整</strong><br><a href="https://github.com/nanocoai/nanoclaw/pull/3025">#3025 [CLOSED] fix(container): raise the agent SDK&#39;s 32000 output-token cap</a> 关闭，容器内 agent SDK 的输出 token 限制得到放宽。</p>
</li>
</ul>
<p>综合来看，今天项目在 Slack 渠道架构上做了一次明显的功能收敛，同时修正了多条 Slack/provisioning 路径上的安全与配置正确性问题，整体工程稳定性有实质提升。</p>
<h2>社区热点</h2>
<p>今日 3 个新 issue 均来自同一提交者 <code>glifocat</code>，形成关于「新机安装体验」的明确反馈集群：</p>
<ul>
<li><a href="https://github.com/nanocoai/nanoclaw/issues/3359">#3359 Node 26 passes check_node but better-sqlite3 11.10.0 cannot build against it</a> — 使用 Homebrew Node 26.7.0 的全新 macOS arm64 机器在引导阶段即失败。</li>
<li><a href="https://github.com/nanocoai/nanoclaw/issues/3354">#3354 Setup leaves 0-byte channel files on a failed git-show copy, and an onecli check runs before its own PATH fix</a> — headless/非登录 SSH 场景下安装流程出现残留文件与检查顺序问题。</li>
<li><a href="https://github.com/nanocoai/nanoclaw/issues/3353">#3353 Dial: outbound SMS rejected by the carrier after send is still recorded as delivered</a> — Dial 短信送达状态误报，影响重试与用户通知。</li>
</ul>
<p>这些 issue 当前评论数为 0，但分别关联着 <a href="https://github.com/nanocoai/nanoclaw/pull/3360">#3360</a>、<a href="https://github.com/nanocoai/nanoclaw/pull/3249">#3249</a> 和 <a href="https://github.com/nanocoai/nanoclaw/pull/3041">#3041</a>/<a href="https://github.com/nanocoai/nanoclaw/pull/3050">#3050</a>，表明维护者已经或正在响应。PR 侧，core-team 的 Slack 系列（#3357、#3358、#3340–#3345）占据主导，反映当前维护重点在 Slack 渠道架构与 provisioning 正确性。</p>
<h2>Bug 与稳定性</h2>
<p>按严重程度排列：</p>
<ul>
<li><p><strong>严重：Node 26 下 better-sqlite3 构建失败，阻塞全新安装</strong><br><a href="https://github.com/nanocoai/nanoclaw/issues/3359">#3359</a>。<code>check_node</code> 只有下限检查，导致 Node 26.7.0 通过检查后，better-sqlite3 11.10.0 编译失败并中止引导。<br><strong>已有修复 PR</strong>：<a href="https://github.com/nanocoai/nanoclaw/pull/3360">#3360</a> 将 better-sqlite3 升级至 13.0.3，并将 Node 最低要求提升到 22；相关 PR <a href="https://github.com/nanocoai/nanoclaw/pull/3249">#3249</a> 处理已存在的超范围 Node。</p>
</li>
<li><p><strong>中等：headless/非登录安装残留 0 字节文件，且 onecli 检查过早执行</strong><br><a href="https://github.com/nanocoai/nanoclaw/issues/3354">#3354</a>。<code>git show</code> 复制失败后留下空 channel 文件，onecli 检查又运行在自己的 PATH 修复之前。目前未见直接 fix PR。</p>
</li>
<li><p><strong>中等：Dial 短信被运营商拒绝后仍标记 delivered</strong><br><a href="https://github.com/nanocoai/nanoclaw/issues/3353">#3353</a>。发送后无法重新评估状态，重试预算不被消耗，agent/owner 均不会收到通知。目前无直接修复 PR，需结合 Dial 适配器状态机处理。</p>
</li>
</ul>
<h2>功能请求与路线图信号</h2>
<ul>
<li><p><strong>Node 运行时支持范围调整</strong><br><a href="https://github.com/nanocoai/nanoclaw/pull/3360">#3360</a> 与 <a href="https://github.com/nanocoai/nanoclaw/pull/3249">#3249</a> 指向下一版本将把 Node 最低版本从 20 提升到 22，并通过 better-sqlite3 13 兼容当前 Node 26。这是一个带破坏性变更的系统要求更新。</p>
</li>
<li><p><strong>Cursor/多 agent provider 生态扩展</strong><br><a href="https://github.com/nanocoai/nanoclaw/pull/3356">#3356 feat(providers): add Cursor Agent SDK payload</a>、<a href="https://github.com/nanocoai/nanoclaw/pull/3355">#3355 feat(setup): add /add-cursor agent provider skill</a> 和 <a href="https://github.com/nanocoai/nanoclaw/pull/3349">#3349 feat: add agent mailbox seam and registry</a> 均处于打开状态。三者组合显示项目正在向「多 agent provider + 统一 mailbox 注册」方向扩展。</p>
</li>
<li><p><strong>Dial 渠道正式接纳</strong><br><a href="https://github.com/nanocoai/nanoclaw/pull/3041">#3041 Dial channel adapter (SMS + AI voice)</a> 与 <a href="https://github.com/nanocoai/nanoclaw/pull/3050">#3050 Dial channel picker/wizard</a> 仍在待合并，但 <a href="https://github.com/nanocoai/nanoclaw/issues/3353">#3353</a> 已经暴露其送达状态机缺陷，预计正式合并前需要配套修复。</p>
</li>
<li><p><strong>Slack agents 默认关闭</strong><br>从 #3357/#3358 的合并看，完整 Slack agents 能力将作为 opt-in 功能，避免默认安装过重。这也是未来其他复杂渠道功能的参考模式。</p>
</li>
</ul>
<h2>用户反馈摘要</h2>
<p>今日 3 个 issue 均无评论，以下反馈来自 issue 正文，但仍准确反映真实用户环境：</p>
<ul>
<li><strong>用户希望开箱即用地跟随上游 Node 版本</strong>：macOS arm64 + Homebrew 默认 Node 26.7.0 是全新机器的常见配置，但安装会因 better-sqlite3 编译失败而中断。提交者认为 <code>check_node</code> 的检查范围应该与实际依赖构建能力一致。</li>
<li><strong>非交互式部署场景被忽略</strong>：#3354 来自干净的 headless SSH 安装，说明 setup 假设用户有交互式登录 shell，导致 PATH 修复和 onecli 检查的顺序错误，且失败后留下 0 字节文件。</li>
<li><strong>Dial 发送状态需要可追溯</strong>：提交者指出「运营商接受发送」和「运营商拒绝发送」是两个不同事实，NanoClaw 当前把前者当作最终结果，导致 agent 与 owner 对消息状态形成错误认知。</li>
</ul>
<h2>待处理积压</h2>
<ul>
<li><strong><a href="https://github.com/nanocoai/nanoclaw/pull/3149">#3149 fix(cli): add --rw flag to groups config add-mount</a></strong> — 创建于 7 月 29 日，已超过 3 周仍未合并，虽然是小改动，但今天仍有更新，说明尚未被放弃。需维护者确认是否进入下一版本。</li>
<li><strong><a href="https://github.com/nanocoai/nanoclaw/pull/3041">#3041 feat(channels): add Dial channel adapter</a> 与 <a href="https://github.com/nanocoai/nanoclaw/pull/3050">#3050 feat(setup): add Dial to the channel picker</a></strong> — 自 7 月 14 日打开，已逾 5 周。考虑到 #3353 报告了 Dial 的实际行为缺陷，需要尽快决定合并方向并补齐状态机问题。</li>
<li><strong><a href="https://github.com/nanocoai/nanoclaw/pull/3249">#3249 fix(setup): handle an existing Node outside the supported range</a></strong> — 打开于 8 月 14 日，与 #3359/#3360 的目标有重叠，建议与 #3360 协调后决定合并顺序或统一成一个修复方案。</li>
</ul>
</details>

<details>
<summary><strong>NullClaw</strong> — <a href="https://github.com/nullclaw/nullclaw">nullclaw/nullclaw</a></summary>

<h1>NullClaw 项目动态日报 - 2026-08-20</h1>
<h2>1. 今日速览</h2>
<p>过去 24 小时内，NullClaw 项目整体活跃度较低：无新 Issue 或新版本发布，仅有 1 个 PR 处于待合并状态。该 PR 针对 README 中星标历史图表失效的问题提出了修复方案，说明项目维护仍在持续跟进文档与展示层面的缺陷。总体来看，社区讨论与参与度较低，项目处于平稳维护阶段。</p>
<h2>2. 版本发布</h2>
<p>今日无新版本发布。</p>
<h2>3. 项目进展</h2>
<ul>
<li><strong><a href="https://github.com/nullclaw/nullclaw/pull/989">#989 [OPEN] fix: restore broken star history chart</a></strong><br>该 PR 旨在修复 README 中星标历史图表无法正常显示的问题。原图表依赖 GitHub stargazer API，但该接口存在访问限制，导致图表损坏。PR 将图表数据源切换为 <code>star-history.dera.page</code>，该服务无需 token 且相对稳定，可确保图表重新正确渲染。目前 PR 仍处于待合并状态，尚未合并。这一改动将改善项目文档的可读性和对外展示效果，但不涉及核心功能变更。</li>
</ul>
<h2>4. 社区热点</h2>
<p>今日无高讨论度或高反馈量的 Issue/PR。唯一新增 PR <a href="https://github.com/nullclaw/nullclaw/pull/989">#989</a> 未显示评论或点赞，社区关注度较低，暂无集中诉求。</p>
<h2>5. Bug 与稳定性</h2>
<ul>
<li><strong>低严重度 Bug：README 星标历史图表损坏</strong><br>描述：README 中的星标历史图表因依赖 GitHub stargazer API 的访问限制而无法正常渲染，影响项目展示效果。<br>状态：已有修复 PR <a href="https://github.com/nullclaw/nullclaw/pull/989">#989</a> 提出，但尚未合并。<br>影响：仅影响 README 的视觉展示，不影响项目运行或核心功能。</li>
</ul>
<h2>6. 功能请求与路线图信号</h2>
<p>今日无新功能请求产生。PR <a href="https://github.com/nullclaw/nullclaw/pull/989">#989</a> 属于文档/展示层面的修复，未反映路线图变化。暂无迹象表明下一版本将包含新功能。</p>
<h2>7. 用户反馈摘要</h2>
<p>今日无 Issue 或 PR 评论可供分析，无法提炼具体用户痛点、使用场景或满意度信息。</p>
<h2>8. 待处理积压</h2>
<p>当前无长期未响应的重要 Issue 或 PR。唯一的待合并项为 <a href="https://github.com/nullclaw/nullclaw/pull/989">#989</a>，属于新提交的修复，尚未超时等待。</p>
</details>

<details>
<summary><strong>IronClaw</strong> — <a href="https://github.com/nearai/ironclaw">nearai/ironclaw</a></summary>

<h1>IronClaw 项目动态日报 — 2026-08-20</h1>
<h2>今日速览</h2>
<p>IronClaw 于昨日正式发布 <strong>v1.3.0 稳定版</strong>，冻结并晋升了 RC2 候选版本。在核心功能推进方面，子代理激活溯源（slice 1）、OOBE 自动化任务原型、以及扩展 Provider 错误规范化三个 XL 级 PR 均已完成合并。同时，通知中心系列 PR（收件箱、运行状态、门禁事件）与持久化沙箱工作已形成活跃的 PR 队列，其中 4 个 PR 处于待合并状态，显示 v1.4.0 周期主要功能正在密集落地。CI 稳定性修复也已合入，将消除合并队列中无界 <code>apt-get</code> 造成的超时。</p>
<h2>版本发布</h2>
<h3><a href="https://github.com/nearai/ironclaw/releases">ironclaw-v1.3.0</a> — 2026-08-19</h3>
<p><strong>内容</strong>：由 <code>1.3.0-rc.2</code> 晋升为稳定版，包含 RC2 中验证的升级与容器修复，以及 RC1 的全部范围。关键修复：</p>
<ul>
<li><strong>从 1.2 升级</strong>：现在可正确接受并保留已发布扩展的 <code>activation_state</code> 字段，不再因该字段在升级过程中触发崩溃循环（crash-loop）。</li>
</ul>
<p><strong>破坏性变更</strong>：无（发布 PR <a href="https://github.com/nearai/ironclaw/pull/7754">#7754</a> 明确标注为三层版本变更，无生产行为变化）。</p>
<p><strong>迁移注意事项</strong>：1.2.x 用户可将此版本作为直接升级目标，建议升级前阅读 <a href="https://github.com/nearai/ironclaw/pull/7456">PR #7456</a>（持久化存储 profile 重构，仍在讨论中），以便规划后续存储布局变更。</p>
<h2>项目进展</h2>
<p>今日合并/关闭了 18 个 PR，值得关注的关键合入：</p>
<p><strong>核心架构与功能</strong></p>
<ul>
<li><a href="https://github.com/nearai/ironclaw/pull/7752">PR #7752</a>（XL 级，已合并）：子代理激活溯源（ActivationProvenance）基础层，增加 <code>activate()</code> 原语，为后台子代理奠定基础。无生产行为变更，新的 <code>builtin.spawn_subagent</code> 仍保持 deny 过滤。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7692">PR #7692</a>（XL 级，已合并）：能力响应规范化计划第 2 步，统一 MCP/Provider 故障为有界、类型化的诊断信息，并保留认证上下文。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7686">PR #7686</a>（XL 级，已合并）：能力结果处理集中化，将 fresh invocation、approval resume、auth resume 统一到单一 <code>capability_response_processor</code>。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/6994">PR #6994</a>（XL 级，已合并）：OOBE 自动化任务原型（轮播卡片、内联卡片、agent 模式选择器），默认通过 <code>oobe_suggestions</code> 部署开关关闭。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7756">PR #7756</a>（L 级，已合并）：CI 修复——统计显示 08-18/08-19 期间 69 次取消的运行中（1,193 个作业），每次停滞均由无界 <code>apt-get</code> 引起；已为所有 CI 操作添加超时边界。</li>
</ul>
<p><strong>等待合并中（关键积压）</strong></p>
<ul>
<li>通知中心系列：<a href="https://github.com/nearai/ironclaw/pull/7697">#7697</a>（已合并）、<a href="https://github.com/nearai/ironclaw/pull/7698">#7698</a>、<a href="https://github.com/nearai/ironclaw/pull/7699">#7699</a>、<a href="https://github.com/nearai/ironclaw/pull/7700">#7700</a>——从前端 UI 到后端持久层已完成，等待合并。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7751">PR #7751</a>（XL 级）：v1.4.0 epic #7732 的第 1 步，将每次命令创建容器改为每个 <code>(tenant, user)</code> 一个可复用容器（Docker Exec ~40ms）。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7743">PR #7743</a>（L 级）：自动化创建预检（对应 Issue #7742）。</li>
<li><a href="https://github.com/nearai/ironclaw/pull/7711">PR #7711</a>（XL 级）：WASM 类型化工具响应、访客迁移与派发错误清理（能力响应规范化收尾）。</li>
</ul>
<h2>社区热点</h2>
<p><strong>最活跃讨论：</strong></p>
<ul>
<li><p><a href="https://github.com/nearai/ironclaw/issues/7732">Issue #7732 “Epic: Persistent per-user sandbox with iron-proxy”</a> — 7 条评论，v1.4.0 核心方向。当前实现为每条 shell 命令创建/销毁容器，目标转为持久化 per-user sandbox 通过 iron-proxy 访问。该 epic 已带动 PR #7751 落地。</p>
</li>
<li><p><a href="https://github.com/nearai/ironclaw/issues/5998">Issue #5998 “Reborn has no transport for a local MCP server”</a> — 从 7 月 11 日维持至今，社区关注度高。核心矛盾：<code>stdio</code> 被拒绝、loopback HTTP 被 <code>deny_private_ip_ranges</code> 拦截，导致本机 MCP 服务完全不可用。已有贡献者提交 <a href="https://github.com/nearai/ironclaw/pull/7757">PR #7757</a> 针对此问题。</p>
</li>
<li><p><a href="https://github.com/nearai/ironclaw/issues/7748">Issue #7748 “IronClaw got confused and stopped working”</a> — 来自 Slack 的用户反馈搬运，缺少复现步骤，但代表了真实使用场景中的稳定性问题。</p>
</li>
</ul>
<p><strong>值得注意的现象</strong>：当前最热的讨论集中在<strong>沙箱持久化</strong>与<strong>本地 MCP 支持</strong>两个方向，均围绕开发者本地使用体验展开；同时通知中心系列 PR（#7697-#7700）在 24 小时窗口内形成模块化提交节奏，属于典型的「后端就绪 → 门禁 → 运行结果 → 前端泛化」流水线推进模式，预计未来 24-48 小时内全栈合入。</p>
<h2>Bug 与稳定性</h2>
<p>按严重程度排列：</p>
<ol>
<li><p><strong>[#7748] IronClaw got confused and stopped working</strong>（用户报告，无严重级别标注）— 用户报告应用陷入困惑状态并停止工作。来源为 Slack 用户反馈，尚无明确复现路径。无对应修复 PR。链接：<a href="https://github.com/nearai/ironclaw/issues/7748">Issue #7748</a></p>
</li>
<li><p><strong>[#7745] Copilot MCP 扩展安装失败</strong>（P2, bug_bash）— 三个子问题：目录中存在重复的 Copilot 条目；安装报 <code>auth_required</code>；token 类型不明确。暂无 fix PR。链接：<a href="https://github.com/nearai/ironclaw/issues/7745">Issue #7745</a></p>
</li>
<li><p><strong>[#7744] Cron 任务 UI 缺少编辑和测试按钮</strong>（P3, bug_bash）— 用户只能查看 cron 任务状态（paused/active），无法编辑或手动触发。功能完整性问题，暂无 fix PR。链接：<a href="https://github.com/nearai/ironclaw/issues/7744">Issue #7744</a></p>
</li>
<li><p><strong>[#7756] CI 合并队列超时</strong>（已修复）— 元问题：所有停滞均由无界 <code>apt-get</code> 导致。已由 <a href="https://github.com/nearai/ironclaw/pull/7756">PR #7756</a> 合并修复，所有 CI 操作已加超时边界。</p>
</li>
<li><p><strong>[#7602] / [#7603] 写入池读压力与检查点批量处理</strong>（已关闭）— 两个 Tier 2/3 性能优化完成：缓存租约围栏 token、按 N 次迭代批量写入 BeforeModel 检查点。已关闭。</p>
</li>
<li><p><strong>[#7753] 能力派发失败时终端 dispatch 记录丢失</strong>（已修复，待合并）— <a href="https://github.com/nearai/ironclaw/pull/7753">PR #7753</a> 保留了 worker 本地能力调用状态，确保失败时能落出持久化的 <code>Failed</code> 终态。</p>
</li>
</ol>
<h2>功能请求与路线图信号</h2>
<p><strong>v1.4.0 路线图信号（高置信度）</strong></p>
<ul>
<li><strong>持久化 per-user 沙箱</strong>（<a href="https://github.com/nearai/ironclaw/issues/7732">#7732</a>，epic）— 已列出 v1.4.0 目标，并有实现 PR #7751（Step 1）在队列中。</li>
<li><strong>Onboarding 渠道优先</strong>（<a href="https://github.com/nearai/ironclaw/issues/7044">#7044</a>，epic，已关闭）— 后端（#6993）与前端原型（#6994）均已合并，进入 v1.4.0 已确定。</li>
<li><strong>通知中心</strong>（<a href="https://github.com/nearai/ironclaw/issues/7688">#7688</a>，已关闭）— 合约、存储、API 已定。</li>
</ul>
<p><strong>正在讨论的新功能</strong></p>
<ul>
<li><strong>自动化创建预检</strong>（<a href="https://github.com/nearai/ironclaw/issues/7742">#7742</a>，suggested P1，v1.3.0 标记）— 作者提出结构化自动化创建需明确区分「编写未来运行」与「执行/证明未来运行」；建立诚实的执行合约（schedule/goal/success criteria）后再持久化。实现 PR <a href="https://github.com/nearai/ironclaw/pull/7743">#7743</a> 已在队列。</li>
<li><strong>本地/环回 MCP 支持</strong>（<a href="https://github.com/nearai/ironclaw/issues/5998">#5998</a>）— 官方尚未置评路线图归属，但外部贡献者 <a href="https://github.com/nearai/ironclaw/pull/7757">PR #7757</a> 提供了只允许字面环回 IP 的窄方案，可能以最小变更进入下一版本。</li>
</ul>
<p><strong>长期 epic 观察</strong></p>
<ul>
<li><strong>[#7038] Storybook + AI-first Design System</strong>（epic）— 8 月 3 日创建，有完整提案包，但今日无动态更新，需观察后续排期。</li>
</ul>
<h2>用户反馈摘要</h2>
<ul>
<li><p><strong>稳定性困惑</strong>（<a href="https://github.com/nearai/ironclaw/issues/7748">#7748</a>）— Slack 用户 bianca.guimaraes-chadwick 反馈「It just got confused and stopped working」。无更多细节，建议维护者跟进获取复现信息。</p>
</li>
<li><p><strong>Slack 连接体验</strong>（<a href="https://github.com/nearai/ironclaw/issues/7681">#7681</a>，已关闭）— 未链接用户在共享频道 @-mention 机器人时，回复对所有人可见，且要求用户手动往返 Web 应用完成链接。已修复，改善隐私性。</p>
</li>
<li><p><strong>本地开发工具链摩擦</strong>（<a href="https://github.com/nearai/ironclaw/issues/5998">#5998</a>）— 开发者明确表达了需要在本机运行 MCP server 与 IronClaw 对接的需求。当前 <code>stdio</code> 和 <code>http://127.0.0.1</code> 均不可用，意味着完全无法使用本地 MCP 生态。</p>
</li>
<li><p><strong>QA 测试反馈</strong>（<a href="https://github.com/nearai/ironclaw/issues/7745">#7745</a>、<a href="https://github.com/nearai/ironclaw/issues/7744">#7744</a>）— QA 侧发现扩展安装引导信息不一致（重复目录项、认证报错不明确）以及 cron UI 功能覆盖不足（缺编辑/测试入口）。</p>
</li>
</ul>
<h2>待处理积压</h2>
<p><strong>长期未响应的活跃 Issue</strong></p>
<ul>
<li><a href="https://github.com/nearai/ironclaw/issues/5998">Issue #5998</a>（已开放 40 天）— 本地 MCP 服务器不可达，虽已有贡献者 PR #7757，但官方尚未明确路线图归属或给出设计评审意见。建议维护者尽快回应，避免外部贡献悬置。</li>
</ul>
<p><strong>等待关注的 PR</strong></p>
<ul>
<li><p><a href="https://github.com/nearai/ironclaw/pull/7516">PR #7516</a>（XL 级，外部贡献者 neo-sky，8 月 12 日创建）— WebUI 操作员界面接入 IronHub agent link。8 天内无维护者明确反馈，存在外部贡献沉没风险。</p>
</li>
<li><p><a href="https://github.com/nearai/ironclaw/pull/7456">PR #7456</a>（XL 级，8 月 10 日创建）— Reborn 持久化存储 profile 无关化重构。涉及存储布局变更，风险中等，需设计评审。</p>
</li>
</ul>
<p><strong>遗留跟踪</strong></p>
<ul>
<li>v1.3.0 发布后，<code>release/2026-08-17</code> 分支生命周期结束，相关 backport 需求应已关闭；后续修复应直接面向主干的 v1.4.0 周期。</li>
<li>【提醒】当前 21 个 PR 待合并，其中 5 个为 XL 级。若合并过于集中可能引发回归面扩大，建议维护者量入为出，保持与 CI 吞吐匹配的合并节奏。</li>
</ul>
</details>

<details>
<summary><strong>LobsterAI</strong> — <a href="https://github.com/netease-youdao/LobsterAI">netease-youdao/LobsterAI</a></summary>

<h2>LobsterAI 项目日报 — 2026-08-20</h2>
<h3>1. 今日速览</h3>
<p>项目今日保持中等活跃度：过去24小时内有<strong>9条 PR 更新</strong>（其中8条已合并/关闭），但<strong>无新版本发布</strong>；<strong>2条 Issue 更新</strong>均为历史遗留（均为4月创建，今日被stale标记刷新）。合并的 PR 集中在安装包构建、Agent 交互修复与 UI 功能增强，其中两条 Windows 安装器修复（#2511/#2512）为昨日新提交且已快速合并，说明维护者对构建稳定性问题响应较快。Issue 侧则处于轻度积压状态，暂无新增用户反馈。</p>
<hr>
<h3>3. 项目进展</h3>
<p>今日合并/关闭的 8 条 PR 主要覆盖三个方向：</p>
<p><strong>Windows 安装器（今日新增并立即合并）</strong></p>
<ul>
<li><a href="https://github.com/netease-youdao/LobsterAI/pull/2511">#2511 fix(installer): support silent upload-first web builds</a> — 支持上传优先的两阶段 Web 安装流程，复用已上传的 NOS 文件，仅重建签名 stub，并加入 SHA-256 前后校验，防止 stub 构建失效。</li>
<li><a href="https://github.com/netease-youdao/LobsterAI/pull/2512">#2512 fix(installer): hide banner for dictbind silent package</a> — 仅对 dictbind 双击静默安装产物隐藏 banner，保留其他静默安装路径的既有行为，并同步更新安装器设计文档。</li>
</ul>
<p><strong>Agent 交互修复</strong></p>
<ul>
<li><a href="https://github.com/netease-youdao/LobsterAI/pull/1560">#1560 fix: 修复Agent编辑后点击原Agent无法切换回聊天界面的问题</a> — 修复 <code>SidebarAgentList</code> 中 <code>agentId === currentAgentId</code> 时直接 return 导致无法切回聊天界面的回归，补齐 <code>onShowCowork()</code> 调用。</li>
<li><a href="https://github.com/netease-youdao/LobsterAI/pull/1545">#1545 fix(agent): sync activeSkillIds immediately when updating current agent&#39;s skills</a> — 修复保存技能配置后徽章不即时刷新的问题，根因是 <code>updateAgent()</code> 未同步 <code>activeSkillIds</code>。</li>
</ul>
<p><strong>功能增强</strong></p>
<ul>
<li><a href="https://github.com/netease-youdao/LobsterAI/pull/1553">#1553 feat(cowork): Write 工具文件卡片及分屏预览面板</a> — 为 Write 工具增加内联文件卡片（FileCard），新增可拖拽的右侧预览面板（FilePreviewPanel），支持 Markdown/HTML/SVG/图片/代码高亮，对应关闭 Issue #1552。</li>
<li><a href="https://github.com/netease-youdao/LobsterAI/pull/1557">#1557 feat(settings): 设置面板侧栏支持搜索筛选分类</a> — 设置侧栏新增搜索框，支持中英关键词 AND 匹配过滤 Tab，无匹配时自动切换至首个可见分类。</li>
</ul>
<p><strong>构建脚本修复</strong></p>
<ul>
<li><a href="https://github.com/netease-youdao/LobsterAI/pull/1555">#1555 fix: npm run dist:mac:x64打包失败</a> — macOS 不支持 <code>sha256sum</code>，在 <code>build-openclaw-runtime.sh</code> 中加入 <code>shasum</code> 兼容。</li>
</ul>
<p><strong>仍待合并</strong>（1条）：</p>
<ul>
<li><a href="https://github.com/netease-youdao/LobsterAI/pull/1547">#1547 fix(scheduledTask): 修复定时任务通知渠道选择后无法改回&quot;不通知&quot;的问题</a> — 已存在4个月，修复 <code>TaskForm.tsx</code> 中 <code>delivery.mode</code> 为 <code>&#39;none&#39;</code> 时回显错误的历史 bug（源自 commit <code>61cfe60</code>），改动量极小（+2行），但至今未合并。</li>
</ul>
<hr>
<h3>4. 社区热点</h3>
<p>今日两条 Issue 更新均带有 <code>[stale]</code> 标记，为 4 月创建的老 Issue，评论数不多，但反映了两个值得关注的方向：</p>
<ul>
<li><p><strong><a href="https://github.com/netease-youdao/LobsterAI/issues/1556">#1556 doc bug: IM机器人配置指南404</a></strong>（2条评论）— 用户报告文档链接（<code>lobsterai.youdao.com/LobsterAI-IM机器人配置指南.md</code>）返回 404，并附截图。文档链接失效是最直接的用户访问障碍，虽非功能 bug，但会中断新用户的上手流程。该 Issue 已挂4个月未关闭，需维护者核实文档部署路径。</p>
</li>
<li><p><strong><a href="https://github.com/netease-youdao/LobsterAI/issues/1552">#1552 feat: AI产物 Markdown 预览及文件卡片支持</a></strong>（1条评论）— 用户详细描述了 Agent 写完文件后只能在聊天中靠 Read 粘贴全文或手动切换文件管理器查看的痛点，并给出了完整的产品需求（文件卡片展示文件名/路径/类型/大小 + 按钮）。该请求已被 PR #1553 实现并合并，属于&quot;需求 → 实现&quot;闭环的成功案例。</p>
</li>
</ul>
<hr>
<h3>5. Bug 与稳定性</h3>
<p>按严重程度排列：</p>
<table>
<thead>
<tr>
<th>严重度</th>
<th>Issue/PR</th>
<th>描述</th>
<th>状态</th>
</tr>
</thead>
<tbody><tr>
<td>中</td>
<td><a href="https://github.com/netease-youdao/LobsterAI/pull/1555">#1555 npm run dist:mac:x64打包失败</a></td>
<td>macOS 打包因 <code>sha256sum</code> 不存在直接失败，阻断发版</td>
<td>已修复并合并</td>
</tr>
<tr>
<td>中</td>
<td><a href="https://github.com/netease-youdao/LobsterAI/pull/1560">#1560 Agent编辑后无法切回聊天界面</a></td>
<td>编辑 Agent 后点击原 Agent 不切换，界面滞留</td>
<td>已修复并合并</td>
</tr>
<tr>
<td>低</td>
<td><a href="https://github.com/netease-youdao/LobsterAI/pull/1545">#1545 技能徽章不即时更新</a></td>
<td>保存技能后需手动切换 Agent 才能看到新的 <code>activeSkillIds</code></td>
<td>已修复并合并</td>
</tr>
<tr>
<td>低</td>
<td><a href="https://github.com/netease-youdao/LobsterAI/pull/1547">#1547 定时任务通知渠道无法改回&quot;不通知&quot;</a></td>
<td>表单初始化未优先检查 <code>delivery.mode==&#39;none&#39;</code>，导致下拉框回显旧值</td>
<td><strong>待合并</strong>（已挂4个月）</td>
</tr>
<tr>
<td>低</td>
<td><a href="https://github.com/netease-youdao/LobsterAI/pull/2511">#2511/#2512 安装器静默安装 banner 与上传流程问题</a></td>
<td>Web 安装器上传流程、dictbind 静默包 banner 显示异常</td>
<td>已合并</td>
</tr>
</tbody></table>
<hr>
<h3>6. 功能请求与路线图信号</h3>
<ul>
<li><strong>AI 产物文件预览（#1552 → #1553）</strong>：已在今日合并的 PR #1553 中落地，预计进入下一版本。该功能提升了 Write 工具在工作流中的使用体验，对写作、文档生成场景有直接价值。</li>
<li><strong>设置面板搜索（#1557）</strong>：已合并，解决设置 Tab 过多时的导航问题，属于低成本高感知的 UX 改进。</li>
<li><strong>引擎启动超时取消（#1546）</strong>：该 PR 今日被标记 stale 但已合并（为4月 PR），功能为启动超 30 秒后显示&quot;取消启动&quot;和&quot;查看日志&quot;按钮，为引擎卡死提供逃逸出口。该能力对调试和容错有实际意义，说明项目在完善任务执行的可中断性。</li>
</ul>
<hr>
<h3>7. 用户反馈摘要</h3>
<ul>
<li><strong>文档可访问性（#1556）</strong>：用户因 IM 机器人配置指南 404 无法完成配置，截图显示页面直接报错。该反馈说明官方文档站点存在链接失效问题，建议维护者建立文档链接自动检查机制。</li>
<li><strong>文件预览需求（#1552）</strong>：用户描述的场景（&quot;Agent 用 Read 读取后全文贴到聊天中占用大量对话空间&quot;）反映了当前聊天界面在处理文件产出时的信息效率缺陷。用户建议的 <code>Write 工具后显示 FileCard</code> 方案已被采纳实现。</li>
<li><strong>无负面情绪较强的反馈</strong>：今日无新增 issue，历史 issue 也未出现激烈讨论。</li>
</ul>
<hr>
<h3>8. 待处理积压</h3>
<p>以下 Issue/PR 长期未得到响应，建议维护者关注：</p>
<ul>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/issues/1556">Issue #1556 — IM机器人配置指南404</a></strong> — 创建于 2026-04-08，持续4个月未关闭，属于文档类低优先级但影响新用户上手的直接问题。</li>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/issues/1552">Issue #1552 — AI产物 Markdown 预览及文件卡片支持</a></strong> — 虽已被 PR #1553 实现，但 Issue 本身未自动关闭，需维护者手动关闭并关联 PR。</li>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1547">PR #1547 — 定时任务通知渠道无法改回&quot;不通知&quot;</a></strong> — 修复代码仅 +2/-0 行，根因明确（commit <code>61cfe60</code> 引入的历史 bug），但长期搁置未合并。建议尽快评审合并，消除已知行为不一致。</li>
<li>另有一批 4 月创建的 PR（#1545、#1546、#1553、#1555、#1557、#1560）今日均被 marked stale，虽大多已实际合并，但 stale bot 扫描时机滞后，建议检查 stale 规则配置，避免对已合并 PR 继续打标。</li>
</ul>
</details>

<details>
<summary><strong>TinyClaw</strong> — <a href="https://github.com/TinyAGI/tinyclaw">TinyAGI/tinyclaw</a></summary>

<p>过去24小时无活动。</p>
</details>

<details>
<summary><strong>Moltis</strong> — <a href="https://github.com/moltis-org/moltis">moltis-org/moltis</a></summary>

<h1>Moltis 项目动态日报 — 2026-08-20</h1>
<h2>1. 今日速览</h2>
<ul>
<li>过去 24 小时项目保持中等活跃度：1 个安全相关 Issue 被关闭，4 个 PR 全部完成合并/关闭，并发布 1 个新版本（20260818.10）。</li>
<li>今日核心是安全修复与 WhatsApp 通道体验优化：修复了 Vault 解锁/恢复接口未鉴权的 CWE-306 漏洞，并解决了 WhatsApp 中 push name 硬编码、回复消息被忽略、工具权限策略过于严格等问题。</li>
<li>所有 PR 均在 1-2 天内从创建到关闭，维护者响应速度良好；Issue #1177 从创建到修复关闭共 21 天，过程透明。</li>
<li>没有新的待合并 PR 或新开 Issue，积压压力较小，项目健康度良好。</li>
</ul>
<h2>2. 版本发布</h2>
<p><strong>Release: 20260818.10</strong>（发布于 2026-08-18，今日纳入统计）</p>
<ul>
<li>当前未提供详细 changelog，从同日合并的 PR 推断，该版本至少包含今日合入的 4 个修复（见下）。</li>
<li><strong>破坏性变更</strong>：PR #1219 调整了非操作员对话中的工具策略层级，使“公开受众”工具重新可用，同时保留对 /sh 命令的严格限制。凡依赖此前“所有非操作员对话均禁用全部工具”行为的配置，需重新验证工具权限预期。</li>
<li><strong>迁移注意事项</strong>：WhatsApp 配置中 <code>push_name</code> 不再被强制覆盖为 “Moltis”，请检查依赖旧行为的自动化脚本或文档示例。</li>
</ul>
<h2>3. 项目进展</h2>
<p>今日合入/关闭的 4 个 PR 均已完成，分别推进了以下方向：</p>
<ul>
<li><p><strong>安全加固（重点）</strong>：PR #1216 修复 Vault 解锁/恢复接口缺少认证的漏洞（CWE-306），该漏洞允许任何未认证远程调用者暴力破解 Vault 凭据。修复后 <code>POST /api/auth/vault/unlock</code> 和 <code>/api/auth/vault/recovery</code> 必须携带有效 <code>AuthSession</code>，不再被 <code>/api/auth/</code> 前缀的公开白名单放行。<br><a href="https://github.com/moltis-org/moltis/pull/1216">PR #1216</a></p>
</li>
<li><p><strong>WhatsApp 消息准确性</strong>：PR #1218 移除硬编码 push name “Moltis”，使 bot 在未保存联系人的会话中正确显示配置名称；PR #1217 修复在 <code>mention_mode = &quot;mention&quot;</code> 的群组中，用户回复 bot 消息时被视为未提及而被丢弃的问题，现在回复与 @提及一样被视为定向寻址。<br><a href="https://github.com/moltis-org/moltis/pull/1218">PR #1218</a> | <a href="https://github.com/moltis-org/moltis/pull/1217">PR #1217</a></p>
</li>
<li><p><strong>工具权限策略修正</strong>：PR #1219 修复 #1170 引入的回归——对非操作员对话强制 deny-all 工具策略时，连公开受众注册的工具也被一并移除，且策略层级 4/5 在公开分享场景中不可达。现在该上限变为可配置，避免过度收紧。<br><a href="https://github.com/moltis-org/moltis/pull/1219">PR #1219</a></p>
</li>
</ul>
<p>整体来看，项目在安全、通道兼容性、权限模型三个维度均有实质进步，且修复均针对真实使用反馈。</p>
<h2>4. 社区热点</h2>
<p>今日唯一的 Issue #1177 为安全漏洞报告，无评论和点赞，但直接催生了 PR #1216，属于典型的高影响低讨论型安全反馈。PR 侧无大量评论聚集，但 #1217 与 #1218 涉及 WhatsApp 群聊交互细节，反映出社区用户对消息路由和身份显示的高敏感度。</p>
<p><strong>热点 Issue</strong>：<br><a href="https://github.com/moltis-org/moltis/issues/1177">Issue #1177 — Vault Unlock/Recovery Endpoints Missing Authentication (CWE-306)</a></p>
<p><strong>诉求分析</strong>：用户发现 Vault 解锁/恢复端点未做鉴权，且被 <code>/api/auth/</code> 前缀白名单误伤。这是典型的“认证路由被公开前缀覆盖”安全设计缺陷，社区期待的是对所有敏感端点进行严格的权限收敛。该问题已在当日通过 PR #1216 修复。</p>
<h2>5. Bug 与稳定性</h2>
<p>按严重程度排列：</p>
<table>
<thead>
<tr>
<th>严重程度</th>
<th>问题</th>
<th>状态</th>
<th>修复 PR</th>
</tr>
</thead>
<tbody><tr>
<td>严重（CWE-306）</td>
<td>Vault 解锁/恢复接口可被未认证远程调用者暴力破解</td>
<td>已关闭</td>
<td><a href="https://github.com/moltis-org/moltis/pull/1216">PR #1216</a></td>
</tr>
<tr>
<td>中等（功能回归）</td>
<td>#1170 引入的工具策略导致公开受众工具被禁用，策略层级 4/5 不可达</td>
<td>已关闭</td>
<td><a href="https://github.com/moltis-org/moltis/pull/1219">PR #1219</a></td>
</tr>
<tr>
<td>中等（交互错误）</td>
<td>群组中回复 bot 消息被丢弃（mention 模式）</td>
<td>已关闭</td>
<td><a href="https://github.com/moltis-org/moltis/pull/1217">PR #1217</a></td>
</tr>
<tr>
<td>低（展示/品牌）</td>
<td>WhatsApp push name 被硬编码为 “Moltis”，与 bot 实际配置名不符</td>
<td>已关闭</td>
<td><a href="https://github.com/moltis-org/moltis/pull/1218">PR #1218</a></td>
</tr>
</tbody></table>
<p>所有已知 Bug 均已在当日获得修复，无遗留未处理 Bug。</p>
<h2>6. 功能请求与路线图信号</h2>
<ul>
<li>本次没有全新的功能请求 Issue。但 PR #1219 的可配置化方向暗示项目正在将“硬编码安全策略”逐步改为“可调策略”，未来可能开放更多策略层级供部署者自定义。</li>
<li>PR #1217 的修复表明 WhatsApp 群聊中“提及”与“回复”双语义已被官方确认并统一处理，后续可能继续优化其他通道的定向消息语义。</li>
<li>从 Issue #1177 的修复方式看，团队可能会对 <code>/api/auth/</code> 前缀下的所有端点进行一次全面的鉴权审计，以减少同类白名单误用风险。</li>
</ul>
<h2>7. 用户反馈摘要</h2>
<ul>
<li>用户报告 Vault 解锁/恢复端点无鉴权，暗示自托管用户对远程攻击面非常关注，期望默认配置即安全。</li>
<li>WhatsApp 场景中，用户侧反馈体现在两个 PR：#1217 表明真实用户会使用“回复”来与 bot 对话（而非必须 @），#1218 表明 bot 显示名错误会让联系人列表外的用户困惑，影响品牌可信度。</li>
<li>没有负面评论或抱怨维护速度的反馈，整体用户互动集中在功能性改进上。</li>
</ul>
<h2>8. 待处理积压</h2>
<ul>
<li>当前无长期未响应的 Issue 或 PR。过去 24 小时内 1 个 Issue 和 4 个 PR 全部关闭，且没有新开条目。</li>
<li>建议维护者关注 <code>is_public_path()</code> 对 <code>/api/auth/</code> 前缀的全局白名单逻辑，可考虑引入更细粒度的路由声明机制，避免未来新增 auth 子路由时再次出现同类漏洞。</li>
</ul>
</details>

<details>
<summary><strong>CoPaw</strong> — <a href="https://github.com/agentscope-ai/CoPaw">agentscope-ai/CoPaw</a></summary>

<h1>CoPaw 项目动态日报 — 2026-08-20</h1>
<h2>今日速览</h2>
<p>过去 24 小时项目活跃度处于高位：共 19 条 Issue 更新（新开/活跃 3 条，关闭 16 条）、45 条 PR 更新（待合并 19 条，已合并/关闭 26 条），无新版本发布。当日合并的 PR 集中在稳定性修复上，其中远程媒体下载导致的会话卡死（#7110）和 envs.json 损坏导致的环境变量静默丢失（#7118）均已完成修复闭环；技能系统（Skill）的多项体验改进（CLI 搜索、名称去重、文件名保留）也一并落地。与此同时，新开放的 Issue 指向钉钉群聊上下文模式（#7158）与 embedding 健康检查超时硬编码（#7156）两个新方向。历史 Issue 清理力度较大（关闭 16 条），但其中包含多起 4 月遗留的长期需求，建议维护者对关闭原因做一次集中说明。</p>
<h2>项目进展</h2>
<p>今日合并/关闭的 PR 在三个维度上推进了项目：</p>
<p><strong>稳定性修复</strong></p>
<ul>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7138">#7138 fix: recover from remote media download timeouts</a>：修复模型提供商下载远程图片/视频超时后，会话因重复发送同一 URL 而持续卡死的问题。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7146">#7146 fix(view_image): freeze remote images before persisting tool results</a>：远程 <code>view_image</code> 在持久化前即被下载并转为不可变 Base64 块，附带大小、超时、重定向和 SSRF 防护，防止后续对话轮次被破坏。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7135">#7135 fix(envs): preserve corrupt files and write envs atomically</a>：损坏的 envs.json 不再被静默吞掉并覆写，改为保留现场 + 原子写入，对应 Issue #7118。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7157">#7157 fix(e2e): dismiss Try Desktop Mode onboarding overlay before tests</a>：消除自 #6645 引入的全屏透明引导层对 E2E 的指针事件拦截，终结 nightly E2E 连续 8 天失败（runs #71–#78）。</li>
</ul>
<p><strong>技能系统与体验</strong></p>
<ul>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7140">#7140 Refactor(cli): refactor skill cli, add search, add batch enable/disable</a>：技能 CLI 重构，新增搜索/过滤和批量启用/禁用，落实 Issue #7090 的需求。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7097">#7097 fix(skill): remove skill bound duplication</a>：按 SKILL.md frontmatter 名称对工作区技能与内置绑定技能去重，修复 Issue #7073。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/6492">#6492 fix(files): preserve uploaded filenames in hints</a>：用户消息提示中保留上传文件原始文件名，解决 #6453 的中文文件名被替换为 UUID 路径的问题。</li>
</ul>
<p><strong>架构与工程能力</strong></p>
<ul>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7114">#7114 refactor(config): make agent config loading async by default</a>：agent 配置加载默认改为非阻塞异步 API。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7037">#7037 feat(computer-use): observe related window surfaces</a>：Computer Use 可额外观察至多 3 个关联窗口表面（原生菜单、下拉框、所属对话框），扩大视觉可达范围。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7089">#7089 ci(datapaw): add a standalone version-driven release pipeline</a>：datapaw 插件获得独立版本驱动发布流水线。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7115">#7115 fix(memory): avoid noisy inbox notifications for unchanged jobs</a>：Auto-Memory/Auto-Dream 执行无实际变更时保持静默，减少定时任务的无效通知。</li>
</ul>
<h2>社区热点</h2>
<ul>
<li><a href="https://github.com/agentscope-ai/QwenPaw/issues/2884">#2884 [Question] 安装当天个人目录内容几乎被清空，软件也被删除</a> — 27 条评论，为当日讨论热度最高。用户于 2026-04-03 反馈 Ubuntu 22.04 上安装 coPaw 后数小时内个人目录与软件本体被清空，情绪激烈（“要疯了”），并猜测是软件缺陷或外部攻击。虽然状态为已关闭，但最近更新于 08-19，社区讨论仍在延续，是本月最需要官方给出明确结论的历史事件。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/issues/6826">#6826 [Bug] 助手消息结束时间显示异常</a> — 4 条评论。用户实测助手思考耗时 2 分钟，页面却显示仅几秒，影响对模型真实耗时的判断。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/issues/6847">#6847 [Question] 同样的任务和模型，Qwenpaw 会被杀软打死，WorkBuddy 不会</a> — 4 条评论。用户反馈杀毒软件频繁拦截并强制关停 Qwenpaw 进程，异构对比凸显其行为特征易被安全软件标记。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/issues/7110">#7110 [Bug] 对话上下文中包含无法下载的图片链接，整个会话不可用</a> — 3 条评论。模型幻觉或网络限制导致的无法访问 URL 会让会话彻底挂起，用户只能 <code>/clear</code>。已由 #7138 和 #7146 修复。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/issues/7013">#7013 [Feature] 为 Chat 增加统一工具面板、Web 服务预览与交互式终端</a> — 3 条评论。用户对 Agent 开发协作闭环有明确诉求，希望在一个工作台内完成产物预览、Diff 查看、Web 服务预览与命令交互。</li>
</ul>
<h2>Bug 与稳定性</h2>
<p>按严重程度排列：</p>
<table>
<thead>
<tr>
<th>严重度</th>
<th>Issue</th>
<th>状态</th>
<th>是否有 fix PR</th>
</tr>
</thead>
<tbody><tr>
<td>严重</td>
<td><a href="https://github.com/agentscope-ai/QwenPaw/issues/2884">#2884 用户个人目录被清空、软件被删</a></td>
<td>已关闭，讨论仍在继续</td>
<td>无公开对应 PR，需官方明确结论</td>
</tr>
<tr>
<td>严重</td>
<td><a href="https://github.com/agentscope-ai/QwenPaw/issues/7118">#7118 envs.json 损坏被静默吞掉并覆写，所有环境变量丢失</a></td>
<td>已关闭</td>
<td>✅ <a href="https://github.com/agentscope-ai/QwenPaw/pull/7135">#7135</a> 已合并/关闭</td>
</tr>
<tr>
<td>高</td>
<td><a href="https://github.com/agentscope-ai/QwenPaw/issues/7110">#7110 不可下载的图片 URL 导致整个会话不可用</a></td>
<td>已关闭</td>
<td>✅ <a href="https://github.com/agentscope-ai/QwenPaw/pull/7138">#7138</a> + <a href="https://github.com/agentscope-ai/QwenPaw/pull/7146">#7146</a> 已合并/关闭</td>
</tr>
<tr>
<td>中</td>
<td><a href="https://github.com/agentscope-ai/QwenPaw/issues/7156">#7156 embedding health check 在后端已预热时仍超时，且 timeout 硬编码无配置项</a></td>
<td>开放（08-20 新开）</td>
<td>❌ 无，等待维护者确认</td>
</tr>
<tr>
<td>中</td>
<td><a href="https://github.com/agentscope-ai/QwenPaw/issues/6624">#6624 Scroll 自动压缩不触发 summarize_when_compact 记忆流程，手动 /compact 可以</a></td>
<td>已关闭</td>
<td>无，设计如此或待确认</td>
</tr>
<tr>
<td>低</td>
<td><a href="https://github.com/agentscope-ai/QwenPaw/issues/6826">#6826 消息结束时间显示异常</a></td>
<td>已关闭</td>
<td>无公开对应 PR</td>
</tr>
</tbody></table>
<p>此外，PR 侧已提交 <a href="https://github.com/agentscope-ai/QwenPaw/pull/7150">#7150 fix: detect and recover from stalled LLM streams</a>（待合并），用于修复上游 LLM 流中断但连接未关闭时 QwenPaw 永久停留在“Thinking”状态的问题（对应 Issue #7102）。</p>
<h2>功能请求与路线图信号</h2>
<ul>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/issues/7013">#7013 Chat 统一工具面板 / Web 服务预览 / 交互式终端</a></strong>（开放，3 评论）：用户希望 Chat 页面有统一工作台承载会话产物、Diff、Web 服务预览和 Web Terminal。与待合并的 <a href="https://github.com/agentscope-ai/QwenPaw/pull/6880">#6880 统一 marketplace（apps/plugins/skills 合并至 /market）</a> 方向一致，Console 前端整合将是下阶段重点。</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/issues/7158">#7158 钉钉群聊上下文模式可配置</a></strong>（08-20 新开）：要求默认按用户隔离，指定群可开启共享上下文。社区对 Channel 侧多租户/共享会话语义有细分需求。</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/issues/7156">#7156 embedding health check 超时可配置</a></strong>（08-20 新开）：超时 5 秒硬编码在预热后端上 elapsed 达 10.4 秒，导致向量召回降级为 BM25-only。属于配置化诉求，落地成本低。</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/issues/7090">#7090 技能池搜索/过滤</a></strong>：已由 <a href="https://github.com/agentscope-ai/QwenPaw/pull/7140">#7140</a> 合并实现，该能力确认进入主分支。</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/issues/3082">#3082 解决健忘症：将“查看 memory.md”写入常驻内存</a></strong>（已关闭）：用户希望模型在不确定时主动查阅 memory.md，而非默认不加载该文档。结合今日合并的 <a href="https://github.com/agentscope-ai/QwenPaw/pull/7115">#7115 无变化任务保持静默通知</a>，记忆系统正处于活跃迭代期。</li>
</ul>
<h2>用户反馈摘要</h2>
<ul>
<li><strong>数据安全是最大的信任危机</strong>：Issue #2884 的用户描述“早上才安装，中午回来个人目录内容几乎被清空”并表达强烈情绪，无论最终原因归属，此类事件对项目声誉影响极大，建议官方以公告或文档形式给出完整技术解释与排查步骤，消除社区疑虑。</li>
<li><strong>杀软误报挫伤实际使用</strong>：Issue #6847 的用户指出同等任务下“Qwenpaw 会被杀软打死，WorkBuddy 不会”，说明 Qwenpaw 的进程行为或文件特征容易触发安全软件告警，可能影响企业/准生产环境用户。</li>
<li><strong>远程媒体路径脆弱</strong>：Issue #7110 的用户遭遇模型幻觉生成的无法访问图片导致整个会话瘫痪，且只能 <code>/clear</code>，是典型的“一处坏链接毁掉整个对话”体验问题，现已有双重修复。</li>
<li><strong>中文用户体验细节被看见</strong>：Issue #6453 的用户反馈中文文件名在提示中被换成不可识别字符且路径冗长，随着 <a href="https://github.com/agentscope-ai/QwenPaw/pull/6492">#6492</a> 合并，此问题得到解决。</li>
<li><strong>记忆/长期上下文是高频诉求</strong>：多个 Issue（#3082、#6624、#3018）从不同角度指向同一核心痛点——记忆与上下文的可靠性、可配置性、可解释性。社区用户普遍愿意维护 memory.md 等文档，但希望模型能主动查阅并有稳定触发机制。</li>
</ul>
<h2>待处理积压</h2>
<p><strong>历史遗留 Issue（4 月创建，长期未获明确结论）：</strong></p>
<ul>
<li><a href="https://github.com/agentscope-ai/QwenPaw/issues/2884">#2884 安装后个人目录被清空</a>：27 条评论，8/19 仍有更新。建议维护者给出正式技术归因。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/issues/3177">#3177 coPaw app 无法启动（Windows 批处理 BOM 错误）</a>：显示 <code>锘緻echo off</code> 等 UTF-8 BOM 被误解析问题，4 月至今未关闭前应已处理，但未见对应 PR 记录。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/issues/3082">#3082 解决健忘症（memory.md 主动查阅）</a>：核心记忆机制诉求。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/issues/3260">#3260 Harness Agents / ACP / 多 Provider 独立配置</a>：获得 1 👍，涉及路线图级能力。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/issues/3261">#3261 浏览器自动化能力差、无法复用登录状态</a>：浏览器自动化是 Agent 落地高频场景，当前反馈偏负面。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/issues/3018">#3018 用户配置存储路径支持自定义</a>：涉及 skills、core files、智能体配置的自定义路径。</li>
</ul>
<p><strong>待审查/待合并的开放 PR 提醒：</strong></p>
<ul>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/6764">#6764 feat(ci): gate main mergeability on tests</a>：为 main 分支添加必需状态检查，防止测试全红时仍被合并（此前 #6418 已发生此类事故）。该 PR 已开放两周，建议优先推进审查，它是 CI 治理闭环的关键一环。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/5861">#5861 fix(desktop): resolve login-shell PATH for packaged macOS backend</a>：修复 macOS 打包后端无法发现用户通过 shell 配置安装的工具，首个贡献者 PR，等待审查。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7150">#7150 fix: detect and recover from stalled LLM streams</a>：对应 #7102 的“Thinking 状态无限挂起”问题，属高影响稳定性修复，建议尽快合入。</li>
<li><a href="https://github.com/agentscope-ai/QwenPaw/pull/7112">#7112 feat(hub): add self-hosted multi-user Hub</a>：体量较大的新功能，引入自托管多用户控制平面，建议尽早组织设计评审。</li>
</ul>
</details>

<details>
<summary><strong>ZeptoClaw</strong> — <a href="https://github.com/qhkm/zeptoclaw">qhkm/zeptoclaw</a></summary>

<p>过去24小时无活动。</p>
</details>

<details>
<summary><strong>EasyClaw</strong> — <a href="https://github.com/gaoyangz77/easyclaw">gaoyangz77/easyclaw</a></summary>

<h1>EasyClaw 项目动态日报 — 2026-08-20</h1>
<h2>1. 今日速览</h2>
<ul>
<li>过去 24 小时内，EasyClaw 仓库未产生新的 Issue 或 PR，社区讨论与协作活动处于静默状态，活跃度较低。</li>
<li>项目连续发布 3 个版本（v1.8.101 → v1.8.103），迭代节奏密集，核心功能持续优化。</li>
<li>更新重点集中在飞书（Feishu）集成稳定性、Gateway 会话与审批、达人协作（Affiliate）以及增量更新可靠性方面。</li>
<li>无新增 Bug 报告、无待合并 PR，项目当前进入发布后稳定期，整体健康度良好。</li>
<li>维护者保持高频发版习惯，但社区外部反馈输入不足，建议关注用户使用后的实际反馈。</li>
</ul>
<h2>2. 版本发布</h2>
<h3>v1.8.103</h3>
<ul>
<li><strong>发布时间</strong>：2026-08-20（基于数据日期推断）</li>
<li><strong>更新内容</strong>：<ul>
<li>改善飞书最终回复（final replies）质量与逻辑</li>
<li>优化 Gateway 会话恢复机制</li>
<li>提升达人协作状态一致性</li>
</ul>
</li>
<li><strong>破坏性变更</strong>：无明确说明</li>
<li><strong>迁移注意事项</strong>：macOS 用户若遇 “&#39;RivonClaw&#39; is damaged and can&#39;t be opened” 提示，需按安装说明处理 Gatekeeper 拦截</li>
<li><strong>链接</strong>：<a href="https://github.com/gaoyangz77/easyclaw/releases/tag/v1.8.103%EF%BC%88%E6%8E%A8%E6%B5%8B%E6%A0%87%E7%AD%BE%EF%BC%8C%E4%BB%A5%E4%BB%93%E5%BA%93%E5%AE%9E%E9%99%85%E4%B8%BA%E5%87%86%EF%BC%89">https://github.com/gaoyangz77/easyclaw/releases/tag/v1.8.103（推测标签，以仓库实际为准）</a></li>
</ul>
<h3>v1.8.102</h3>
<ul>
<li><strong>更新时间</strong>：紧邻上一版本</li>
<li><strong>更新内容</strong>：<ul>
<li>提高增量更新可靠性</li>
<li>改善飞书连接稳定性</li>
<li>优化达人报价编辑体验</li>
<li>改进 Gateway 执行审批流程</li>
</ul>
</li>
<li><strong>破坏性变更</strong>：无明确说明</li>
<li><strong>迁移注意事项</strong>：同 v1.8.103 的 macOS Gatekeeper 处理方式</li>
<li><strong>链接</strong>：<a href="https://github.com/gaoyangz77/easyclaw/releases/tag/v1.8.102%EF%BC%88%E6%8E%A8%E6%B5%8B%E6%A0%87%E7%AD%BE%EF%BC%8C%E4%BB%A5%E4%BB%93%E5%BA%93%E5%AE%9E%E9%99%85%E4%B8%BA%E5%87%86%EF%BC%89">https://github.com/gaoyangz77/easyclaw/releases/tag/v1.8.102（推测标签，以仓库实际为准）</a></li>
</ul>
<h3>v1.8.101</h3>
<ul>
<li><strong>更新时间</strong>：更早于 v1.8.102</li>
<li><strong>更新内容</strong>：<ul>
<li>优化达人 Campaign 条款支持</li>
<li>改进按店铺的 Working Agenda 功能</li>
<li>完善设备分配逻辑</li>
<li>强化 WMS 校验规则</li>
<li>修复 Gateway 模型服务商选择的持久化问题</li>
</ul>
</li>
<li><strong>破坏性变更</strong>：无明确说明</li>
<li><strong>迁移注意事项</strong>：无额外说明</li>
<li><strong>链接</strong>：<a href="https://github.com/gaoyangz77/easyclaw/releases/tag/v1.8.101%EF%BC%88%E6%8E%A8%E6%B5%8B%E6%A0%87%E7%AD%BE%EF%BC%8C%E4%BB%A5%E4%BB%93%E5%BA%93%E5%AE%9E%E9%99%85%E4%B8%BA%E5%87%86%EF%BC%89">https://github.com/gaoyangz77/easyclaw/releases/tag/v1.8.101（推测标签，以仓库实际为准）</a></li>
</ul>
<h2>3. 项目进展</h2>
<ul>
<li>今日无 PR 被合并或关闭，无代码评审活动。</li>
<li>通过连续发布 v1.8.101～v1.8.103，项目在 24 小时内完成了多轮功能优化与稳定性修复，实际推进了以下模块：<ul>
<li><strong>飞书集成</strong>：回复质量、连接稳定性、会话恢复能力</li>
<li><strong>Gateway 服务</strong>：会话恢复、执行审批、模型服务商配置持久化</li>
<li><strong>达人协作（Affiliate）</strong>：报价编辑、条款、状态一致性</li>
<li><strong>系统可靠性</strong>：增量更新、WMS 校验、设备分配</li>
</ul>
</li>
<li>由于无 PR 数据，无法提供代码层面的具体提交信息，但版本发布本身即为项目向前迈进的有力信号。</li>
</ul>
<h2>4. 社区热点</h2>
<ul>
<li>今日无活跃 Issues 或 PRs，无高讨论量话题。</li>
<li>仓库当前处于发布驱动的迭代状态，社区讨论暂未形成热点。</li>
<li>建议关注后续用户对 v1.8.102/103 中飞书与 Gateway 改动的反馈，可能成为下轮讨论焦点。</li>
</ul>
<h2>5. Bug 与稳定性</h2>
<ul>
<li>今日无新报告的 Bug、崩溃或回归问题。</li>
<li>从版本更新说明来看，已知修复方向包括：<ul>
<li>Gateway 会话恢复（v1.8.103）</li>
<li>飞书连接稳定性（v1.8.102）</li>
<li>增量更新可靠性（v1.8.102）</li>
<li>模型服务商选择持久化（v1.8.101）</li>
</ul>
</li>
<li>所有此类修复已随新版本发布，无需等待额外 fix PR。</li>
<li>macOS 用户的 Gatekeeper 提示属于已知安装问题，新版本安装说明中已提供处理指引，非运行时缺陷。</li>
</ul>
<h2>6. 功能请求与路线图信号</h2>
<ul>
<li>今日无新增功能请求 Issue。</li>
<li>连续版本更新显示以下方向为项目当前重点（可能进入后续迭代）：<ul>
<li>飞书最终回复的智能化和上下文一致性</li>
<li>Gateway 会话恢复与审批流程的自动化</li>
<li>达人协作中报价、条款、状态的统一管理</li>
<li>多店铺 Working Agenda 与设备分配</li>
<li>WMS 校验的深化</li>
</ul>
</li>
<li>这些方向可能对应项目路线图中的「企业集成稳定性」与「协作工作流」双主线。</li>
</ul>
<h2>7. 用户反馈摘要</h2>
<ul>
<li>今日无 Issues 评论，无法提炼新的用户痛点或使用场景。</li>
<li>可参考历史版本更新所隐含的用户诉求：<ul>
<li>使用飞书作为前端入口的用户对对话连续性、连接稳定性有较高要求</li>
<li>达人运营用户需要更灵活的报价编辑与状态同步能力</li>
<li>多门店/多设备场景下希望工作日程和设备分配更可控</li>
</ul>
</li>
<li>建议维护者主动在 Release notes 下方或 Discord/微信群收集反馈，以补充此部分信息。</li>
</ul>
<h2>8. 待处理积压</h2>
<ul>
<li>当前无长期未响应的 Issue 或 PR。</li>
<li>仓库状态清爽，无积压风险。</li>
<li>提醒：由于今日 Issue/PR 数据为零，建议维护者检查是否通知渠道（如邮件、Slack 集成）存在遗漏，确保没有遗漏社区输入。</li>
</ul>
<hr>
<p><em>数据来源：<a href="https://github.com/gaoyangz77/easyclaw">https://github.com/gaoyangz77/easyclaw</a> （统计时间截至 2026-08-20）</em></p>
</details>

<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Agents Ecosystem Digest 2026-08-20</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-agents-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-agents-en</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      <description>OpenClaw Ecosystem Digest 2026-08-20 Issues: 307 | PRs: 500 | Projects covered: 13 | Generated: 2026-08-20 04:55 UTC OpenClaw NanoBot Zeroclaw PicoClaw NanoClaw NullClaw IronClaw LobsterAI TinyClaw Moltis CoPaw ZeptoClaw EasyClaw OpenClaw Deep Dive OpenClaw Project Digest — 2026-08-20 1. Today&amp;#39;s Overview OpenClaw saw a very high level of activity over the last 24 hours: 307 issues were updated (254 open/active, 53 closed) and 500 PRs were touched (428 open, 72 merged/closed), with no new rel...</description>
      <content:encoded><![CDATA[<h1>OpenClaw Ecosystem Digest 2026-08-20</h1>
<blockquote>
<p>Issues: 307 | PRs: 500 | Projects covered: 13 | Generated: 2026-08-20 04:55 UTC</p>
</blockquote>
<ul>
<li><a href="https://github.com/openclaw/openclaw">OpenClaw</a></li>
<li><a href="https://github.com/HKUDS/nanobot">NanoBot</a></li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw">Zeroclaw</a></li>
<li><a href="https://github.com/sipeed/picoclaw">PicoClaw</a></li>
<li><a href="https://github.com/qwibitai/nanoclaw">NanoClaw</a></li>
<li><a href="https://github.com/nullclaw/nullclaw">NullClaw</a></li>
<li><a href="https://github.com/nearai/ironclaw">IronClaw</a></li>
<li><a href="https://github.com/netease-youdao/LobsterAI">LobsterAI</a></li>
<li><a href="https://github.com/TinyAGI/tinyclaw">TinyClaw</a></li>
<li><a href="https://github.com/moltis-org/moltis">Moltis</a></li>
<li><a href="https://github.com/agentscope-ai/CoPaw">CoPaw</a></li>
<li><a href="https://github.com/qhkm/zeptoclaw">ZeptoClaw</a></li>
<li><a href="https://github.com/gaoyangz77/easyclaw">EasyClaw</a></li>
</ul>
<hr>
<h2>OpenClaw Deep Dive</h2>
<h1>OpenClaw Project Digest — 2026-08-20</h1>
<h2>1. Today&#39;s Overview</h2>
<p>OpenClaw saw a very high level of activity over the last 24 hours: 307 issues were updated (254 open/active, 53 closed) and 500 PRs were touched (428 open, 72 merged/closed), with no new releases published. The project remains in a heavy stabilization phase, with two P0 gateway-startup regressions affecting 2026.7.x upgrades, a concentrated cluster of P1 message-delivery and session-state bugs, and an active wave of model-selection and auth-provider fix PRs. Maintainer review appears to be the main bottleneck: many P1 issues carry <code>needs-maintainer-review</code> or <code>needs-product-decision</code> labels with linked but unmerged fix PRs. No release shipped today, so the large volume of merged work is accumulating toward the next version.</p>
<h2>2. Releases</h2>
<p>No new releases were published in the last 24 hours.</p>
<h2>3. Project Progress</h2>
<p>72 PRs were merged or closed in the last 24 hours. Notable completed items visible in the top-traffic set:</p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/pull/126531">PR #126531</a> — fix(models): preserve Codex selection for catalog-seeded models (closes #126525). Users who explicitly selected the Codex harness for an OpenAI model were silently running through the embedded harness.</li>
<li><a href="https://github.com/openclaw/openclaw/pull/126492">PR #126492</a> — fix: preserve GPT-5.6 Max and Ultra through Codex (follow-up to #126182). Requested reasoning effort was being silently omitted or downgraded.</li>
<li><a href="https://github.com/openclaw/openclaw/pull/116489">PR #116489</a> — feat(security): require acknowledgement for install policy warnings; <code>security.installPolicy</code> commands can now return <code>warn</code>, and interactive CLI installs require the exact target name to continue.</li>
<li><a href="https://github.com/openclaw/openclaw/pull/120900">PR #120900</a> — feat(ui): review install policy warnings in the Control UI with an <code>acknowledgeInstallPolicyWarning: true</code> option.</li>
<li><a href="https://github.com/openclaw/openclaw/pull/126303">PR #126303</a> — fix(ui): balance completed-work spacing in the Control UI (closes #126302).</li>
</ul>
<p>Closed issues today include the orchestration refactor <a href="https://github.com/openclaw/openclaw/issues/104871">Issue #104871</a>, overflow-recovery user-message duplication <a href="https://github.com/openclaw/openclaw/issues/66443">Issue #66443</a>, session bloat from <code>skillsSnapshot</code>/<code>systemPromptReport</code> <a href="https://github.com/openclaw/openclaw/issues/45718">Issue #45718</a>, and the multi-agent <code>infer image generate</code> owner-selection failure <a href="https://github.com/openclaw/openclaw/issues/124926">Issue #124926</a>.</p>
<p>The open-PR pipeline is heavily focused on: model/harness selection correctness, gateway cold-start recovery, Android↔gateway RPC compatibility, Control UI refresh stability, memory index freshness, and subagent delivery accounting.</p>
<h2>4. Community Hot Topics</h2>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/48003">Issue #48003</a> — <strong>Steer mode does not inject messages mid-turn for main sessions</strong> (P1, diamond lobster, 20 comments, 4 👍). <code>messages.queue.mode: &quot;steer&quot;</code> queues messages until the turn completes instead of injecting at tool boundaries. The most-discussed issue and a top pain point for interactive control.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/38327">Issue #38327</a> — <strong>&quot;Cannot convert undefined or null to object&quot; with google-vertex/gemini-3.1-pro-preview on 2026.3.2</strong> (P1, 14 comments, 3 👍). A long-running auth/model regression that still draws heavy engagement.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/108435">Issue #108435</a> — <strong>Gateway fails to start after update to 2026.7.1</strong> (P0, diamond lobster, 14 comments, 3 👍). Fails under systemd, ollama, and manual launch with &quot;gateway did not start on 127.0...&quot;.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/53628">Issue #53628</a> — <strong><code>${XDG_CONFIG_HOME}</code> not processed when installing a skill</strong> (P3, 14 comments). Docker-based users hit config-path indirection during clawhub skill installs.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/113306">Issue #113306</a> — <strong>SQLite snapshot restore lacks end-to-end crash and identity guarantees</strong> (P1, 13 comments). Restore can report success without durable parent-directory linking or final identity guards.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/88657">Issue #88657</a> — <strong>DeepSeek V4 Flash incomplete turns (<code>payloads=0, tools=2, stopReason=stop</code>)</strong> (P2, 11 comments). Regression between 2026.5.26 and 2026.5.27/28 via OpenRouter.</li>
</ul>
<p>The underlying need across these threads is production reliability: users are running real gateways and are highly sensitive to upgrade regressions, silent message loss, and auth/model-path failures.</p>
<h2>5. Bugs &amp; Stability</h2>
<p>Two P0 release-blocking regressions are open:</p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/108435">Issue #108435</a> — <strong>Gateway crash-loop after upgrade to 2026.7.1</strong>; fails under systemd, ollama, and manual launch (diamond lobster, <code>impact:crash-loop</code>, <code>impact:ux-release-blocker</code>).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/112395">Issue #112395</a> — <strong>Startup migration preflight blocks gateway after 6.11 → 7.1 upgrade</strong>; migration tables and leases are empty while the state DB appears healthy (P0, diamond lobster, <code>ux-release-blocker</code>).</li>
</ul>
<p>High-severity P1 issues updated in the last 24h:</p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/48003">Issue #48003</a> — steer mode not injecting messages mid-turn (<code>impact:message-loss</code>).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/113306">Issue #113306</a> — SQLite snapshot restore identity/crash guarantees (<code>impact:data-loss</code>).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/123799">Issue #123799</a> — production operators need upgrade/backport guidance for the Codex compact 404 on 2026.5.12; related #123706 closed as already-implemented on main.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/97680">Issue #97680</a> — beta-tagged updates leave official external plugins on the <code>latest</code> dist-tag instead of the requested beta.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/90944">Issue #90944</a> — <code>sessions_yield</code> resume reply recorded but not delivered; users receive the child raw summary instead of the parent reply.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/80498">Issue #80498</a> — subagent completion announcements premature or duplicated after tool-use turns.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/83598">Issue #83598</a> — <code>anthropic:claude-cli</code> OAuth refresh still dead-ends the main lane in 2026.5.12 despite the #73682 fix.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/77249">Issue #77249</a> — Slack socket-mode reconnect supervisor hangs on zombie WSS with no event/log emitted.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/119454">Issue #119454</a> — stuck-session recovery self-suppresses (<code>action=observe_only reason=active_embedded_run</code>) and wedges the lane until restart.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/124284">Issue #124284</a> — subagent spawn fails with vLLM openai-completions + thinking since 2026.8.1-beta.2; the new <code>wrapStreamFnWithProviderPromptState</code> wrapper interferes with vLLM.</li>
</ul>
<p>Active fix PRs for related stability issues: <a href="https://github.com/openclaw/openclaw/pull/126523">PR #126523</a> (gateway cold restart stalls with restored subagent runs), <a href="https://github.com/openclaw/openclaw/pull/126540">PR #126540</a> (Android app cannot send messages against 2026.7.1-2 gateway), <a href="https://github.com/openclaw/openclaw/pull/126424">PR #126424</a> (keep conversation delivery within agent bindings), <a href="https://github.com/openclaw/openclaw/pull/126535">PR #126535</a> (memory status ignores offline source drift), <a href="https://github.com/openclaw/openclaw/pull/126497">PR #126497</a> (TUI stale running state after run completion), and <a href="https://github.com/openclaw/openclaw/pull/126402">PR #126402</a> (Control UI config form corrupts 64-bit id strings).</p>
<h2>6. Feature Requests &amp; Roadmap Signals</h2>
<p>Long-standing feature asks that continue to receive traffic:</p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/16555">Issue #16555</a> — TTL/expiry for delivery queue messages to prevent stale entries flooding channels on restart (P1, diamond lobster).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/33975">Issue #33975</a> — fallback approval mode + model attribution in messages (P2).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/45501">Issue #45501</a> — configurable <code>session.resetPrompt</code> startup message (P3).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/9912">Issue #9912</a> — <code>maxTurns</code>/<code>maxToolCalls</code> limit for agent iterations (P2).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/7476">Issue #7476</a> — WhatsApp sticker send support (P3).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/10944">Issue #10944</a> — configurable <code>parseMode</code> for Telegram (P3).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/79168">Issue #79168</a> — content-based prompt-injection scanning on tool output (P2, security).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/42276">Issue #42276</a> — line-overwrite reasoning stream display.</li>
<li><a href="https://github.com/openclaw/openclaw/issues/37842">Issue #37842</a> — graph-aware loop detection for <code>sessions_send</code> (triangular/polygonal cascades bypass <code>maxPingPongTurns</code>).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/95840">Issue #95840</a> — <code>contextPruning mode: cache-ttl</code> never fires on OpenAI models because <code>isCacheTtlEligibleProvider</code> excludes OpenAI.</li>
</ul>
<p>Features actively moving in PRs — likely candidates for the next release — include: generic QR-based plugin setup steps (<a href="https://github.com/openclaw/openclaw/pull/119341">PR #119341</a> and <a href="https://github.com/openclaw/openclaw/pull/118169">PR #118169</a> for Signal first-account linking), recovery of offline device placements (<a href="https://github.com/openclaw/openclaw/pull/126284">PR #126284</a>), Browser Harness as the preferred model action engine (<a href="https://github.com/openclaw/openclaw/pull/126255">PR #126255</a>), staged slash-command arguments in the Control UI composer (<a href="https://github.com/openclaw/openclaw/pull/123356">PR #123356</a>), and a delivery-target option for <code>/v1/responses</code> callers so HTTP-driven subagent completions can be delivered (<a href="https://github.com/openclaw/openclaw/pull/126501">PR #126501</a>).</p>
<h2>7. User Feedback Summary</h2>
<p>The dominant user sentiment is concern about upgrade reliability. Production operators report being blocked by the 2026.7.1 gateway startup failure (<a href="https://github.com/openclaw/openclaw/issues/108435">#108435</a>) and the 6.11 → 7.1 migration preflight block (<a href="https://github.com/openclaw/openclaw/issues/112395">#112395</a>); one operator explicitly requested operational backport guidance after a fix landed only on main (<a href="https://github.com/openclaw/openclaw/issues/123799">#123799</a>). Model-path regressions continue to frustrate users: DeepSeek V4 Flash incomplete turns (<a href="https://github.com/openclaw/openclaw/issues/88657">#88657</a>), Vertex/Gemini &quot;undefined or null to object&quot; (<a href="https://github.com/openclaw/openclaw/issues/38327">#38327</a>), and vLLM subagent spawn breakage (<a href="https://github.com/openclaw/openclaw/issues/124284">#124284</a>). Message-delivery complaints cluster around subagents and <code>sessions_yield</code> — users receiving the wrong output or no output at all (<a href="https://github.com/openclaw/openclaw/issues/90944">#90944</a>, <a href="https://github.com/openclaw/openclaw/issues/80498">#80498</a>). A multi-agent fleet maintainer reported that <code>infer image generate</code> was unusable without an explicit agent selector (<a href="https://github.com/openclaw/openclaw/issues/124926">#124926</a>, closed today). On the positive side, the quick fixes for Codex selection and GPT-5.6 Max/Ultra reasoning effort (<a href="https://github.com/openclaw/openclaw/pull/126531">#126531</a>, <a href="https://github.com/openclaw/openclaw/pull/126492">#126492</a>) and the security install-policy acknowledgement feature (<a href="https://github.com/openclaw/openclaw/pull/116489">#116489</a>, <a href="https://github.com/openclaw/openclaw/pull/120900">#120900</a>) show responsive iteration on both correctness and admin safety.</p>
<h2>8. Backlog Watch</h2>
<p>Long-running issues and PRs that remain unanswered or stuck and need maintainer attention:</p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/issues/30381">Issue #30381</a> — chatCompletions should ignore request <code>model</code> when <code>x-openclaw-agent-id</code> is present (P2, diamond lobster, open since 2026-03-01, <code>clawsweeper-recovery-stuck</code>).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/16555">Issue #16555</a> — delivery-queue TTL/expiry (P1, diamond lobster, open since 2026-02-14, <code>recovery-stuck</code>).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/77249">Issue #77249</a> — reconnect supervisor hangs on zombie WSS with no log event (P1, diamond lobster, open since 2026-05-04).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/15022">Issue #15022</a> — coalesce interleaved text blocks into a single outbound message (P2, diamond lobster, open since 2026-02-12).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/37842">Issue #37842</a> — graph-aware loop detection for <code>sessions_send</code> (P2, diamond lobster, open since 2026-03-06).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/9607">Issue #9607</a> — Himalaya skill doc gaps and incorrect command syntax (P3, platinum hermit, open since 2026-02-05).</li>
<li><a href="https://github.com/openclaw/openclaw/issues/7476">Issue #7476</a> — WhatsApp sticker send support (P3, diamond lobster, open since 2026-02-02).</li>
</ul>
<p>Stale or needs-proof PRs waiting for weeks to months:</p>
<ul>
<li><a href="https://github.com/openclaw/openclaw/pull/84758">PR #84758</a> — subagents execution-backend placement contract (open since 2026-05-21, <code>needs proof</code>).</li>
<li><a href="https://github.com/openclaw/openclaw/pull/95847">PR #95847</a> — credit requester-consumed descendant subagent completions (open since 2026-06-22, <code>needs proof</code>).</li>
<li><a href="https://github.com/openclaw/openclaw/pull/112326">PR #112326</a> — prevent reverse <code>sessions_send</code> on A2A target turns (open since 2026-07-21, <code>needs proof</code>).</li>
<li><a href="https://github.com/openclaw/openclaw/pull/96011">PR #96011</a> — guard Skill Workshop <code>create</code> proposals from existing-skill patch content (open since 2026-06-23, <code>waiting on author</code>).</li>
<li><a href="https://github.com/openclaw/openclaw/pull/111922">PR #111922</a> — filter assistant process chatter from memory dreams (stale, open since 2026-07-20, ready for maintainer look).</li>
</ul>
<hr>
<h2>Cross-Ecosystem Comparison</h2>
<h1>Cross-Project Comparison Report — Personal AI Assistant / Agent Ecosystem</h1>
<p><strong>Date:</strong> 2026-08-20</p>
<hr>
<h2>1. Ecosystem Overview</h2>
<p>The personal AI assistant open-source landscape remains heavily fragmented around the &quot;Claw&quot; family (OpenClaw and its derivatives) plus independent platforms (IronClaw, CoPaw, Moltis, EasyClaw), with activity concentrated in a few high-velocity cores and long tails of dormant or maintenance-only projects. The dominant theme across all active projects is <strong>production reliability</strong>: upgrade regressions, message-delivery correctness, auth/model-path failures, and state-persistence integrity account for most high-severity issues. Release cadence is bimodal — IronClaw and EasyClaw shipped stable releases this cycle, while OpenClaw, ZeroClaw, and CoPaw accumulated large merge volumes toward upcoming cuts. Community governance is becoming a bottleneck in the largest projects, with maintainer review queues and RFC decision backlogs explicitly called out in OpenClaw, ZeroClaw, and CoPaw digests.</p>
<hr>
<h2>2. Activity Comparison</h2>
<table>
<thead>
<tr>
<th>Project</th>
<th>Issues Updated (closed)</th>
<th>PRs Updated (merged/closed)</th>
<th>Release Status</th>
<th>Health Score (1–5)</th>
</tr>
</thead>
<tbody><tr>
<td>OpenClaw</td>
<td>307 (53)</td>
<td>500 (72)</td>
<td>None (accumulating toward next)</td>
<td>3.5</td>
</tr>
<tr>
<td>NanoBot</td>
<td>3 (0)</td>
<td>20 (7)</td>
<td>None</td>
<td>3.5</td>
</tr>
<tr>
<td>ZeroClaw</td>
<td>26 (1)</td>
<td>50 (7)</td>
<td>None (v0.8.5 tracker, target Aug 30)</td>
<td>3.0</td>
</tr>
<tr>
<td>PicoClaw</td>
<td>1 (1)</td>
<td>5 (2)</td>
<td>None</td>
<td>2.5</td>
</tr>
<tr>
<td>NanoClaw</td>
<td>3 (0)</td>
<td>33 (23)</td>
<td>None</td>
<td>4.5</td>
</tr>
<tr>
<td>NullClaw</td>
<td>0</td>
<td>1 (0)</td>
<td>None</td>
<td>1.5</td>
</tr>
<tr>
<td>IronClaw</td>
<td>15 (6)</td>
<td>39 (18)</td>
<td><strong>v1.3.0 stable shipped</strong></td>
<td>4.5</td>
</tr>
<tr>
<td>LobsterAI</td>
<td>2 (0)</td>
<td>9 (8, mostly stale-sweep)</td>
<td>None</td>
<td>2.5</td>
</tr>
<tr>
<td>TinyClaw</td>
<td>0</td>
<td>0</td>
<td>None</td>
<td>1.0</td>
</tr>
<tr>
<td>Moltis</td>
<td>1 (1)</td>
<td>4 (4)</td>
<td>20260818.10 (Aug 18)</td>
<td>4.0</td>
</tr>
<tr>
<td>CoPaw</td>
<td>19 (16)</td>
<td>45 (26)</td>
<td>None (2.1.0-beta in circulation)</td>
<td>4.5</td>
</tr>
<tr>
<td>ZeptoClaw</td>
<td>0</td>
<td>0</td>
<td>None</td>
<td>1.0</td>
</tr>
<tr>
<td>EasyClaw</td>
<td>0</td>
<td>0</td>
<td><strong>3 releases (v1.8.101–103)</strong></td>
<td>3.0</td>
</tr>
</tbody></table>
<p><strong>Notes:</strong> Health score reflects merge velocity, blocker load, backlog hygiene, and release cadence. OpenClaw&#39;s raw volume is 10–100× any peer, but two open P0 release-blockers and a <code>needs-maintainer-review</code> bottleneck cap its score. NanoClaw, IronClaw, and CoPaw show the best velocity-to-backlog ratios. TinyClaw and ZeptoClaw are fully inactive.</p>
<hr>
<h2>3. OpenClaw&#39;s Position</h2>
<ul>
<li><strong>Community size:</strong> OpenClaw operates at a different scale entirely — 307 issues and 500 PRs touched daily versus 3–50 PRs for all peers. It is the reference implementation that the NanoClaw/ZeroClaw/PicoClaw/NullClaw family forks from, giving it de facto standards-setting power over skills, channels, gateway architecture, and the &quot;diamond lobster&quot; severity taxonomy.</li>
<li><strong>Advantages:</strong> Broadest channel/integration surface; the strongest security feature momentum this cycle (install-policy acknowledgement in CLI and Control UI); responsive model-path fixes (Codex harness selection, GPT-5.6 reasoning-effort preservation) merged same-day; the only project with explicit P0/<code>impact:release-blocker</code> escalation discipline.</li>
<li><strong>Technical approach:</strong> Gateway-centric architecture with a Control UI, a skills ecosystem, and a delivery-queue/message-routing layer. Its current weakness is the same as its strength — the surface area is so large that upgrade regressions (two P0 startup failures on the 2026.7.x line) and subagent/session-state bugs concentrate here before anywhere else.</li>
<li><strong>Differentiation:</strong> Competitors are either smaller forks reducing scope (ZeroClaw&#39;s lighter-core RFC), platform-specific rebuilds (NanoClaw on Node.js), or independent architectures (IronClaw&#39;s multi-tenant model, CoPaw&#39;s Qwen/agentscope stack). None match OpenClaw&#39;s breadth, but IronClaw and CoPaw surpass it in merge-to-release discipline this cycle.</li>
</ul>
<hr>
<h2>4. Shared Technical Focus Areas</h2>
<ol>
<li><strong>Upgrade &amp; startup reliability</strong> — OpenClaw (P0 gateway crash-loop #108435, migration preflight #112395; operators requesting backport guidance #123799), IronClaw (1.2→1.3 <code>activation_state</code> crash-loop, fixed in v1.3.0), NanoClaw (Node 26 passes check but <code>better-sqlite3</code> fails to build, #3359), EasyClaw (Gateway session recovery in v1.8.103), CoPaw (Windows launch failure #3177).</li>
<li><strong>Message-delivery correctness</strong> — OpenClaw (<code>sessions_yield</code> replies undelivered #90944; premature subagent completion announcements #80498; steer-mode mid-turn injection #48003), NanoClaw (Dial SMS falsely marked delivered #3353), CoPaw (undownloadable image URL bricks conversation #7110), Moltis (WhatsApp replies to bot dropped in mention mode, fixed #1217).</li>
<li><strong>Auth/OAuth/model-path failures</strong> — OpenClaw (Vertex/Gemini &quot;undefined or null to object&quot; #38327; Anthropic CLI OAuth refresh #83598), NanoBot (Docker OAuth login broken by non-root permission model #5444), ZeroClaw (Anthropic OAuth PR #9420), IronClaw (Copilot MCP extension <code>auth_required</code> install failure #7745), NanoClaw (unverifiable stored sign-in must fail closed #3339).</li>
<li><strong>Install/onboarding robustness</strong> — ZeroClaw (Windows <code>TaskDialogIndirect</code> failure #9290/#10111; Android/Termux generic-binary selection #7911; degraded <code>config init</code> #9436), NanoClaw (headless/CI install leaves 0-byte files #3354), LobsterAI (macOS <code>sha256sum</code> packaging break #1555), CoPaw (home-directory wipe report #2884).</li>
<li><strong>Memory &amp; state persistence integrity</strong> — NanoBot (Dream cursor stuck after recovered tool errors → duplicate edits #5441; token-estimation errors prevent consolidation #5402), CoPaw (corrupt <code>envs.json</code> silently overwritten #7118; auto-compression bypasses summarization #6624), OpenClaw (SQLite snapshot restore lacks crash/identity guarantees #113306), NanoClaw (agent mailbox seam/registry #3349).</li>
<li><strong>Security hardening</strong> — Moltis (CWE-306 unauthenticated vault unlock/recovery, fixed #1216), OpenClaw (install-policy warning acknowledgement), ZeroClaw (shell-child confinement escape PR #9827; SOP permission contract RFC #9598), CoPaw (SSRF/bounded-download protections for remote media #7146).</li>
<li><strong>Tool/context limit configurability</strong> — ZeroClaw (fixed 50K-char tool-result truncation cluster #10114–10116), NanoBot (prompt-token estimation undercounts by 30–50%, #5403), OpenClaw (<code>contextPruning cache-ttl</code> never fires on OpenAI #95840), CoPaw (hardcoded 5s embedding health-check timeout #7156).</li>
</ol>
<hr>
<h2>5. Differentiation Analysis</h2>
<table>
<thead>
<tr>
<th>Project</th>
<th>Primary Target User</th>
<th>Architectural Distinction</th>
<th>Feature Focus</th>
</tr>
</thead>
<tbody><tr>
<td>OpenClaw</td>
<td>Power users / production operators</td>
<td>Self-hosted gateway + Control UI + skills; largest channel matrix</td>
<td>Breadth, model-path correctness, delivery reliability</td>
</tr>
<tr>
<td>NanoBot (HKUDS)</td>
<td>TUI/WebUI hobbyists, autonomous-agent operators</td>
<td>Lightweight Python, Herdr-hosted panes, Dream memory cron</td>
<td>TUI polish, memory compaction, monetized-agent experiments</td>
</tr>
<tr>
<td>ZeroClaw</td>
<td>Developers wanting a lean core</td>
<td>RFC-driven modularization; SOP process orchestration; goal mode</td>
<td>Security confinement, install reliability, governance reform</td>
</tr>
<tr>
<td>PicoClaw (Sipeed)</td>
<td>Embedded/low-footprint users</td>
<td>Minimal binary (Sipeed vendor), Telegram/LINE channels</td>
<td>Telegram UX, honest config warnings, routed-agent memory</td>
</tr>
<tr>
<td>NanoClaw</td>
<td>Node.js/TypeScript developers, Slack-first teams</td>
<td>Node/TS stack, <code>better-sqlite3</code>, provisioning/approval flows</td>
<td>Slack agents (gated install), SMS/voice (Dial), setup robustness</td>
</tr>
<tr>
<td>IronClaw (Near)</td>
<td>Multi-tenant enterprise/platform teams</td>
<td>Durable inbox contracts, per-user sandboxes, capability normalization</td>
<td>Notifications, CI discipline, upgrade safety</td>
</tr>
<tr>
<td>LobsterAI (NetEase Youdao)</td>
<td>Chinese desktop users</td>
<td>Desktop GUI clients, Windows/mac installers, engine overlay</td>
<td>Agent-settings UX, Windows distribution hardening</td>
</tr>
<tr>
<td>Moltis</td>
<td>Privacy/security-sensitive small deployments</td>
<td>Minimal, security-first HTTP layer</td>
<td>Vault auth, WhatsApp group correctness, tool-policy configurability</td>
</tr>
<tr>
<td>CoPaw (agentscope)</td>
<td>Chinese-language agent developers</td>
<td>Qwen/agentscope stack, ReMe memory, computer-use</td>
<td>Skill CLI, Chinese filename preservation, self-hosted Hub, marketplace</td>
</tr>
<tr>
<td>EasyClaw</td>
<td>E-commerce affiliate operators (TK Copilot)</td>
<td>Closed-loop release model, no public issue surface</td>
<td>Feishu integration, Gateway recovery, Affiliate workflows</td>
</tr>
</tbody></table>
<hr>
<h2>6. Community Momentum &amp; Maturity</h2>
<p><strong>Tier 1 — High-velocity, rapidly iterating:</strong></p>
<ul>
<li><strong>NanoClaw</strong> (23 PRs merged, core-team same-day bugfixes), <strong>CoPaw</strong> (26 merged, 16 issues closed, 8 straight red E2E runs unbroken), <strong>IronClaw</strong> (18 merged plus a stable v1.3.0 release). These three show the healthiest merge-to-open ratios and direct issue→PR closure patterns.</li>
</ul>
<p><strong>Tier 2 — Steady with structural constraints:</strong></p>
<ul>
<li><strong>OpenClaw</strong> — massive throughput but stabilize-in-place: 72 merges against 428 open PRs, two P0s, and maintainer review explicitly named as the bottleneck.</li>
<li><strong>NanoBot</strong> — meaningful feature merges (TUI, memory perf, <code>ask_clarification</code>) but a growing conflict pile blocks P0/P1 stability work.</li>
<li><strong>ZeroClaw</strong> — high PR volume with a dedicated v0.8.5 stabilization tracker, yet RFC decision queues and <code>waiting-on-author</code> PRs throttle progress.</li>
<li><strong>Moltis</strong> — small but exemplary: zero open items at end of day, security issue closed by same-day fix.</li>
<li><strong>EasyClaw</strong> — shipping rapidly (3 releases) but entirely release-driven with no observable community feedback loop.</li>
</ul>
<p><strong>Tier 3 — Low/dormant:</strong></p>
<ul>
<li><strong>PicoClaw</strong> (stale PRs, one fix after a 5-month issue lifecycle), <strong>LobsterAI</strong> (stale-sweep masquerading as progress — 6 of 8 closed PRs were unmerged April-era items), <strong>NullClaw/TinyClaw/ZeptoClaw</strong> (one open PR or zero activity).</li>
</ul>
<p><strong>Maturity signals:</strong> OpenClaw and ZeroClaw are in stabilization/governance phases typical of post-growth projects; IronClaw and Moltis demonstrate the cleanest release discipline; CoPaw and NanoClaw are in active expansion with frictional edges (CI, install paths) that indicate scaling pains.</p>
<hr>
<h2>7. Trend Signals</h2>
<ol>
<li><strong>Upgrade reliability is now a product requirement, not a bug category.</strong> Operators blocked by OpenClaw&#39;s 2026.7.1 startup failure, IronClaw&#39;s 1.2→1.3 crash-loop, and NanoClaw&#39;s Node 26 build break reveal a systemic gap: version checks validate lower bounds, not dependency matrices. Expect demand for upgrade-testing matrices, backport policies, and rollback guarantees.</li>
<li><strong>Monetized and unattended autonomous operation is emerging.</strong> NanoBot&#39;s paid x402/ScanPay MCP proposal and EasyClaw&#39;s affiliate-automation business model signal a shift from personal-assistant to revenue-generating-agent deployments, which will drive demands for billing, audit trails, and payment-provider abstractions.</li>
<li><strong>Memory is becoming a first-class subsystem with integrity guarantees.</strong> NanoBot&#39;s Dream cursor corruption, CoPaw&#39;s ReMe/Scroll gaps, OpenClaw&#39;s snapshot-restore identity issues, and ZeroClaw&#39;s truncation design flaws all point to the same need: memory pipelines need transactional semantics, idempotent cursors, and configurable token accounting — not heuristic compaction.</li>
<li><strong>Multi-agent/subagent delivery accounting remains unsolved.</strong> Wrong-output, no-output, and duplicated-output bugs recur across OpenClaw (#90944, #80498), IronClaw (run outcomes), and NanoClaw (agent mailbox seam). HTTP-driven and cross-agent delivery targets are actively being designed (OpenClaw PR #126501).</li>
<li><strong>Local/on-device tooling is a rising constraint.</strong> IronClaw&#39;s 40-day-old loopback-MCP blocker (#5998) finally received a fix PR; OpenClaw&#39;s memory status and ZeroClaw&#39;s proxy selectors show similar on-device integration friction. Developers want local MCP, local models, and offline-capable agents.</li>
<li><strong>Security posture is shifting from access control to supply-chain and install-time safety.</strong> OpenClaw&#39;s install-policy acknowledgement, ZeroClaw&#39;s confinement-escape fix, Moltis&#39;s vault CWE-306, and CoPaw&#39;s SSRF protections indicate hardening across the install→runtime→tool-execution chain.</li>
<li><strong>For AI agent developers, the actionable takeaways:</strong> (a) treat install-time and upgrade-time paths as first-class CI citizens (headless, non-login shell, Docker non-root, Node/OS matrix); (b) make delivery status observable and retryable rather than optimistic; (c) design memory and session state with crash-safe, idempotent write patterns; (d) expect maintainer-review latency in the largest projects and prefer projects with demonstrated issue→PR→merge closure rates (IronClaw, Moltis, CoPaw, NanoClaw) for time-sensitive contributions.</li>
</ol>
<hr>
<h2>Peer Project Reports</h2>
<details>
<summary><strong>NanoBot</strong> — <a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a></summary>

<h2>1. Today&#39;s Overview</h2>
<p>NanoBot shows steady, healthy activity on 2026-08-20: 3 issues were updated (all still open) and 20 pull requests received updates, with 7 PRs merged or closed. The closing of 7 PRs today — spanning TUI/UX improvements, WebUI shutdown behavior, memory compaction performance, and a new <code>ask_clarification</code> tool — indicates active feature work progressing through review. The open-PR queue (13 items) includes several high-priority fixes (P0/P1) that are marked as having conflicts, suggesting maintainer attention is needed to land critical stability work. No new releases were published today. Overall, the project is in a productive phase with a meaningful volume of merged work, though the backlog of conflicting high-severity PRs is a growing risk.</p>
<h2>2. Releases</h2>
<p>No new releases were published in the last 24 hours.</p>
<h2>3. Project Progress</h2>
<p>Seven PRs were merged or closed today:</p>
<ul>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5449">#5449 — fix(tui): keep navigation commands in Herdr panes</a></strong> (closed): Preserves native TUI conversation navigation (<code>/sessions</code>, <code>/new-chat</code>, <code>/branch</code>) inside Herdr-hosted panes, clarifying that Herdr owns terminal topology while nanobot owns sessions/chats/branches.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5448">#5448 — feat(tui): start fresh chats in launch workspace</a></strong> (closed): TUI launches now start in a fresh WebSocket session using the command launch directory as the initial workspace, while preserving explicit <code>--session</code>/<code>--workspace</code> overrides; removes obsolete last-session persistence.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5443">#5443 — fix(tui): expose /exit in command menu</a></strong> (closed): Makes the existing <code>/exit</code> behavior discoverable via the slash-command menu, completion, and discovery, routing through the existing local shutdown path.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5440">#5440 — perf(memory): reuse conversation prefix for local compaction</a></strong> (closed): Builds idle/token-overflow/<code>/new</code> consolidation requests from the ordinary model-facing prefix and appends a temporary instruction, preserving structured tool calls while disabling tool execution.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5438">#5438 — fix(webui): return promptly after Ctrl-C</a></strong> (closed): Fixes slow WebUI shutdown by releasing client leases with <code>wait_for_stop=False</code> on both foreground exit paths and leaving on-demand gateway shutdown to the monitor.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5341">#5341 — fix(skills): make weather workflow Windows-safe</a></strong> (closed): Replaces bare <code>curl</code> in the weather skill example to avoid PowerShell&#39;s <code>Invoke-WebRequest</code> alias, preventing first-command failures on Windows.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/4527">#4527 — Add ask_clarification tool</a></strong> (closed): Adds a built-in <code>ask_clarification</code> tool with focused question/type/context/options parameters, short-circuits agent turns when clarification is requested, and renders results correctly in the WebUI.</li>
</ul>
<h2>4. Community Hot Topics</h2>
<p>Comment/reaction activity is currently low (0 comments across all items), but several threads stand out by priority, age, or novelty:</p>
<ul>
<li><strong><a href="https://github.com/HKUDS/nanobot/issues/5447">Issue #5447 — Paid security-scan MCP integration (nanobot + ScanPay x402)</a></strong>: A user operating an &quot;autonomous agent revenue stack&quot; proposes integrating nanobot with ScanPay (a Solana x402 micropayment security scanner at 0.0007 SOL per scan) and an AgentBridge job system. This is a novel commercial/monetized-agent use case and the most notable new feature request today.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5271">PR #5271 — fix(session): prevent stale background task saves (priority: p0, conflict)</a></strong>: The only P0 item in the queue. It addresses stale background work overwriting sessions after <code>/new</code>; despite its severity, it is marked with conflicts and has been open since 2026-08-06.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/4853">PR #4853 — feat(tools): add nano_timer core tool (priority: p1, conflict)</a></strong>: Open since 2026-07-08, this dependency-free time/timezone/calendar tool remains the longest-pending P1 feature and is blocked on conflicts.</li>
</ul>
<p>Underlying needs: users are pushing nanobot toward (a) monetizable autonomous operation (paid MCP/x402 scanning), (b) reliable background/state handling for long-running agents, and (c) better time-aware tooling.</p>
<h2>5. Bugs &amp; Stability</h2>
<p>Two new bugs were reported in the last 24 hours, both with fix PRs already in the queue:</p>
<ul>
<li><strong><a href="https://github.com/HKUDS/nanobot/issues/5444">Issue #5444 — Failed to login OpenAI via OAuth in Docker</a></strong> (new): OAuth login flow fails inside Docker — the redirect callback is served but token exchange breaks. Two fix PRs target the same root cause (OAauth token storage writing to unmanaged paths that are read-only after dropping to the non-root user): <a href="https://github.com/HKUDS/nanobot/pull/5446">#5446 — route OpenAI Codex OAuth storage through nanobot&#39;s data dir</a> and <a href="https://github.com/HKUDS/nanobot/pull/5445">#5445 — fix(docker): persist OAuth client data</a>. Note: PR #5446&#39;s summary explicitly references the <code>PermissionError</code> on <code>/home/...</code> in Docker, confirming a permission issue rather than a protocol issue.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/issues/5441">Issue #5441 — Dream: recovered tool error permanently blocks the memory cursor</a></strong> (new): A Dream run that successfully commits memory edits can still be rejected as &quot;did not complete&quot; if any tool event errored, leaving <code>memory/.dream_cursor</code> stale. Subsequent runs then reprocess the same history batch, duplicating edits. <a href="https://github.com/HKUDS/nanobot/pull/5442">Fix PR #5442</a> advances the cursor when tool errors were recovered and reports why a run didn&#39;t complete.</li>
</ul>
<p>Pre-existing stability fixes still awaiting merge (all open with conflicts): <a href="https://github.com/HKUDS/nanobot/pull/5271">#5271 (P0, stale background task saves)</a>, <a href="https://github.com/HKUDS/nanobot/pull/5403">#5403 (P1, incorrect prompt-token estimation prevents memory consolidation)</a>, <a href="https://github.com/HKUDS/nanobot/pull/5379">#5379 (memory consolidation truncation is lossy)</a>, and <a href="https://github.com/HKUDS/nanobot/pull/5257">#5257 (sustained-goal continuation loops when turn goes idle)</a>.</p>
<h2>6. Feature Requests &amp; Roadmap Signals</h2>
<ul>
<li><strong><a href="https://github.com/HKUDS/nanobot/issues/5447">Issue #5447 — Paid security-scan MCP integration</a></strong>: Requests enabling nanobot to consume paid MCP/x402 services (Solana micropayments per scan). If accepted, this could land as an MCP-client payment extension in a future release, though it likely requires architecture discussion for crypto payment support.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5420">PR #5420 — feat(webui): turn observability and safe recovery</a></strong> (open): Projects each turn into one answer surface with ordered reasoning/tool activity, accumulated provider usage, and explicit interrupted-work recovery.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5408">PR #5408 — feat(webui): follow-up suggestions</a></strong> (open): Ephemeral, chat-scoped follow-up suggestions after successful WebUI turns, with a strict provider-neutral line protocol (DeerFlow-style composer behavior).</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5405">PR #5405 — feat(skills): manual-only invocation</a></strong> (open): Adds <code>disable-model-invocation: true</code> frontmatter so side-effectful skills (deploy/publish) are user-only.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/4853">PR #4853 — nano_timer core tool</a></strong> (open, P1): UTC/local time, timezone, and calendar fields as a dependency-free core tool.</li>
</ul>
<p>Near-term release prediction: the WebUI UX cluster (turn observability + follow-up suggestions) plus the TUI polish PRs merged today suggest the next release will focus on interface usability. The P0/P1 memory and session safety fixes are likely to be prioritized for inclusion once conflicts are resolved, since they address data-corruption and context-window risks.</p>
<h2>7. User Feedback Summary</h2>
<ul>
<li><strong>Docker OAuth pain point (<a href="https://github.com/HKUDS/nanobot/issues/5444">#5444</a>)</strong>: The non-root user model in the Docker image breaks OAuth login because credential writes go to unmanaged platformdirs; users cannot log in to OpenAI at all in containers. Two independent contributors submitted fixes, signaling real friction.</li>
<li><strong>Memory corruption risk in Dream (<a href="https://github.com/HKUDS/nanobot/issues/5441">#5441</a>)</strong>: A rejected-but-committed Dream run causes repeated duplicate edits on every subsequent run. This is a data-integrity problem that erodes user trust in autonomous memory features; the author of the issue also submitted the fix PR, indicating a motivated user-contributor base.</li>
<li><strong>Monetization intent (<a href="https://github.com/HKUDS/nanobot/issues/5447">#5447</a>)</strong>: Users are operating autonomous agent revenue stacks and want nanobot to interoperate with paid security-scanning services — a signal that the project is being adopted in production/commercial settings, not just personal assistant use.</li>
</ul>
<p>Overall, users are relying on nanobot for long-running, unattended operation (Dream cron, background tasks, sustained goals), and the reported bugs cluster around exactly those production concerns: state persistence, OAuth/reliability in Docker, and idempotent memory handling.</p>
<h2>8. Backlog Watch</h2>
<p>Items needing maintainer attention, ranked by priority and age:</p>
<ul>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5271">PR #5271 — fix(session): prevent stale background task saves (P0, conflict)</a></strong>: Open since 2026-08-06; highest-severity PR in queue but marked with conflicts. Should be resolved and merged first.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/4853">PR #4853 — feat(tools): add nano_timer core tool (P1, conflict)</a></strong>: Open since 2026-07-08 — the oldest open PR. Conflict status is blocking a long-awaited dependency-free time tool.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5403">PR #5403 — fix(memory): use API-reported prompt tokens (P1, conflict)</a></strong>: Fixes context-window overflow because local tiktoken estimation undercounts by 30–50%; consolidation never triggers. References issue #5402.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5379">PR #5379 — fix(memory): preserve full consolidation input</a></strong>: Lossless bounded chunks replacing lossy truncation; complements #5403.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/pull/5405">PR #5405 — feat(skills): support manual-only invocation</a></strong>: Conflicting and open since 2026-08-16; important for safe deployment/publish skills.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot/issues/5447">Issue #5447 — Paid security-scan MCP integration</a></strong>: No maintainer response yet; a first-response/design-guidance comment would help set expectations for this forward-looking request.</li>
</ul>
</details>

<details>
<summary><strong>Zeroclaw</strong> — <a href="https://github.com/zeroclaw-labs/zeroclaw">zeroclaw-labs/zeroclaw</a></summary>

<h2>1. Today&#39;s Overview</h2>
<p>ZeroClaw logged heavy activity on 2026-08-20: 26 issues were updated (25 open, 1 closed) and 50 PRs were touched (43 open, 7 merged/closed), with no release shipped. The project remains in a high-throughput stabilization and review cycle, with several large, high-risk PRs (security confinement, Anthropic OAuth, channel authorization) waiting on maintainer or author action. New bug clusters emerged around deterministic tool-result truncation, plugin-install recoverability, and a flaky parallel-runtime test, while the v0.8.5 stabilization tracker keeps the release line pointed at August 30. The volume of <code>needs-maintainer-review</code> RFCs and a dedicated maintainer decision queue indicate review throughput is the current bottleneck.</p>
<h2>2. Releases</h2>
<p>No new releases in this window. The last shipped baseline remains v0.8.4; the v0.8.5 finite weekly stabilization line is tracked in <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9459">Issue #9459</a>.</p>
<h2>3. Project Progress</h2>
<p>Seven PRs were merged or closed in the last 24 hours (the specific PRs are not named in the top-20 active sample). The one visible closure is <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9470">Issue #9470</a>, the accepted task to correct Reliable fallback telemetry attribution and stale fallback notices, marking that observability fix complete.</p>
<p>Substantial open PRs continued advancing through review:</p>
<ul>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9126">PR #9126</a> — plugin typed instance-config validation (large, high-risk, core/agent/runtime).</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9827">PR #9827</a> — stops shell children escaping validated confinement across sandbox backends (large, p1).</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9428">PR #9428</a> — sender authorization for Bluesky and Reddit inbound channels (p1, XL).</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9378">PR #9378</a> — persists failed/cancelled ACP turn transcripts, the fix for the S1 transcript-loss bug.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10163">PR #10163</a> — anchors the flaky <code>process_stats</code> rapid-resample test to its timing premise.</li>
</ul>
<h2>4. Community Hot Topics</h2>
<ul>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/6165">Issue #6165</a> — <em>RFC: Prefer a lighter ZeroClaw core through external integrations</em> (17 comments, risk:high, needs-maintainer-review). The longest-running architecture debate; underlying need is reducing core configuration/surface area by moving long-tail integrations out-of-tree.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8692">Issue #8692</a> — <em>Maintainer decision queue for RFCs and design issues</em> (13 comments). A governance signal that RFC and design decisions are piling up faster than maintainers can dispose of them.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9598">Issue #9598</a> — <em>RFC: Define the SOP capability permission contract</em> (8 comments, risk:high). Seeking final authority for <code>required_permissions</code> in SOP; a v0.9.0 target.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8586">Issue #8586</a> — <em>refactor(gateway): centralize webhook channel message dispatch</em> (7 comments, in-progress). Community interest in consolidating webhook ingress lifecycle.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/7911">Issue #7911</a> — <em>install.sh selects a generic Linux binary on Android/Termux</em> (4 comments). Real install pain for Android users, now with a docs clarification PR (<a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10160">PR #10160</a>).</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9702">Issue #9702</a> — <em>RFC: Goal mode v2 — durable continuation and paired Web controls</em> (4 comments, risk:high).</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9990">Issue #9990</a> — <em>RFC: Calibrate PR risk and security approval requirements</em> (4 comments, risk:high).</li>
</ul>
<h2>5. Bugs &amp; Stability</h2>
<p>Newly surfaced (created/updated within the window):</p>
<ul>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10114">Issue #10114</a>, <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10115">Issue #10115</a>, <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10116">Issue #10116</a> — a related S2 cluster on tool-result truncation: a fixed 50,000-character cap unrelated to the model context window, invisible truncation outside the model&#39;s context, and byte-wise middle-out cutting instead of spilling to a file handle. No fix PR yet; the cluster suggests the <code>results_collect.rs</code> truncation path needs a design change.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10162">Issue #10162</a> — <code>plugin install</code> persists the package before config-entry seeding and cannot retry the seed phase, leaving partially installed plugins.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10161">Issue #10161</a> — <code>process_stats</code> rapid-resample test flakes under the Parallel Runtime Test gate; <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10163">PR #10163</a> fixes the test.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10111">Issue #10111</a> — new user report of the Windows <code>TaskDialogIndirect</code> entry-point failure, duplicating <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9290">Issue #9290</a>.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10106">Issue #10106</a> — exact proxy selectors reject supported transcription services (<code>groq</code>, <code>openai</code>, <code>deepgram</code>, etc.).</li>
</ul>
<p>Active high-severity bugs:</p>
<ul>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9333">Issue #9333</a> (S1) — failed ACP turns disappear after switching sessions; fix PR <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9378">PR #9378</a> is open but needs author action.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9290">Issue #9290</a> (S1) — Windows desktop installer fails at launch with missing <code>TaskDialogIndirect</code>; awaiting a fix.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10042">Issue #10042</a> (S1, CI) — MSRV system dependency installation can consume the full job timeout.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9929">Issue #9929</a> (S2, p1, blocked) — headless SOP step turns get a session path but are never persisted.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9436">Issue #9436</a> (S2, p1) — <code>config init</code> writes template sections that fail the strict loader; still reproduces on <code>master</code>.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10089">Issue #10089</a> — ZeroCode ignores terminal-native bracketed paste while an agent turn is running.</li>
</ul>
<h2>6. Feature Requests &amp; Roadmap Signals</h2>
<ul>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/6165">Issue #6165</a> — lighter core via external integrations is the strongest architectural signal; likely to shape post-v0.8.5 modularization.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9702">Issue #9702</a> — Goal mode v2 with durable continuation and paired browser controls; a v0.9.0-era candidate alongside the SOP contract.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9598">Issue #9598</a> — SOP capability permission contract, explicitly targeting v0.9.0.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9990">Issue #9990</a> — calibrating PR risk/security approval requirements, a process RFC that would change contributor friction.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10041">Issue #10041</a> — isolated, non-attesting Blacksmith debugging lane for CI.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10159">Issue #10159</a> — verify pinned release tools on native runners before the next release.</li>
<li>The <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9459">v0.8.5 tracker</a> shows weekly release cuts through August 30; the webhook dispatch centralization (<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8586">#8586</a>) and Reliable telemetry corrections are the most likely candidates for the next cut.</li>
</ul>
<h2>7. User Feedback Summary</h2>
<ul>
<li><strong>Windows installation is the loudest pain point</strong>: two reports (<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9290">#9290</a>, <a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10111">#10111</a>) of the desktop app failing instantly with a missing <code>TaskDialogIndirect</code> entry point; the v0.8.3 installer is affected and this remains unresolved for users.</li>
<li><strong>Android/Termux users</strong> (<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/7911">#7911</a>) get a generic Linux binary instead of a usable Android build; docs are being updated, but the underlying packaging gap remains.</li>
<li><strong>Onboarding degradation</strong> (<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9436">#9436</a>): fresh installs start with a degraded config and <code>config migrate</code> exits 1 — a poor first-run experience still reproducible on master.</li>
<li><strong>ZeroCode TUI users</strong> (<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/10089">#10089</a>) lose paste functionality during agent turns, interrupting real workflows.</li>
<li>Maintainers and contributors are signaling process fatigue: the RFC decision queue (<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8692">#8692</a>), the risk-calibration RFC (<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9990">#9990</a>), and the lighter-core proposal (<a href="https://github.com/zeroclaw-labs/zeroclaw/issues/6165">#6165</a>) all reflect a desire for lower governance overhead and a smaller core.</li>
</ul>
<h2>8. Backlog Watch</h2>
<ul>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/6165">Issue #6165</a> — open since April 27, 17 comments, <code>needs-maintainer-review</code>, risk:high. The longest-pending architecture decision in the queue.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/8692">Issue #8692</a> — the maintainer decision tracker itself is accumulating unresolved RFCs; acceptance/rejection throughput is the constraint.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9451">PR #9451</a> — DORA telemetry retirement, <code>do-not-merge</code>, open since July 27, awaiting maintainer review.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9419">PR #9419</a> and <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9420">PR #9420</a> — credential rotation and Anthropic OAuth support, both large, high-risk, <code>do-not-merge</code>, open since July 26.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10035">PR #10035</a> — heartbeat MCP child symlink fixture test, <code>do-not-merge</code>, small but stalled.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9427">PR #9427</a> — LINE group authorization, <code>stale-candidate</code>, blocked on its dependency <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9428">#9428</a>.</li>
<li>PRs waiting on author action: <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/10034">PR #10034</a>, <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9428">PR #9428</a>, <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9433">PR #9433</a>, <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9378">PR #9378</a>, <a href="https://github.com/zeroclaw-labs/zeroclaw/pull/9827">PR #9827</a> — several are p1 security or data-loss fixes whose review progress is blocked on author responses.</li>
<li><a href="https://github.com/zeroclaw-labs/zeroclaw/issues/9929">Issue #9929</a> — headless SOP persistence bug is accepted but <code>blocked</code>, with no fix PR attached.</li>
</ul>
</details>

<details>
<summary><strong>PicoClaw</strong> — <a href="https://github.com/sipeed/picoclaw">sipeed/picoclaw</a></summary>

<h1>PicoClaw Project Digest — 2026-08-20</h1>
<h2>1. Today&#39;s Overview</h2>
<p>PicoClaw saw moderate activity over the last 24 hours: 1 issue was closed, and 5 pull requests were touched, of which 2 were closed/merged and 3 remain open. No new releases were published. The closed issue (#1305) resolves a longstanding bug from March where a startup banner polluted STDOUT and broke shell completion generation. Feature work is progressing on the Telegram channel (interactive command UX, topic support) and model fallback configuration, though three PRs are flagged as stale and need maintainer review. Overall project health is stable, with active bug triage but a slightly aging open-PR queue.</p>
<h2>2. Releases</h2>
<p>No new releases were published in the reporting window.</p>
<h2>3. Project Progress</h2>
<p>Two PRs were closed/merged today:</p>
<ul>
<li><strong><a href="https://github.com/sipeed/picoclaw/pull/3341">#3341 — feat(telegram): add interactive command UX and formatted ephemeral fallback</a></strong> (As-tsaqib) — Overhauls the Telegram command experience by removing the need for full CLI-style subcommand grammar (e.g. for <code>/memory</code>), simplifies the verbose <code>/help</code> output, and adds formatted ephemeral fallback for structured content.</li>
<li><strong><a href="https://github.com/sipeed/picoclaw/pull/3200">#3200 — feat(models): add configurable default fallback chain</a></strong> (lc6464) — Introduces a dedicated default-chain workflow on the web UI&#39;s models page, letting users set a default model, add/reorder fallback models, and persist the chain via the backend API. This PR was stale (open since July 1) before being closed.</li>
</ul>
<p>Three PRs remain open and actively updated:</p>
<ul>
<li><strong><a href="https://github.com/sipeed/picoclaw/pull/3329">#3329 — fix(line): warn on inert webhook_host / webhook_port instead of seeding them</a></strong> — Fixes misleading LINE channel configuration.</li>
<li><strong><a href="https://github.com/sipeed/picoclaw/pull/3316">#3316 — fix: routed-agent context management</a></strong> — Addresses routed agents losing conversation history.</li>
<li><strong><a href="https://github.com/sipeed/picoclaw/pull/3315">#3315 — Support topics in private bot chats</a></strong> — Fixes Telegram topic handling for private chats.</li>
</ul>
<h2>4. Community Hot Topics</h2>
<p>The most active item was <strong><a href="https://github.com/sipeed/picoclaw/issues/1305">Issue #1305 — [BUG] new banner print to STDOUT, break completion flow</a></strong> (4 comments, closed) — Reported in March, it documents how the banner introduced by PR #1008 corrupts <code>picoclaw completion zsh</code> output, breaking shell completion scripts. The long lifecycle (March → August) suggests the fix took months to land.</p>
<p><strong><a href="https://github.com/sipeed/picoclaw/pull/3329">PR #3329 — warn on inert webhook_host / webhook_port</a></strong> addresses the closely related underlying need: users want configuration fields to either work or produce clear warnings rather than silently doing nothing. The PR argues that <code>line.settings.webhook_host</code>/<code>webhook_port</code> are declared, defaulted, and env-bound but never read, since the LINE channel mounts <code>WebhookPath()</code> on the shared gateway server. This reflects broader community demand for honest, observable configuration behavior.</p>
<h2>5. Bugs &amp; Stability</h2>
<ul>
<li><strong>High — Routed-agent context loss (<a href="https://github.com/sipeed/picoclaw/pull/3316">PR #3316</a>)</strong>: Routed agents in Discord channels do not remember previous messages; history, summarization, compression, and seahorse bootstrap are not respected, and auto-compaction never triggers. Open PR exists; fix still pending. </li>
<li><strong>Medium — Banner breaks shell completion (<a href="https://github.com/sipeed/picoclaw/issues/1305">Issue #1305</a>)</strong>: STDOUT banner output corrupts generated completion scripts. Fixed and closed today.</li>
<li><strong>Medium — Inert LINE webhook settings (<a href="https://github.com/sipeed/picoclaw/pull/3329">PR #3329</a>, fixes #3328)</strong>: <code>webhook_host</code>/<code>webhook_port</code> are seeded and env-bound but never read, giving users a false sense of configuration. Fix PR open; not yet merged.</li>
</ul>
<h2>6. Feature Requests &amp; Roadmap Signals</h2>
<p>The following feature signals are likely candidates for the next release:</p>
<ul>
<li><strong>Telegram interactive command UX (<a href="https://github.com/sipeed/picoclaw/pull/3341">PR #3341</a>)</strong>: Closed today — a strong signal this lands next, reducing CLI-style friction for <code>/memory</code> and streamlining <code>/help</code>.</li>
<li><strong>Telegram topics in private bot chats (<a href="https://github.com/sipeed/picoclaw/pull/3315">PR #3315</a>)</strong>: Extends topic support beyond forum supergroups to private chats via <code>IsTopicMessage</code>; complements the Telegram UX work.</li>
<li><strong>Configurable default model fallback chain (<a href="https://github.com/sipeed/picoclaw/pull/3200">PR #3200</a>)</strong>: Web UI-driven fallback model ordering, closed today — likely in the next version given its web-facing scope.</li>
</ul>
<h2>7. User Feedback Summary</h2>
<ul>
<li><strong>Scripting needs clean stdout</strong>: The banner bug (#1305) shows users rely on PicoClaw emitting machine-readable output (completion scripts), and any stray STDOUT text is a breaking regression.</li>
<li><strong>Telegram UX friction</strong>: Users find full subcommand grammar for <code>/memory</code> cognitively heavy and <code>/help</code> output overly verbose; the community response is a push toward interactive, formatted commands.</li>
<li><strong>Context loss in routed agents</strong>: A real user pain point — dispatch-rule configurations result in amnesiac agents and no auto-compaction, degrading long-running conversations.</li>
<li><strong>Config transparency</strong>: Users dislike settings that silently do nothing (LINE <code>webhook_host</code>/<code>webhook_port</code>); the preferred behavior is an explicit warning over silent seeding.</li>
</ul>
<h2>8. Backlog Watch</h2>
<ul>
<li><strong><a href="https://github.com/sipeed/picoclaw/pull/3316">PR #3316 — routed-agent context management</a></strong>: Open since 2026-08-03, flagged <code>[stale]</code>; addresses a high-impact memory bug and needs maintainer attention.</li>
<li><strong><a href="https://github.com/sipeed/picoclaw/pull/3315">PR #3315 — Telegram topics in private chats</a></strong>: Open since 2026-08-03, flagged <code>[stale]</code>; a focused, low-risk fix that has not received review.</li>
<li><strong><a href="https://github.com/sipeed/picoclaw/pull/3329">PR #3329 — LINE webhook config warning</a></strong>: Open since 2026-08-11, no comment activity; pending merge for an issue-fixing change.</li>
<li><strong><a href="https://github.com/sipeed/picoclaw/pull/3200">PR #3200 — model fallback chain</a></strong>: Open since 2026-07-01, flagged <code>[stale]</code> before being closed today; worth confirming it was merged rather than abandoned.</li>
</ul>
</details>

<details>
<summary><strong>NanoClaw</strong> — <a href="https://github.com/qwibitai/nanoclaw">qwibitai/nanoclaw</a></summary>

<h1>NanoClaw Project Digest — 2026-08-20</h1>
<h2>1. Today&#39;s Overview</h2>
<p>NanoClaw saw a high-activity day: 33 PRs updated in the last 24 hours, with 23 merged or closed and 10 still open. Three new issues were filed, all centered on setup robustness and SMS delivery accuracy. The core team landed a significant reorganization of the Slack channel (base adapter vs. agents feature), several provisioning/approvals hardening fixes, and a Telegram group picker. No new releases were published. Overall project health looks strong, with the main risk集中于 install-time failures on current Node runtimes and headless environments.</p>
<h2>2. Releases</h2>
<p>No new releases in the last 24 hours.</p>
<h2>3. Project Progress</h2>
<p>Merged/closed PRs advanced several areas:</p>
<ul>
<li><strong>Slack architecture split</strong> — <a href="https://github.com/nanocoai/nanoclaw/pull/3358">#3358</a> splits the payload: <code>/add-slack</code> now ships the base adapter only, while the agents feature lives in <code>/slack-agent-flow</code>; companion <a href="https://github.com/nanocoai/nanoclaw/pull/3357">#3357</a> makes <code>--slack-agents</code> install the full agents feature (child bots, a2a rooms, canvases, DM onboarding).</li>
<li><strong>Slack invite handling</strong> — <a href="https://github.com/nanocoai/nanoclaw/pull/3342">#3342</a> declines owner-absent channel invites instead of escalating them as approve/reject cards.</li>
<li><strong>Provisioning &amp; approvals</strong> — <a href="https://github.com/nanocoai/nanoclaw/pull/3340">#3340</a> records the delivering instance on <code>pending_approvals</code>; <a href="https://github.com/nanocoai/nanoclaw/pull/3344">#3344</a> adds optional request-origin metadata on app creation; <a href="https://github.com/nanocoai/nanoclaw/pull/3345">#3345</a> forwards client version metadata on Slack service requests.</li>
<li><strong>Bug fixes</strong> — <a href="https://github.com/nanocoai/nanoclaw/pull/3339">#3339</a> fails closed when a stored sign-in can&#39;t be verified; <a href="https://github.com/nanocoai/nanoclaw/pull/3341">#3341</a> derives the Slack service from the credential&#39;s issuer; <a href="https://github.com/nanocoai/nanoclaw/pull/3025">#3025</a> raises the agent SDK&#39;s 32,000 output-token cap.</li>
<li><strong>Telegram</strong> — <a href="https://github.com/nanocoai/nanoclaw/pull/3351">#3351</a> adds an approved group connection picker via <code>/connect_group</code>.</li>
</ul>
<p>Still open and moving: Cursor Agent SDK provider with <code>/add-cursor</code> setup skill (<a href="https://github.com/nanocoai/nanoclaw/pull/3356">#3356</a>, <a href="https://github.com/nanocoai/nanoclaw/pull/3355">#3355</a>), agent mailbox seam and registry (<a href="https://github.com/nanocoai/nanoclaw/pull/3349">#3349</a>), and Node runtime support (<a href="https://github.com/nanocoai/nanoclaw/pull/3360">#3360</a>).</p>
<h2>4. Community Hot Topics</h2>
<p>Issue/PR discussion is minimal (all three new issues have 0 comments), but the most active topics by recent updates are:</p>
<ul>
<li><strong><a href="https://github.com/nanocoai/nanoclaw/issues/3359">#3359 — Node 26 passes check_node but better-sqlite3 11.10.0 cannot build</a></strong> — fresh macOS arm64 + Homebrew Node 26.7.0 aborts at bootstrap. Underlying need: Node version checks must validate against the dependency matrix, not just a lower bound.</li>
<li><strong><a href="https://github.com/nanocoai/nanoclaw/issues/3354">#3354 — 0-byte channel files and PATH-ordered onecli check on headless installs</a></strong> — setup assumes a login/interactive shell; fails on non-login SSH sessions. Underlying need: install must be robust in CI/headless contexts.</li>
<li><strong><a href="https://github.com/nanocoai/nanoclaw/issues/3353">#3353 — Dial outbound SMS recorded as delivered despite carrier rejection</a></strong> — delivery status is never revisited after carrier rejection, leaving <code>status = &#39;delivered&#39;</code> and untouched retry budgets.</li>
<li><strong>Long-running feature PRs</strong> — the Dial channel adapter and setup picker (<a href="https://github.com/nanocoai/nanoclaw/pull/3041">#3041</a>, <a href="https://github.com/nanocoai/nanoclaw/pull/3050">#3050</a>, open since July 14) and the CLI <code>--rw</code> flag for <code>groups config add-mount</code> (<a href="https://github.com/nanocoai/nanoclaw/pull/3149">#3149</a>, open since July 29) remain the most heavily awaited contributions.</li>
</ul>
<h2>5. Bugs &amp; Stability</h2>
<p>Three bugs were reported in the last 24 hours, ranked by severity:</p>
<ol>
<li><strong>High — <a href="https://github.com/nanocoai/nanoclaw/issues/3359">#3359</a>: Node 26 passes the version check but <code>better-sqlite3</code> can&#39;t compile.</strong> Blocks fresh installs on current Homebrew Node. Fix exists in open PR <a href="https://github.com/nanocoai/nanoclaw/pull/3360">#3360</a> (upgrade to better-sqlite3 13.0.3, raise host minimum from Node 20 to Node 22).</li>
<li><strong>Medium — <a href="https://github.com/nanocoai/nanoclaw/issues/3353">#3353</a>: Dial SMS falsely marked delivered.</strong> Carrier rejections after acceptance don&#39;t update the session row or retry budget. No fix PR yet.</li>
<li><strong>Medium — <a href="https://github.com/nanocoai/nanoclaw/issues/3354">#3354</a>: Setup leaves 0-byte channel files on failed <code>git show</code> copy; onecli check runs before its own PATH fix.</strong> Corrupts installs on non-login/headless machines. No dedicated fix PR yet; related setup-hardening PR <a href="https://github.com/nanocoai/nanoclaw/pull/3249">#3249</a> remains open.</li>
</ol>
<p>Also fixed today: <strong>#3339</strong> (unverifiable stored sign-in was treated as passed) and <strong>#3341</strong> (Slack install token and Slack service were configured independently and never paired).</p>
<h2>6. Feature Requests &amp; Roadmap Signals</h2>
<p>In-flight features point to a packed next release:</p>
<ul>
<li><strong>Cursor Agent SDK provider</strong> (<a href="https://github.com/nanocoai/nanoclaw/pull/3356">#3356</a>, <a href="https://github.com/nanocoai/nanoclaw/pull/3355">#3355</a>) — new provider support with setup skill.</li>
<li><strong>Agent mailbox seam and registry</strong> (<a href="https://github.com/nanocoai/nanoclaw/pull/3349">#3349</a>) — shared by NanoClaw and the agents it runs; SQLite remains the included implementation.</li>
<li><strong>Dial channel (SMS + AI voice calls)</strong> (<a href="https://github.com/nanocoai/nanoclaw/pull/3041">#3041</a>, <a href="https://github.com/nanocoai/nanoclaw/pull/3050">#3050</a>) — still pending; bug <a href="https://github.com/nanocoai/nanoclaw/issues/3353">#3353</a> will need to be addressed before it can be considered stable.</li>
<li><strong>Node 22 minimum + better-sqlite3 13</strong> (<a href="https://github.com/nanocoai/nanoclaw/pull/3360">#3360</a>) — a clear roadmap shift toward current runtimes and a resolution for #3359.</li>
<li><strong>Slack agents gated install</strong> (<a href="https://github.com/nanocoai/nanoclaw/pull/3357">#3357</a>) — merged; base Slack experience is now the default, with <code>--slack-agents</code> for the full feature set.</li>
</ul>
<p>Prediction: the next release will likely include the Node 22 baseline, the Slack agents split, the Cursor provider payload, and the Telegram group picker.</p>
<h2>7. User Feedback Summary</h2>
<p>Real user pain points this cycle come from <code>glifocat</code>, who hit setup failures on a fresh macOS arm64 machine and a clean headless box:</p>
<ul>
<li>The Node check&#39;s lower-bound-only logic gives false confidence on Node 26, then fails at native module compile time.</li>
<li>Setup assumes login shells: <code>~/.local/bin</code> missing from PATH breaks a pre-PATH onecli check, and <code>git show</code> failures leave 0-byte channel files without cleanup.</li>
<li>Dial users need delivery status to reflect actual carrier outcomes, including rejection handling and retry semantics.</li>
</ul>
<p>On the positive side, core-team fix velocity is high — multiple provisioning and Slack bugs were identified and merged the same day, indicating responsive maintenance and a project in active, healthy development.</p>
<h2>8. Backlog Watch</h2>
<p>Items needing maintainer attention:</p>
<ul>
<li><strong><a href="https://github.com/nanocoai/nanoclaw/pull/3149">#3149</a> — <code>--rw</code> flag for <code>groups config add-mount</code></strong> (open since 2026-07-29, ~3 weeks). Straightforward CLI fix awaiting review.</li>
<li><strong><a href="https://github.com/nanocoai/nanoclaw/pull/3041">#3041</a> and <a href="https://github.com/nanocoai/nanoclaw/pull/3050">#3050</a> — Dial channel adapter and setup picker</strong> (open since 2026-07-14, ~5 weeks). Large feature PRs that need maintainer review and now have a related bug (#3353) to reconcile.</li>
<li><strong><a href="https://github.com/nanocoai/nanoclaw/pull/3249">#3249</a> — handle existing Node outside the supported range</strong> (open since 2026-08-14). Directly relevant to #3359 and needs coordination with the Node-runtime PR #3360 to avoid conflicting changes.</li>
</ul>
</details>

<details>
<summary><strong>NullClaw</strong> — <a href="https://github.com/nullclaw/nullclaw">nullclaw/nullclaw</a></summary>

<h1>NullClaw Project Digest — 2026-08-20</h1>
<h2>1. Today&#39;s Overview</h2>
<p>Activity is minimal: no issues were updated in the last 24 hours and no releases were published. One pull request (#989) is open, addressing a broken star history chart in the README, with no merges or closures recorded today. The project appears to be in a low-maintenance phase, with the single open PR awaiting review or merge. No new bugs, feature requests, or community discussions surfaced through the issue tracker.</p>
<h2>2. Releases</h2>
<p>No new releases were published in the last 24 hours.</p>
<h2>3. Project Progress</h2>
<p>No pull requests were merged or closed today. The only activity is PR #989, which remains open:</p>
<ul>
<li><a href="https://github.com/nullclaw/nullclaw/pull/989">#989 [OPEN] fix: restore broken star history chart</a> — Submitted by FaintFlower; proposes replacing the GitHub stargazer API dependency with star-history.dera.page so the README chart renders correctly.</li>
</ul>
<h2>4. Community Hot Topics</h2>
<ul>
<li><a href="https://github.com/nullclaw/nullclaw/pull/989">#989 fix: restore broken star history chart</a> — The only active PR. It addresses a functional regression in the project&#39;s README: the star history chart stopped rendering because the GitHub stargazer API it depends on is subject to access restrictions. The contributor proposes a token-free alternative service with a verified chart URL. This indicates ongoing community interest in keeping the project&#39;s public-facing documentation accurate and visually functional, even amid low overall activity.</li>
</ul>
<h2>5. Bugs &amp; Stability</h2>
<ul>
<li><strong>Medium severity:</strong> Broken star history chart in README, caused by reliance on the GitHub stargazer API being access-restricted. The chart fails to render for visitors. A fix exists in open PR <a href="https://github.com/nullclaw/nullclaw/pull/989">#989</a>; no other bugs, crashes, or regressions were reported in the last 24 hours.</li>
</ul>
<h2>6. Feature Requests &amp; Roadmap Signals</h2>
<p>No feature requests were filed or updated in the last 24 hours. The only roadmap-adjacent signal is PR #989, which is a maintenance fix rather than a new feature. No data suggests specific additions for the next version.</p>
<h2>7. User Feedback Summary</h2>
<p>Feedback data is limited to the single PR contribution. The author&#39;s pain point is the reliance on the GitHub stargazer API for README rendering, which breaks without a token — a friction point for both maintainers and visitors viewing the repository. The proposed solution (switching to a token-free chart service) suggests mild dissatisfaction with the current setup and a preference for dependency-light alternatives.</p>
<h2>8. Backlog Watch</h2>
<ul>
<li><a href="https://github.com/nullclaw/nullclaw/pull/989">#989 fix: restore broken star history chart</a> — Open since 2026-08-19 with no comments or maintainer response observed. As the only outstanding PR, it warrants maintainer attention to confirm the alternative chart service is acceptable and to merge or provide feedback, so the README regression is resolved.</li>
</ul>
</details>

<details>
<summary><strong>IronClaw</strong> — <a href="https://github.com/nearai/ironclaw">nearai/ironclaw</a></summary>

<h1>IronClaw Project Digest — 2026-08-20</h1>
<h2>1. Today&#39;s Overview</h2>
<p>High-activity day: 15 issues updated (9 open, 6 closed) and 39 PRs updated (21 open, 18 merged/closed), capped by the stable release of <strong>ironclaw-v1.3.0</strong>. The notification system made the biggest advance — the durable inbox contracts, storage, and product APIs merged (#7697) with three follow-up PRs (run outcomes, run gates, WebUI notification center) still open. The capability-response-normalization effort progressed with two of three PRs merged (#7686, #7692), and a CI-stability fix (#7756) landed to stop merge-queue timeouts caused by unbounded <code>apt-get</code> operations. New v1.4.0-scoped work is underway on persistent per-user sandboxes (#7732 / #7751) and bounded automation creation preflight (#7742 / #7743).</p>
<h2>2. Releases</h2>
<p><strong>ironclaw-v1.3.0</strong> (2026-08-19) — stable promotion of <code>1.3.0-rc.2</code>, including all RC1/RC2 scope.</p>
<ul>
<li><strong>Fixed:</strong> Upgrades from 1.2 now accept and preserve the released extension <code>activation_state</code> field instead of crash-looping during state application.</li>
<li><strong>Breaking changes:</strong> None indicated — this is a stability/upgrade-fix promotion.</li>
<li><strong>Migration notes:</strong> The 1.2→1.3 upgrade path is the explicitly validated fix; users still on 1.2 should upgrade to resolve the <code>activation_state</code> crash-loop.</li>
</ul>
<h2>3. Project Progress</h2>
<p>Merged/closed PRs today:</p>
<ul>
<li><strong>#7754</strong> — Release promotion <code>1.3.0-rc.2</code> → <code>1.3.0</code> (version + lockfile only, no behavior change). <a href="https://github.com/nearai/ironclaw/pull/7754">https://github.com/nearai/ironclaw/pull/7754</a></li>
<li><strong>#7756</strong> — CI fix: bounded every unbounded CI operation (apt hangs, uncapped jobs, external downloads); addresses merge-queue timeouts across 69 cancelled runs / 1,193 jobs. <a href="https://github.com/nearai/ironclaw/pull/7756">https://github.com/nearai/ironclaw/pull/7756</a></li>
<li><strong>#7752</strong> — Subagent activation provenance, <code>activate()</code> primitive, and derived autonomous-wake cap (slice 1). Foundation for background subagents with no production behavior change yet. <a href="https://github.com/nearai/ironclaw/pull/7752">https://github.com/nearai/ironclaw/pull/7752</a></li>
<li><strong>#7697</strong> — Durable user inbox and product APIs: typed notification contracts, per-recipient storage, pagination, unread counts, read/archive lifecycle. <a href="https://github.com/nearai/ironclaw/pull/7697">https://github.com/nearai/ironclaw/pull/7697</a></li>
<li><strong>#7692</strong> — Normalized provider failures and auth diagnostics for model context (PR 2 of the capability-response-normalization plan). <a href="https://github.com/nearai/ironclaw/pull/7692">https://github.com/nearai/ironclaw/pull/7692</a></li>
<li><strong>#7686</strong> — Centralized capability outcome processing in <code>ironclaw_host_runtime</code> (PR 1 of the same plan; behavior-preserving). <a href="https://github.com/nearai/ironclaw/pull/7686">https://github.com/nearai/ironclaw/pull/7686</a></li>
<li><strong>#6994</strong> — OOBE automation-tasks prototype (WebUI carousel, inline cards, agent-mode pill), gated behind an off-by-default flag; closes onboarding epic #7044. <a href="https://github.com/nearai/ironclaw/pull/6994">https://github.com/nearai/ironclaw/pull/6994</a></li>
</ul>
<p>Correspondingly closed issues: #7044 (channel-first onboarding epic), #7688 (notification inbox contracts), #7681 (Slack unlinked-user connect message), #7602 (Tier 2 lease-fence token cache), #7603 (Tier 3 checkpoint batching), #6993 (OOBE backend wiring).</p>
<h2>4. Community Hot Topics</h2>
<ul>
<li><strong>#7732 — Epic: Persistent per-user sandbox with iron-proxy</strong> (7 comments, the most-commented item this cycle). Discusses replacing create/remove-per-command Docker containers with a reusable per-user container; <code>/workspace</code> persistence per <code>(tenant, user)</code>; loop executors deferred. Directly tied to open PR #7751 (Step 1, Docker Exec). <a href="https://github.com/nearai/ironclaw/issues/7732">https://github.com/nearai/ironclaw/issues/7732</a></li>
<li><strong>#5998 — No transport for local/on-device MCP servers</strong> (open since 07-11; 1 comment). <code>stdio</code> is rejected and loopback HTTP is denied, blocking local MCP development entirely. Now has a proposed fix from a new contributor: PR #7757. <a href="https://github.com/nearai/ironclaw/issues/5998">https://github.com/nearai/ironclaw/issues/5998</a></li>
<li><strong>#7603 — Tier 3: Batch BeforeModel checkpoints</strong> (2 comments; closed). Performance-driven issue estimating −14 rows/turn by batching checkpoint writes; closed with the tier work. <a href="https://github.com/nearai/ironclaw/issues/7603">https://github.com/nearai/ironclaw/issues/7603</a></li>
</ul>
<p>Underlying needs: developers want on-device/local tooling (MCP over loopback), persistent per-user compute environments, and reduced database write pressure per turn.</p>
<h2>5. Bugs &amp; Stability</h2>
<p>Ranked by severity:</p>
<ol>
<li><strong>#7748 — &quot;IronClaw got confused and stopped working&quot;</strong> (open). User-reported complete work stoppage via Slack; no repro details and no fix PR yet — highest severity due to total failure, but under-investigated. <a href="https://github.com/nearai/ironclaw/issues/7748">https://github.com/nearai/ironclaw/issues/7748</a></li>
<li><strong>#7745 — Copilot MCP extension install fails</strong> (P2, qa-bug). <code>auth_required</code> error, duplicate catalog entries (<code>mcp-gh-copilot-mcp</code> vs. a second Copilot entry), and unclear token type. Blocks a flagship extension install on Railway QA. No fix PR yet. <a href="https://github.com/nearai/ironclaw/issues/7745">https://github.com/nearai/ironclaw/issues/7745</a></li>
<li><strong>#7744 — Cron job UI missing edit and test buttons</strong> (P3, qa-bug). Users can view jobs and status but cannot edit or manually trigger them; no fix PR yet. <a href="https://github.com/nearai/ironclaw/issues/7744">https://github.com/nearai/ironclaw/issues/7744</a></li>
<li><strong>#7760 — Unpinned lineage-drop in <code>AgentTurnProcessStateMetadata::from_state</code></strong> (open). Deliberate dropping of subagent lineage on state-derived rewrites is not covered by tests; needs a pin to prevent accidental behavior change. <a href="https://github.com/nearai/ironclaw/issues/7760">https://github.com/nearai/ironclaw/issues/7760</a></li>
<li><strong>CI merge-queue timeouts</strong> — every stall traced to unbounded <code>apt-get</code> (69 runs, 1,193 jobs affected); fixed and merged in #7756. <a href="https://github.com/nearai/ironclaw/pull/7756">https://github.com/nearai/ironclaw/pull/7756</a></li>
</ol>
<p>Also fixed via the 1.3.0 release: 1.2→1.3 upgrade crash-loop on the extension <code>activation_state</code> field.</p>
<h2>6. Feature Requests &amp; Roadmap Signals</h2>
<ul>
<li><strong>Persistent per-user sandbox</strong> (#7732, v1.4.0 epic; PR #7751 implements Step 1 with reusable per-user containers and Docker Exec). Strong next-version candidate. <a href="https://github.com/nearai/ironclaw/issues/7732">https://github.com/nearai/ironclaw/issues/7732</a></li>
<li><strong>Local MCP server on literal loopback IP</strong> (#5998; PR #7757 by a new contributor). Long-requested capability for on-device MCP; likely to land soon if reviewed. <a href="https://github.com/nearai/ironclaw/pull/7757">https://github.com/nearai/ironclaw/pull/7757</a></li>
<li><strong>Bounded automation creation preflight</strong> (#7742; PR #7743). Adds a <code>ready</code> / <code>needs_setup</code> / <code>needs_input</code> protocol to distinguish authoring from executing automations; part of #6879. <a href="https://github.com/nearai/ironclaw/issues/7742">https://github.com/nearai/ironclaw/issues/7742</a></li>
<li><strong>Notification product surface</strong> — inbox backend merged (#7697); open PRs #7699 (actionable run gates), #7700 (authoritative run outcomes), #7698 (generalized WebUI notification center) point to full notification UX in the next release. <a href="https://github.com/nearai/ironclaw/pull/7699">https://github.com/nearai/ironclaw/pull/7699</a></li>
<li><strong>WASM typed tool response, guest migration, and dispatch-error cleanup</strong> (#7711) — final PR of the capability-response-normalization stack. <a href="https://github.com/nearai/ironclaw/pull/7711">https://github.com/nearai/ironclaw/pull/7711</a></li>
<li><strong>Design System / Storybook epic</strong> (#7038) and <strong>IronHub agent-link operator surface</strong> (#7516) remain open longer-term signals. <a href="https://github.com/nearai/ironclaw/issues/7038">https://github.com/nearai/ironclaw/issues/7038</a></li>
</ul>
<p>Prediction: v1.4.0 will likely bundle persistent sandboxes, the notification center/run-gate UX, automation preflight, and loopback-MCP support.</p>
<h2>7. User Feedback Summary</h2>
<ul>
<li><strong>Reliability complaint:</strong> A Slack user (bianca.guimaraes-chadwick) reported &quot;It just got confused and stopped working&quot; — a clear satisfaction risk, currently lacking repro detail (#7748). <a href="https://github.com/nearai/ironclaw/issues/7748">https://github.com/nearai/ironclaw/issues/7748</a></li>
<li><strong>Slack onboarding privacy:</strong> Unlinked users received a public connect notice in shared channels plus a manual round trip; fixed and closed (#7681). <a href="https://github.com/nearai/ironclaw/issues/7681">https://github.com/nearai/ironclaw/issues/7681</a></li>
<li><strong>Local-development blocker:</strong> Users cannot connect MCP servers running on the same machine (stdio rejected, loopback HTTP denied) — a recurring pain point since July (#5998). <a href="https://github.com/nearai/ironclaw/issues/5998">https://github.com/nearai/ironclaw/issues/5998</a></li>
<li><strong>Cron management gap:</strong> Users can view cron jobs but not edit or test them from the UI (#7744). <a href="https://github.com/nearai/ironclaw/issues/7744">https://github.com/nearai/ironclaw/issues/7744</a></li>
<li><strong>Extension install friction:</strong> Copilot MCP install fails with confusing auth/token requirements and duplicate catalog entries (#7745). <a href="https://github.com/nearai/ironclaw/issues/7745">https://github.com/nearai/ironclaw/issues/7745</a></li>
</ul>
<h2>8. Backlog Watch</h2>
<ul>
<li><strong>#5998 — Local MCP transport</strong> (open 40 days). Now has a fix PR (#7757) from a new contributor; needs maintainer review to avoid further stall. <a href="https://github.com/nearai/ironclaw/issues/5998">https://github.com/nearai/ironclaw/issues/5998</a></li>
<li><strong>#7516 — Operator surface for IronHub agent link</strong> (open since 08-12, new contributor). WebUI cannot complete an agent link without CLI access; PR awaiting attention. <a href="https://github.com/nearai/ironclaw/pull/7516">https://github.com/nearai/ironclaw/pull/7516</a></li>
<li><strong>#7456 — Profile-agnostic durable storage</strong> (open since 08-10, core contributor, risk: medium). Restructures Reborn storage roots and security envelope; no activity in the last day. <a href="https://github.com/nearai/ironclaw/pull/7456">https://github.com/nearai/ironclaw/pull/7456</a></li>
<li><strong>#7038 — Design System / Storybook epic</strong> (open since 08-03). Large UX proposal package still awaiting momentum; referenced proposal PR #7257. <a href="https://github.com/nearai/ironclaw/issues/7038">https://github.com/nearai/ironclaw/issues/7038</a></li>
</ul>
</details>

<details>
<summary><strong>LobsterAI</strong> — <a href="https://github.com/netease-youdao/LobsterAI">netease-youdao/LobsterAI</a></summary>

<h1>LobsterAI Project Digest — 2026-08-20</h1>
<h2>1. Today&#39;s Overview</h2>
<p>The project saw moderate activity: 9 PRs were updated (8 closed, 1 still open) and 2 issues were touched, both remaining open. Most of the closed PRs are April-era items (<code>#1545</code>–<code>#1560</code>) that were swept in a stale-triage pass, suggesting maintainers are actively cleaning an aging backlog rather than shipping those changes — notably, the feature request in <code>#1552</code> remains open despite a linked implementation PR being closed. The genuinely fresh work is on Windows installer tooling (<code>#2511</code>, <code>#2512</code>, authored 2026-08-19), which indicates active build/distribution engineering. No new releases were published. Overall, the project is healthy but in a &quot;consolidation&quot; phase: backlog hygiene + Windows packaging hardening, with no release cadence activity.</p>
<h2>2. Releases</h2>
<p>None in this window.</p>
<h2>3. Project Progress</h2>
<p>The 8 closed PRs break into two distinct groups:</p>
<p><strong>Fresh Windows installer work (2026-08-19/20):</strong></p>
<ul>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/pull/2511">#2511 — fix(installer): support silent upload-first web builds</a></strong> — Adds a two-pass Windows web-installer flow that reuses an already-uploaded NOS-hosted package, rebuilds only the signed WebSetup stub, and enforces a before/after SHA-256 invariant so the stub pass cannot invalidate the uploaded payload.</li>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/pull/2512">#2512 — fix(installer): hide banner for dictbind silent package</a></strong> — Suppresses the plugin-owned silent banner only for the dictbind double-click-silent channel, preserving existing behavior for other silent install paths and keeping UAC/RequestExecutionLevel unchanged.</li>
</ul>
<p><strong>April-era PRs closed in the stale sweep (not merged per remaining open linked issues):</strong></p>
<ul>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1545">#1545 — fix(agent): sync activeSkillIds immediately when updating current agent&#39;s skills</a></strong> — Fixes the agent settings panel not refreshing Active Skill Badges until switching agents; root cause was <code>updateAgent()</code> not updating <code>state.skill.activeSkillIds</code>.</li>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1546">#1546 — feat(engine-overlay): 引擎启动超时后显示取消启动和查看日志按钮</a></strong> — After 30s of engine startup, shows &quot;Cancel startup&quot; and &quot;View logs&quot; escape buttons instead of forcing a 5-minute hard timeout.</li>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1553">#1553 — feat(cowork): Write 工具文件卡片及分屏预览面板</a></strong> — Inline file card for Write tool results plus a resizable 320–900px preview panel (Markdown, HTML sandbox iframe, SVG, images, syntax-highlighted code). Linked to <code>#1552</code>, which is <strong>still open</strong> — this PR did not merge.</li>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1555">#1555 — fix: npm run dist:mac:x64打包失败</a></strong> — macOS lacks <code>sha256sum</code>; adds <code>shasum</code> compatibility in <code>build-openclaw-runtime.sh</code>.</li>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1557">#1557 — feat(settings): 设置面板侧栏支持搜索筛选分类</a></strong> — Search box in the settings sidebar with NFKC-normalized, AND-matched Chinese/English keyword filtering; auto-switches tab when the selected one is filtered out.</li>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1560">#1560 — fix: 修复Agent编辑后点击原Agent无法切换回聊天界面的问题</a></strong> — <code>SidebarAgentList.handleSwitch</code> early-returned on the already-selected agent, stranding users on the &quot;My Agents&quot; screen after editing.</li>
</ul>
<h2>4. Community Hot Topics</h2>
<ul>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/issues/1556">#1556 — [OPEN] doc bug: IM机器人配置指南404</a></strong> — Most-commented item (2 comments). Users are hitting a 404 on the IM bot configuration guide at <code>lobsterai.youdao.com</code>. Underlying need: broken documentation is hurting onboarding for IM integration, a core LobsterAI use case.</li>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/issues/1552">#1552 — [OPEN] feat: AI产物 Markdown 预览及文件卡片支持</a></strong> — 1 comment. Users want inline file card + preview after Write tool calls, citing poor UX when agents generate Markdown/HTML/code: reading content into chat wastes context, and switching to the file manager is disruptive. This is the clear community priority for agent-output ergonomics.</li>
</ul>
<h2>5. Bugs &amp; Stability</h2>
<p>Ranked by severity:</p>
<ol>
<li><strong>Mac packaging broken (High)</strong> — <code>npm run dist:mac:x64</code> fails on macOS because the runtime build script assumes <code>sha256sum</code>, which macOS doesn&#39;t ship. Fix exists in <strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1555">#1555</a></strong> (closed; needs verification/re-merge against current main).</li>
<li><strong>Scheduled task notification state bug (Medium)</strong> — <strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1547">#1547</a></strong> (OPEN): after selecting an IM channel then saving &quot;不通知&quot; (no notification), re-editing the task shows the previous IM channel instead of &quot;none&quot;. Root cause traced to inconsistent handling of <code>delivery.mode</code> in <code>TaskForm.tsx</code>. A +2-line fix is ready but not yet merged.</li>
<li><strong>Agent switch dead-end (Medium/Low)</strong> — Editing an agent and clicking the previously selected agent doesn&#39;t return to chat. Fixed in <strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1560">#1560</a></strong> (closed stale; fix still needed).</li>
<li><strong>Stale Active Skill Badges (Low)</strong> — Skill list changes don&#39;t reflect in the UI until manual agent switch. Fix in <strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1545">#1545</a></strong> (closed stale).</li>
<li><strong>Docs 404 (Low) — <a href="https://github.com/netease-youdao/LobsterAI/issues/1556">#1556</a></strong> — IM configuration guide returns 404. No fix PR yet.</li>
</ol>
<h2>6. Feature Requests &amp; Roadmap Signals</h2>
<ul>
<li><strong>AI artifact preview is the strongest roadmap signal.</strong> Issue <a href="https://github.com/netease-youdao/LobsterAI/issues/1552">#1552</a> and its associated PR <a href="https://github.com/netease-youdao/LobsterAI/pull/1553">#1553</a> cover file cards, Markdown/HTML/SVG/code preview, and a split-pane panel. Although the PR was stale-closed, the spec is complete and the underlying need persists — expect this to be re-implemented in an upcoming release, possibly with the FilePreviewPanel architecture from <code>#1553</code>.</li>
<li><strong>Settings UX improvements appear committed.</strong> Sidebar search/filter (<a href="https://github.com/netease-youdao/LobsterAI/pull/1557">#1557</a>) and engine-overlay escape controls (<a href="https://github.com/netease-youdao/LobsterAI/pull/1546">#1546</a>) address long-standing usability complaints about the settings panel and startup hangs.</li>
<li><strong>Windows distribution expansion.</strong> The August installer PRs (<a href="https://github.com/netease-youdao/LobsterAI/pull/2511">#2511</a>, <a href="https://github.com/netease-youdao/LobsterAI/pull/2512">#2512</a>) signal investment in silent/upload-first web installers and channel-specific packaging (dictbind) — likely preparing for broader or automated Windows rollout.</li>
<li><strong>Feedback from raw April dates:</strong> the delayed re-emergence of old fixes (Apr → Aug) suggests the team is merging long-pending robustness work into a single larger release rather than shipping incrementally.</li>
</ul>
<h2>7. User Feedback Summary</h2>
<ul>
<li><strong>Documentation integrity:</strong> direct report of a broken IM configuration guide link, with user-provided screenshot — dissatisfaction with docs availability for a key integration feature.</li>
<li><strong>Workflow pain in agent-generated files:</strong> users dislike pasting large file contents into chat to preview agent output; they want in-app preview and file cards immediately after Write calls. The request explicitly calls out writing/document-generation scenarios as currently poor experiences.</li>
<li><strong>Configuration persistence confusion:</strong> the scheduled-task notification bug (<code>#1547</code>) shows settings silently reverting/not honoring &quot;none&quot;, eroding trust in saved configuration.</li>
<li><strong>Navigation friction:</strong> the agent-edit-then-click bug (<code>#1560</code>) and stale skill badges (<code>#1545</code>) are small but recurrent UI inconsistencies that interrupt flow in the agent management workflow.</li>
<li><strong>Positive signal:</strong> the detailed, well-scoped feature requests (with screenshots and exact acceptance criteria) suggest a technically engaged user base that is collaborating constructively with maintainers.</li>
</ul>
<h2>8. Backlog Watch</h2>
<ul>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/pull/1547">#1547 — fix(scheduledTask) OPEN PR</a></strong> — The only non-stale open PR. Reviewed-ready, tiny (+2 lines), fixes a real configuration bug. Needs maintainer review/merge before the next snapshot.</li>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/issues/1556">#1556 — doc 404 (OPEN, stale since Apr, 2 comments)</a></strong> — Unanswered for over 4 months. A doc-fix PR would be trivial and resolves visible community frustration.</li>
<li><strong><a href="https://github.com/netease-youdao/LobsterAI/issues/1552">#1552 — file preview feature (OPEN, stale since Apr)</a></strong> — Its implementation PR was swept as stale; the issue needs an explicit decision: re-open the feature branch, assign to a milestone, or close with a rationale.</li>
<li><strong>April stale-sweep casualties</strong> — PRs <a href="https://github.com/netease-youdao/LobsterAI/pull/1545">#1545</a>, <a href="https://github.com/netease-youdao/LobsterAI/pull/1546">#1546</a>, <a href="https://github.com/netease-youdao/LobsterAI/pull/1553">#1553</a>, <a href="https://github.com/netease-youdao/LobsterAI/pull/1555">#1555</a>, <a href="https://github.com/netease-youdao/LobsterAI/pull/1557">#1557</a>, <a href="https://github.com/netease-youdao/LobsterAI/pull/1560">#1560</a> contain fully specified fixes (mac packaging, agent switch, skill sync, settings search, startup overlay) that were closed without merge. The mac packaging fix (<code>#1555</code>) is especially time-sensitive. If still valid against current main, they should be rebased and re-opened rather than lost.</li>
</ul>
</details>

<details>
<summary><strong>TinyClaw</strong> — <a href="https://github.com/TinyAGI/tinyclaw">TinyAGI/tinyclaw</a></summary>

<p>No activity in the last 24 hours.</p>
</details>

<details>
<summary><strong>Moltis</strong> — <a href="https://github.com/moltis-org/moltis">moltis-org/moltis</a></summary>

<h2>Moltis Project Digest — 2026-08-20</h2>
<h3>1. Today&#39;s Overview</h3>
<p>Moltis saw a fully merged, zero-open-items day. Four pull requests were closed and merged, the only recently reported open issue was closed by its fix, and a new release (20260818.10) was published. All activity landed in the mainline with no remaining open PRs or active issues at end of day. The work focused on security hardening and WhatsApp channel correctness, indicating a mature maintenance phase with fast turnaround on bug reports.</p>
<h3>2. Releases</h3>
<ul>
<li><strong>20260818.10</strong> — published 2026-08-18. No changelog details are included in the available data. The release predates the fixes merged in this window (Aug 19–20), so those changes are expected in a subsequent build.</li>
</ul>
<h3>3. Project Progress</h3>
<p>All four PRs updated in the last 24 hours were merged/closed:</p>
<ul>
<li><strong><a href="https://github.com/moltis-org/moltis/pull/1216">PR #1216</a> — fix(httpd): require authentication for vault unlock and recovery</strong> — Closes the CWE-306 security issue where vault unlock/recovery endpoints had no authentication.</li>
<li><strong><a href="https://github.com/moltis-org/moltis/pull/1217">PR #1217</a> — fix(whatsapp): treat a reply to the bot as addressing it</strong> — Fixes dropped messages in group chats when <code>mention_mode = &quot;mention&quot;</code>; replies are now recognized as directed at the bot.</li>
<li><strong><a href="https://github.com/moltis-org/moltis/pull/1218">PR #1218</a> — fix(whatsapp): stop hardcoding the push name to &quot;Moltis&quot;</strong> — Bot identity in WhatsApp presence/group chats now reflects the configured bot name instead of a hardcoded value.</li>
<li><strong><a href="https://github.com/moltis-org/moltis/pull/1219">PR #1219</a> — fix(channels): make the untrusted-turn tool ceiling configurable</strong> — Corrects a side effect of #1170 that denied all tools to untrusted turns in shared chats, making the ceiling configurable and restoring unreachable tool-policy layers.</li>
</ul>
<h3>4. Community Hot Topics</h3>
<p>No issues or PRs accumulated comments or reactions in the last 24 hours. The two active topic clusters were:</p>
<ul>
<li><strong>Vault endpoint security</strong> — <a href="https://github.com/moltis-org/moltis/issues/1177">Issue #1177</a> drew the fix <a href="https://github.com/moltis-org/moltis/pull/1216">PR #1216</a>. Underlying need: trust/safety of authentication-critical HTTP endpoints.</li>
<li><strong>WhatsApp group behavior</strong> — <a href="https://github.com/moltis-org/moltis/pull/1217">PR #1217</a> and <a href="https://github.com/moltis-org/moltis/pull/1218">PR #1218</a> from the same contributor address the underlying need for reliable, correctly-labeled bot presence in group chats.</li>
</ul>
<h3>5. Bugs &amp; Stability</h3>
<ul>
<li><strong>Critical</strong> — <a href="https://github.com/moltis-org/moltis/issues/1177">Issue #1177</a> (CWE-306): <code>POST /api/auth/vault/unlock</code> and <code>POST /api/auth/vault/recovery</code> accepted unauthenticated remote calls because <code>/api/auth/</code> was blanket-allowlisted, enabling brute-force vault attacks. Fix merged in <a href="https://github.com/moltis-org/moltis/pull/1216">PR #1216</a>.</li>
<li><strong>Medium</strong> — <a href="https://github.com/moltis-org/moltis/pull/1217">PR #1217</a>: WhatsApp group replies to the bot were dropped as &quot;bot was not mentioned,&quot; breaking conversational flow in mention mode. Fixed.</li>
<li><strong>Medium</strong> — <a href="https://github.com/moltis-org/moltis/pull/1219">PR #1219</a>: Regression from #1170 made untrusted-turn tool policy a hardcoded deny-all, removing public-audience tools and making policy layers 4–5 unreachable in some shared contexts. Now configurable and fixed.</li>
<li><strong>Low</strong> — <a href="https://github.com/moltis-org/moltis/pull/1218">PR #1218</a>: Hardcoded WhatsApp push name misidentified bots in group chats. Fixed.</li>
</ul>
<h3>6. Feature Requests &amp; Roadmap Signals</h3>
<p>No explicit user feature requests were filed in this window. The main roadmap signal is <strong><a href="https://github.com/moltis-org/moltis/pull/1219">PR #1219</a></strong>, which converts a hardcoded tool-policy ceiling into a configurable setting — indicating continued investment in granular, per-channel tool policy and audience-based trust boundaries. The cluster of WhatsApp fixes also signals ongoing hardening of channel integrations; further channel-level configurability is a reasonable expectation for the next version.</p>
<h3>7. User Feedback Summary</h3>
<p>No direct user comments, reactions, or qualitative feedback landed in the last 24 hours. Reconstructed pain points from the data: users reported a serious security exposure with vault unlock/recovery endpoints (<a href="https://github.com/moltis-org/moltis/issues/1177">#1177</a>) and experienced broken WhatsApp group interactions where replies to the bot were ignored and bot identity was wrong. The fast close of the security issue and the same-day merging of all fixes indicate a responsive maintainer team, which is a positive satisfaction signal.</p>
<h3>8. Backlog Watch</h3>
<p>No open issues or open PRs remain. The backlog is clear; there are no long-unanswered items requiring maintainer attention.</p>
</details>

<details>
<summary><strong>CoPaw</strong> — <a href="https://github.com/agentscope-ai/CoPaw">agentscope-ai/CoPaw</a></summary>

<h1>CoPaw Project Digest — 2026-08-20</h1>
<h2>1. Today&#39;s Overview</h2>
<p>CoPaw saw a high-activity day with 45 PRs updated (26 merged/closed, 19 open) and 19 issues touched (16 closed, 3 open). No new releases were published, so the project is operating on QwenPaw 2.1.0-beta/2.0.1 as the latest available versions. A strong bug-fix wave landed today covering remote media download failures, corrupt <code>envs.json</code> handling, uploaded filename preservation, and skill deduplication. Feature work remains active, including a self-hosted multi-user Hub, a unified marketplace, and a MiniMax M3 provider addition. Maintenance health is generally solid, though CI flakiness and E2E test stability required two dedicated fix PRs.</p>
<h2>2. Releases</h2>
<p>No new releases were published in the last 24 hours. The most recent versions in circulation remain QwenPaw 2.0.1 (stable desktop/pip) and 2.1.0-beta, with 2.1.0 referenced in bug reports as carrying the ReMe 0.4.1.5 and agentscope 2.0.4.post1 stack.</p>
<h2>3. Project Progress</h2>
<p>The following PRs were merged/closed today and advanced the codebase:</p>
<ul>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7135">fix(envs): preserve corrupt files and write envs atomically</a></strong> (#7135) — Fixes <a href="https://github.com/agentscope-ai/QwenPaw/issues/7118">#7118</a>, where an unparseable <code>envs.json</code> was silently overwritten, losing all stored environment variables.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7146">fix(view_image): freeze remote images before persisting tool results</a></strong> (#7146) — Remote <code>view_image</code> URLs are now downloaded with bounded size/timeout/redirect/SSRF protections and persisted as immutable Base64 blocks, preventing broken links from destroying conversation turns.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7138">fix: recover from remote media download timeouts</a></strong> (#7138) — Addresses conversations getting stuck when a provider returns <code>Timeout while downloading url</code>.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/6492">fix(files): preserve uploaded filenames in hints</a></strong> (#6492) — Closes <a href="https://github.com/agentscope-ai/QwenPaw/issues/6453">#6453</a>; the console now retains browser-supplied original filenames (e.g., Chinese names) in user-facing messages instead of UUID-prefixed paths.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7140">refactor(cli): refactor skill CLI, add search, add batch enable/disable</a></strong> (#7140) — Adds searchable filtering to <code>qwenpaw skills config</code> and batch enable/disable, addressing <a href="https://github.com/agentscope-ai/QwenPaw/issues/7090">#7090</a>.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7097">fix(skill): remove skill bound duplication</a></strong> (#7097) — Deduplicates workspace and bound skills by SKILL.md frontmatter name, resolving <a href="https://github.com/agentscope-ai/QwenPaw/issues/7073">#7073</a>.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7114">refactor(config): make agent config loading async by default</a></strong> (#7114) — Promotes <code>load_agent_config_async</code> to the public <code>load_agent_config</code> API and moves sync loading to a private method.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7115">fix(memory): avoid noisy inbox notifications for unchanged jobs</a></strong> (#7115) — Auto-Memory/Auto-Dream now stay silent when a job runs successfully with no actual changes; only meaningful updates or failures notify users.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7037">feat(computer-use): observe related window surfaces</a></strong> (#7037) — Computer Use now observes up to three related windows (menus, drop-downs, owned dialogs) while keeping the selected window as the stable target.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7147">fix(xiaoyi): report proactive send failures and normalize session IDs</a></strong> (#7147) — XiaoYi channel now surfaces delivery failures and handles <code>xiaoyi:</code>-prefixed session IDs correctly.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7089">ci(datapaw): add a standalone version-driven release pipeline</a></strong> (#7089) — Datapaw plugin gets its own release pipeline independent of main QwenPaw cadence.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7157">fix(e2e): dismiss Try Desktop Mode onboarding overlay before tests</a></strong> (#7157) — Unbreaks the nightly E2E job, red for 8 consecutive runs since #6645 introduced the overlay.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7155">test(unit): widen timing tolerance for flaky sandbox offload test</a></strong> (#7155) — Stabilizes <code>test_sandbox_slow_setup_does_not_consume_offload_budget</code>.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7038">fix(website): home WorksForYou &amp; update blog &amp; add QwenPaw Creator blog</a></strong> (#7038) — Website content updates.</li>
</ul>
<h2>4. Community Hot Topics</h2>
<ul>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/issues/2884">#2884 — Personal directory wiped after installing CoPaw on Ubuntu 22.04</a></strong> — 27 comments, the most active issue by far. The user reports near-total deletion of their home directory contents and the software itself on the day of installation. The issue is closed but was still being updated as recently as August 19, indicating an ongoing discussion around root-cause attribution (CoPaw behavior vs. external compromise).</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/issues/6826">#6826 — Assistant message end time displays incorrectly</a></strong> — 4 comments. A 2-minute real thinking time is shown as a few seconds in the UI; QwenPaw 2.0.1, Windows 11, pip install.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/issues/6847">#6847 — Qwenpaw gets killed by antivirus while WorkBuddy does not</a></strong> — 4 comments. Users report antivirus software force-terminating Qwenpaw during task execution; likely a false-positive or behavioral-trigger concern affecting production trust.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/issues/7013">#7013 — Unified tool panel, web service preview and interactive terminal for Chat</a></strong> — 3 comments, open. A substantial UX proposal for an agent development workbench (file preview, diffs, local web services, web terminal).</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/issues/7110">#7110 — Undownloadable image URL renders an entire conversation unusable</a></strong> — 3 comments. Model-hallucinated or network-blocked image links permanently break the session until <code>/clear</code>; fixed by PRs #7138 and #7146.</li>
</ul>
<h2>5. Bugs &amp; Stability</h2>
<p>Ranked by severity:</p>
<ol>
<li><strong>Potential data loss — <a href="https://github.com/agentscope-ai/QwenPaw/issues/2884">#2884 directory content cleared on Ubuntu 22.04</a></strong> (27 comments, closed) — The most severe report, alleging home-directory deletion after a fresh install. Old (April) but still being updated; warrants a maintainer post-mortem or public explanation to settle user concern.</li>
<li><strong>Silent env var loss — <a href="https://github.com/agentscope-ai/QwenPaw/issues/7118">#7118 corrupt envs.json is swallowed and overwritten</a></strong> — Fixed by <a href="https://github.com/agentscope-ai/QwenPaw/pull/7135">#7135</a>, which preserves the corrupt file for inspection and switches to atomic writes.</li>
<li><strong>Conversation bricking — <a href="https://github.com/agentscope-ai/QwenPaw/issues/7110">#7110 undownloadable image link kills session</a></strong> — Fixed by <a href="https://github.com/agentscope-ai/QwenPaw/pull/7138">#7138</a> (remote media download timeouts) and <a href="https://github.com/agentscope-ai/QwenPaw/pull/7146">#7146</a> (immutable Base64 image freezing).</li>
<li><strong>Embedding health check failure — <a href="https://github.com/agentscope-ai/QwenPaw/issues/7156">#7156 health check times out even when backend is warm; timeout hardcoded</a></strong> — Open, new today. With QwenPaw 2.1.0, a warm Ollama backend (0.5s embed) still fails the 5s health check (10.4s elapsed), silently degrading to BM25-only retrieval. The hardcoded timeout in <code>reme/...</code> needs a config knob.</li>
<li><strong>Antivirus termination — <a href="https://github.com/agentscope-ai/QwenPaw/issues/6847">#6847 process killed by security software</a></strong> — Closed with 4 comments; a compatibility/packaging issue that erodes user confidence.</li>
<li><strong>Memory pipeline gap — <a href="https://github.com/agentscope-ai/QwenPaw/issues/6624">#6624 auto-compression (Scroll) does not trigger <code>summarize_when_compact</code></a></strong> — Closed; manual <code>/compact</code> works but automatic token-threshold eviction bypasses the memory summarization flow.</li>
<li><strong>UI timing — <a href="https://github.com/agentscope-ai/QwenPaw/issues/6826">#6826 message end time shows seconds instead of actual thinking duration</a></strong> — Closed; cosmetic but misleading for users evaluating model performance.</li>
<li><strong>No startup — <a href="https://github.com/agentscope-ai/QwenPaw/issues/3177">#3177 CoPaw app cannot launch on Windows</a></strong> — Closed; garbled wrapper output (<code>锘緻echo</code> / <code>芒聙聶</code>) suggests a UTF-8 BOM/encoding defect in the CLI wrapper batch file.</li>
</ol>
<h2>6. Feature Requests &amp; Roadmap Signals</h2>
<ul>
<li><strong>Skill management UX (shipped)</strong> — Search/filter and batch enable/disable in the skill CLI (<a href="https://github.com/agentscope-ai/QwenPaw/issues/7090">#7090</a>) landed via <a href="https://github.com/agentscope-ai/QwenPaw/pull/7140">#7140</a>. A concurrent open issue asks for the same search/filter experience in the GUI skill import page.</li>
<li><strong>Chinese filename preservation (shipped)</strong> — <a href="https://github.com/agentscope-ai/QwenPaw/issues/6453">#6453</a> closed by <a href="https://github.com/agentscope-ai/QwenPaw/pull/6492">#6492</a>: uploaded Chinese filenames now survive into LLM context hints.</li>
<li><strong>Agent workbench — <a href="https://github.com/agentscope-ai/QwenPaw/issues/7013">#7013 unified tool panel, Web service preview, interactive terminal</a></strong> — Open, cross-cutting feature touching core, console, and channels; the strongest roadmap signal for a more complete agent development loop.</li>
<li><strong>DingTalk context modes — <a href="https://github.com/agentscope-ai/QwenPaw/issues/7158">#7158 configurable per-group shared vs. isolated contexts</a></strong> — New today; a channel-specific collaboration feature, likely candidate for 2.1.x.</li>
<li><strong>Self-hosted multi-user Hub — <a href="https://github.com/agentscope-ai/QwenPaw/pull/7112">#7112 open PR</a></strong> — Opt-in control plane running isolated QwenPaw instances for local accounts via <code>qwenpaw hub</code>; could become a flagship enterprise-facing feature.</li>
<li><strong>Unified marketplace — <a href="https://github.com/agentscope-ai/QwenPaw/pull/6880">#6880 open PR</a></strong> — Consolidates app/plugin/skill marketplaces under a shared <code>/market</code> page.</li>
<li><strong>Deep research/execution — <a href="https://github.com/agentscope-ai/QwenPaw/issues/3074">#3074</a> and <a href="https://github.com/agentscope-ai/QwenPaw/issues/3260">#3260</a></strong> — Users continue to request DeerFlow-style harness/longGraph orchestration and ACP/Codex/OpeCode support. Repeated asks signal demand for structured deep-research workflows.</li>
<li><strong>Proactive memory — <a href="https://github.com/agentscope-ai/QwenPaw/issues/3082">#3082 make the agent consult memory.md when uncertain</a></strong> — Wants &quot;checking the map&quot; to be a standing behavior, not dependent on context overflow.</li>
<li><strong>Custom storage paths — <a href="https://github.com/agentscope-ai/QwenPaw/issues/3018">#3018 user config path customization</a></strong> — Closed but still relevant for power users managing skills/core files/agents across machines.</li>
<li><strong>MiniMax M3 — <a href="https://github.com/agentscope-ai/QwenPaw/pull/4881">#4881 open PR</a></strong> — Adds MiniMax-M3 as the default built-in model for both CN and international endpoints.</li>
<li><strong>CI gating — <a href="https://github.com/agentscope-ai/QwenPaw/pull/6764">#6764 open PR</a></strong> — Makes required status checks mandatory on <code>main</code> after a regression was merged with three failing test jobs; important for long-term stability.</li>
</ul>
<h2>7. User Feedback Summary</h2>
<ul>
<li><strong>Chinese-language user base dominates the conversation</strong>, with 17 of 19 issues written in Chinese. Localization and CJK filename handling are recurring themes — <a href="https://github.com/agentscope-ai/QwenPaw/issues/6453">#6453</a> was directly addressed by a merge today, which is positive signal.</li>
<li><strong>Serious trust concern around data safety</strong>: the #2884 report (home directory wiped, 27 comments) remains the loudest unresolved fear, even though the issue is technically closed. No maintainer explanation is visible in the provided data.</li>
<li><strong>Security software conflicts (#6847)</strong> and <strong>browser automation weakness (#3261)</strong> are eroding user willingness to rely on QwenPaw for long-running or unattended tasks.</li>
<li><strong>Memory behavior is a top expectation</strong>: users are frustrated when the agent forgets or when automatic compression does not follow the configured summarization rules (#6624, #3082).</li>
<li><strong>Satisfaction signals</strong>: users are actively requesting richer professional workflows (workbench, Hub, marketplace, DingTalk shared context), which suggests the existing UX is approaching production-ready and the community wants the next level of collaboration and control.</li>
</ul>
<h2>8. Backlog Watch</h2>
<ul>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/issues/2884">#2884 — directory wipe report, 27 comments, closed but unresolved narrative</a></strong> — The highest-signal item needing a maintainer follow-up or official statement; silence allows FUD to persist.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/5861">#5861 — macOS packaged backend cannot discover user-installed tools (open PR since July 8)</a></strong> — First-time contributor PR fixing login-shell PATH inheritance for Finder/Dock launches; awaiting review for over six weeks.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/4881">#4881 — MiniMax M3 provider addition (open PR since June 1)</a></strong> — A small, well-scoped change that has been under review for over two months.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/6764">#6764 — CI gate on main (open PR since August 6)</a></strong> — Defends against another regression-by-merge (already happened once with #6418); needs prioritization.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/6880">#6880 — unified marketplace (open PR since August 10)</a></strong> — Large UX consolidation under review; no visible roadmap commitment.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7150">#7150 — stalled LLM stream detection (open, new)</a></strong> — Fixes the indefinite &quot;Thinking&quot; state when an upstream stream stops without closing; important for production reliability.</li>
<li><strong><a href="https://github.com/agentscope-ai/QwenPaw/pull/7112">#7112 — self-hosted multi-user Hub (open PR)</a></strong> — Significant architectural addition currently without maintainer discussion in the visible data.</li>
</ul>
</details>

<details>
<summary><strong>ZeptoClaw</strong> — <a href="https://github.com/qhkm/zeptoclaw">qhkm/zeptoclaw</a></summary>

<p>No activity in the last 24 hours.</p>
</details>

<details>
<summary><strong>EasyClaw</strong> — <a href="https://github.com/gaoyangz77/easyclaw">gaoyangz77/easyclaw</a></summary>

<h1>EasyClaw Project Digest — 2026-08-20</h1>
<h2>1. Today&#39;s Overview</h2>
<p>EasyClaw published three consecutive releases (v1.8.101, v1.8.102, v1.8.103) within the observation window, indicating an active release cadence, but saw zero Issue or PR activity in the last 24 hours. All three releases focus on iterative hardening rather than new headline features, with emphasis on Feishu (Lark) integration stability, Gateway session management, and Affiliate collaboration workflows. The repo&#39;s open-source community surface (Issues/PRs) is currently dormant, with all observable progress occurring through version releases. Overall project health is stable; the project is shipping regularly but lacks visible community contribution momentum in this window.</p>
<h2>2. Releases</h2>
<p>Three new versions were published — <a href="https://github.com/gaoyangz77/easyclaw/releases">v1.8.101</a>, <a href="https://github.com/gaoyangz77/easyclaw/releases">v1.8.102</a>, <a href="https://github.com/gaoyangz77/easyclaw/releases">v1.8.103</a>. No breaking changes or migration notes were included; each release is an incremental improvement over the prior.</p>
<ul>
<li><strong>v1.8.103 — TK Copilot:</strong> Improves Feishu final replies, Gateway session recovery, and Affiliate collaboration consistency.</li>
<li><strong>v1.8.102 — TK Copilot:</strong> Improves differential update reliability, Feishu connection stability, Affiliate offer editing, and Gateway execution approvals.</li>
<li><strong>v1.8.101 — TK Copilot:</strong> Improves Affiliate campaign terms, per-shop Working Agendas, device assignments, WMS validation, and Gateway provider persistence.</li>
</ul>
<p>The fast succession of three patch-level versions suggests a rolling-fix workflow where issues are addressed and shipped quickly rather than batched into larger releases.</p>
<h2>3. Project Progress</h2>
<p>No Pull Requests were merged or closed in the last 24 hours, and no PRs are currently open. However, the three releases indicate forward movement in several subsystems:</p>
<ul>
<li><strong>Gateway/execution layer:</strong> session recovery (v1.8.103), execution approvals (v1.8.102), provider selection persistence (v1.8.101).</li>
<li><strong>Feishu integration:</strong> final reply handling (v1.8.103), connection stability (v1.8.102).</li>
<li><strong>Affiliate/达人 workflows:</strong> collaboration consistency (v1.8.103), offer editing (v1.8.102), campaign terms (v1.8.101).</li>
<li><strong>Infrastructure:</strong> per-shop Working Agendas, device assignment, and WMS validation (v1.8.101); differential update reliability (v1.8.102).</li>
</ul>
<h2>4. Community Hot Topics</h2>
<p>No Issues or PRs were active in the last 24 hours, so there are no threads to analyze for community discussion, reactions, or needs. The repository&#39;s discussion surface is effectively quiet at this snapshot.</p>
<h2>5. Bugs &amp; Stability</h2>
<p>No bugs, crashes, or regressions were reported via Issues in the last 24 hours. Indirectly, the releases contain stability-focused fixes that indicate previously known problem areas: Feishu connection drops, Gateway session loss, and unreliable differential updates. The rapid release of v1.8.102 and v1.8.103 immediately after v1.8.101 suggests the maintainers are actively patching regressions or stability issues introduced by newly shipped changes, though no public bug reports exist to confirm severity.</p>
<h2>6. Feature Requests &amp; Roadmap Signals</h2>
<p>No explicit feature requests were filed in the observation window. Roadmap signals must be inferred from release notes:</p>
<ul>
<li>Deeper <strong>Affiliate (达人) collaboration tooling</strong> — campaign terms, offer editing, and consistency fixes are receiving repeated attention, suggesting this is an actively evolving business area.</li>
<li><strong>Per-shop Working Agendas</strong> and <strong>device assignments</strong> are newer capabilities that may expand in scope.</li>
<li><strong>WMS validation</strong> integration hints at supply-chain/warehouse use cases being explored.</li>
<li><strong>Gateway execution approvals</strong> point toward a governance/approval workflow layer that may get more features in upcoming versions.</li>
<li>Given the pattern of three rapid releases, the next version (v1.8.104 or v1.9.x) will likely contain further Feishu and Gateway reliability fixes rather than major new functionality.</li>
</ul>
<h2>7. User Feedback Summary</h2>
<p>With no Issues or PRs in the window, direct user feedback is unavailable. Indirect signals from release notes suggest recurring pain points: users relying on Feishu for final replies experienced connection instability; Gateway sessions were being lost, requiring recovery logic; and Affiliate collaboration state was inconsistent across sessions. The repeated &quot;Improve/改善&quot; phrasing across all three releases indicates a reactive maintenance mode, where reported frictions are being addressed incrementally. No signals of satisfaction or dissatisfaction can be assessed from this snapshot.</p>
<h2>8. Backlog Watch</h2>
<p>No open Issues or PRs exist in the observable data, so there are no long-unanswered threads requiring maintainer attention. The absence of a backlog suggests either a clean queue, or that issue reporting is happening outside the GitHub tracker (e.g., private channels), which is consistent with the project&#39;s release-driven, closed-loop maintenance pattern.</p>
</details>

<hr>
<p><em>This digest is auto-generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI 开源趋势日报 2026-08-20</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-trending</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-trending</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      <description>AI 开源趋势日报 2026-08-20 数据来源: GitHub Trending + GitHub Search API（含 AI 与大数据 / 数据分析 / 数据挖掘趋势） | 生成时间: 2026-08-20 04:55 UTC AI 开源趋势日报（2026-08-20） 1. 今日速览 今日 GitHub Trending 榜单未抓取到，但通过主题搜索（122 个去重项目）观察，AI Agent 与 RAG 领域占据绝对主流。 超高星项目 ECC（241k）与 Hermes Agent（233k）聚焦智能体性能优化与自主成长，标志着社区正从“能做 Agent”迈向“做好 Agent”。 轻量化、本地化 AI 工具（AnythingLLM、Ollama、Cherry Studio 等）持续升温，隐私优先与自托管成为重要卖点。 RAG 涌现“无向量”检索（PageIndex）和知识图谱解析（Graphify）等新路线，正在挑战传统向量数据库的单一方案。 “从零构建”类教学项目（learn-claude-code、tiny-llm、hello-agents）活跃，开发者对原理性知识...</description>
      <content:encoded><![CDATA[<h1>AI 开源趋势日报 2026-08-20</h1>
<blockquote>
<p>数据来源: GitHub Trending + GitHub Search API（含 AI 与大数据 / 数据分析 / 数据挖掘趋势） | 生成时间: 2026-08-20 04:55 UTC</p>
</blockquote>
<hr>
<h1>AI 开源趋势日报（2026-08-20）</h1>
<h2>1. 今日速览</h2>
<ul>
<li>今日 GitHub Trending 榜单未抓取到，但通过主题搜索（122 个去重项目）观察，AI Agent 与 RAG 领域占据绝对主流。</li>
<li>超高星项目 ECC（241k）与 Hermes Agent（233k）聚焦智能体性能优化与自主成长，标志着社区正从“能做 Agent”迈向“做好 Agent”。</li>
<li>轻量化、本地化 AI 工具（AnythingLLM、Ollama、Cherry Studio 等）持续升温，隐私优先与自托管成为重要卖点。</li>
<li>RAG 涌现“无向量”检索（PageIndex）和知识图谱解析（Graphify）等新路线，正在挑战传统向量数据库的单一方案。</li>
<li>“从零构建”类教学项目（learn-claude-code、tiny-llm、hello-agents）活跃，开发者对原理性知识的渴求显著上升。</li>
</ul>
<h2>2. 各维度热门项目</h2>
<h3>🔧 AI 基础工具</h3>
<ul>
<li><a href="https://github.com/pytorch/pytorch">pytorch/pytorch</a> ⭐102,492 — 核心深度学习框架，仍是 AI 研究与生产的底座。</li>
<li><a href="https://github.com/huggingface/transformers">huggingface/transformers</a> ⭐164,271 — 最主流的模型定义与微调框架，覆盖文本、视觉与多模态。</li>
<li><a href="https://github.com/vllm-project/vllm">vllm-project/vllm</a> ⭐89,487 — 高吞吐 LLM 推理引擎，生产级部署的事实标准之一。</li>
<li><a href="https://github.com/ollama/ollama">ollama/ollama</a> ⭐179,000 — 一键本地运行多种开源大模型的 CLI，推动 AI 平民化。</li>
<li><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a> ⭐144,592 — Agent/RAG 应用开发框架，生态庞大。</li>
<li><a href="https://github.com/gradio-app/gradio">gradio-app/gradio</a> ⭐43,390 — 快速构建机器学习演示应用，加速模型展示与分享。</li>
<li><a href="https://github.com/ultralytics/ultralytics">ultralytics/ultralytics</a> ⭐60,778 — YOLO 系列目标检测与视觉任务工具箱，工业落地广泛。</li>
</ul>
<h3>🤖 AI 智能体/工作流</h3>
<ul>
<li><a href="https://github.com/affaan-m/ECC">affaan-m/ECC</a> ⭐241,223 — Agent 性能优化系统，提供技能、记忆、安全等模块，今日热度极高。</li>
<li><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a> ⭐233,143 — “与你共同成长”的自主智能体，强调持续学习与适应。</li>
<li><a href="https://github.com/Significant-Gravitas/AutoGPT">Significant-Gravitas/AutoGPT</a> ⭐186,689 — 通用自主 AI 智能体的开创者，愿景是人人可用的 AI。</li>
<li><a href="https://github.com/browser-use/browser-use">browser-use/browser-use</a> ⭐109,794 — 让 AI 代理像人一样操作浏览器，是 Agent 上网的关键工具。</li>
<li><a href="https://github.com/thedotmack/claude-mem">thedotmack/claude-mem</a> ⭐91,280 — 为所有 Agent 提供跨会话持久记忆，解决上下文丢失痛点。</li>
<li><a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a> ⭐47,195 — 超轻量、自托管的个人 AI Agent 框架，支持 MCP 与多智能体。</li>
<li><a href="https://github.com/Hmbown/CodeWhale">Hmbown/CodeWhale</a> ⭐40,827 — Rust 编写的终端编码智能体，强调可扩展性与社区共建。</li>
<li><a href="https://github.com/langchain-ai/langgraph">langchain-ai/langgraph</a> ⭐40,060 — 构建有弹性、可观测的 Agent 编排框架。</li>
</ul>
<h3>📦 AI 应用</h3>
<ul>
<li><a href="https://github.com/langgenius/dify">langgenius/dify</a> ⭐152,954 — 一站式 Agentic 工作流与 RAG 应用平台，支持云端/私有化部署。</li>
<li><a href="https://github.com/open-webui/open-webui">open-webui/open-webui</a> ⭐149,296 — 高人气自托管 AI 聊天界面，兼容 Ollama 与 OpenAI API。</li>
<li><a href="https://github.com/harry0703/MoneyPrinterTurbo">harry0703/MoneyPrinterTurbo</a> ⭐111,341 — 输入主题即可一键生成高清短视频的 AI 自动化工作流。</li>
<li><a href="https://github.com/Mintplex-Labs/anything-llm">Mintplex-Labs/anything-llm</a> ⭐64,942 — 本地优先的全功能 AI 助手，支持私有知识库与多模型。</li>
<li><a href="https://github.com/ZhuLinsen/daily_stock_analysis">ZhuLinsen/daily_stock_analysis</a> ⭐63,415 — LLM 驱动的多市场股票智能分析系统，含行情、新闻与自动推送。</li>
<li><a href="https://github.com/CherryHQ/cherry-studio">CherryHQ/cherry-studio</a> ⭐50,803 — 集成 300+ 助手与自主智能体的 AI 生产力工作室。</li>
<li><a href="https://github.com/hugohe3/ppt-master">hugohe3/ppt-master</a> ⭐48,062 — 将文档/主题转化为原生 PowerPoint，支持动画、图表与模板。</li>
<li><a href="https://github.com/666ghj/BettaFish">666ghj/BettaFish</a> ⭐42,044 — 多 Agent 舆情分析助手，从零实现，不依赖框架。</li>
</ul>
<h3>🧠 大模型/训练</h3>
<ul>
<li><a href="https://github.com/open-compass/opencompass">open-compass/opencompass</a> ⭐7,320 — LLM 评测平台，支持 100+ 数据集与主流模型，是模型迭代的重要参照。</li>
<li><a href="https://github.com/skyzh/tiny-llm">skyzh/tiny-llm</a> ⭐4,509 — 在 Apple Silicon 上从零构建微型 vLLM 推理系统，最佳教学项目。</li>
<li><a href="https://github.com/llm-jp/awesome-japanese-llm">llm-jp/awesome-japanese-llm</a> ⭐1,425 — 日语 LLM 综合资源列表，反映多语言模型社区活跃度。</li>
<li><a href="https://github.com/testtimescaling/testtimescaling.github.io">testtimescaling/testtimescaling.github.io</a> ⭐113 — 关于 LLM 测试时扩展的综述仓库，梳理“what/how/where/well”。</li>
<li><a href="https://github.com/AarambhDevHub/aarambh-studio">AarambhDevHub/aarambh-studio</a> ⭐78 — 纯 Rust + Candle 构建的解码器 LLM，支持 MoE 与多模态，探索轻量级训练路线。</li>
</ul>
<h3>🔍 RAG/知识库</h3>
<ul>
<li><a href="https://github.com/Graphify-Labs/graphify">Graphify-Labs/graphify</a> ⭐108,409 — 将代码库、文档、配置转为确定性知识图谱，无需向量库，适合代码理解。</li>
<li><a href="https://github.com/infiniflow/ragflow">infiniflow/ragflow</a> ⭐88,869 — 领先的开源 RAG 引擎，深度融合 Agent 与上下文层。</li>
<li><a href="https://github.com/mem0ai/mem0">mem0ai/mem0</a> ⭐63,639 — AI Agent 的通用记忆层，实现跨会话持久化。</li>
<li><a href="https://github.com/run-llama/llama_index">run-llama/llama_index</a> ⭐51,749 — 领先的文档 Agent 与 OCR 平台，支持复杂 RAG 场景。</li>
<li><a href="https://github.com/milvus-io/milvus">milvus-io/milvus</a> ⭐45,704 — 云原生高性能向量数据库，支撑大规模向量检索。</li>
<li><a href="https://github.com/VectifyAI/PageIndex">VectifyAI/PageIndex</a> ⭐35,259 — 基于推理的“无向量”RAG 文档索引，降低存储与 token 成本。</li>
<li><a href="https://github.com/qdrant/qdrant">qdrant/qdrant</a> ⭐34,074 — 高性能向量数据库兼搜索引擎，面向下一代 AI。</li>
<li><a href="https://github.com/lancedb/lancedb">lancedb/lancedb</a> ⭐11,198 — 嵌入式多模态检索库，开发者友好的本地 RAG 方案。</li>
</ul>
<h2>3. 趋势信号分析</h2>
<p>今日开源 AI 社区呈现三个明确信号：第一，Agent 工程化正在成为主战场——ECC、Hermes Agent、claude-mem 等超高分项目不再停留在“演示型 Agent”，而是深入性能优化、记忆持久化、跨工具编排等生产级问题，说明行业已从“概念验证”进入“基础设施打磨”阶段。第二，轻量本地化与“无向量”新范式并行：Ollama、AnythingLLM、Cherry Studio 等强调数据隐私和零成本运行，同时 PageIndex、Graphify 跳出传统向量数据库思路，用推理和知识图谱实现更低成本、更可解释的检索，这可能重塑 RAG 技术栈。第三，教育型资源爆发：learn-claude-code、tiny-llm、hello-agents 等“手写 AI”项目获得大量关注，反映出社区在快速应用工具后渴望深入原理，形成“产-学”闭环。此外，Ollama 迅速支持 Kimi、GLM 等新模型，显示本地部署生态与最新模型发布节奏的强耦合。</p>
<h2>4. 社区关注热点</h2>
<ul>
<li><strong>Agent 性能优化与记忆管理</strong>：ECC、claude-mem、mem0 等解决了 Agent 在长任务中“失忆”和“低效”的问题，是构建可靠 Agent 的刚需。</li>
<li><strong>“无向量”RAG 与知识图谱</strong>：PageIndex 和 Graphify 提供了不依赖嵌入向量的新路径，在成本、可解释性和特定领域（如代码）上有显著优势。</li>
<li><strong>本地优先的 AI 助手</strong>：AnythingLLM、Cherry Studio、nanobot 让个人用户和中小企业无需云端即可获得完整 AI 能力，符合隐私合规趋势。</li>
<li><strong>从零手写 AI 系统</strong>：tiny-llm、learn-claude-code、Aarambh-studio 等项目是深入理解 AI 原理的绝佳教材，适合开发者提升技术深度。</li>
<li><strong>多语言与垂直领域模型生态</strong>：awesome-japanese-llm、Finance-LLMs 等表明社区正在围绕具体语言和行业构建专门知识库与工具链，是细分机会所在。</li>
</ul>
<hr>
<p><em>本日报由 <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a> 自动生成。</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>AI Open Source Trends 2026-08-20</title>
      <link>https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-trending-en</link>
      <guid isPermaLink="true">https://huang-yi-dae.github.io/agents-radar/#2026-08-20/ai-trending-en</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      <description>AI Open Source Trends 2026-08-20 Sources: GitHub Trending + GitHub Search API (AI, big data, data analysis, data mining trends) | Generated: 2026-08-20 04:55 UTC AI / ML / Data Open Source Trends Report — 2026-08-20 Note: GitHub Today&amp;#39;s Trending was unavailable; this report is based on 122 deduplicated AI-related repositories from GitHub Topic Search, reflecting projects active in the last 7 days. 1. Today&amp;#39;s Highlights The AI open-source ecosystem remains intensely concentrated on AI age...</description>
      <content:encoded><![CDATA[<h1>AI Open Source Trends 2026-08-20</h1>
<blockquote>
<p>Sources: GitHub Trending + GitHub Search API (AI, big data, data analysis, data mining trends) | Generated: 2026-08-20 04:55 UTC</p>
</blockquote>
<hr>
<h1>AI / ML / Data Open Source Trends Report — 2026-08-20</h1>
<p><em>Note: GitHub Today&#39;s Trending was unavailable; this report is based on 122 deduplicated AI-related repositories from GitHub Topic Search, reflecting projects active in the last 7 days.</em></p>
<hr>
<h2>1. Today&#39;s Highlights</h2>
<p>The AI open-source ecosystem remains intensely concentrated on AI agents, with agent harnesses and coding agents (hermes-agent at 233k stars, AutoGPT at 186k, browser-use at 109k, learn-claude-code at 74k) commanding the largest communities. The RAG stack is visibly shifting from vector-only retrieval toward knowledge-graph and memory-based architectures — Graphify (108k) explicitly eliminates the vector store, while claude-mem (91k) and mem0 (63k) reframe retrieval as persistent agent memory. Token-efficiency tooling has emerged as a fresh niche: caveman (99k) and headroom (66k) both attack the cost of agentic workloads, signaling that token spend is now a first-class engineering concern. Terminal-native coding agents in systems languages (CodeWhale in Rust, DeepSeek-Reasonix in Go) point to an infrastructure layer maturing beyond Python-only tooling. Finally, vertical applications — finance (daily_stock_analysis), job search (career-ops), presentations (ppt-master), and public-opinion analysis (BettaFish) — demonstrate a wave of practical, domain-specific AI deployments.</p>
<hr>
<h2>2. Top Projects by Category</h2>
<h3>🔧 AI Infrastructure</h3>
<ul>
<li><strong><a href="https://github.com/langchain-ai/langchain">langchain-ai/langchain</a></strong> ⭐144,592 — The agent engineering platform and most widely adopted framework for building LLM-powered chains, tools, and agents.</li>
<li><strong><a href="https://github.com/ollama/ollama">ollama/ollama</a></strong> ⭐179,000 — Local LLM runtime with one-command model serving, now the default entry point for running open-weight models on developer machines.</li>
<li><strong><a href="https://github.com/vllm-project/vllm">vllm-project/vllm</a></strong> ⭐89,487 — High-throughput, memory-efficient LLM inference and serving engine that has become the de facto standard for self-hosted serving.</li>
<li><strong><a href="https://github.com/firecrawl/firecrawl">firecrawl/firecrawl</a></strong> ⭐169,732 — The &quot;context API&quot; for search, scraping, and web interaction at scale, positioning itself as essential data plumbing for LLM applications.</li>
<li><strong><a href="https://github.com/huggingface/transformers">huggingface/transformers</a></strong> ⭐164,271 — The model-definition framework for state-of-the-art ML across text, vision, audio, and multimodal tasks.</li>
<li><strong><a href="https://github.com/0xPlaygrounds/rig">0xPlaygrounds/rig</a></strong> ⭐8,326 — Modular Rust framework for building scalable LLM applications, standing out in the growing Rust AI ecosystem.</li>
<li><strong><a href="https://github.com/headroomlabs-ai/headroom">headroomlabs-ai/headroom</a></strong> ⭐66,918 — Compresses tool outputs, logs, and RAG chunks before they reach the LLM, cutting token usage by 20% for coding agents and 60–95% for JSON.</li>
<li><strong><a href="https://github.com/Eigenwise/atomic-agents">Eigenwise/atomic-agents</a></strong> ⭐6,186 — Builds AI agents &quot;atomically&quot; with composable, reusable primitives for agent engineering.</li>
</ul>
<h3>🤖 AI Agents / Workflows</h3>
<ul>
<li><strong><a href="https://github.com/NousResearch/hermes-agent">NousResearch/hermes-agent</a></strong> ⭐233,143 — &quot;The agent that grows with you,&quot; a personal AI agent from the Hermes model lineage with the largest agent-community footprint in this dataset.</li>
<li><strong><a href="https://github.com/Significant-Gravitas/AutoGPT">Significant-Gravitas/AutoGPT</a></strong> ⭐186,689 — The long-standing open-source vision for accessible autonomous agents; remains the reference point for agentic workflows.</li>
<li><strong><a href="https://github.com/browser-use/browser-use">browser-use/browser-use</a></strong> ⭐109,794 — Makes websites accessible to AI agents, enabling browser automation at scale and powering the &quot;computer-use&quot; wave.</li>
<li><strong><a href="https://github.com/shareAI-lab/learn-claude-code">shareAI-lab/learn-claude-code</a></strong> ⭐74,711 — A nano Claude Code-like agent harness built from 0 to 1 in pure Bash; a learning-native project that has exploded in popularity.</li>
<li><strong><a href="https://github.com/HKUDS/nanobot">HKUDS/nanobot</a></strong> ⭐47,195 — Ultra-lightweight, self-hosted personal AI agent framework in Python with WebUI, tools, memory, MCP, and multi-agent workflows.</li>
<li><strong><a href="https://github.com/zhayujie/CowAgent">zhayujie/CowAgent</a></strong> ⭐46,580 — Open-source super AI assistant and agent harness (formerly chatgpt-on-wechat) that plans tasks, runs tools, and self-evolves with memory.</li>
<li><strong><a href="https://github.com/Hmbown/CodeWhale">Hmbown/CodeWhale</a></strong> ⭐40,827 — Open-source terminal coding agent written in Rust, emphasizing continuous community improvement.</li>
<li><strong><a href="https://github.com/esengine/DeepSeek-Reasonix">esengine/DeepSeek-Reasonix</a></strong> ⭐34,886 — DeepSeek-native terminal coding agent engineered around prefix-cache stability, built in Go.</li>
</ul>
<h3>📦 AI Applications</h3>
<ul>
<li><strong><a href="https://github.com/harry0703/MoneyPrinterTurbo">harry0703/MoneyPrinterTurbo</a></strong> ⭐111,341 — One-click AI short-video generation from a topic or keyword using LLM-driven automated workflows.</li>
<li><strong><a href="https://github.com/Mintplex-Labs/anything-llm">Mintplex-Labs/anything-llm</a></strong> ⭐64,942 — Local-first, own-your-intelligence desktop and self-hosted LLM workspace with full RAG and agent capabilities.</li>
<li><strong><a href="https://github.com/santifer/career-ops">santifer/career-ops</a></strong> ⭐65,939 — Open-source AI job search: scans job portals, scores listings with a structured A–F rubric, and tailors CVs from your AI coding CLI.</li>
<li><strong><a href="https://github.com/ZhuLinsen/daily_stock_analysis">ZhuLinsen/daily_stock_analysis</a></strong> ⭐63,415 — LLM-powered multi-market stock analysis system with multi-source market data, real-time news, decision dashboards, and automated notifications.</li>
<li><strong><a href="https://github.com/CherryHQ/cherry-studio">CherryHQ/cherry-studio</a></strong> ⭐50,803 — AI productivity studio with smart chat, autonomous agents, 300+ assistants, and unified access to frontier LLMs.</li>
<li><strong><a href="https://github.com/hugohe3/ppt-master">hugohe3/ppt-master</a></strong> ⭐48,062 — AI turns documents or topics into real native PowerPoint decks with shapes, transitions, animations, charts, and audio narration.</li>
<li><strong><a href="https://github.com/666ghj/BettaFish">666ghj/BettaFish</a></strong> ⭐42,044 — Multi-agent public-opinion analysis assistant built from scratch, breaking information cocoons, forecasting trends, and supporting decisions.</li>
<li><strong><a href="https://github.com/ScrapeGraphAI/Scrapegraph-ai">ScrapeGraphAI/Scrapegraph-ai</a></strong> ⭐29,753 — AI-powered Python scraper that converts natural-language queries into structured extraction pipelines.</li>
</ul>
<h3>🧠 LLMs / Training</h3>
<ul>
<li><strong><a href="https://github.com/tensorflow/tensorflow">tensorflow/tensorflow</a></strong> ⭐197,070 — The original open-source ML framework and one of the most-starred AI repositories in history.</li>
<li><strong><a href="https://github.com/pytorch/pytorch">pytorch/pytorch</a></strong> ⭐102,492 — Tensors and dynamic neural networks with strong GPU acceleration; the default research and production training framework.</li>
<li><strong><a href="https://github.com/keras-team/keras">keras-team/keras</a></strong> ⭐64,242 — &quot;Deep Learning for humans,&quot; the high-level API now on Keras 3 with multi-backend support.</li>
<li><strong><a href="https://github.com/open-compass/opencompass">open-compass/opencompass</a></strong> ⭐7,320 — LLM evaluation platform covering 100+ datasets and a broad range of open and proprietary models, from Llama to GPT-4.</li>
<li><strong><a href="https://github.com/skyzh/tiny-llm">skyzh/tiny-llm</a></strong> ⭐4,509 — Build a tiny vLLM + Qwen on Apple Silicon to learn LLM inference systems; an outstanding systems-education resource.</li>
<li><strong><a href="https://github.com/AarambhDevHub/aarambh-studio">AarambhDevHub/aarambh-studio</a></strong> ⭐78 — Decoder-only LLM built from scratch in pure Rust with Candle, featuring Gated DeltaNet, sparse attention, and fine-grained MoE.</li>
<li><strong><a href="https://github.com/llm-jp/awesome-japanese-llm">llm-jp/awesome-japanese-llm</a></strong> ⭐1,425 — The definitive overview of Japanese LLMs, tracking a fast-growing non-English model ecosystem.</li>
</ul>
<h3>🔍 RAG / Knowledge</h3>
<ul>
<li><strong><a href="https://github.com/langgenius/dify">langgenius/dify</a></strong> ⭐152,954 — The leading open-source platform for agentic workflows and RAG pipelines, deployable on cloud, VPC, or self-hosted.</li>
<li><strong><a href="https://github.com/Graphify-Labs/graphify">Graphify-Labs/graphify</a></strong> ⭐108,409 — Turns any codebase, docs, SQL schemas, and PDFs into a queryable knowledge graph via deterministic AST parsing — no vector store required.</li>
<li><strong><a href="https://github.com/thedotmack/claude-mem">thedotmack/claude-mem</a></strong> ⭐91,280 — Captures agent session activity, compresses it with AI, and injects relevant context back into future sessions — persistent memory for every agent.</li>
<li><strong><a href="https://github.com/infiniflow/ragflow">infiniflow/ragflow</a></strong> ⭐88,869 — Leading open-source RAG engine fusing deep document understanding with agent capabilities as the context layer for LLMs.</li>
<li><strong><a href="https://github.com/mem0ai/mem0">mem0ai/mem0</a></strong> ⭐63,639 — Universal memory layer for AI agents, enabling long-term, self-hosted memory across sessions.</li>
<li><strong><a href="https://github.com/run-llama/llama_index">run-llama/llama_index</a></strong> ⭐51,749 — The leading document agent and OCR platform for connecting enterprise data to LLMs.</li>
<li><strong><a href="https://github.com/milvus-io/milvus">milvus-io/milvus</a></strong> ⭐45,704 — High-performance, cloud-native vector database built for scalable vector ANN search.</li>
<li><strong><a href="https://github.com/qdrant/qdrant">qdrant/qdrant</a></strong> ⭐34,074 — High-performance, massive-scale vector database and search engine for next-generation AI applications.</li>
</ul>
<hr>
<h2>3. Trend Signal Analysis</h2>
<p>The most explosive community attention is concentrated on agent harnesses and coding agents. Projects like hermes-agent, learn-claude-code, ECC, and CodeWhale show developers standardizing on agent scaffolds that attach to Claude Code, Codex, Cursor, and other CLI ecosystems. Tellingly, several of the fastest-growing projects are not model providers but &quot;agent skill layers&quot; — ECC, scientific-agent-skills, caveman, and learn-claude-code — suggesting the competition has shifted from models to agent capabilities and craft.</p>
<p>A distinct new direction is token-efficiency tooling: caveman (99k, &quot;why use many token when few token do trick&quot;) and headroom (66k, 60–95% token reduction on JSON) both attack the cost of agentic workloads, a signal that token spend is now a first-class engineering concern. Knowledge-graph RAG is also displacing pure vector search — Graphify explicitly eliminates the vector store, while cognee, mem0, and claude-mem reframe RAG as persistent agent memory rather than one-shot retrieval infrastructure.</p>
<p>On the tech-stack front, Rust and Go are penetrating AI infrastructure: rig, qdrant, zvec, lancedb, and meilisearch in Rust; CodeWhale, DeepSeek-Reasonix, and RAGFlow in Go. The strong presence of Chinese-origin projects (CowAgent, QwenPaw, BettaFish, daily_stock_analysis, JeecgBoot) indicates a parallel, rapidly maturing ecosystem serving Chinese-language and global users. These trends connect directly to recent open-weight releases — DeepSeek-native tooling, Qwen-based assistants, and Kimi/GLM support in Ollama — showing that open-source infrastructure is tightly tracking the frontier of new LLM releases.</p>
<hr>
<h2>4. Community Hot Spots</h2>
<ul>
<li><strong>Claude Code / coding-agent skill ecosystem</strong> — learn-claude-code, claude-mem, caveman, ECC, and scientific-agent-skills are all built around coding CLIs; this is where the most active developer experimentation is happening right now.</li>
<li><strong>Agent memory layers</strong> — mem0, claude-mem, and cognee are racing to define persistent, self-hosted memory for agents; memory is quickly becoming the moat in agent architecture.</li>
<li><strong>Token-efficiency and cost compression</strong> — caveman and headroom demonstrate that minimizing token consumption is now a major optimization axis for production agent workloads, with 60–95% cost reductions on structured data.</li>
<li><strong>Knowledge-graph RAG without vector stores</strong> — Graphify&#39;s deterministic AST-parsing approach challenges vector-database assumptions and is worth watching as a potential new RAG paradigm.</li>
<li><strong>Vertical AI applications in finance and careers</strong> — daily_stock_analysis, Finance-LLMs, and career-ops show strong community appetite for practical, high-value domain tools built on agent frameworks rather than general-purpose chatbots.</li>
</ul>
<hr>
<p><em>This digest is auto-generated by <a href="https://github.com/huang-yi-dae/agents-radar">agents-radar</a>.</em></p>
]]></content:encoded>
    </item>
  </channel>
</rss>
