claude-code - 💡(How to fix) Fix [Bug] Config save not triggered on Enter key press [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/david/.local/share/claude/versions/2.1.119 (expected in multi-process scenarios)\n at mH6 (/$bunfs/root/src/entrypoints/cli.js:2736:2177)\n at E$8 (/$bunfs/root/src/entrypoints/cli.js:2736:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-24T06:15:02.721Z"}]

TL;DR

The issue can be mitigated by not pressing esc after changing a config value and instead leaving the config without dismissing the changes.

Guidance

• The problem seems to be related to how changes are persisted when using the enter key to cycle through values in the config.
• To verify if a change has been persisted, check the config after leaving and re-entering it without pressing esc.
• The error message suggests a potential issue with lock acquisition, but it's marked as non-fatal and may not be directly related to the saving issue.
• Try leaving the config without pressing esc to see if the changes are saved as expected.

Example

No code snippet is provided as the issue seems to be related to the behavior of the claude application rather than a specific code snippet.

Notes

The provided error message is marked as non-fatal and may not be directly related to the issue at hand. The problem seems to be more related to the user interface and user experience of the claude application.

Recommendation

Apply workaround: The best course of action seems to be to avoid pressing esc after making changes to the config and instead leave the config without dismissing the changes, allowing them to be persisted.