[GH-ISSUE #684] [CHORE]: Refactor handleStreamResponse #391

Closed
opened 2026-02-22 18:19:17 -05:00 by yindo · 0 comments
Owner

Originally created by @timothycarambat on GitHub (Feb 6, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/684

Originally assigned to: @timothycarambat on GitHub.

What would you like to see?

The handleStreamResponse function is a disaster right now. We should handle stream responses from the LLM provider if the function exists (meaning that it is a special case).

If the function does not exist in the class then we fall back to the OpenAI catchall functionality. This will simplify the context and which how streamed responses are handled.

Originally created by @timothycarambat on GitHub (Feb 6, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/684 Originally assigned to: @timothycarambat on GitHub. ### What would you like to see? The `handleStreamResponse` function is a disaster right now. We should handle stream responses from the LLM provider if the function exists (meaning that it is a special case). If the function does not exist in the class then we fall back to the OpenAI catchall functionality. This will simplify the context and which how streamed responses are handled.
yindo added the enhancementcore-team-onlyfeature request labels 2026-02-22 18:19:17 -05:00
yindo closed this issue 2026-02-22 18:19:17 -05:00
yindo changed title from [CHORE]: Refactor `handleStreamResponse` to [GH-ISSUE #684] [CHORE]: Refactor `handleStreamResponse` 2026-06-05 14:35:03 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#391