fix: strip profile embedding vectors from public responses - #343
Merged
EyJunge1 merged 1 commit intoOct 1, 2026
Merged
Conversation
Keep centroid/anchor for internal similarity and pending cleanup apply, but omit them from memory-tool profile reads and profile API payloads so responses stay small enough for the model and UI. Based on work by share121 in tickernelz#304.
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
1 participant
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
centroid/anchorembeddings from public profile payloads (memory toolprofilemode,GET /api/user-profile, profile snapshots, and AI-cleanup preview responses).pendingCleanupsfor apply/merge viatoPublicProfileData(clone + strip).main(no unrelated v2/index.jscommits). Credit to @share121 for the original approach.Test plan
bun test tests/profile-utils.test.tsbun test tests/api-handlers-profile-strip.test.tsmode: "profile"output has nocentroid/anchorGET /api/user-profilepayload stays small and UI still renders preferences/patterns/workflows