claude-code - 💡(How to fix) Fix [Bug] Agent executes destructive database operations without confirmation, causing data loss [2 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/farrukh_kh/.local/share/claude/versions/2.1.123 (expected in multi-process scenarios)\n at x86 (/$bunfs/root/src/entrypoints/cli.js:2769:2177)\n at Jw8 (/$bunfs/root/src/entrypoints/cli.js:2769:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-01T09:54:48.091Z"},{"error":"Error: EACCES: permission denied, open '/etc/hosts'\n at writeFileSync (unknown)\n at XyH (/$bunfs/root/src/entrypoints/cli.js:142:1405)\n at n4H (/$bunfs/root/src/entrypoints/cli.js:139:7)\n at call (/$bunfs/root/src/entrypoints/cli.js:4919:1359)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-01T10:29:52.381Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T10:10:38.490Z"}]

TL;DR

The issue can be mitigated by ensuring proper database backup and validation before running Claude Opus, and checking the agent's configuration to prevent unintended DROP DATABASE operations.

Guidance

• Review the agent's configuration to understand why it executed a DROP DATABASE command before the rename operation, potentially causing data loss.
• Verify the integrity of the new dump to determine if it's valid or not, considering the loss of 7.8GB of local data.
• Check the error logs for any permission or lock acquisition issues that might have contributed to the problem, such as the reported EACCES error.
• Consider implementing a more robust backup strategy to prevent similar data losses in the future.

Example

No specific code snippet can be provided without more context about the agent's configuration or the Claude Opus version being used.

Notes

The provided error logs indicate multiple issues, including lock acquisition failures and permission denied errors, which might be related to the agent's behavior or the environment setup.

Recommendation

Apply a workaround by closely monitoring and validating the agent's actions, especially when performing critical operations like database renames, to prevent unintended data loss.