Skip to content

Persist agent service state instead of keeping agents only in memory #5267

Open

Description

@bobbai00

Task Summary

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.

Sessions today and after

Task Type

  • Refactor / Cleanup
  • DevOps / Deployment / CI
  • Testing / QA
  • Documentation
  • Performance
  • Other

Activity

  1. added theissue type on May 28, 2026
  2. added 2 commits that reference this issue on Jun 5, 2026
    460d4f5
    e47c3fd
  3. bobbai00 commented on Nov 16, 2026

    @bobbai00
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions