Repository navigation
告诉角色:写给规划者的信会开一个规划者回合 - #454
Merged
Merged
Conversation
工程师习惯把“已开始”“已完成”这类进度直接写给规划者,规划者读完无事可做, 收尾信还会再告诉它一遍。#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 里规划者 85% 的回合没写任何信。#453 让抄送不再叫醒规划者,但对照里没有可测的效果:工程师并不抄送,而是把“t1 已开始”“t1 已完成并提交”这类进度直接写给规划者。规划者读完无事可做,任务的收尾信还会再告诉它一遍。
改了什么
各角色“怎么写信”的说明里加一句事实:
没有改代码逻辑,写不写仍由角色决定。
对照
同一个请求(让规划者拆四个任务做一个 Python 小工具,三个并行,一个依赖前三个),每组 4 个项目,Codex + gpt-6.1-sol:
局限
🤖 Generated with Claude Code