claude-code - 💡(How to fix) Fix [FEATURE] Show error reason in retry status line [2 comments, 2 participants]

There is no indication of what error triggered the retry (429, 529, timeout, ECONNRESET, etc.). Additionally, pressing Esc cancels the retry loop but does not display the error — it simply returns to the input prompt and the error information is lost entirely. Show the error type inline in the retry status: When the user presses Esc to cancel the retry loop, display the last error message before returning to the input prompt, so the error is not lost.

• Opening log files in another terminal to find the error — this is cumbersome and the log path is not well-documented.
• Waiting for all 10 retries to complete hoping the error is shown at the end — wastes time if the issue is persistent.

1. If it's a network error or auth issue, I'd rather cancel immediately and fix the problem
2. But currently I can't tell the difference, and pressing Esc loses the error entirely

TL;DR

Displaying the error type inline in the retry status and showing the last error message when the user cancels the retry loop can improve the user experience.

Guidance

• Modify the retry status line to include the error type, such as (529 overloaded_error) or (ECONNRESET), to provide immediate feedback to the user.
• Update the Esc key behavior to display the last error message before returning to the input prompt, ensuring the error information is not lost.
• Consider logging the error messages in a well-documented location, such as a log file, to provide an alternative way for users to access error information.
• Review the current logging mechanism to ensure it is user-friendly and accessible.

Example

# Pseudo-code example of displaying error type in retry status
retry_status = f"Retrying in {timeout}s · attempt {attempt}/{max_attempts} ({error_type})"
print(retry_status)

Notes

The proposed solution requires modifications to the Claude Code application, specifically the retry mechanism and error handling. The exact implementation details may vary depending on the application's architecture and programming language.

Recommendation

Apply the proposed workaround by modifying the retry status line and Esc key behavior to display error information, as it directly addresses the user's need for informed decision-making during the retry window.