Repository navigation
feat(dashboard): Show conversation memories in popovers - #2641
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This comment has been minimized.
This comment has been minimized.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
Author
|
The |
thomasjiangcy
approved these changes
Nov 4, 2026
Recalled memories open from a chip under the prompt that recalled them, and captured memories open from a row at the end of the Turn that captured them. Details show recalled and captured counts and open one list that jumps to each memory in the transcript. The memory API now returns each recall and capture with its Turn. The plugin event reader returns the Turn id to make that possible. Co-Authored-By: Thomas Jiang <20501235+thomasjiangcy@users.noreply.github.com>
…call A recalled memory that is also in a capture snapshot now still needs store access, so a captured private memory does not show as recalled to other viewers. A prompt that starts more than one Turn shows a Recalled chip for each Turn. Co-Authored-By: Thomas Jiang <20501235+thomasjiangcy@users.noreply.github.com>
sentry-junior
Bot
force-pushed
the
feat/dashboard-memory-popovers
branch
from
November 4, 2026 07:41
150f780 to
9b93ad8
Compare
Contributor
|
33 screenshot changes — 27 changed · 6 added · 0 removed Review screenshots in Frameshift
Show 12 more changed screenshots
9 more changed screenshots in Frameshift. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9b93ad8. Configure here.
Event, context, and Automation prompts now show their Recalled chips, so a memory list jump can find their Turns. A jump now waits for the transcript and clears a search that would hide the row.
This branch was successfully deployed
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.
Shows which memories a conversation recalled and captured, tied to the turn that did it. This follows the popover design agreed in #team-spec-eng.
Transcript
Details panel
N recalled · N captured).API (hard cutover)
PluginConversationEventRecordnow includes an optionalturnId./conversations/:id/memoriesreturns{ events: [{ memoryIds, source, turnId }], memories: [{ id, content, visibility }] }. Recalled memories resolve from the store for the viewer. Captured memories come from the event snapshot.Out of scope
Open question: a captured private memory still shows to anyone who can see the conversation's private content, as before. A recalled private memory shows only to its owner. We should pick one rule.
Testing
conversation-details.spec.ts) pass.tests/unit/conversations/web-batch-messages.test.ts(webActorFromEmail), the same as on main.via @thomasjiangcy.
--
View Session [Sentry]