You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Persist agent service state instead of keeping agents only in memory #5267
Agents live only in the agent service's memory, so a restart or a second replica loses every conversation.
Store each conversation (its message list, settings and owner) and load it when needed. Once #9455 lands, the message list is the whole conversation, so the step tree no longer needs storing. Where to store it is still open: a table of the agent service's own, or a resource kind from #9395.
Done when a restart keeps every conversation and any replica can serve one. Who may open a conversation is #5268.
Moved out of #9453. Saving conversations waits for the resource unification in #9395, where a conversation becomes a resource kind with its owner, its versions and access control. Once #9455 lands, the message list is the whole conversation, so that list is what gets stored.
Activity
Add DKNet Agent and remove DB credentials from the CU(#10)
feat: make the DKNet agent more robust (#15)
bobbai00 commentedon Nov 16, 2026
Moved out of #9453. Saving conversations waits for the resource unification in #9395, where a conversation becomes a resource kind with its owner, its versions and access control. Once #9455 lands, the message list is the whole conversation, so that list is what gets stored.