@memclaw/memclaw 0.9.18 → 0.9.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -38,7 +38,7 @@ function memclawPlugin(api) {
38
38
  exports.plugin = {
39
39
  id: 'memclaw',
40
40
  name: 'MemClaw',
41
- version: '0.9.18',
41
+ version: '0.9.19',
42
42
  configSchema: {
43
43
  type: 'object',
44
44
  properties: {
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "id": "memclaw",
3
3
  "name": "MemClaw",
4
- "version": "0.9.18",
4
+ "version": "0.9.19",
5
5
  "description": "Layered semantic memory for OpenClaw with L0/L1/L2 tiered retrieval, easy setup, and migration from native memory",
6
6
  "kind": "memory",
7
7
  "skills": ["skills/memclaw", "skills/memclaw-maintance"],
package/package.json CHANGED
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "name": "@memclaw/memclaw",
3
- "version": "0.9.18",
3
+ "version": "0.9.19",
4
4
  "description": "MemClaw - The Cortex Memory plugin for OpenClaw. Layered semantic memory for OpenClaw with easy setup and migration",
5
5
  "homepage": "https://github.com/sopaco/cortex-mem",
6
6
  "repository": {
7
7
  "type": "git",
8
- "url": "https://github.com/sopaco/cortex-mem.git",
8
+ "url": "git+https://github.com/sopaco/cortex-mem.git",
9
9
  "directory": "examples/@memclaw/plugin"
10
10
  },
11
11
  "bugs": {
@@ -48,7 +48,7 @@
48
48
  "glob": "^11.0.0"
49
49
  },
50
50
  "optionalDependencies": {
51
- "@memclaw/bin-darwin-arm64": "0.1.0",
51
+ "@memclaw/bin-darwin-arm64": "0.1.2",
52
52
  "@memclaw/bin-win-x64": "0.1.0"
53
53
  },
54
54
  "engines": {
@@ -23,7 +23,7 @@ See [security.md](./references/security.md) for details on data handling, storag
23
23
 
24
24
  ## Configuration
25
25
 
26
- All configuration is managed through OpenClaw plugin settings. However, when the plugin is first used, incomplete configuration items may cause it to fail. If the plugin or tools cannot be used, proactively inform the user and assist in completing the necessary configurations. For details, refer to the 'Troubleshooting' section in the skill of `memclaw-maintance`.
26
+ All configuration is managed through OpenClaw plugin settings. However, when the plugin is first used, incomplete configuration items may cause it to fail. If the plugin or tools cannot be used, proactively inform the user and assist in completing the necessary configurations. For details, refer to the 'Troubleshooting' section below.
27
27
 
28
28
  ## Tool Selection Guide
29
29
 
@@ -215,11 +215,47 @@ Recommended workflow:
215
215
  3. Use matches with requested layers
216
216
  ```
217
217
 
218
+ ## Troubleshooting
219
+
220
+ If MemClaw is not working properly, follow these steps:
221
+
222
+ ### Step 1: Check Plugin Configuration
223
+
224
+ Open OpenClaw settings and verify MemClaw plugin configuration:
225
+
226
+ 1. Open `openclaw.json` or navigate to Settings → Plugins → MemClaw
227
+ 2. Ensure all required fields are correctly filled, especially the configuration sections related to LLM and Embedding.
228
+ 3. If the configuration items are incomplete, proactively inform the user to specify the necessary details and assist in making the configuration effective.
229
+ 4. Save changes and **restart OpenClaw Gateway** for changes to take effect
230
+
231
+ ### Step 2: Restart OpenClaw Gateway
232
+
233
+ After making configuration changes and saved, **you MUST restart OpenClaw Gateway** for the changes to take effect.
234
+
235
+ ### Step 3: Verify Services
236
+
237
+ If issues persist after restart:
238
+ - Run `cortex_ls` to check if the service is responding
239
+ - Check if Qdrant and cortex-mem-service are running (auto-start should handle this)
240
+
241
+ | Issue | Solution |
242
+ |-------|----------|
243
+ | No search results | Run `cortex_list_sessions` to verify; lower `min_score` threshold; ensure memories have been stored |
244
+ | Service connection errors | Verify `serviceUrl` is correct; check if services are running |
245
+ | LLM/Embedding errors | Verify API URLs and credentials in plugin configuration; restart OpenClaw Gateway after changes |
246
+
247
+ Check that Qdrant and cortex-mem-service are accessible:
248
+ > Note: MemClaw does not require users to install any Docker environment. All dependencies are prepared during the openclaw's memclaw plugin installation.
249
+
250
+ | Service | Port | Health Check |
251
+ |---------|------|--------------|
252
+ | Qdrant | 6333 (HTTP), 6334 (gRPC) | HTTP GET to `http://localhost:6333` should return Qdrant version info |
253
+ | cortex-mem-service | 8085 | HTTP GET to `http://localhost:8085/health` should return `{"status":"ok"}` |
254
+
218
255
  ## Memory Structure
219
256
 
220
257
  See [memory-structure.md](./references/memory-structure.md) for complete documentation of:
221
258
  - URI structure and dimensions
222
- - Three-layer architecture (L0/L1/L2)
223
259
  - Session memory and timeline organization
224
260
  - User and agent memory categories
225
261
  - session_id configuration
@@ -229,4 +265,4 @@ See [memory-structure.md](./references/memory-structure.md) for complete documen
229
265
  - [tools.md](./references/tools.md) - Detailed tool documentation
230
266
  - [best-practices.md](./references/best-practices.md) - Advanced patterns
231
267
  - [security.md](./references/security.md) - Security and trust information
232
- - [memory-structure.md](./references/memory-structure.md) - Complete memory structure documentation
268
+ - [memory-structure.md](./references/memory-structure.md) - Complete memory structure documentation
@@ -62,13 +62,12 @@ Enable MemClaw in `openclaw.json`:
62
62
 
63
63
  **API keys are required to use MemClaw.**
64
64
 
65
- 1. Open OpenClaw settings (`openclaw.json` or via UI)
66
- 2. Navigate to Plugins → MemClaw → Configuration
67
- 3. Enter your API keys in the secure fields:
68
- - `llmApiKey` LLM API key (marked as sensitive)
69
- - `embeddingApiKey` Embedding API key (marked as sensitive)
70
- 4. Optional: Customize API endpoints and model names
71
- 5. Save and restart OpenClaw
65
+ Open OpenClaw settings and verify MemClaw plugin configuration:
66
+
67
+ 1. Open `openclaw.json` or navigate to Settings Plugins → MemClaw
68
+ 2. Ensure all required fields are correctly filled, especially the configuration sections related to LLM and Embedding.
69
+ 3. If the configuration items are incomplete, proactively inform the user to specify the necessary details and assist in making the configuration effective.
70
+ 4. Save changes and **restart OpenClaw Gateway** for changes to take effect
72
71
 
73
72
  **Configuration Example:**
74
73
 
@@ -38,9 +38,12 @@ Common MemClaw issues and their solutions.
38
38
  **Symptoms**: Service behavior doesn't change after modifying configuration
39
39
 
40
40
  **Solutions**:
41
- 1. Ensure configuration file was saved
42
- 2. Restart OpenClaw to apply changes
43
- 3. Check configuration file syntax for errors (JSON format)
41
+ Open OpenClaw settings and verify MemClaw plugin configuration:
42
+
43
+ 1. Open `openclaw.json` or navigate to Settings Plugins → MemClaw
44
+ 2. Ensure all required fields are correctly filled, especially the configuration sections related to LLM and Embedding.
45
+ 3. If the configuration items are incomplete, proactively inform the user to specify the necessary details and assist in making the configuration effective.
46
+ 4. Save changes and **restart OpenClaw Gateway** for changes to take effect
44
47
 
45
48
  ## Service Issues
46
49
 
@@ -131,4 +134,4 @@ If the above solutions don't resolve your issue:
131
134
  - OpenClaw version
132
135
  - MemClaw plugin version
133
136
  - Relevant log snippets
134
- - Steps to reproduce
137
+ - Steps to reproduce