claude-code - 💡(How to fix) Fix [Feature Request] Allow selective image deletion without requiring conversation compaction [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/avinashsangle/.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-25T03:53:13.790Z"},{"error":"AxiosError: Request failed with status code 403\n at zl (/$bunfs/root/src/entrypoints/cli.js:114:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:119:12696)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:121:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T04:33:29.900Z"},{"error":"AxiosError: Request failed with status code 403\n at zl (/$bunfs/root/src/entrypoints/cli.js:114:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:119:12696)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:121:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T04:33:45.600Z"},{"error":"Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"messages.16.content.2.image.source.base64.data: At least one of the image dimensions exceed max allowed size for many-image requests: 2000 pixels"},"request_id":"req_011CaPvRbufSo7yumU5FJdYZ"}\n at generate (/$bunfs/root/src/entrypoints/cli.js:11:55121)\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T05:16:48.726Z"},{"error":"Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"messages.16.content.9.image.source.base64.data: At least one of the image dimensions exceed max allowed size for many-image requests: 2000 pixels"},"request_id":"req_011CaPvhGSprR2HZ8Fx9jyJP"}\n at generate (/$bunfs/root/src/entrypoints/cli.js:11:55121)\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T05:20:20.552Z"}]

TL;DR

Check image dimensions to ensure they do not exceed the maximum allowed size of 2000 pixels for many-image requests.

Guidance

• Review the error messages indicating that at least one of the image dimensions exceeds the max allowed size for many-image requests.
• Verify the size of the images being attempted to be deleted to confirm if they are within the allowed limits.
• Consider resizing images to be under 2000 pixels in dimension if they are too large.
• Check for any other potential issues related to lock acquisition failures or Axios errors, but prioritize image size as the primary cause.

Example

No specific code example is provided due to the nature of the issue, but ensuring image dimensions are within the specified limits is crucial.

Notes

The provided errors suggest issues with image size and potential permission or request errors. However, the most direct and actionable issue to address first is the image size.

Recommendation

Apply workaround by resizing images to be within the allowed size limits to prevent request failures due to dimension exceeded errors.