Repository navigation
refactor(history): read execution history from Codex on demand - #61
Merged
Merged
Conversation
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.
Why
用户要求执行历史由 Codex 保存,查看时按需读取。Agent Loop 停止长期保存第二套执行轨迹。
What changed
Scope
覆盖看板、实时通知和飞书进度。业务输入输出、汇报、审批及任务状态继续持久保存。不处理旧 Thread,不迁移旧轨迹,不部署或清理生产数据。
Tradeoffs
历史读取依赖 Codex。未知增量位置保留重读提示。缺口身份因内存上限被淘汰后,运行中的历史保持保守提示,完整结束后可以恢复。
Blast Radius
影响看板历史与飞书进度恢复。执行控制与历史读取分离,读取不能恢复 Thread、启动 Turn 或回答审批。
Verification
最终独立复查因模型连接错误未能返回结论。前两轮复查发现的问题均有修正及回归测试。