fix: improve response timeout error message with user-friendly description

[echobt]

Summary

Improves the 'Response timeout' error message displayed during streaming communication failures.

Changes

Replace generic 'Response timeout' message with a more descriptive, user-friendly error message:

The provider appears to be overloaded or your internet connection/proxy is experiencing issues communicating with it.

This helps users understand potential causes when they encounter timeout errors.

Files Modified

• src/cortex-tui/src/runner/event_loop/streaming.rs (2 occurrences)
• src/cortex-tui/src/runner/event_loop/subagent.rs (1 occurrence)

Testing

• Code compiles without errors (cargo check -p cortex-tui)
• All error messages updated consistently

[greptile-apps]

Greptile Overview

Greptile Summary

Improved timeout error messaging by replacing generic "Response timeout" with a descriptive message explaining potential causes (provider overload or network/proxy issues).

• Updated error messages in streaming.rs at two timeout locations (30s chunk timeout and 60s initial connection timeout)
• Updated error message in subagent.rs for Task tool timeout failures
• All three occurrences now provide consistent, user-friendly guidance

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are purely cosmetic string replacements that improve user experience without altering any logic, control flow, or error handling behavior
• No files require special attention

Important Files Changed

Filename	Overview
src/cortex-tui/src/runner/event_loop/streaming.rs	Updated timeout error message in two locations to provide clearer user guidance
src/cortex-tui/src/runner/event_loop/subagent.rs	Updated timeout error message for subagent task failures

Sequence Diagram

sequenceDiagram
participant User
participant EventLoop
participant Stream as Response Stream
participant Provider as LLM Provider
User->>EventLoop: Send message
EventLoop->>Provider: complete(request) with 60s timeout
alt Initial connection timeout
Provider--xEventLoop: Timeout after 60s
EventLoop->>User: Error: "The provider appears to be overloaded..."
else Connection successful
Provider-->>EventLoop: Stream established
loop Process stream events
EventLoop->>Stream: next() with 30s timeout
alt Chunk received
Stream-->>EventLoop: ResponseEvent (delta/done/tool_call)
EventLoop->>User: Display content
else Chunk timeout
Stream--xEventLoop: Timeout after 30s
EventLoop->>User: Error: "The provider appears to be overloaded..."
end
end
end

Loading

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[echobt]

🛡️ Security Audit Report

Status: ✅ APPROVED

Scans Performed

#	Scan	Result
1	Hardcoded secrets	✅ None found
2	Unsafe patterns	✅ Safe - no unsafe blocks in changes
3	Injection vulnerabilities	✅ None found

Analysis

The changes are security-safe:

• All modifications are static string literals with no user input concatenation
• No format string vulnerabilities - using .to_string() on static strings
• No sensitive information leakage - generic user-friendly error message
• No path traversal risks - timeout error handling only

Verification

Check	Result
Static string (no interpolation)	✅ Pass
No user input in error message	✅ Pass
No sensitive data exposed	✅ Pass
No format string injection	✅ Pass

---

Security audit performed by automated security-auditor agent