Update SDK documentation examples to use conversation.set_security_analyzer #130
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
…alyzer - Fix security analyzer examples in security.mdx to use conversation.set_security_analyzer() instead of deprecated Agent parameter - Update MCP integration example to use new security analyzer API - Update custom security analyzer example to use new API - This aligns with the deprecation of security_analyzer parameter in Agent constructor Co-authored-by: openhands <openhands@all-hands.dev>
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
This PR updates the SDK documentation examples to use the new
conversation.set_security_analyzer()API instead of the deprecatedsecurity_analyzerparameter in the Agent constructor.Changes Made
Security Guide (
sdk/guides/security.mdx)conversation.set_security_analyzer(LLMSecurityAnalyzer())instead ofadd_security_analyzerparameterMCP Guide (
sdk/guides/mcp.mdx)security_analyzer=LLMSecurityAnalyzer()from Agent constructor and addedconversation.set_security_analyzer(LLMSecurityAnalyzer())after conversation creationContext
This aligns with the deprecation of the
security_analyzerparameter in the Agent constructor (deprecated in v1.1.0, removed in v1.3.0). The new approach usesconversation.set_security_analyzer()to maintain the same functionality while using the updated API.Related PRs
Testing
The documentation examples now reflect the current API and should work correctly with the latest SDK version.
@malhotra5 can click here to continue refining the PR