如果你在写agent循环，试试把监控逻辑和校验逻辑拆成两套独立循环，思路会更清晰。
Jerry Liu在推特中提出，agent循环应拆分为两种独立类型。前向压力循环用于无聊天输入时持续监控环境的自主agent。反向压力循环负责爬山算法和确保输出正确，包括测试、验证和性能测试。这种分离可以理清原本杂糅的逻辑。
agent loops should be separated into two pieces: - "forward pressure loops" are how you get autonomo...
agent loops should be separated into two pieces: - "forward pressure loops" are how you get autonomous agents that continually monitor the environment without chat input - "backpressure loops" is hillclimbing and making sure the output is correct dex @dexhorthy is it possible that the idea of “loops” can be detangled into “forward pressure” (events, crons, while true loops, /goal nudges) that pushes new work / iteration, and “back pressure” (tests, verification, performance testing) that drives model inside a particular task/goal Have we (in)conveniently complected these separable concerns? How does the conversation evolve if we deal with each separately? 🔗 View Quoted Tweet 💬 2 🔄 0 ❤️ 8 👀 963 📊 3 ⚡