@vshulcz/deja-vu 0.22.0 → 0.22.1

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 +5 -3
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -7,7 +7,7 @@
7
7
 
8
8
  <p align="center"><strong>Your coding agents stop re-debugging what you already fixed.</strong></p>
9
9
 
10
- **deja starts full**: the history 38 agents already wrote, with no model and no capture step. It
10
+ **deja starts full**: the history 41 agents already wrote, with no model and no capture step. It
11
11
  indexes the sessions your coding agents already wrote to disk — months of
12
12
  history from before you installed it — and serves them back over MCP, in
13
13
  whichever agent asks.
@@ -19,7 +19,7 @@ Antigravity, Grok Build, OpenClaw, pi, omp, DeepSeek Harness, Hermes, Kiro,
19
19
  Reasonix and Zed. deja turns those files into one memory layer that all of them
20
20
  can read.
21
21
 
22
- One Go binary. No LLM, no embeddings, no API key, and no network path besides a daily release check, which DEJA_OFFLINE=1 turns off.
22
+ One Go binary. No LLM, no embeddings, no API key. The network is used only by commands you run for it, such as `deja update` and `deja sync ssh`, and by a daily release check, which DEJA_OFFLINE=1 turns off.
23
23
  **58% fewer tokens** on a task this machine had already solved (53,558 against 126,222 with nothing wired, and 52,815 against 103,443 on a later build with the arms run alternately, eleven runs an arm each time). **88.1% hit@1** on LongMemEval-S (470-question cleaned set), **millisecond** lookups over gigabytes of history.
24
24
 
25
25
  ```sh
@@ -30,7 +30,9 @@ npm install -g @vshulcz/deja-vu # then: deja install --auto
30
30
  `deja install --auto` wires MCP recall into every coding agent it finds on the
31
31
  machine and turns on session-start recall where the agent supports it. Ten
32
32
  seconds to install, about ten to index, and the next session already knows.
33
- Use `--all` for the MCP tools without the session-start hook.
33
+ Use `--all` for the MCP tools without the session-start hook. `deja` on its own
34
+ opens a search screen over every agent's history, where you can read a session,
35
+ resume it, or continue it in another agent.
34
36
 
35
37
  Full documentation, the harness matrix and the benchmarks:
36
38
  [github.com/vshulcz/deja-vu](https://github.com/vshulcz/deja-vu) ·
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vshulcz/deja-vu",
3
- "version": "0.22.0",
3
+ "version": "0.22.1",
4
4
  "description": "deja-vu: memory for coding agents from the sessions they already wrote to disk — Claude Code, Codex, Cursor and the rest — local, from the CLI or over MCP.",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -43,12 +43,12 @@
43
43
  "package.json"
44
44
  ],
45
45
  "optionalDependencies": {
46
- "@vshulcz/deja-vu-darwin-arm64": "0.22.0",
47
- "@vshulcz/deja-vu-darwin-amd64": "0.22.0",
48
- "@vshulcz/deja-vu-linux-arm64": "0.22.0",
49
- "@vshulcz/deja-vu-linux-amd64": "0.22.0",
50
- "@vshulcz/deja-vu-windows-arm64": "0.22.0",
51
- "@vshulcz/deja-vu-windows-amd64": "0.22.0"
46
+ "@vshulcz/deja-vu-darwin-arm64": "0.22.1",
47
+ "@vshulcz/deja-vu-darwin-amd64": "0.22.1",
48
+ "@vshulcz/deja-vu-linux-arm64": "0.22.1",
49
+ "@vshulcz/deja-vu-linux-amd64": "0.22.1",
50
+ "@vshulcz/deja-vu-windows-arm64": "0.22.1",
51
+ "@vshulcz/deja-vu-windows-amd64": "0.22.1"
52
52
  },
53
53
  "mcpName": "io.github.vshulcz/deja-vu"
54
54
  }