supermemory/apps
abhay-codes07 8129fec5d6
fix(extension): stop fragmenting memories that contain commas or newlines
The Included Memories popup stores the memory list on a data-* attribute by
joining it into a single string (String(response.data) / response.data), then
reads it back by splitting on [,\n] in showMarkerPopover and in the T3 popup.
Memory text is free-form and frequently contains commas and newlines, so a
single memory was fragmented into several rows. In T3 that also desynced the
per-item delete: the clicked index no longer mapped to a real memory, so
removal spliced the wrong entry and rewrote the injected prompt from the
mangled list.

Store the list as JSON on the attribute and parse it back, so a memory with a
comma or newline survives as one item. serializeMemoriesForDataset returns an
empty string for an empty list so existing "memories present" truthiness checks
on the attribute are unchanged, and parseMemoriesFromDataset falls back to the
old delimiter split for any legacy value. This is confined to the popup's own
display data: the GET_RELATED_MEMORIES response and the injected
dataset.supermemories prompt text are left exactly as they were, so recall
behaviour does not change. Applied consistently across ChatGPT, Claude, Gemini
and T3, with unit tests for the round-trip.
2026-07-22 20:37:37 +05:30
..
browser-extension fix(extension): stop fragmenting memories that contain commas or newlines 2026-07-22 20:37:37 +05:30
docs fix(docs): prefix raw internal href/src literals with /docs (#1333) 2026-07-22 00:40:16 -07:00
mcp docs: restructure documentation site and update integration UI (#1331) 2026-07-21 20:19:30 -07:00
memory-graph-playground fix(deps): bump next to 16.0.7 in memory-graph-playground (critical CVE) (#1082) 2026-06-16 21:10:32 -07:00
raycast-extension feat: mobile responsive, lint formats, toast, render issue fix (#688) 2026-01-21 03:11:53 +00:00
web docs: restructure documentation site and update integration UI (#1331) 2026-07-21 20:19:30 -07:00