@supermemory/eve 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.
Files changed (2) hide show
  1. package/README.md +27 -2
  2. package/package.json +7 -3
package/README.md CHANGED
@@ -9,10 +9,21 @@ gives Eve tools to search, remember, extract, and forget.
9
9
 
10
10
  ## Add memory to Eve
11
11
 
12
+ From an Eve project, add the provider from Eve's integration registry:
13
+
14
+ ```bash
15
+ eve add memory/supermemory
16
+ ```
17
+
18
+ Or install it yourself:
19
+
12
20
  ```bash
13
21
  npm install @supermemory/eve
14
22
  ```
15
23
 
24
+ The provider supports Eve 0.47.3 and newer 0.x releases. Set `SUPERMEMORY_API_KEY` from the
25
+ [Supermemory console](https://console.supermemory.ai).
26
+
16
27
  Create a memory slot in the consuming Eve agent. `supermemory(...)` configures the provider;
17
28
  `defineMemory(...)` binds it to an Eve-managed scope.
18
29
 
@@ -26,12 +37,15 @@ export default defineMemory({
26
37
  namespace: "your-company-agent-v1",
27
38
  description: "Recall and manage durable context for the current user.",
28
39
  provider: supermemory({
29
- apiKey: process.env.SUPERMEMORY_API_KEY!,
40
+ apiKey: () => process.env.SUPERMEMORY_API_KEY!,
30
41
  }),
31
42
  scope: byPrincipal,
32
43
  });
33
44
  ```
34
45
 
46
+ Pass `apiKey` as a function so the key is read when the agent runs, not when `eve build` loads the
47
+ slot. A plain string also works, but then the key must be set in the build environment too.
48
+
35
49
  Pick a namespace for the agent and keep it stable. If it changes, Eve sees a different memory space.
36
50
  `description` is added to the tool descriptions the model sees, so keep it short and say what this
37
51
  memory is for.
@@ -120,7 +134,7 @@ export default defineMemory({
120
134
  namespace: "your-company-agent-v1",
121
135
  description: "Recall and manage durable context for the current user.",
122
136
  provider: supermemory({
123
- apiKey: process.env.SUPERMEMORY_API_KEY!,
137
+ apiKey: () => process.env.SUPERMEMORY_API_KEY!,
124
138
  containerTagPrefix: "eve_agent",
125
139
  autoSearch: {
126
140
  enabled: true,
@@ -174,3 +188,14 @@ npm run typecheck
174
188
  npm run build
175
189
  npm pack --dry-run
176
190
  ```
191
+
192
+ ### Publishing
193
+
194
+ Pushes to `main` run the release workflow. After checks and a packaged-import smoke test pass,
195
+ the workflow publishes the version in `package.json` if it is not already on npm. Bump the
196
+ package version and update `package-lock.json` to ship a new release; no Git tag is required.
197
+ Publishing uses npm trusted publishing with GitHub Actions OIDC; no `NPM_TOKEN` secret is needed.
198
+ In the npm package's trusted publisher settings, select GitHub Actions, set the organization to
199
+ `supermemoryai`, the repository to `eve-supermemory`, and the workflow filename to `release.yml`.
200
+ Leave the environment name empty and allow direct `npm publish`. The release job uses a
201
+ GitHub-hosted runner because npm trusted publishing does not support self-hosted runners.
package/package.json CHANGED
@@ -1,7 +1,11 @@
1
1
  {
2
2
  "name": "@supermemory/eve",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "description": "Durable user context, retrieval, extraction, remembering, and forgetting for Eve agents.",
5
+ "repository": {
6
+ "type": "git",
7
+ "url": "git+https://github.com/supermemoryai/eve-supermemory.git"
8
+ },
5
9
  "type": "module",
6
10
  "files": [
7
11
  "dist"
@@ -35,11 +39,11 @@
35
39
  "devDependencies": {
36
40
  "@biomejs/biome": "2.5.7",
37
41
  "@types/node": "24.x",
38
- "eve": "0.47.3",
42
+ "eve": "0.66.1",
39
43
  "typescript": "7.0.2"
40
44
  },
41
45
  "peerDependencies": {
42
- "eve": "^0.47.3"
46
+ "eve": ">=0.47.3 <1"
43
47
  },
44
48
  "publishConfig": {
45
49
  "access": "public"