waku-memory 0.4.0 → 0.4.1

package/.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "waku",
-  "version": "0.4.0",
-  "description": "Waku Memory: durable memory for your Codex sessions. memory.recall brings what is known about a project into a session; memory.remember keeps what matters; the plugin's hooks open each session with a brief and send each turn to be remembered.",
+  "version": "0.4.1",
+  "description": "Waku Memory: durable memory for your Codex sessions. memory.recall brings what is known about a project into a session; memory.remember keeps what matters; the plugin's hooks open each session with a brief and send each turn to be remembered. What you type and what the agent replies is sent to Waku's servers and on to Anthropic, which is what turns a session into memories; your files, the commands the agent runs and its reasoning are not. This is an alpha and its data can be lost.",
   "skills": "./skills/",
   "hooks": "./hooks/hooks.json",
   "interface": {

package/dist/capture.js

@@ -252,6 +252,15 @@ export function hookInvocation(execPath, indexPath) {
 // Codex-only machine has no other way to learn that the same three hooks
 // exist there too, or that installing the Waku plugin instead is the other
 // route to the same events (codexPluginPresent, this file's own enable()).
+//
+// This text now exists in four places with no mechanism sharing it (found
+// 2026-09-10, status.md item 9's dated paragraph): this DISCLOSURE, the
+// Codex plugin manifest's "description" (.codex-plugin/plugin.json, pinned
+// by plugin.test.mjs), skills/waku/SKILL.md's "sent to Waku" bullet, and
+// the frontend's OAuth consent page (waku-memory-frontend
+// app/oauth/consent/page.tsx, its CONSENT_DISCLOSURE constant). A change to
+// the two facts here -- where captured content goes, and that this is an
+// alpha -- has to be carried to the other three by hand.
 export const DISCLOSURE = 'Captured content is sent to our servers and to Anthropic for extraction. ' +
     'This is an alpha whose data can be lost. ' +
     'What you type, what the agent replies, and the names of the tools it uses are sent; ' +

package/dist/hook.js

@@ -63,7 +63,7 @@ export { SESSION_END_HOOK_TIMEOUT_S, SESSION_END_TIMEOUT_MS } from "./harnesses.
 // hook.test.mjs's drift check (against package.json) both need it; task 14
 // (spec 012 §9) bumps this, package.json and the plugin manifest
 // (.codex-plugin/plugin.json) to 0.3.0 together.
-export const SHIM_VERSION = '0.4.0';
+export const SHIM_VERSION = '0.4.1';
 // Exported for capture.ts, which writes the file this module reads.
 export const CONFIG_FILE_NAME = 'config.json';
 // Same-directory temp file + rename, exactly atomicWriteJson's technique in

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "waku-memory",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Install Waku Memory into your agent harness, and turn on automatic session capture.",
   "keywords": ["mcp", "memory", "claude-code", "agent", "waku"],
   "homepage": "https://github.com/ShenSeanChen/waku-memory-backend/tree/spec-driven/shim#readme",

package/skills/waku/SKILL.md

@@ -16,8 +16,17 @@ learn, and brings it back into later sessions.
   a procedure or a fact they will want next time. Use their words. Do not
   store secrets, credentials or file contents.
 - What the person types and what you reply is sent to Waku after each turn
-  by the plugin's hooks; tool output is not.
+  by the plugin's hooks; tool output is not. It goes on to Anthropic, which
+  is what turns a session into memories. This is an alpha and its data can
+  be lost.
 
 One-time setup the person does: after installing, Codex asks them to
 review and trust this plugin's hooks (`/hooks` in the CLI). Until then
 the brief and the capture do not run.
+
+<!-- This bullet's two facts (where captured content goes, and that this
+     is an alpha) also live in capture.ts's DISCLOSURE, the Codex plugin
+     manifest's "description" (.codex-plugin/plugin.json), and the
+     frontend's OAuth consent page (waku-memory-frontend
+     app/oauth/consent/page.tsx's CONSENT_DISCLOSURE). No mechanism shares
+     the string; a change here has to be carried to the other three. -->