claude-code - 💡(How to fix) Fix [Bug] Claude skips steps in multi-step instructions and ignores user constraints [1 comments, 2 participants]

[{"error":"Error: Request was aborted.\n at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T17:28:12.888Z"},{"error":"Error: Request was aborted.\n at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T22:00:59.884Z"},{"error":"Error: Request was aborted.\n at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T23:03:23.063Z"},{"error":"Error: File does not exist. Note: your current working directory is D:\Danil\Cloud\Git\work\whimsy\undead-steam.\n at call (B:/~BUN/root/src/entrypoints/cli.js:4778:7630)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T23:05:15.035Z"}]

TL;DR

Check the current working directory and file paths to ensure they are correct, as the "File does not exist" error suggests a potential issue with file accessibility.

Guidance

• Verify that the current working directory D:\\Danil\\Cloud\\Git\\work\\whimsy\\undead-steam is correct and that the required files are present in this directory or its subdirectories.
• Review the makeRequest function in cli.js to understand how requests are being made and why they might be getting aborted, potentially due to incorrect file paths or network issues.
• Ensure that the Request was aborted errors are not related to a network connectivity problem or a server-side issue by checking the server status and network connection.
• Consider checking for any recent changes in the code or environment that might have introduced these errors.

Notes

The provided information does not specify the exact steps or rules that are being skipped, making it difficult to provide a precise fix. The errors suggest issues with file accessibility and request aborts, which could be related to various factors including but not limited to network connectivity, server status, or incorrect file paths.

Recommendation

Apply workaround: Check and correct file paths and directories to ensure that all necessary files are accessible, and investigate network connectivity and server status to address the "Request was aborted" errors.