claude-code - 💡(How to fix) Fix [Feature Request] Add manual expansion control for pasted text in prompts [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/seanconner/.local/share/claude/versions/2.1.112 (expected in multi-process scenarios)\n at Od_ (/$bunfs/root/src/entrypoints/cli.js:2748:2177)\n at Ke6 (/$bunfs/root/src/entrypoints/cli.js:2748:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-26T10:50:41.421Z"},{"error":"AxiosError: Request failed with status code 404\n at XU (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12736)\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 processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T03:04:16.385Z"},{"error":"AxiosError: Request failed with status code 404\n at XU (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12736)\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 processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T03:08:23.307Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/seanconner.\n at call (/$bunfs/root/src/entrypoints/cli.js:4727:7630)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T03:10:25.207Z"}]

TL;DR

Manually expanding pasted text may require adjustments to the application's text processing or a workaround to handle condensed references.

Guidance

• The issue seems to involve text processing and reference handling, so reviewing the application's text expansion logic might be necessary.
• Checking the error logs for patterns or clues about what triggers the errors could help in identifying a potential fix or workaround.
• The 404 status codes in the error logs suggest that some requests are failing to find their targets, which might be related to the text expansion issue.
• Investigating the Lock acquisition failed error could provide insights into potential concurrency or file access issues affecting the application.

Notes

The provided information does not directly point to a specific code fix, so further investigation into the application's logic and error patterns is needed.

Recommendation

Apply workaround: Given the lack of a clear code fix from the provided information, applying a workaround, such as manually handling text expansion or adjusting the application's configuration to better handle pasted text, seems like the most viable option.