fix: ensure most recent session metadata wins during gateway store merge #1823
+37
−11
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
thewilloftheshadow
added a commit
that referenced
this pull request
Jan 26, 2026
Member
|
Squash-merged on main. Commits:
Tests:
|
steipete
pushed a commit
to mertcicekci0/clawdbot
that referenced
this pull request
Jan 26, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
The web dashboard at
/sessionswas displaying an outdated timestamp (15d ago) for one of my sessions, while the/statuscommand issued in Telegram correctly displayed "updated just now" for the session. This PR fixes this by ensuring the most recently updated session entry takes precedence.Initial Prompt
The
/statuscommand is correctly showing the main session as 'updated just now', but the web dashboard at/sessionsis displaying an outdated 'updated 15 days ago' timestamp for the same session.Please investigate the root cause of this discrepancy. Identify why the
/statuscommand and the web dashboard are displaying different updatedAt timestamps for the same session, and ensure consistent session metadata across all Clawdbot interfaces.Notes