claude-code - 💡(How to fix) Fix [Bug] Drag-and-drop screenshots display full file path instead of [Image #N] format [2 comments, 3 participants]

[{"error":"AxiosError: Request failed with status code 401\n at tF (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12744)\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:117:2467)\n at async vo (/$bunfs/root/src/entrypoints/cli.js:420:4112)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:2267:190)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:6566:22652)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-15T14:58:57.544Z"},{"error":"AxiosError: Request failed with status code 401\n at tF (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12744)\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:117:2467)\n at async lg1 (/$bunfs/root/src/entrypoints/cli.js:2410:14018)\n at async ks9 (/$bunfs/root/src/entrypoints/cli.js:2410:14557)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-15T14:59:00.044Z"},{"error":"AxiosError: Request failed with status code 401\n at tF (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12744)\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:117:2467)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:8376:20310)\n at async vo (/$bunfs/root/src/entrypoints/cli.js:420:4112)\n at async kB5 (/$bunfs/root/src/entrypoints/cli.js:8376:20067)\n at async Ht7 (/$bunfs/root/src/entrypoints/cli.js:8376:20702)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-15T14:59:02.321Z"},{"error":"Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"req_011Ca5kmpUXeG1LBs8UQgoH9"}\n at generate (/$bunfs/root/src/entrypoints/cli.js:11:52772)\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-15T14:59:36.524Z"},{"error":"Error: ENOENT: no such file or directory, open '/var/folders/wv/d7d61bfx2qjbk5zc7f0zhnr40000gn/T/TemporaryItems/NSIRD_screencaptureui \r _kMXZlQ/スクリーンショット 2026-04-16 0.13.54.png'\n at readFileSync (unknown)\n at readFileBytesSync (/$bunfs/root/src/entrypoints/cli.js:53:1344)\n at Gv9 (/$bunfs/root/src/entrypoints/cli.js:1770:39042)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:5274:170)\n at map (native:1:11)\n at j (/$bunfs/root/src/entrypoints/cli.js:5274:161)\n at D (/$bunfs/root/src/entrypoints/cli.js:5275:128)\n at jx4 (/$bunfs/root/src/entrypoints/cli.js:490:1884)\n at dispatch (/$bunfs/root/src/entrypoints/cli.js:490:2560)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:476:110943)","timestamp":"2026-04-15T15:15:29.016Z"}]

TL;DR

The issue can be addressed by modifying the code to handle file names and display them in a user-friendly format, such as "[Image #N]", instead of showing the full file path.

Guidance

• Review the code that handles file uploads and displays file names to identify where the full file path is being displayed.
• Consider adding a function to truncate or format file names to display only the file name without the full path.
• Check for any recent code changes that may have introduced this behavior and revert them if necessary.
• If the issue is related to a specific library or dependency, consider updating or modifying it to handle file names correctly.

Example

// Example of how to format file names
const fileName = 'スクリーンショット 2026-04-16.png';
const formattedName = `[Image #${indexOfFile}] ${fileName.split('/').pop()}`;
console.log(formattedName);

Notes

The provided error logs indicate authentication and server errors, but they may not be directly related to the issue of file name display. The focus should be on modifying the code to handle file names correctly.

Recommendation

Apply a workaround by modifying the code to format file names correctly, as the root cause of the issue seems to be related to a code change or a specific library/dependency.