waku-memory 0.1.0 → 0.3.0

package/.codex-plugin/plugin.json

@@ -0,0 +1,15 @@
+{
+  "name": "waku",
+  "version": "0.3.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.",
+  "skills": "./skills/",
+  "hooks": "./hooks/hooks.json",
+  "interface": {
+    "displayName": "Waku Memory",
+    "shortDescription": "Memory that follows you across sessions",
+    "developerName": "Waku",
+    "category": "Developer Tools",
+    "capabilities": ["Read", "Write"],
+    "websiteURL": "https://www.waku.one/"
+  }
+}

package/.mcp.json

@@ -0,0 +1,9 @@
+{
+  "mcpServers": {
+    "waku": {
+      "type": "http",
+      "url": "https://api.waku.one/mcp",
+      "default_tools_approval_mode": "approve"
+    }
+  }
+}

package/README.md

@@ -0,0 +1,55 @@
+# waku-memory
+
+This package is the shim that connects an agent harness to Waku Memory. It
+points Claude Code's or Codex's MCP config at Waku's server, and it can turn
+on capture: hooks that send each turn of a session to the server, so the
+agent remembers a project across sessions without anyone typing the same
+conventions twice.
+
+## Commands
+
+- `npx waku-memory setup [--name <name>] [--url <url>]` adds the Waku MCP
+  server to Claude Code's config.
+- `npx waku-memory capture enable [flags]` turns on automatic capture: it
+  shows a disclosure, asks you to accept it, then installs hooks for every
+  harness this machine has.
+- `npx waku-memory login [--url <ingest-base>]` signs in through the
+  browser and mints an API key, without you ever seeing it.
+- `npx waku-memory capture disable` removes exactly the hook entries
+  `capture enable` added. Your saved key stays where it is.
+- `npx waku-memory capture status` prints whether capture is installed for
+  Claude Code and for Codex, and whether a key is saved. It only reads.
+
+`capture enable` takes these flags:
+
+- `--login` signs in through the browser without asking first.
+- `--key <key>` uses this key without asking first.
+- `--url <ingest-base>` points capture at a server other than the default.
+- `--since <N>d` limits the history scan to the last N days.
+- `--all` scans full history instead of `--since`.
+- `--no-bootstrap` skips the history scan and its question entirely.
+
+## Codex
+
+Codex can run Waku's hooks and MCP server through two routes.
+
+**The plugin.** Install Waku from a Codex plugin marketplace. The plugin
+needs no Node on your machine; it carries its own hooks and its own MCP
+server, and Codex signs you in with its own OAuth flow when you install it.
+Codex still runs a new hook only after you trust it: open `/hooks` in Codex
+and trust Waku's entries once.
+
+**The CLI.** `npx waku-memory capture enable` on a machine with Codex
+installed writes the `[mcp_servers.waku]` table into
+`~/.codex/config.toml` and three entries (`SessionStart`, `Stop`,
+`SessionEnd`) into `~/.codex/hooks.json`. This route runs the compiled
+shim directly, so it needs Node 20 or newer. Codex asks the same trust
+step: open `/hooks` and trust Waku's three entries once.
+
+When both routes are present on the same machine, the plugin wins:
+`capture enable` leaves both Codex files untouched and says so, since the
+plugin already carries the hooks and the MCP server.
+
+`login` works the same way on Codex as it does on Claude Code: it signs you
+in and stores the key at `~/.waku-memory/config.json`, without touching
+either harness's config.