Add WebSocket streaming to chatbot UI #91
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implements real-time token streaming with automatic HTTP fallback when WebSocket fails. Connection is reused within the same session for better performance. - Stream responses token-by-token for better UX - Fallback to HTTP if WebSocket unavailable - Reuse connections per session - Add comprehensive test coverage Closes jenkinsci#82
berviantoleo
added
the
enhancement
berviantoleo
reviewed
Jan 6, 2026
berviantoleo
approved these changes
Jan 7, 2026
GunaPalanivel
force-pushed
the
feature/websocket-ui-integration
branch
from
c996edd to
1682182
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Implements real-time WebSocket streaming for chatbot responses with automatic HTTP fallback.
What's Changed
How It Works
The UI now tries WebSocket first for streaming responses. If that fails (timeout, disconnection, or unsupported), it automatically falls back to the existing HTTP endpoint. No configuration needed - it just works.
Testing
All existing tests still pass, plus 8 new tests covering:
Backward Compatibility
✅ Fully backward compatible - HTTP REST endpoints unchanged
Closes #82
Related to #29