Merged
Conversation
We had only one "sessions" table that contained a json blob with all the messages of a session. This was bad, especially for session updates. This change extracts the session messages into its own table. A nice change that comes with this is that we now save the messages in real time and not only when the loop ends. This also marks a slow start of moving things out of the runtime which is starting to get crowded. Signed-off-by: Djordje Lukic <djordje.lukic@docker.com>
When the session store fails to open or migrate, backup the existing database file (and WAL/SHM files) and attempt to start fresh. This prevents users from being locked out due to corrupt or incompatible database files. Signed-off-by: Djordje Lukic <djordje.lukic@docker.com>
Contributor
Is there anything I can do? Whether it's related to this or something general. @rumpl |
Member
Author
|
@Pnkcaht here's what you can do:
Thanks |
Member
|
@rumpl works for me. cagent took a second or two to start |
dgageot
approved these changes
Jan 28, 2026
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.
Refactor session persistence. A new PersistentRuntime wrapper intercepts runtime events (new events, not sent back to the caller: MessageAddedEvent, SubSessionCompletedEvent, SummaryAddedEvent) and persists session changes to the store. The runtime has very little store things left, to be removed in a followup.
The database schema is normalized with a new
session_itemstable for messages, summaries, and sub-session references, replacing the previous JSON-encoded messages column. Migrations handle data conversion from the legacy format.