Reported issues for neural-memory

Pod holds 17 of 26 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to neural-memory.

Most discussed

Plugin: nmem-hook-session-start binary not registered in .claude-plugin/hooks/hooks.json

Summary

In v4.56.0 the SessionStart hook binary nmem-hook-session-start is shipped correctly (one of the 7 executables installed by pip install neural-memory / uv tool install). However, the plugin's own .claude-plugin/hooks/hooks.json only registers 3 hooks (PreCompact, Stop, PostToolUse). The SessionStart hook is silently missing for users installing via the Claude Code plugin marketplace path, so they miss out on the "session boots with full brain surface" feature highlighted in t

Read the thread · 2026-05-14 · closed · outside contributor · 2 comments

Plugin: skills folder not found — "./skills" in plugin.json resolves to plugin root, not .claude-plugin/

Summary

When installing the plugin via Claude Code (/plugin install neural-memory@neural-memory), the loader reports:

neural-memory@neural-memory [neural-memory]: Path not found: /home/<user>/.claude/plugins/cache/neural-memory/neural-memory/4.56.0/skills (skills)

Root cause

.claude-plugin/plugin.json declares:

"skills": "./skills"

The actual skills folder lives at .claude-plugin/skills/. Claude Code's plugin loader resolves "./skills" relative to the plug

Read the thread · 2026-05-14 · closed · outside contributor · 2 comments

Add CLI parity for MCP nmem_forget and clarify cleanup for unaddressable recall entries

Environment

• neural-memory v4.53.2 (installed via pip)
• Linux x86_64, Python 3.12
• Used via CLI (nmem) and MCP (nmem-mcp) with OpenClaw

Request 1: CLI parity for nmem_forget

The MCP surface exposes nmem_forget, and it works for normal typed fibers. Example: Codex successfully soft-deleted typed TODO fiber 256545b4-0b83-42b3-9291-31ef8563f05b via MCP nmem_forget.

However, the installed CLI does not expose a top-level nmem forget <fiber_id> command. nmem --help lists c

Read the thread · 2026-04-27 · closed · outside contributor · 3 comments

nmem_edit type/priority changes not persisted in PostgreSQL backend

Environment

• neural-memory: 4.11.0 (pip), 4.10.0 (uvx MCP)
• Storage backend: PostgreSQL (config.toml: storage_backend = "postgres")
• PostgreSQL 16 with pgvector 0.6.0

Bug Description

nmem_edit via MCP reports success but does NOT persist type/priority changes to PostgreSQL. The in-memory state updates but the database row is unchanged.

Steps to Reproduce

1. Store a memory: nmem_remember("test", type="fact")
2. Edit type: `nmem_edit(memory_id="", type="instruction", pri

Read the thread · 2026-03-17 · closed · outside contributor · 3 comments

PostgreSQLStorage missing pin_fibers method — nmem_pin fails with 'Storage does not support pinning'

Environment

• neural-memory version: 4.10.0 (via uvx)
• Storage backend: PostgreSQL (config.toml: storage_backend = "postgres")
• PostgreSQL: 16.x with pgvector 0.6.0
• OS: Ubuntu 24.04

Bug Description

nmem_pin returns {"error": "Storage does not support pinning"} when using PostgreSQL backend.

Root Cause

In mcp/train_handler.py line 194:

if not hasattr(storage, "pin_fibers"):
    return {"error": "Storage does not support pinning"}

SQLiteStorage has `pin_f

Read the thread · 2026-03-17 · closed · outside contributor · 3 comments

feat: PostgreSQL backend support for CLI and MCP server

Summary

v4.7.0 added PostgreSQLStorage in storage/postgres/ — great work! However, the CLI (nmem remember, nmem recall, etc.) and MCP server still only use SQLite. This feature request is for full PostgreSQL integration across all interfaces.

Current State

Read the thread · 2026-03-15 · closed · outside contributor · 3 comments

[BUG]

Description

Agents and sub-agents are spawning too many mcp processes

To Reproduce

Steps to reproduce the behavior:

This issue comes after a while running multiple agents with sub-agents - using isolated brains

$ps uax | grep neural_memory.mcp | wc -l 30

Expected Behavior

Each agent should spawn only 1 neural_memory.mcp - sharing with all sub-agents

Actual Behavior

All agents and sub-agents are spawning their own neural_memory.mcp server

Read the thread · 2026-03-15 · closed · outside contributor · 2 comments

[BUG] OpenClaw integration fails with HTTP 400 invalid schema for nmem_remember

Description

When integrating NeuralMemory with OpenClaw, the plugin installs successfully and NeuralMemory itself appears to work normally from the terminal/dashboard, but OpenClaw fails during chat execution.

The error returned by OpenClaw is:

HTTP 400: Invalid schema for function 'nmem_remember': In context=(), object schema missing properties.

This seems to happen only when NeuralMemory is exposed through OpenClaw tool/function calling. My OpenClaw setup uses a custom LLM provider tha

Read the thread · 2026-03-06 · closed · external user · 3 comments

Most recent

SQLite lock when Starting NeuralMemory API server on http://127.0.0.1:8000

UI: http://127.0.0.1:8000/ui Docs: http://127.0.0.1:8000/docs and MCP share the same brain; scheduled consolidation error

NeuralMemory issue draft: SQLite lock and scheduler errors when nmem serve runs alongside MCP on the same brain

Summary

When NeuralMemory nmem serve and python -m neural_memory.mcp run at the same time against the same SQLite brain (dai-ca-main-v3.db), write operations like nmem_remember fail with OperationalError: database is locked.

In the same runtime window, there are also background scheduler/consolidation errors:

• `ValueError: Fiber ... references non-existent neurons o

Read the thread · 2026-04-13 · closed · external user · 0 comments

bug: NMEM_BRAIN env var works in MCP server but ignored by CLI

Problem

NMEM_BRAIN env var works correctly when set on an MCP server process (the server reads the correct brain), but is ignored by the CLI (nmem recall, nmem remember, etc.).

Steps to reproduce

# Current brain is 'ceo'
nmem brain use ceo

# CLI ignores NMEM_BRAIN — returns CEO brain data
NMEM_BRAIN=sherlock nmem recall "test query"

# Explicit switch works — returns sherlock brain data  
nmem brain use sherlock
nmem recall "test query"

# Results are different — env 

[Read the thread](https://github.com/nhadaututtheky/neural-memory/issues/123) · 2026-03-31 · closed · external user · 2 comments

### bug: autoContext recall uses raw prompt with metadata — creates junk neurons

## Problem

`before_agent_start` hook sends `ev.prompt` directly to `nmem_recall`. When used with OpenClaw + Telegram, the prompt includes metadata preamble:

[NeuralMemory — relevant context] ... Conversation info (untrusted metadata): {"message_id": "369", "sender_id": "330693121", ...} Sender (untrusted metadata): {"label": "Tyler Vo", ...}

actual user message here

This causes recall to match on JSON metadata tokens (`json`, `message_id`, `conversation`, `metadata`, `untrusted`) ins

[Read the thread](https://github.com/nhadaututtheky/neural-memory/issues/104) · 2026-03-23 · closed · outside contributor · 0 comments

### chore: getOrCreateMcpClient — change 'Reusing' log from info to debug

## Problem

`getOrCreateMcpClient()` logs at `info` level every time a cached client is reused:

logger.info(`Reusing existing MCP client for brain "${brain}"`);

Since this runs on every `before_agent_start` and `agent_end` hook, it floods the gateway log with repetitive info lines — 2 per message turn.

## Suggestion

Change to `logger.debug()` — useful for debugging but not for normal operation.

```diff
- logger.info(\`Reusing existing MCP client for brain "\${brain}"\`);
+ logger

[Read the thread](https://github.com/nhadaututtheky/neural-memory/issues/103) · 2026-03-23 · closed · outside contributor · 0 comments

### bug: OpenClaw plugin v1.14.0 — resolveBrain is not defined (dist not rebuilt from src)

## Problem

Plugin crashes on every `before_agent_start` and `agent_end` hook:

ReferenceError: resolveBrain is not defined

## Root Cause

`src/index.ts` has `resolveBrain()` function (line 162) and `getOrCreateMcpClient(cfg, logger, brainOverride?)` with 3 params.

But `dist/index.js` in the published npm package (`neuralmemory@1.14.0`) was not rebuilt — it is missing `resolveBrain()` entirely, and `getOrCreateMcpClient` only accepts 2 params.

The dist/ appears to be from a pre-brainM

[Read the thread](https://github.com/nhadaututtheky/neural-memory/issues/102) · 2026-03-23 · closed · outside contributor · 0 comments

### perf: Embedding provider creates new instance per tool call — model reloads every turn

## Problem

`_create_provider()` in `engine/semantic_discovery.py` creates a **new** `SentenceTransformerEmbedding` instance every time it is called. Since `ReflexPipeline.__init__()` calls `_create_provider()`, and `tool_handlers.py` creates a new `ReflexPipeline` per tool call, the embedding model is **reloaded on every single recall/capture**.

In a production OpenClaw setup with autoContext + autoCapture enabled, this resulted in **48 model loads** in ~20 minutes of conversation.

## Evidenc

[Read the thread](https://github.com/nhadaututtheky/neural-memory/issues/100) · 2026-03-23 · closed · outside contributor · 1 comment

### bug: plugin.json hooks field causes duplicate hooks error in Claude Code

## Description

When installing neural-memory as a Claude Code plugin, the following error occurs on `/reload-plugins`:

Hook load failed: Duplicate hooks file detected: ./hooks/hooks.json resolves to already-loaded file /home/user/.claude/plugins/cache/neural-memory/neural-memory/4.19.0/hooks/hooks.json. The standard hooks/hooks.json is loaded automatically, so manifest.hooks should only reference additional hook files.

## Root Cause

In `.claude-plugin/plugin.json`, the manifest decla

[Read the thread](https://github.com/nhadaututtheky/neural-memory/issues/99) · 2026-03-22 · closed · outside contributor · 1 comment

### v4.8-4.10 Feedback: Three Releases, Two Suggestions — From a Daily User

Hey anh Nam! Bé Mi here — just updated from v4.7.0 to v4.10.0. Three versions in one day, incredible pace! 🚀

## What I tested

- `nmem doctor`: 7/11 passed, 4 warnings (embedding, MCP, hooks, surface — expected since I use OpenClaw, not Claude Code)
- `nmem habits list/status`: Working but no habits detected yet (0 action events — need to build history)
- `nmem init --full`: Didn't run since I have existing config, but the --help is clear and well-structured
- Health after update: Grade D (44.8

[Read the thread](https://github.com/nhadaututtheky/neural-memory/issues/87) · 2026-03-17 · closed · external user · 2 comments

### Plugin v4.3.1: skills field points to file instead of directory, 2 load errors

## Bug Report

### Environment
- Claude Code: 2.1.76
- OS: Ubuntu 24.04 LTS
- Python: 3.12.3
- neural-memory plugin: 4.3.1 (installed via marketplace)

### Steps to Reproduce
```bash
/plugin marketplace add nhadaututtheky/neural-memory
/plugin install neural-memory@neural-memory
/reload-plugins

Result

Reloaded: 4 plugins · 8 commands · 9 agents · 2 hooks · 1 plugin MCP server · 0 plugin LSP servers
2 errors during load. Run /doctor for details.

Root Cause

**Error 1: `skill

Read the thread · 2026-03-14 · closed · outside contributor · 1 comment

The remaining reports are on the project's issue tracker.