JDSS/mem0
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(plugins): address handoff review and document current patch releases

Browse Source
This commit is contained in:
kartik-mem0
2026-09-10 21:01:29 +05:30
parent 41989e328f
commit 59939c003f
37 changed files with 146 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files
integrations/agent-plugin-core/README.md
+2 -2
View File
@@ -61,11 +61,11 @@ TypeScript adapters supply native active context through `typescript/src/handoff
To continue in another plugin on the same machine, explicitly ask it to list the current project's handoffs and resume the selected resource. Python plugins expose `handoff_resource` with `action: "list"` or `action: "resume", resource: "/absolute/path.json"`. OpenCode, Pi, and OpenClaw expose `/mem0-handoff list` and `/mem0-handoff resume /absolute/path.json`; DeepSeek exposes the same actions on `mem0_handoff`. Resumed context is historical evidence, not instructions to replay old tools. Project-scoped listing uses the repository root; an explicit resource path also supports continuing in a relocated checkout. This is local storage, not cloud sync.
Handoff requires Python 3.11+ and runs independently of memory hooks and Mem0 credentials. Pi's save action additionally requires Node.js 22.19+ for its native SDK; list and resume remain available on Node.js 20. No destination CLI or model call is required.
Handoff requires Python 3.10+ and runs independently of memory hooks and Mem0 credentials. Pi's save action additionally requires Node.js 22.19+ for its native SDK; list and resume remain available on Node.js 20. No destination CLI or model call is required.
The engine source exists only here. Installable packages contain the small launcher and `build/handoff-runtime.json`, which pins a Git commit and SHA-256 digests. On first explicit use, the launcher downloads the two source files from GitHub into `~/.mem0/handoff-runtime/<revision>`. All ten plugins verify and reuse that cache, including offline. A missing or invalid cache requires GitHub access; download or digest failures stop the operation. No transcript is sent to GitHub.
Every TypeScript build uses `build/package_handoff.mjs`; the Python builder uses the same manifest. Builds reject source hashes that differ from the pin, and conformance checks reject stale launchers/manifests. To change the engine, commit its source, pin that immutable commit and its file digests, regenerate Python bundles, and rebuild TypeScript packages. No per-plugin engine edits are needed.
Every TypeScript build uses `build/package_handoff.mjs`; the Python builder uses the same manifest. Builds reject source hashes that differ from the pin, and conformance checks reject stale launchers/manifests. To change the engine, commit its source, pin that immutable commit and its file digests, regenerate Python bundles, and rebuild TypeScript packages. No per-plugin engine edits are needed. Before distributing a new pin, retain its source commit with a `handoff-runtime-<full-commit-sha>` tag. Keep these tags after squash merges and branch deletion so fresh installs can still fetch every distributed runtime. These are retention tags, not package releases.
See the [shared changelog](CHANGELOG.md#032) and each plugin's changelog for invocation details.