feat: upgrade OpenWebUI pipes with native HITL - #72
Merged
Conversation
rlippmann
marked this pull request as ready for review
August 19, 2026 07:24
rlippmann
marked this pull request as draft
August 19, 2026 07:26
rlippmann
marked this pull request as ready for review
August 19, 2026 07:26
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Upgrade both OpenWebUI Pipe reference integrations to version 0.10.0 for the Context Compiler dev13 / Directive Drafter dev2 dependencies, and replace the Directive Drafter transcript-marker approval flow with native OpenWebUI confirmation.
Why
The branch keeps the Pipe integrations aligned with the upgraded Python packages and OpenWebUI lifecycle. Directive Drafter now presents a native
__event_call__confirmation dialog, so the drafted directive is reviewed before it can affect authoritative state. Approved directives go through the Context CompilerEngine; rejected directives do not change state, and no pending approval marker is written into the conversation transcript.Example metadata
Enginestate transitionqwen2.5:14b-instructCanonicalDirective, then applied only through the Engine after user confirmation.Checklist
Notes
0.10.0.__event_call__confirmation for approval../scripts/validate_python.sh— 212 passed, 6 skippednpx --yes markdownlint-cli2 python/reference_integrations/openwebui_pipe/README.md— passedgit diff --check— passed