@remnic/import-supermemory 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +94 -0
- package/package.json +1 -1
package/README.md
ADDED
|
@@ -0,0 +1,94 @@
|
|
|
1
|
+
# @remnic/import-supermemory
|
|
2
|
+
|
|
3
|
+
Import a Supermemory JSON export into Remnic.
|
|
4
|
+
|
|
5
|
+
This package is an optional companion for `@remnic/cli`. Install it only when
|
|
6
|
+
you want to migrate memories out of Supermemory and into Remnic's local memory
|
|
7
|
+
store.
|
|
8
|
+
|
|
9
|
+
## Install
|
|
10
|
+
|
|
11
|
+
```bash
|
|
12
|
+
npm install -g @remnic/cli
|
|
13
|
+
npm install -g @remnic/import-supermemory
|
|
14
|
+
```
|
|
15
|
+
|
|
16
|
+
If you use Remnic from a project instead of globally, add both packages to the
|
|
17
|
+
same project:
|
|
18
|
+
|
|
19
|
+
```bash
|
|
20
|
+
pnpm add @remnic/cli @remnic/import-supermemory
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
## Export From Supermemory
|
|
24
|
+
|
|
25
|
+
Export or collect your Supermemory memories as JSON. The importer accepts:
|
|
26
|
+
|
|
27
|
+
- A flat JSON array of memory objects.
|
|
28
|
+
- An object with one of these array keys: `memoryEntries`, `memories`,
|
|
29
|
+
`results`, or `data`.
|
|
30
|
+
|
|
31
|
+
Each memory can provide content in `content`, `memory`, `summary`, or `title`.
|
|
32
|
+
Remnic keeps Supermemory IDs, timestamps, container tags, source metadata, and
|
|
33
|
+
the source file path when they are present.
|
|
34
|
+
|
|
35
|
+
If your Supermemory export is paginated, combine the pages into one flat array
|
|
36
|
+
or into an object like this:
|
|
37
|
+
|
|
38
|
+
```json
|
|
39
|
+
{
|
|
40
|
+
"memories": [
|
|
41
|
+
{
|
|
42
|
+
"id": "mem_123",
|
|
43
|
+
"content": "The user prefers short release notes.",
|
|
44
|
+
"updatedAt": "2026-05-05T12:00:00Z",
|
|
45
|
+
"containerTags": ["product"]
|
|
46
|
+
}
|
|
47
|
+
]
|
|
48
|
+
}
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
## Dry Run First
|
|
52
|
+
|
|
53
|
+
Run a dry run before writing anything:
|
|
54
|
+
|
|
55
|
+
```bash
|
|
56
|
+
remnic import --adapter supermemory --file ./supermemory-memories.json --dry-run
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
When the count and warnings look right, run the import:
|
|
60
|
+
|
|
61
|
+
```bash
|
|
62
|
+
remnic import --adapter supermemory --file ./supermemory-memories.json
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
The importer writes records with `sourceLabel: "supermemory"` and
|
|
66
|
+
`metadata.kind: "supermemory_memory"` so you can audit where imported memories
|
|
67
|
+
came from later.
|
|
68
|
+
|
|
69
|
+
## Privacy
|
|
70
|
+
|
|
71
|
+
Parsing and writing run locally. If your Remnic extraction or consolidation
|
|
72
|
+
pipeline is configured to use a remote model provider, imported content may be
|
|
73
|
+
sent to that provider during normal Remnic processing. Use local model routing
|
|
74
|
+
or gateway settings if you need the full migration path to stay local.
|
|
75
|
+
|
|
76
|
+
## API
|
|
77
|
+
|
|
78
|
+
```ts
|
|
79
|
+
import { adapter, supermemoryAdapter } from "@remnic/import-supermemory";
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
Both exports expose the same Remnic importer adapter:
|
|
83
|
+
|
|
84
|
+
- `name: "supermemory"`
|
|
85
|
+
- `sourceLabel: "supermemory"`
|
|
86
|
+
- `parse(input, options)`
|
|
87
|
+
- `transform(parsed)`
|
|
88
|
+
- `writeTo(target, memories)`
|
|
89
|
+
|
|
90
|
+
## More Documentation
|
|
91
|
+
|
|
92
|
+
- Remnic importer docs: https://github.com/joshuaswarren/remnic/blob/main/docs/importers.md
|
|
93
|
+
- Supermemory migration guide: https://remnic.ai/guides/import-supermemory/
|
|
94
|
+
- Package source: https://github.com/joshuaswarren/remnic/tree/main/packages/import-supermemory
|