@ubundi/openclaw-cortex 2.10.2 → 2.10.3

package/dist/internal/agent-instructions.js

@@ -46,7 +46,7 @@ You have long-term memory powered by the Cortex plugin. Memories persist permane
 ### Tools — Use These
 
 - **\`cortex_search_memory\`** — Search long-term memory. Params: \`query\`, \`limit\` (1–50), \`mode\` (all|decisions|preferences|facts|recent), \`scope\` (all|session|long-term). **Before saying "I don't know", search first.**
-- **\`cortex_save_memory\`** — Save important facts, decisions, preferences. Params: \`text\`, \`type\` (preference|decision|fact|transient), \`importance\` (high|normal|low), \`checkNovelty\`. **Auto-capture stores topic summaries, not specifics.** When the conversation contains concrete details — key patterns, exact metrics, SQL, config values, CLI commands, library choices with rationale, architecture decisions, bug root causes — save them explicitly. If someone could ask about it later and need the exact answer, save it now.
+- **\`cortex_save_memory\`** — Save important facts, decisions, preferences. Params: \`text\`, \`type\` (preference|decision|fact|transient), \`importance\` (high|normal|low), \`checkNovelty\`. **TRIGGER: After every response where you provide or discuss specific implementation details, call this tool before ending your turn.** Auto-capture stores summaries like "User is setting up Redis caching" — it will NOT preserve the key pattern, strategy, or rationale. If your response contains a detail someone could ask about later and need the exact answer, save it NOW. Format as self-contained facts: \`"Redis cache key: arclight:user:{userId}, cache-aside with invalidation helper. Chosen 2026-01-15."\` NOT \`"User discussed Redis caching."\`
 - **\`cortex_get_memory\`** — Fetch a specific memory by \`nodeId\` (from search results).
 - **\`cortex_forget\`** — Remove memories by \`entity\` or \`session\`. Always search and confirm with the user first.
 - **\`cortex_set_session_goal\`** — Set the session objective (\`goal\`) to bias recall and tag captures. Call at session start.${opts?.agentRole ? `\n\nAgent role: ${opts.agentRole} — memory capture and recall are tuned for this focus area.` : ""}

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "openclaw-cortex",
   "name": "Cortex Memory",
   "description": "Long-term memory powered by Cortex — Auto-Recall, Auto-Capture, agent memory tools, and deduplication",
-  "version": "2.10.2",
+  "version": "2.10.3",
   "configSchema": {
     "type": "object",
     "properties": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ubundi/openclaw-cortex",
-  "version": "2.10.2",
+  "version": "2.10.3",
   "description": "OpenClaw plugin for Cortex memory — Auto-Recall, Auto-Capture, and agent memory tools",
   "type": "module",
   "main": "./dist/index.js",

package/skill/SKILL.md

@@ -23,7 +23,21 @@ These are non-negotiable. Violating them produces incorrect answers.
 
 **5. CONFIDENCE CALIBRATION.** If auto-recall gives you partial context on a topic, the full answer IS in memory. Search harder — don't hedge.
 
-**6. SAVE IMPLEMENTATION DETAILS EXPLICITLY.** Auto-capture extracts topic-level summaries, not specifics. When the conversation contains concrete implementation details — key patterns, exact metrics, SQL statements, config values, CLI commands, library choices with rationale, migration decisions, bug root causes with debugging chains, performance numbers (before/after) — you MUST save them explicitly using `cortex_save_memory`. If a detail is specific enough that someone could ask about it later and need the exact answer, save it proactively. One well-structured save with full context beats three fragments. Don't save every sentence — general topic mentions and status updates are fine for auto-capture.
+**6. SAVE IMPLEMENTATION DETAILS EXPLICITLY.** After every response where you provide or discuss specific implementation details, you MUST call `cortex_save_memory` before ending your turn. Auto-capture extracts topic-level summaries ("User is setting up Redis caching"), not specifics — it will NOT preserve the details.
+
+**The trigger:** If your response contains a concrete technical detail that someone could ask about later and need the exact answer, save it NOW — not later, not "auto-capture will handle it." Call `cortex_save_memory` as the last action in your turn.
+
+**What requires an explicit save:**
+- Key patterns, schemas, or formats (e.g. `arclight:user:{userId}`, cache-aside strategy)
+- Exact metrics and performance numbers (before/after)
+- SQL statements, CLI commands, config values
+- Library/package choices with version-specific rationale (e.g. "chose SendGrid over Resend because SOC 2 Type 2")
+- Architecture/migration decisions with specific reasoning
+- Bug root causes with the full debugging chain
+
+**Format saves for recall:** Structure each save as a self-contained fact with context. Example: `"Redis cache key pattern: arclight:user:{userId}, using cache-aside strategy with invalidation helper. Chosen 2026-01-15."` NOT `"User discussed Redis caching."`
+
+**What auto-capture handles fine (no explicit save needed):** general topic mentions, conversational context, status updates. One well-structured save with full context beats three fragments.
 
 ## Session Goals