Repository navigation
抄送给规划者的信不再单独叫醒它，留到它下一回合一起读 - #453
Merged
Merged
Conversation
gifG（$913，6950 次调用）里规划者 3109 个回合有 2636 个什么都没写，花了 $93， 占总花费 10%。任何写给或抄送它的信都会开一个回合：抄送 1784 次，直接写 778 次。 抄送是知会，不要求收信人做事。现在只被抄送的规划者不被叫醒，信和任务内交接 放在一起，它下次因为写给它的信或任务关闭而醒来时读到。直接写给它的信照旧 立刻开回合。Argus 只改了送达的时机，没有替谁判断信重不重要。 各角色“怎么写信”的说明加半句，讲明抄送给规划者的信等它下一回合；规划者提示里 那一节的标题改为“抄送和任务内交接”。 Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Merged
lbx154
added a commit
that referenced
this pull request
Nov 11, 2026
工程师习惯把“已开始”“已完成”这类进度直接写给规划者，规划者读完无事可做， 收尾信还会再告诉它一遍。#453 只拦了抄送，拦不到这些。 在“怎么写信”的说明里加一句事实：写给规划者的信会开一个规划者回合，计划要改时 才写；做了什么、交付了什么，收尾信已经会告诉它。写不写仍由角色决定。 对照（同一个四任务项目，各 4 次，gpt-6.1-sol）： 改之前 规划者回合 38，中途写给规划者 20 封，总花费 $2.33 #453 规划者回合 38，中途写给规划者 19 封，总花费 $2.27 #453+这句 规划者回合 19，中途写给规划者 0 封，总花费 $2.00 三组都是 4/4 做完。 Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
为什么
gifG（p-a63b11e9，$913，6950 次调用）的记录：
任何写给或抄送规划者的信都会开一个回合。回合中途的信里，抄送给它的有 1784 次（工程师 1397，审查员 387），直接写给它的有 778 次。
改了什么
抄送是知会，不要求收信人做事。只被抄送的规划者不再被叫醒：信放进
project.beside，和任务内交接一起，等它下次因为写给它的信或任务关闭而醒来时读到。直接写给它的信照旧立刻开回合。Argus 只改了送达的时机，没有判断哪封信重要。
提示里跟着改了两处文字，都是对机制的如实描述：
Copies and hand-overs inside your tasks since your last turn。验证
beside。--preview-url的两个 CLI 测试），基线上同样失败。没验证的
没有用真实模型跑对照。这次改动不会去掉全部空回合：直接写给规划者的 778 次，以及任务关闭带来的回合仍然在。规划者被叫醒时每次重发整份任务清单的问题也没动。
🤖 Generated with Claude Code