@nowledge/openclaw-nowledge-mem 0.8.14 → 0.8.16

package/CHANGELOG.md

@@ -4,6 +4,25 @@ All notable changes to the Nowledge Mem OpenClaw plugin will be documented in th
 
 ## Unreleased
 
+## [0.8.16] - 2026-04-15
+
+### Fixed
+
+- Fixed a regression in `0.8.15` where supplement-mode startup could fail during plugin registration because the status tool was passed an undefined `memorySlot` variable. This could block the plugin before corpus supplement or native tools became available.
+- Added coverage for the implicit default path where OpenClaw leaves the memory slot on `memory-core`.
+
+## [0.8.15] - 2026-04-15
+
+### Fixed
+
+- **Corpus supplement now works cleanly while `memory-core` stays on the memory slot.** The plugin is now published as a dual-role OpenClaw plugin, so it can remain loaded for corpus supplement and native Nowledge Mem tools even when `memory-core` owns the primary memory slot.
+- **Supplement mode no longer shadows `memory-core`'s own `memory_search` / `memory_get` tools.** Those compatibility tools now register only when Nowledge Mem itself owns the memory slot.
+- **No local source patch should be needed for dreaming integration.** Earlier builds could fall into a broken topology where the plugin was disabled before supplement registration ever mattered, which made users patch local plugin source to keep corpus mode alive.
+
+### Changed
+
+- The OpenClaw manifest and runtime export now declare the plugin as `["memory", "context-engine"]`, which matches its real capabilities and keeps supplement mode alive beside `memory-core`.
+
 ## [0.8.14] - 2026-04-14
 
 ### Fixed

package/CLAUDE.md

@@ -82,9 +82,9 @@ Enable when memory-core is the memory slot and you want cross-tool knowledge to
 
 ## Context Engine (CE) Architecture
 
-The plugin registers both a **memory slot** (`kind: "memory"`) and a **context engine** (`api.registerContextEngine`). These are independent registrations:
+The plugin is published as a dual-role OpenClaw plugin (`kind: ["memory", "context-engine"]`). These roles remain independent at runtime:
 
-- **Memory slot**: provides `memory_search` + `memory_get`, activates OpenClaw's "Memory Recall" system prompt section. Always active.
+- **Memory slot**: provides `memory_search` + `memory_get` and activates OpenClaw's "Memory Recall" system prompt section only when `plugins.slots.memory = "openclaw-nowledge-mem"`. In supplement mode with `memory-core`, these compatibility tools stay off so memory-core keeps owning that surface.
 - **Context engine**: activated when user sets `plugins.slots.contextEngine: "nowledge-mem"`. Replaces hooks with richer CE lifecycle.
 
 ### CE vs Hooks (dual-path design)

package/README.md

@@ -240,6 +240,8 @@ When OpenClaw's memory-core is the primary memory slot and Nowledge Mem runs alo
 
 Requires OpenClaw >= 2026.4.5.
 
+As of `0.8.15`, this works without local source edits. The plugin now stays active beside `memory-core` for supplement mode, while leaving `memory-core`'s own `memory_search` / `memory_get` pair in place.
+
 If OpenClaw stores a top-level `dreaming` object on this plugin while it owns the memory slot, that is expected. Dreaming remains OpenClaw-native host config; this plugin accepts it so memory-core can run the dreaming engine alongside Nowledge Mem without registration errors.
 
 ### Three Modes at a Glance
@@ -529,6 +531,10 @@ All 10 plugin tools register automatically when the plugin loads. No tool-level
 }
 ```
 
+**`corpusSupplement: true` is set, but startup still logs `corpus=false`**
+
+Update to `0.8.15` or newer. Older builds could disable the plugin too early when `memory-core` owned the memory slot, which made supplement mode look unavailable even on new OpenClaw builds.
+
 If `openclaw status` shows a CRITICAL warning about `plugins.allow`, this is the fix. Run `nowledge_mem_status` inside a conversation to check both plugin trust and memory slot status.
 
 Do not list `nowledge_mem_*` tool names in `tools.allow` — OpenClaw silently strips allowlists that contain only plugin entries, so the config looks active but does nothing.

package/openclaw.plugin.json

@@ -2,8 +2,8 @@
 	"id": "openclaw-nowledge-mem",
 	"name": "Nowledge Mem",
 	"description": "Cross-tool knowledge graph memory for OpenClaw with Working Memory, graph search, and session distillation.",
-	"version": "0.8.14",
-	"kind": "memory",
+	"version": "0.8.16",
+	"kind": ["memory", "context-engine"],
 	"skills": [
 		"skills/memory-guide"
 	],

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@nowledge/openclaw-nowledge-mem",
 	"displayName": "Nowledge Mem for OpenClaw",
-	"version": "0.8.14",
+	"version": "0.8.16",
 	"type": "module",
 	"description": "Nowledge Mem memory plugin for OpenClaw, local-first personal knowledge base",
 	"author": {

package/src/context-engine.js

@@ -1,7 +1,8 @@
 /**
  * Nowledge Mem Context Engine for OpenClaw.
  *
- * Registers alongside the memory slot (kind: "memory"). When users activate
+ * Registers alongside the memory slot (plugin kind includes both "memory" and
+ * "context-engine"). When users activate
  * this CE via `plugins.slots.contextEngine: "nowledge-mem"`, it takes over
  * prompt assembly and adds richer lifecycle behavior:
  *

package/src/index.js

@@ -26,13 +26,14 @@ import { createStatusTool } from "./tools/status.js";
 import { createThreadFetchTool } from "./tools/thread-fetch.js";
 import { createThreadSearchTool } from "./tools/thread-search.js";
 import { createTimelineTool } from "./tools/timeline.js";
+import { resolveRegistrationMode } from "./register-mode.js";
 
 export default {
 	id: "openclaw-nowledge-mem",
 	name: "Nowledge Mem",
 	description:
 		"Local-first knowledge graph memory for AI agents — cross-AI continuity, powered by Nowledge Mem",
-	kind: "memory",
+	kind: ["memory", "context-engine"],
 
 	register(api) {
 		const logger = api.logger;
@@ -43,9 +44,19 @@ export default {
 			space: cfg.space,
 		});
 
-		// OpenClaw memory-slot compatibility (required for system prompt activation)
-		api.registerTool(createMemorySearchTool(client, logger));
-		api.registerTool(createMemoryGetTool(client, logger));
+		const { memorySlot, memorySlotSelected } = resolveRegistrationMode({
+			pluginId: api.id,
+			configuredMemorySlot: api.config?.plugins?.slots?.memory,
+		});
+
+		// Only the active memory slot should provide the OpenClaw-compatible
+		// memory_search / memory_get pair. When memory-core owns the slot, this
+		// plugin can still stay loaded for corpus supplement, thread sync, and
+		// native Nowledge Mem tools without shadowing memory-core's tools.
+		if (memorySlotSelected) {
+			api.registerTool(createMemorySearchTool(client, logger));
+			api.registerTool(createMemoryGetTool(client, logger));
+		}
 
 		// Nowledge Mem native tools (our differentiators)
 		api.registerTool(createSaveTool(client, logger));
@@ -61,7 +72,6 @@ export default {
 		// Diagnostics — pass runtime config so the status tool can detect:
 		//   - plugins.allow missing or not including this plugin
 		//   - memory/context-engine slot routing for capture and recall
-		const memorySlot = api.config?.plugins?.slots?.memory;
 		const contextEngineSlot = api.config?.plugins?.slots?.contextEngine;
 		const pluginsAllow = api.config?.plugins?.allow;
 		let contextEngineRegistered = false;
@@ -161,7 +171,7 @@ export default {
 
 		const remoteMode = !isDefaultApiUrl(cfg.apiUrl);
 		logger.info(
-			`nowledge-mem: initialized (context=${cfg.sessionContext}, digest=${cfg.sessionDigest}, corpus=${cfg.corpusSupplement}, mode=${remoteMode ? `remote → ${cfg.apiUrl}` : "local"})`,
+			`nowledge-mem: initialized (memorySlotSelected=${memorySlotSelected}, context=${cfg.sessionContext}, digest=${cfg.sessionDigest}, corpus=${cfg.corpusSupplement}, mode=${remoteMode ? `remote → ${cfg.apiUrl}` : "local"})`,
 		);
 	},
 };

package/src/register-mode.js

@@ -0,0 +1,9 @@
+export function resolveRegistrationMode({ pluginId, configuredMemorySlot }) {
+	const memorySlot = configuredMemorySlot ?? "memory-core";
+	const memorySlotSelected = memorySlot === pluginId;
+	return {
+		memorySlot,
+		memorySlotSelected,
+		registerMemoryCompatTools: memorySlotSelected,
+	};
+}