docs: Update Cody Guardrails documentation with known limitations #1181
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
- Add Known Limitations section with 4 key points - Clarify exact string matching requirement (10+ lines) - Specify 290,000 indexed repositories coverage - Note BYOK limitation and Cody Gateway requirement - List supported platforms (Web app, VS Code, JetBrains IDEs) - Update callout to be more specific about Enterprise + Gateway requirements
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
MaedahBatool
approved these changes
Jun 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Update Cody Guardrails Documentation with Known Limitations
This PR enhances the Cody Guardrails documentation by adding clarity around limitations and requirements.
Changes Made
Added Known Limitations Section:
Updated Callout:
Why These Changes
The previous documentation didn't clearly communicate important limitations that affect customer deployments, particularly around BYOK compatibility and the exact matching mechanism.