claude-code - 💡(How to fix) Fix API stream timeout causes silent failure - no retry, no user notification [1 comments, 1 participants]

API Error: Stream idle timeout - partial response received

This error appears in internal logs but is not surfaced to the user.

TL;DR

Implementing a retry mechanism for the Anthropic API or displaying the "API Error: Stream idle timeout - partial response received" error message to the user can potentially resolve the issue.

Guidance

• Investigate the Anthropic API documentation for built-in retry mechanisms or error handling guidelines that can be integrated into Claude Code.
• Modify the Claude Code application to catch and handle the "API Error: Stream idle timeout - partial response received" error, displaying it to the user or triggering a retry attempt.
• Review the tmux session and long-running agent workflow configurations to ensure they are not contributing to the timeout issue.
• Consider implementing a heartbeat or periodic check within Claude Code to detect and respond to idle states.

Example

No specific code example can be provided without knowing the implementation details of Claude Code or the Anthropic API. However, a generic approach might involve wrapping API calls in a try-catch block to handle timeouts and trigger retries or error messages.

Notes

The exact implementation details of the retry mechanism or error handling will depend on the specific requirements of the Claude Code application and the Anthropic API. This solution assumes that the "API Error: Stream idle timeout - partial response received" error is a reliable indicator of the timeout issue.

Recommendation

Apply a workaround by modifying Claude Code to handle the "API Error: Stream idle timeout - partial response received" error, as this directly addresses the silent failure issue described.