Correct Recents timestamp age for newly sent messages#3994
Merged
louis030195 merged 1 commit intoJun 11, 2026
Merged
Conversation
louis030195
reviewed
Jun 11, 2026
louis030195
left a comment
Collaborator
There was a problem hiding this comment.
looks great, nice test coverage too fyi
louis030195
pushed a commit
that referenced
this pull request
Jun 11, 2026
Ships cloud pipes for enterprise builds: the new cloud entry in the pipes dropdown drives one managed GCP VM per org (provision/start/stop, org AI presets from the dashboard, team-shared + dashboard-managed pipes, per-pipe last-run state). Also ships the chat recents age fix (#3994) and pipes/engine route changes since v2.5.31. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
This PR fixes incorrect age labels in the chat
Recentssidebar where a newly sent message could still show an older value like51m.Changes
lastUserMessageAtfrom the actual saved user messages in the foreground save pathlastUserMessageAtduring chat metadata hydrationlastUserMessageAtin the background router save path so stale values are not reintroducedBefore -
Screen.Recording.2026-06-11.at.2.51.35.PM.mov
After -
Screen.Recording.2026-06-11.at.2.43.45.PM.mov