claude-code - 💡(How to fix) Fix [Bug] Project autoMemoryDirectory setting ignored, defaults to global memory path instead [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/vscode/.local/share/claude/versions/2.1.101 (expected in multi-process scenarios)\n at qQ$ (/$bunfs/root/src/entrypoints/cli.js:2838:2153)\n at Ee8 (/$bunfs/root/src/entrypoints/cli.js:2838:1233)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T15:55:19.274Z"},{"error":"Error: Error normalizing tool input: ZodError: [\n {\n "expected": "string",\n "code": "invalid_type",\n "path": [\n "old_string"\n ],\n "message": "Invalid input: expected string, received undefined"\n },\n {\n "expected": "string",\n "code": "invalid_type",\n "path": [\n "new_string"\n ],\n "message": "Invalid input: expected string, received undefined"\n },\n {\n "code": "unrecognized_keys",\n "keys": [\n "old_str",\n "new_str"\n ],\n "path": [],\n "message": "Unrecognized keys: \"old_str\", \"new_str\""\n }\n]\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:4772:1005)\n at map (native:1:11)\n at E_$ (/$bunfs/root/src/entrypoints/cli.js:4772:556)\n at cm7 (/$bunfs/root/src/entrypoints/cli.js:7925:7500)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T16:13:11.878Z"}]

TL;DR

The issue can be resolved by configuring the autoMemoryDirectory setting to point to the correct path, /workspace/.ai/memory/, to ensure that memories are stored in the git-tracked project path instead of the user-global path.

Guidance

• Verify that the autoMemoryDirectory setting is correctly configured in the project's settings.json file to point to /workspace/.ai/memory/.
• Check if there are any other configurations or environment variables that might be overriding the autoMemoryDirectory setting.
• Consider manually moving the accumulated feedback files from the user-global path to the project path to consolidate the memories.
• Review the error messages to ensure that there are no other issues that need to be addressed, such as the lock acquisition failure or the ZodError.

Notes

The provided error messages do not seem to be directly related to the issue of memories being stored in the wrong path, but they should still be investigated to ensure that they are not causing any other problems.

Recommendation

Apply workaround: Manually configure the autoMemoryDirectory setting and move the accumulated feedback files to the correct path, as the root cause of the issue is the incorrect configuration of the autoMemoryDirectory setting.