GenarrativeAI/Genarrative
11
0
Fork 0
Code Issues 14 Pull Requests 3 Actions Packages Projects 3 Releases Wiki Activity

AGC上下文丢失问题 #249

New Issue
Closed
opened 2026-09-02 16:12:29 +08:00 by k88936 · 4 comments
k88936 commented 2026-09-02 16:12:29 +08:00
Member
Copy Link
Copy Source

上下文丢失问题
image.png.png

当前实现:

AGC和codex进程间通信实现调用,

docs/project-memory/shared-memory/decision-log.md:7567
codex方面使用 "ephemeral": true, 它的会话数据只留在内存中, 只有AGC保存了会话数据.
当前没有有效的codex内部聊天记忆的恢复, codex进程崩溃后会丢失上下文

限制:
codex app-server 没有提供加载聊天历史的接口
codex持久化的jsonl结构我们使用的不同

上下文丢失问题 ![image.png.png](/attachments/4279048b-c372-447a-9f5a-62a06f9446cc) 当前实现: AGC和codex进程间通信实现调用, docs/project-memory/shared-memory/decision-log.md:7567 codex方面使用 "ephemeral": true, 它的会话数据只留在内存中, 只有AGC保存了会话数据. 当前没有有效的codex内部聊天记忆的恢复, codex进程崩溃后会丢失上下文 限制: ~~codex app-server 没有提供加载聊天历史的接口~~ codex持久化的jsonl结构我们使用的不同
image.png.png
311 KiB
k88936 commented 2026-09-02 16:21:56 +08:00
Author
Member
Copy Link
Copy Source

how:

  • 允许codex自己持久化会话历史, AGC保留thread ID, 恢复时回到同一个thread
    or
  • fork codex , 实现ThreadStore trait, 会话统一用AGC的jsonl保存加载(扯蛋
    or
  • 每次重启首个turn发送历史消息,,,,
how: * 允许codex自己持久化会话历史, AGC保留thread ID, 恢复时回到同一个thread or * fork codex , 实现ThreadStore trait, 会话统一用AGC的jsonl保存加载(扯蛋 or * 每次重启首个turn发送历史消息,,,,
k88936 added this to the 陶泥儿gameAgent project 2026-09-02 16:22:08 +08:00
k88936 commented 2026-09-02 16:49:07 +08:00
Author
Member
Copy Link
Copy Source

每次重启首个turn发送历史消息 吧

每次重启首个turn发送历史消息 吧
k88936 reopened this issue 2026-09-04 14:10:58 +08:00
k88936 commented 2026-09-04 14:13:38 +08:00
Author
Member
Copy Link
Copy Source

判断失误: codex存在thread/inject_items方法可以纳入会话历史

判断失误: codex存在thread/inject_items方法可以纳入会话历史
kdletters added the Kind/Bug label 2026-09-07 15:26:44 +08:00
kdletters commented 2026-09-07 17:44:59 +08:00
Member
Copy Link
Copy Source

This was generated by AI during triage.

#282 已采用 thread/inject_items 作为恢复方向，但该 PR 当前仍请求修改。最新阻塞是：历史读取或注入失败后，未完成初始化的线程仍留在连接池，重试会把它当作已创建线程复用并跳过注入，造成上下文永久丢失，部分注入成功时还可能重复或乱序。

请让恢复流程在任一步失败时淘汰线程/连接，并由重试重新创建、按 turn/回合记录幂等注入；补充进程重启、注入失败后重试、尾行损坏和长历史预算的回归测试。只有这些场景都能恢复，才能关闭上下文丢失问题。

> *This was generated by AI during triage.* #282 已采用 thread/inject_items 作为恢复方向，但该 PR 当前仍请求修改。最新阻塞是：历史读取或注入失败后，未完成初始化的线程仍留在连接池，重试会把它当作已创建线程复用并跳过注入，造成上下文永久丢失，部分注入成功时还可能重复或乱序。 请让恢复流程在任一步失败时淘汰线程/连接，并由重试重新创建、按 turn/回合记录幂等注入；补充进程重启、注入失败后重试、尾行损坏和长历史预算的回归测试。只有这些场景都能恢复，才能关闭上下文丢失问题。
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Kind/Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project 陶泥儿gameAgent
Assignees
Clear assignees
HuangJiaJia JenkenB k88936 (王德宇) kdletters (段舒康) laura2008 (王乐) lhk229 (孔令弘) Loer (农洛儿) loong suzmii (董羽秦) taobaisu (叶东旭) wuxiangwanzi (王子民) YixuanLiu ziyu
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GenarrativeAI/Genarrative#249
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?