claude-code - 💡(How to fix) Fix [Bug] CLAUDE_CONFIG_DIR env var ignored; still loads ~/.claude/CLAUDE.md [1 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/sam/.local/share/claude/versions/2.1.104 (expected in multi-process scenarios)\n at Tc_ (/$bunfs/root/src/entrypoints/cli.js:2836:2153)\n at Se6 (/$bunfs/root/src/entrypoints/cli.js:2836:1233)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-12T17:46:28.611Z"}]

TL;DR

The issue can be resolved by ensuring that the CLAUDE_CONFIG_DIR environment variable is correctly set and that the claude code is updated to respect this variable when reading configuration files.

Guidance

• Verify that the CLAUDE_CONFIG_DIR environment variable is set to the desired directory (/Users/sam/x) before running the claude code.
• Check if there are any default or fallback configurations that are causing the claude code to read from ~/.claude/CLAUDE.md instead of the specified directory.
• Review the documentation at https://code.claude.com/docs/en/claude-directory to ensure that the expected behavior is correctly understood.
• Consider checking for any existing CLAUDE.md files in the specified directory (/Users/sam/x/CLAUDE.md) to ensure that the correct configuration is being used.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue may be related to a bug or incorrect implementation in the claude code, and further investigation may be required to determine the root cause.

Recommendation

Apply workaround: Set the CLAUDE_CONFIG_DIR environment variable to the desired directory and verify that the claude code is respecting this variable. This may involve updating the claude code or configuration to correctly handle the specified directory.