Add Pro prompt redaction integration#538
Open
Axiaoiac wants to merge 2 commits into
Open
Conversation
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
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
This PR integrates FlocksPro prompt redaction into the Flocks agent runtime and Pro settings UI.
The actual sensitive detection engine and bundled wheels live in the corresponding
flocksprobranch. This PR makes Flocks apply the Pro hook in the real model/tool/title/summary flows, so sensitive values can be redacted before model input and restored before tool execution or user-visible output.Changes
llm.call.beforehook output back to the real provider request.Behavior
When the feature is enabled in FlocksPro settings:
systemmessages are kept unchanged.user,assistant, andtoolmessages are redacted before entering the model.Validation
tests/session/test_runner_llm_hooks.pytests/session/test_stream_processor.pywebui npm run buildResult: passed locally.
Related
Requires the corresponding FlocksPro branch:
codex/privacy-detect-pro-cleanThat branch provides the bundled sensitive detection runtime, prompt redaction settings, hook implementation, and documentation.