It's basic: it opens a Ydoc for any streamed message, calculates the Ydoc updates, and transmits only those updates, with basic support for emitters and Redis. I've applied it to the reasoning block, but it can easily be added to other serializations (if needed).
Since it's a draft, I've implemented a new, dedicated Ydoc manager class and left the existing Ydoc manager unchanged.
I've done some testing, and it seems to work correctly, as expected, but in my current setup it's difficult to me work on it properly (slow connection on mobile device, home remote dev server, no pods, etc.): Please review and test it more deeply
BR
Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/open-webui/open-webui/pull/24126
**Author:** [@rgaricano](https://github.com/rgaricano)
**Created:** 4/25/2026
**Status:** ❌ Closed
**Base:** `dev` ← **Head:** `dev-Yjs_streaming_chat`
---
### 📝 Commits (10+)
- [`fe6783c`](https://github.com/open-webui/open-webui/commit/fe6783c16699911c7be17392596d579333fb110c) Merge pull request #19030 from open-webui/dev
- [`fc05e0a`](https://github.com/open-webui/open-webui/commit/fc05e0a6c5d39da60b603b4d520f800d6e36f748) Merge pull request #19405 from open-webui/dev
- [`e3faec6`](https://github.com/open-webui/open-webui/commit/e3faec62c58e3a83d89aa3df539feacefa125e0c) Merge pull request #19416 from open-webui/dev
- [`9899293`](https://github.com/open-webui/open-webui/commit/9899293f050ad50ae12024cbebee7e018acd851e) Merge pull request #19448 from open-webui/dev
- [`140605e`](https://github.com/open-webui/open-webui/commit/140605e660b8186a7d5c79fb3be6ffb147a2f498) Merge pull request #19462 from open-webui/dev
- [`6f1486f`](https://github.com/open-webui/open-webui/commit/6f1486ffd0cb288d0e21f41845361924e0d742b3) Merge pull request #19466 from open-webui/dev
- [`d95f533`](https://github.com/open-webui/open-webui/commit/d95f533214e3fe5beb5e41ec1f349940bc4c7043) Merge pull request #19729 from open-webui/dev
- [`a727153`](https://github.com/open-webui/open-webui/commit/a7271532f8a38da46785afcaa7e65f9a45e7d753) 0.6.43 (#20093)
- [`6adde20`](https://github.com/open-webui/open-webui/commit/6adde203cd292a9e3af9c64a2ae36b603fed096a) Merge pull request #20394 from open-webui/dev
- [`f9b0534`](https://github.com/open-webui/open-webui/commit/f9b0534e0c442631d1cb7205169588b9b6204179) Merge pull request #20522 from open-webui/dev
### 📊 Changes
**6 files changed** (+383 additions, -10 deletions)
<details>
<summary>View changed files</summary>
📝 `backend/open_webui/socket/main.py` (+33 -2)
📝 `backend/open_webui/socket/utils.py` (+97 -2)
📝 `backend/open_webui/utils/middleware.py` (+33 -5)
📝 `src/lib/components/chat/Chat.svelte` (+19 -1)
📝 `src/lib/components/chat/Messages/ResponseMessage.svelte` (+16 -0)
➕ `src/lib/utils/ChatMessageYjs.ts` (+185 -0)
</details>
### 📄 Description
PR to FIX Issue https://github.com/open-webui/open-webui/issues/23733 as I drew it in https://github.com/open-webui/open-webui/issues/23733#issuecomment-4265946838
---
This is a draft for using Ydoc to transmit message updates and address the main issue described in https://github.com/open-webui/open-webui/issues/23733.
It's basic: it opens a Ydoc for any streamed message, calculates the Ydoc updates, and transmits only those updates, with basic support for emitters and Redis. I've applied it to the reasoning block, but it can easily be added to other serializations (if needed).
Since it's a draft, I've implemented a new, dedicated Ydoc manager class and left the existing Ydoc manager unchanged.
I've done some testing, and it seems to work correctly, as expected, but in my current setup it's difficult to me work on it properly (slow connection on mobile device, home remote dev server, no pods, etc.): Please review and test it more deeply
BR
___
### Contributor License Agreement
- [X] By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/24126
Author: @rgaricano
Created: 4/25/2026
Status: ❌ Closed
Base:
dev← Head:dev-Yjs_streaming_chat📝 Commits (10+)
fe6783cMerge pull request #19030 from open-webui/devfc05e0aMerge pull request #19405 from open-webui/deve3faec6Merge pull request #19416 from open-webui/dev9899293Merge pull request #19448 from open-webui/dev140605eMerge pull request #19462 from open-webui/dev6f1486fMerge pull request #19466 from open-webui/devd95f533Merge pull request #19729 from open-webui/deva7271530.6.43 (#20093)6adde20Merge pull request #20394 from open-webui/devf9b0534Merge pull request #20522 from open-webui/dev📊 Changes
6 files changed (+383 additions, -10 deletions)
View changed files
📝
backend/open_webui/socket/main.py(+33 -2)📝
backend/open_webui/socket/utils.py(+97 -2)📝
backend/open_webui/utils/middleware.py(+33 -5)📝
src/lib/components/chat/Chat.svelte(+19 -1)📝
src/lib/components/chat/Messages/ResponseMessage.svelte(+16 -0)➕
src/lib/utils/ChatMessageYjs.ts(+185 -0)📄 Description
PR to FIX Issue https://github.com/open-webui/open-webui/issues/23733 as I drew it in https://github.com/open-webui/open-webui/issues/23733#issuecomment-4265946838
This is a draft for using Ydoc to transmit message updates and address the main issue described in https://github.com/open-webui/open-webui/issues/23733.
It's basic: it opens a Ydoc for any streamed message, calculates the Ydoc updates, and transmits only those updates, with basic support for emitters and Redis. I've applied it to the reasoning block, but it can easily be added to other serializations (if needed).
Since it's a draft, I've implemented a new, dedicated Ydoc manager class and left the existing Ydoc manager unchanged.
I've done some testing, and it seems to work correctly, as expected, but in my current setup it's difficult to me work on it properly (slow connection on mobile device, home remote dev server, no pods, etc.): Please review and test it more deeply
BR
Contributor License Agreement
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
[PR #24126] FIX: Issue#23733 - Ydoc_streaming_chatto [PR #24126] [CLOSED] FIX: Issue#23733 - Ydoc_streaming_chat