claude-code - 💡(How to fix) Fix [Bug] Rapid token consumption spike after session reset (23% usage in 1 minute) [1 comments, 2 participants]

[{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\zhang\AppData\Local\Temp\claude\C--Users-zhang-Desktop-FX-2026\43bc992a-7053-43a5-9d68-3fac5cc28b81\tasks\ab0f58b278f61ddcc.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:8754:299)","timestamp":"2026-05-04T12:12:48.044Z"},{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\zhang\AppData\Local\Temp\claude\C--Users-zhang-Desktop-FX-2026\43bc992a-7053-43a5-9d68-3fac5cc28b81\tasks\a76248188b0f25097.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:8754:299)","timestamp":"2026-05-04T12:18:49.664Z"},{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\zhang\AppData\Local\Temp\claude\C--Users-zhang-Desktop-FX-2026\43bc992a-7053-43a5-9d68-3fac5cc28b81\tasks\a21e3e89c11b2ecb7.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:8754:299)","timestamp":"2026-05-04T12:21:02.740Z"},{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\zhang\AppData\Local\Temp\claude\C--Users-zhang-Desktop-FX-2026\43bc992a-7053-43a5-9d68-3fac5cc28b81\tasks\ac7177a6f8100f508.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:8754:299)","timestamp":"2026-05-04T12:27:39.279Z"},{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\zhang\AppData\Local\Temp\claude\C--Users-zhang-Desktop-FX-2026\43bc992a-7053-43a5-9d68-3fac5cc28b81\tasks\a87b36bce6c9c6130.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:8754:299)","timestamp":"2026-05-04T12:34:07.496Z"},{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\zhang\AppData\Local\Temp\claude\C--Users-zhang-Desktop-FX-2026\43bc992a-7053-43a5-9d68-3fac5cc28b81\tasks\a6fd7b547b81cf9a1.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:8754:299)","timestamp":"2026-05-04T12:42:54.162Z"},{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\zhang\AppData\Local\Temp\claude\C--Users-zhang-Desktop-FX-2026\43bc992a-7053-43a5-9d68-3fac5cc28b81\tasks\a97dd0e43e0e46647.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:8754:299)","timestamp":"2026-05-04T12:52:22.149Z"},{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\zhang\AppData\Local\Temp\claude\C--Users-zhang-Desktop-FX-2026\43bc992a-7053-43a5-9d68-3fac5cc28b81\tasks\afa442c5663aa2646.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:8754:299)","timestamp":"2026-05-04T12:55:59.730Z"},{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\zhang\AppData\Local\Temp\claude\C--Users-zhang-Desktop-FX-2026\43bc992a-7053-43a5-9d68-3fac5cc28b81\tasks\a2928edab123cbcaa.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:8754:299)","timestamp":"2026-05-04T13:19:29.903Z"},{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\zhang\AppData\Local\Temp\claude\C--Users-zhang-Desktop-FX-2026\43bc992a-7053-43a5-9d68-3fac5cc28b81\tasks\afb157d466b6b9799.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:8754:299)","timestamp":"2026-05-04T13:33:31.330Z"},{"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-05-04T13:43:33.416Z"},{"error":"Error: 429 {"type":"error","error":{"type":"rate_limit_error","message":"This request would exceed your account's rate limit. Please try again later."},"request_id":"req_011CahdQfciH73JbrSUNWcEL"}\n at generate (B:/~BUN/root/src/entrypoints/cli.js:11:57304)\n at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-04T13:44:19.812Z"},{"error":"Error: 429 {"type":"error","error":{"type":"rate_limit_error","message":"This request would exceed your account's rate limit. Please try again later."},"request_id":"req_011CahdefK13uYjEA3DmdUDF"}\n at generate (B:/~BUN/root/src/entrypoints/cli.js:11:57304)\n at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-04T13:47:29.789Z"},{"error":"Error: 429 {"type":"error","error":{"type":"rate_limit_err…

TL;DR

The issue seems to be related to rate limiting and file handling errors, so a likely fix or workaround involves addressing these errors, possibly by implementing rate limiting handling or fixing file path issues.

Guidance

• Investigate the ENOENT: no such file or directory errors to ensure that the file paths being used are correct and the files exist before attempting to unlink them.
• Implement handling for rate limit errors (429) to prevent requests from being aborted, possibly by adding a retry mechanism with a delay.
• Review the code at B:/~BUN/root/src/entrypoints/cli.js:8754:299 and B:/~BUN/root/src/entrypoints/cli.js:50:3448 to understand why files are being unlinked and requests are being aborted.
• Consider adding logging to track when rate limit errors occur and how the application responds to them.

Example

No specific code example can be provided without more context, but a general approach to handling rate limit errors might involve a function like:

function makeRequestWithRetry(options) {
  try {
    // Make the request
  } catch (error) {
    if (error.status === 429) {
      // Wait for a certain period before retrying
      setTimeout(() => makeRequestWithRetry(options), 1000);
    } else {
      throw error;
    }
  }
}

Notes

The provided information is truncated, which might limit the ability to give a comprehensive solution. The issue seems to involve both file system errors and network request errors, suggesting a complex problem that may require adjustments in multiple parts of the application.

Recommendation

Apply a workaround by implementing a retry mechanism for rate limit errors and ensure that file paths are correctly handled to prevent ENOENT errors. This approach is chosen because it directly addresses the errors mentioned in the issue report.