@vib795/agent-memory 0.1.11 → 0.1.12

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 +92 -13
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -322,32 +322,111 @@ A transcript summary reads fine and still leaves the next agent asking questions
322
322
 
323
323
  ## Use
324
324
 
325
- Two different jobs, and it is worth being clear about which is which.
325
+ Three commands, two different jobs. You type the slash command in your agent; the
326
+ agent runs the CLI. The terminal equivalents are shown so you can see what it did,
327
+ and drive it by hand when you want to.
326
328
 
327
- **Moving a thread between windows.** In window A:
329
+ ### `/remember` — keep what stays true
330
+
331
+ Mid-session, when something worth keeping has been established:
328
332
 
329
333
  ```
330
- /handoff
334
+ /remember
335
+ /remember the retry policy on the orders webhook
331
336
  ```
332
337
 
333
- It prints a pickup line. In window B, any repo, paste it:
338
+ Bare, it selects the durable knowledge itself. With an argument, it writes that and
339
+ nothing else. Either way it makes one terminal call, and `write` reports each id:
334
340
 
335
341
  ```
336
- Read C:\Users\you\.agents\handoffs\migrate-orders-to-result-type.md and continue this work. Follow the Next action.
342
+ created auth-service [system]
343
+ created use-sessions [decision]
344
+ warning: use-sessions: redacted 1x github-token
337
345
  ```
338
346
 
339
- **Keeping what stays true.** `/handoff` also writes durable knowledge into the graph
340
- in the same request — same turn, no extra credit. Mid-session, when something worth
341
- keeping is established and you are not switching windows:
347
+ That warning is the redactor firing before anything reached disk. The skill then
348
+ repeats the list back to you with titles attached, so you can see what was captured
349
+ without opening the files.
350
+
351
+ What it ran, which you can run yourself:
342
352
 
353
+ ```bash
354
+ agent-memory write --from-json - --source remember <<'JSON'
355
+ {"nodes":[
356
+ {"id":"use-sessions","type":"decision",
357
+ "title":"Chose server sessions over JWT",
358
+ "body":"Why: revocation had to take effect immediately.\nRejected: short-TTL JWT, because logout would lag by the TTL.\nImplemented in src/auth/session.js:42.",
359
+ "edges":[{"rel":"evidence-for","dst":"auth-service"}]}
360
+ ]}
361
+ JSON
343
362
  ```
344
- /remember
345
- /remember the retry policy on the orders webhook
363
+
364
+ ### `/recall` — answer from memory before deriving again
365
+
366
+ You rarely type this one. Ask a question memory should already answer and the agent
367
+ invokes it on its own, because the skill description advertises what is in the store:
368
+
369
+ ```
370
+ Why do we use sessions instead of JWT here?
371
+ /recall the auth decision
372
+ ```
373
+
374
+ It reads the routing map first, then pulls only the notes it needs:
375
+
376
+ ```bash
377
+ agent-memory tree # what exists, scoped to this repo
378
+ agent-memory get use-sessions --depth 1 # that note plus its neighbourhood
379
+ agent-memory search "session revocation" # full text, when the tree misses
380
+ ```
381
+
382
+ A note that is still current prints clean, with its edges:
383
+
384
+ ```
385
+ ## use-sessions [decision] depth 0
386
+ Chose server sessions over JWT
387
+
388
+ Why: revocation had to take effect immediately.
389
+
390
+ -> evidence-for auth-service
346
391
  ```
347
392
 
348
- And in any repo, later, ask a question that memory should already answer. The agent
349
- invokes `/recall` on its own, because the skill description tells it what is in
350
- there.
393
+ Once the code has moved on underneath it, the same note arrives carrying the warning.
394
+ This is the part that keeps the store honest:
395
+
396
+ ```
397
+ ## use-sessions [decision] depth 0 [captured 47 commits ago — verify before trusting]
398
+ ```
399
+
400
+ ### `/handoff` — move a thread to another window
401
+
402
+ In window A:
403
+
404
+ ```
405
+ /handoff
406
+ ```
407
+
408
+ It writes the working-state file and prints a pickup line. In window B, any repo,
409
+ paste it:
410
+
411
+ ```
412
+ Read ~/.agents/handoffs/migrate-orders-to-result-type.md and continue this work. Follow the Next action.
413
+ ```
414
+
415
+ `/handoff` also writes durable knowledge into the graph in the same request — same
416
+ turn, no extra request charged. To see what it produced:
417
+
418
+ ```bash
419
+ ls ~/.agents/handoffs/ # index.md, <thread>.md, one <thread>.prev.md
420
+ agent-memory tree # the nodes it captured on the way past
421
+ ```
422
+
423
+ ### Housekeeping
424
+
425
+ ```bash
426
+ agent-memory doctor # after install, after an upgrade, when something looks off
427
+ agent-memory compact # dedup, decay, regenerate the routing digest
428
+ agent-memory tree --repo # every repo, not just this one
429
+ ```
351
430
 
352
431
  ## Where things live
353
432
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vib795/agent-memory",
3
- "version": "0.1.11",
3
+ "version": "0.1.12",
4
4
  "description": "Durable cross-repo knowledge graph for GitHub Copilot and Claude Code. Markdown source of truth, disposable SQLite index, zero runtime dependencies.",
5
5
  "keywords": [
6
6
  "github-copilot",