LangGraph / LangChain
Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.
The launch integration story is detail-first: each entry should state status, function, validation evidence, and limitations rather than relying on a logo wall.
Pavri integrates through framework paths (LangGraph / LangChain, CrewAI, OpenAI Agents SDK, Anthropic Claude Agent SDK, Google Agent Development Kit, Microsoft AutoGen / Agent Framework, Generic Adapter), coding-agent endpoint coverage across macOS, Windows, Linux, Local MCP Broker routes, and downstream security and response workflows.
This page is substantive and indexable because it includes named integration paths, functions, status language, and limitations.
Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.
Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.
Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.
Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.
Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.
Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.
Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.
Assistant examples include Claude Code, Cursor, Windsurf, GitHub Copilot agent mode and VS Code agentic workflows, Gemini CLI, Aider, Claude Desktop, and JetBrains AI Assistant. Validation and limitations are maintained in coverage detail.
Inventory MCP servers and tools; route configured tool calls through Pavri's Local MCP Broker when enabled.
Send detection and decision context to downstream ticketing, notification, containment, and investigation workflows.
Enroll managed developer endpoints and deploy endpoint-sensor components according to OS-specific requirements.
Share the framework, assistant, MCP client, operating system, or response workflow you need validated.