Skip to content

docs: clarify Guardian does not block agent writes - #2845

Open
liukatkat wants to merge 4 commits into
mainfrom
katrina/guardian-non-blocking
Open

liukatkat wants to merge 4 commits into
mainfrom
katrina/guardian-non-blocking

Conversation

@liukatkat

@liukatkat liukatkat commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Corrects the Guardian overview description of what happens when findings are detected. The previous wording implied a blocking regeneration loop that runs until the scan is clean. In reality, Guardian returns findings to the agent and the agent decides whether to regenerate — the write is not blocked.

🤖 Generated with Claude Code

Guardian returns findings to the agent rather than looping until the
scan is clean; the agent decides whether to regenerate.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@mintlify

mintlify Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
semgrep-docs 🟢 Ready View Preview Sep 21, 2026, 10:43 PM

Clarify that Guardian does not block writes despite findings.
The merge from main restored the "loop until clean" framing. Reapply
both edits against the rewritten page: the intro sentence and step 4 of
the "How Guardian works" list.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

This branch was successfully deployed

1 active deployment
staging - docs 8c93e13e Deployed Sep 21, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants