Repository navigation
docs(guardrails): say that BYO middleware reads no files - #1191
Closed
apetraru-uipath wants to merge 1 commit into
Closed
apetraru-uipath wants to merge 1 commit into
apetraru-uipath wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are recorded for this documentation-only guardrail clarification and middleware reference update.
No open issues 🎉
What changed in this PR
This documentation-only PR clarifies BYO guardrail behavior and completes the LangChain guardrail middleware reference. It makes no runtime or API changes.
Changes:
- Clarifies that BYO guardrails evaluate text only, even though
UiPathByoGuardrailMiddlewareacceptsdetection_scope. - Adds
UiPathPromptInjectionMiddlewareto the middleware table and parameter list, documenting its LLM-only, PRE-only scope and threshold range and default.
| File | Description |
|---|---|
docs/guardrails.md |
Corrects BYO file-handling documentation and adds the prompt-injection middleware reference. |
Review effort: Balanced
apetraru-uipath
force-pushed
the
docs/guardrails-byo-files
branch
from
November 4, 2026 15:12
4d55a3d to
fc355ff
Compare
apetraru-uipath
changed the title
The Files (attachments) section said a BYO connector reads the files when it declares document support. The Agents backend evaluates BYO guardrails on the text only and never passes them the files. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
apetraru-uipath
force-pushed
the
docs/guardrails-byo-files
branch
from
November 4, 2026 20:15
fc355ff to
e924043
Compare
apetraru-uipath
changed the title
|
Contributor
Author
|
Superseded by #1195. |
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.
What changed?
Docs only,
docs/guardrails.md: the Files (attachments) section said a BYO connector reads the files when it declares document support. The Agents backend evaluates BYO guardrails on the text only and never passes them the files, so the sentence now saysUiPathByoGuardrailMiddlewareacceptsdetection_scopebut BYO guardrails evaluate text only.These pages are published through uipath-python, whose Publish Docs has failed since 2026-10-26 on a Git LFS clone of this repo. UiPath/uipath-python#1975 fixes that and makes the same BYO correction in the core docs. Merging this one dispatches a republish, which succeeds only once #1975 is in.
How has this been tested?
Built the full uipath.github.io site locally the way Publish Docs does (plugin clones, symlinks,
uv run mkdocs build) with this page: it builds, and the renderedlangchain/guardrailspage shows the new BYO sentence.Are there any breaking changes?
No version bump: docs only (precedent #1068).
🤖 Generated with Claude Code