{"slug":"clawhub-sedelev-install-memex-claw","facts":[{"factKey":"vendor","category":"vendor","label":"Vendor","value":"Clawhub","href":"https://clawhub.ai/sedelev/skills/install-memex-claw","sourceUrl":"https://clawhub.ai/sedelev/skills/install-memex-claw","sourceType":"profile","confidence":"medium","observedAt":"2026-10-10T23:07:09.239Z","isPublic":true},{"factKey":"protocols","category":"compatibility","label":"Protocol compatibility","value":"OpenClaw","href":"https://www.xpersona.co/api/v1/agents/clawhub-sedelev-install-memex-claw/contract","sourceUrl":"https://www.xpersona.co/api/v1/agents/clawhub-sedelev-install-memex-claw/contract","sourceType":"contract","confidence":"medium","observedAt":"2026-10-10T23:07:09.239Z","isPublic":true},{"factKey":"traction","category":"adoption","label":"Adoption signal","value":"1.2K downloads","href":"https://clawhub.ai/sedelev/install-memex-claw","sourceUrl":"https://clawhub.ai/sedelev/install-memex-claw","sourceType":"profile","confidence":"medium","observedAt":"2026-10-10T23:07:09.239Z","isPublic":true},{"factKey":"latest_release","category":"release","label":"Latest release","value":"3.0.0","href":"https://clawhub.ai/sedelev/install-memex-claw","sourceUrl":"https://clawhub.ai/sedelev/install-memex-claw","sourceType":"release","confidence":"medium","observedAt":"2026-05-25T19:34:23.847Z","isPublic":true},{"factKey":"handshake_status","category":"security","label":"Handshake status","value":"UNKNOWN","href":"https://www.xpersona.co/api/v1/agents/clawhub-sedelev-install-memex-claw/trust","sourceUrl":"https://www.xpersona.co/api/v1/agents/clawhub-sedelev-install-memex-claw/trust","sourceType":"trust","confidence":"medium","observedAt":null,"isPublic":true}],"changeEvents":[{"eventType":"release","title":"Release 3.0.0","description":"v3.0.0 — REVERT to daemon-based install. The 2.0.x plugin-based path (npm package @parallelclaw/memex-openclaw) is officially DEPRECATED after running into a series of OpenClaw plugin-SDK frictions: security scanner blocks any child_process in tarball (even in bin/), no api.registerCli use in bundled extensions (might be buggy per issue #80621), api.registerTool doesn't expose to LLM toolset (need MCP wiring anyway), allowConversationAccess required as user-side opt-in, better-sqlite3 native binary rebuild needed per install, plus conv_id formula divergence from the file-watcher would create duplicate-namespace data for existing users. None of that is worth fighting through when memex-mvp's daemon-based approach was already production-proven on every deployment (self-hosted OpenClaw + Moonshot Kimi-Claw + macOS workstations). v3.0.0 restores the v1.0.3 daemon flow updated for memex-mvp 0.11.6+: install daemon, run scan + backfill-channels, wire memex into cfg.mcp.servers (correct nested key), restart gateway. Added explicit migration section at the top for users who tried the deprecated plugin — uninstall block, .bak restore hint, note that captured plugin data stays in memex.db (UNIQUE prevents duplicates with daemon-source rows). Step 5 retains the v2.0.2 nested-key fix (cfg.mcp.servers vs cfg.mcpServers — the latter was silently ignored by OpenClaw 2026.5+ MCP runtime adapter). Step 7d retains the LLM-toolset verification (open fresh session, ask agent to invoke memex_search, ensure it doesn't fall back to raw sqlite). The plugin-based v2.0.x history is preserved on ClawHub for archaeology; users on v2.0.x can migrate to v3.0.0 via the migration block. v2.0.2 — Step 5 (MCP wiring) is now MANDATORY, and the config key bug is fixed. Pre-v2.0.2 the script wrote MCP server config to cfg.mcpServers (top-level, camelCase), but OpenClaw 2026.5+ actually reads from cfg.mcp.servers (nested under 'mcp'). The flat key was silently ignored — meaning every install via v2.0.0/v2.0.1 had broken retrieval: capture worked (Bug 6 fixed correctly) but the LLM never saw memex_search in its toolset because the MCP runtime adapter couldn't find any 'memex' server registration. Field-validated 2026-05-25: after correcting to cfg.mcp.servers.memex + restart + fresh session, the LLM agent correctly invoked memex_search and returned real April-2026 conversation results from memex.db. Architectural clarification added at top of Step 5: api.registerTool() from a non-bundled plugin creates RPC tools in OpenClaw's gateway registry (callable via direct tool.call) but does NOT inject them into the LLM's function-calling toolset — only cfg.mcp.servers does that, at session start. New Step 7d verification — the LLM toolset check — guides the user through opening a fresh session and asking the agent to use memex_search; if the agent falls back to raw sqlite, the MCP wiring is wrong. Cleanup logic deletes any stale cfg.mcpServers.memex entry left by earlier skill versions. Step 5 demoted 'optional but recommended' label removed — without MCP wiring, the agent cannot retrieve from memex inside conversations; this is no longer a nice-to-have. Pairs with memex-openclaw v0.1.5+. v2.0.1 — Bug 6 fix: Step 4 now explicitly grants hooks.allowConversationAccess=true alongside enabled=true. Without this, OpenClaw 2026.5+ silently BLOCKS the agent_end hook for non-bundled (npm-installed) plugins as a security default — the plugin would register and tools would work, but no new conversations would actually be captured. Field-validated on a self-hosted VPS: BEFORE fix, 9006 rows from legacy file-watcher only; AFTER fix, +3 rows after test message with raw_type='openclaw-agent-end' (plugin marker, not legacy). Skill Step 7 verification expanded into 7a/7b/7c: 7a checks gateway log has no 'BLOCKED' messages for agent_end; 7b snapshots row count before+after a test message and asserts diff ≥ 2 with raw_type='openclaw-agent-end' so the plugin path is proven, not just the legacy fallback; 7c keeps the original conversation_id shape check. Documentation up front explains WHY allowConversationAccess is a manual user-opt-in (OpenClaw security model — non-bundled plugins cannot self-declare; analogous to Android runtime permissions). Pairs with memex-openclaw v0.1.5+. v2.0.0 — MAJOR REWRITE: skill now installs the new memex-openclaw plugin (npm: @parallelclaw/memex-openclaw) instead of the v0.11.x memex-sync file-watcher daemon. Plugin runs INSIDE OpenClaw via the native OpenClaw 2026.5+ plugin SDK — subscribes to 'agent_end' hook for per-turn capture, 'before_compaction' for preserving messages about to drop from context, registers as a MemoryCorpusSupplement so memex content shows up in built-in memory_search tool. Channel detection is FREE — comes from ctx.messageProvider/channelId, no regex parsing of message text needed. Eliminates ~1000 lines of brittle parser code from memex-mvp (channel markers, sessions.json reader, .reset/.checkpoint file recognition, channel auto-discovery — all unnecessary because OpenClaw hands the plugin structured event data directly). Conv-id scheme: 'openclaw-<platform>-<channelId>' for per-user threads (telegram/discord), 'openclaw-<platform>-<session8>' for cli/cron fallback. Skill flow simplified: Discovery → install memex-mvp (≥ 0.12 needed) → stop+disable old daemon if present → install plugin → enable in openclaw.json → wire memex MCP server → restart. Multi-plugin coexistence: Mem0/Memoria/memex can all be active simultaneously, the corpus supplement merges results in built-in memory_search. Honest positioning added at top: memex-openclaw is most useful as a BRIDGE — pair with memex-mvp + other clients (Claude Code, Hermes, Telegram) for unified cross-client memory. Single-OpenClaw users with built-in memory-core may not need this. Requires OpenClaw 2026.5+ (plugin SDK). v1.0.3 — paired with memex-mvp v0.11.5 file-watcher era (now superseded by v2.0.0). (the first release where OpenClaw ingestion can be trusted end-to-end on BOTH self-hosted OpenClaw and Moonshot Kimi-Claw). Bumps version checks throughout (≥ 0.11.5 now required, was ≥ 0.10.14). Rewrites Step 4b around the matured v0.11.x channel-aware pipeline: documents two-mode routing (auto-detected kimi-claw vs self-hosted), the --mode override flag, the new backfill banner with separate counts for main / checkpoint / reset files. Adds a 'What you get out of v0.11.5 vs older' table summarising every fix between v0.11.0 and v0.11.5 so users upgrading from any prior version know what changes. Key wins for self-hosted OpenClaw (the dominant case — ~90% of installs per maintainer feedback): (a) checkpoint snapshots are auto-skipped to avoid 30-40x row duplication; (b) .reset.* full session archives are now picked up (v0.11.4 added it, v0.11.5 made shouldIngest actually allow them through — the real reset filename ends in '.833Z' not '.jsonl' so v0.11.4's logic was dead code); (c) content-based session-type detection survives main-session rotation when sessions.json has dropped the entry. Key wins for Kimi-Claw users: (a) Kimi-web header strips correctly without optional [Time:] block; (b) tool-results inherit the parent conversation instead of orphaning into a fallback bucket. Adds documentation of .reset.* archive ingestion in Step 4 — self-hosted users typically gain 3-7K messages of long-term Telegram history (~140 MB) that were invisible to memex before. No behavior change in install / daemon / MCP wiring — Discovery + Steps 1-3 + 5-8 unchanged. v1.0.2 — fixes two friction points: Step 6 (Verify) moved DB-content checks to new Step 8 (post-restart) since inbox isn't drained until first MCP server start. plugins.allow troubleshooting generalised. Pairs with memex-mvp v0.10.15. v1.0.1 — adds 'Before this skill can be installed' bootstrap section documenting the one-time plugins.allow edit on fresh OpenClaw VPS. v1.0 — first release. Wires memex into an OpenClaw gateway WHEREVER OpenClaw runs: Linux VPS, Linux workstation, macOS workstation, macOS server — all four equally first-class. Discovery checks OpenClaw / Node ≥ 20 / existing memex install / existing daemon / sessions count / systemd-user (Linux only) / gateway config location. Branches intelligently: if memex is already installed (e.g. via the generic install-memex skill for Claude Code), skips install+daemon and just merges memex into the OpenClaw gateway's MCP-server config. Otherwise full platform-aware install: Linux → ~/.config/systemd/user/memex-sync.service with loginctl enable-linger attempt; macOS → ~/Library/LaunchAgents/com.parallelclaw.memex.sync.plist. EACCES handled via ~/.npm-global prefix fix (no sudo). MCP wiring uses absolute path from `which memex` (MCP-stdio doesn't inherit shell PATH), merges into the OpenClaw config without overwriting other MCP servers. Verifies end-to-end before declaring done. Zero questions to the user — discovery → actions → verification. Adds 18 MCP tools (memex_search, memex_recent, memex_overview, memex_store_document, memex_import_file, etc.) to OpenClaw after gateway restart. Pairs nicely with install-memex (generic skill) when the same machine ALSO runs Claude Code / Cursor / Telegram capture — both skills share ~/.memex/data/memex.db so the corpus is unified. Memex runtime emits zero outbound network traffic.","href":"https://clawhub.ai/sedelev/install-memex-claw","sourceUrl":"https://clawhub.ai/sedelev/install-memex-claw","sourceType":"release","confidence":"medium","observedAt":"2026-05-25T19:34:23.847Z","isPublic":true}]}