2026-02-24T08-01-29_auto_memory/memories.db-wal, memory/2026-02-24-openclaw
This commit is contained in:
parent
d46667c89f
commit
515623870f
12
memory/2026-02-24-openclaw-memory-slot-conflict-fix.md
Normal file
12
memory/2026-02-24-openclaw-memory-slot-conflict-fix.md
Normal file
@ -0,0 +1,12 @@
|
||||
# 2026-02-24 Session Notes
|
||||
|
||||
## OpenClaw Memory Slot Conflict Fix
|
||||
|
||||
Session began with implementation of a plan to fix the OpenClaw memory slot conflict. OpenClaw enforces single-occupancy on the memory slot—only one plugin with `kind: "memory"` can be active. The `signet-memory-openclaw` plugin was being shadowed by OpenClaw's built-in `memory-core` plugin because the connector never set `plugins.slots.memory` in its config patch.
|
||||
|
||||
The fix involved three changes to `packages/connector-openclaw/src/index.ts`:
|
||||
1. Add `plugins.slots.memory: "signet-memory-openclaw"` to the connector's config patch (~line 291) to claim the memory slot
|
||||
2. Disable OpenClaw's native `agents.defaults.memorySearch` system (which conflicts with Signet's daemon-based memory/search) by setting `enabled: false`
|
||||
3. Add migration logic in `patchAllConfigsWithPlugin()` (~line 526) to fix existing installations that already have the plugin entry but are missing the slot assignment
|
||||
|
||||
Session began reading the connector source to understand current implementation before applying changes.
|
||||
Binary file not shown.
Binary file not shown.
Loading…
x
Reference in New Issue
Block a user