Repository navigation
docs(grayswan): describe what post_call sends to Cygnal - #1968
Merged
Merged
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
Author
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
yucheng-berri
approved these changes
Oct 1, 2026
This branch was successfully deployed
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
Documents the Gray Swan post_call behavior shipped in BerriAI/litellm#43770 (LIT-6628). The page only said post_call scans "Model Outputs", so admins had no way to know that Cygnal now also receives the request conversation, the request
toolsand the answer's tool callsThe new "What Cygnal receives on
post_call" section under Choosing Guardrail Modes covers four things. A post_call-only setup now sends user prompts and tool results to Gray Swan. Tool-call-only answers are scanned, soblockcan return 400 andfail_open: falsecan fail those requests. The skip flags scope what is sent,scan_only_tool_resultsalso drops the requesttools, and Cygnal gets the answer alone when the conversation can't be read. Per-chunk streaming checks carry the conversation tooThe post_call row in the mode table is updated to match, and two existing typos are fixed ("recommmended", "treu")
scripts/check-writing-style.jsis clean on the page.scripts/check-docs.pyreports 4 errors, all indocs/harness/and the same on mainLink to Devin session: https://app.devin.ai/sessions/6b56dc5062414c51b44c3f65cbcad683
Open in Devin Desktop: https://app.devin.ai/desktop/session/6b56dc5062414c51b44c3f65cbcad683?variant=devin
Requested by: @yucheng-berri