Repository navigation
fix: block only normalized AgentSentry V3 BLOCK decisions - #1213
Merged
yaozheng-fang merged 1 commit intoNov 6, 2026
Merged
Conversation
Normalize DecisionType with int() so numeric strings such as "2" are handled consistently. Block only when the normalized decision is 2; allow other, missing, or unconvertible decision values regardless of Degraded or DegradeAction. Preserve unavailable responses for transport, API, and response errors. Align decision, degradation, conversion, and service-error tests.
YuWeihung
force-pushed
the
fix/agentsentry-decision-type
branch
from
November 6, 2026 08:26
e24b5a5 to
8f59776
Compare
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.
AgentSentry V3 allowed decisions were rejected when Degraded was true or absent. Normalize DecisionType with int() and block only when the result is 2, including the string "2". Other, missing, or unconvertible decision values allow the operation, independently of Degraded and DegradeAction.
Transport failures, HTTP/API errors, and malformed response structures still return unavailable. Existing local input and tool-plan checks are unchanged. No public API or configuration changes.