fix: add __metadata__ fields and __event_emitter__ custom types#1265
Merged
Classic298 merged 1 commit intoMay 25, 2026
Merged
Conversation
Adds user_prompt, system_prompt, sources to the __metadata__ example. Expands __event_emitter__ to cover custom type forwarding through socket.io.
Collaborator
|
thanks! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary
user_prompt,system_prompt,sourcesto the__metadata__JSON example__metadata__explaining capture intent and recommended Pipe usage__event_emitter__to cover customtypeforwarding through socket.ioWhy
The current
__metadata__example is missing three fields that the backend populates. The__event_emitter__section doesn't mention that customtypestrings are forwarded to socket.io clients. Both of these things actually exist in OWUI today but aren't documented (and would've saved me a day of hacking).