fix: manage AI bindings separately per connection #14760
+51
−7
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.
What it does
Moves all AI backend bindings into ConnectionContainerModules. Therefore these are now scoped per connection (i.e. frontend) instead of globally for all connections.
The global bindings lead to a lot of interference when multiple connections were open. In fact AI streaming did only work for the latest connection.
Related to #14143
How to test
Follow-ups
Related to #14143 this prepares the code base to simplify / streamline a lot of the delegation mechanics.
Breaking changes
Attribution
Review checklist
Reminder for reviewers