claude-code - 💡(How to fix) Fix [Bug] Agent stuck in idle state without progression [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/naman/.local/share/claude/versions/2.1.121 (expected in multi-process scenarios)\n at p66 (/$bunfs/root/src/entrypoints/cli.js:2769:2177)\n at YY8 (/$bunfs/root/src/entrypoints/cli.js:2769:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T08:52:14.832Z"},{"error":"McpToolCallError: invalid parameters: json: cannot unmarshal string into Go struct field SearchCodeParams.limit of type int\n at Sp7 (/$bunfs/root/src/entrypoints/cli.js:4890:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T08:52:49.493Z"},{"error":"McpToolCallError: invalid parameters: json: cannot unmarshal string into Go struct field SearchCodeParams.limit of type int\n at Sp7 (/$bunfs/root/src/entrypoints/cli.js:4890:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T08:52:52.483Z"},{"error":"Error: Executable not found in $PATH: "rec"\n at spawn (unknown)\n at spawn (node:child_process:667:35)\n at spawn (node:child_process:14:39)\n at uT3 (/$bunfs/root/src/entrypoints/cli.js:7631:607)\n at AAK (/$bunfs/root/src/entrypoints/cli.js:7631:384)\n at async r (/$bunfs/root/src/entrypoints/cli.js:9212:62908)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T09:02:54.480Z"},{"error":"Error: console.error: [bun] Warning: ws.WebSocket 'unexpected-response' event is not implemented in bun\n at K (/$bunfs/root/src/entrypoints/cli.js:545:11688)\n at emitWarning (ws:43:42)\n at #onOrOnce (ws:170:18)\n at Rz6 (/$bunfs/root/src/entrypoints/cli.js:7624:4503)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T09:02:54.491Z"},{"error":"Error: Executable not found in $PATH: "rec"\n at spawn (unknown)\n at spawn (node:child_process:667:35)\n at spawn (node:child_process:14:39)\n at uT3 (/$bunfs/root/src/entrypoints/cli.js:7631:607)\n at AAK (/$bunfs/root/src/entrypoints/cli.js:7631:384)\n at async r (/$bunfs/root/src/entrypoints/cli.js:9212:62908)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T09:05:13.772Z"},{"error":"Error: Executable not found in $PATH: "rec"\n at spawn (unknown)\n at spawn (node:child_process:667:35)\n at spawn (node:child_process:14:39)\n at uT3 (/$bunfs/root/src/entrypoints/cli.js:7631:607)\n at AAK (/$bunfs/root/src/entrypoints/cli.js:7631:384)\n at async r (/$bunfs/root/src/entrypoints/cli.js:9212:62908)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T09:08:01.192Z"},{"error":"Error: Executable not found in $PATH: "rec"\n at spawn (unknown)\n at spawn (node:child_process:667:35)\n at spawn (node:child_process:14:39)\n at uT3 (/$bunfs/root/src/entrypoints/cli.js:7631:607)\n at AAK (/$bunfs/root/src/entrypoints/cli.js:7631:384)\n at async r (/$bunfs/root/src/entrypoints/cli.js:9212:62908)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T09:09:30.533Z"},{"error":"Error: Executable not found in $PATH: "rec"\n at spawn (unknown)\n at spawn (node:child_process:667:35)\n at spawn (node:child_process:14:39)\n at uT3 (/$bunfs/root/src/entrypoints/cli.js:7631:607)\n at AAK (/$bunfs/root/src/entrypoints/cli.js:7631:384)\n at async r (/$bunfs/root/src/entrypoints/cli.js:9212:62908)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T09:09:30.632Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T10:29:29.803Z"}]

TL;DR

The agent is likely stuck due to multiple errors, including lock acquisition failures, invalid parameters, and missing executables in the $PATH.

Guidance

• Verify that the rec executable is installed and available in the system's $PATH, as multiple errors indicate it's missing.
• Check the parameters passed to the SearchCodeParams function, ensuring that the limit field is an integer, as errors suggest invalid parameters.
• Investigate the lock acquisition failure for the /Users/naman/.local/share/claude/versions/2.1.121 path, which might be related to multi-process scenarios.
• Review the system's configuration and dependencies to ensure that all required executables and libraries are properly installed and configured.

Example

No specific code snippet can be provided without more context, but ensuring the rec executable is installed and configured correctly is a crucial step.

Notes

The provided errors suggest a mix of configuration, dependency, and potential code issues. Without more specific information about the system's setup and the code being executed, it's challenging to provide a precise fix.

Recommendation

Apply a workaround by installing the missing rec executable and verifying the system's configuration to ensure all dependencies are met, as this seems to be a critical issue based on the provided error messages.