Fix/bedrock streaming timeouts #280
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Configurable Request Timeout Setting
Summary
This PR adds a configurable timeout setting for agent chat requests, replacing the hardcoded 15-minute timeout with a user-configurable option while maintaining all existing timeout functionality.
Changes Made
🔧 Settings Infrastructure
requestTimeoutstate with 15-minute default valueagentChatConfig💬 Agent Chat Integration
requestTimeoutinstead of hardcoded valuerequestTimeout * 60 * 1000(minutes to milliseconds)👤 User Experience Improvements
Key Features
✅ Configurable Timeout: Users can set custom timeout values (default: 15 minutes)
✅ Persistent Settings: Timeout preference survives app restarts
✅ Enhanced Feedback: Multiple notification channels (console, chat, toast)
✅ Backward Compatible: Maintains existing 15-minute default behavior
✅ Heartbeat Integration: Works seamlessly with existing 30-second heartbeat monitoring
✅ Request Abortion: Proper cleanup when timeout is reached
Technical Implementation
Settings Flow
agentChatConfig.requestTimeoutuseAgentChathook reads setting viauseSettings()Timeout Handling
UI Components
Testing Considerations
Breaking Changes
None - this is a purely additive feature with backward compatibility.
Related Issues
Addresses timeout configuration requests and improves user control over agent response timeouts.
Screenshots
Settings UI showing new timeout configuration field in Agent Chat section
Ready for Review ✅