Coverage overview

Use the control point that matches how the agent runs.

Pavri uses framework instrumentation for agents built in code and endpoint controls for coding agents acting from developer workstations, then maps both into one operating model.

Review framework agents Review coding agents

Pavri launch coverage spans seven framework integration paths and coding-agent coverage across macOS, Windows, and Linux. Coverage depth varies by framework, version, operating system, assistant, entitlement, permission, and action path.

Launch coverage

Two agent environments, one shared value model.

Coverage is precise because framework agents and coding agents expose different control points. Pavri keeps their mechanisms distinct while preserving one investigation and policy model.

Framework agents

Integration paths: LangGraph / LangChain, CrewAI, OpenAI Agents SDK, Anthropic Claude Agent SDK, Google Agent Development Kit, Microsoft AutoGen / Agent Framework, Generic Adapter.

Inline framework decisions: allow / alert / deny

Coding agents

Managed developer endpoint coverage: macOS, Windows, Linux.

Local MCP Broker, PolicyCache, and local evidence/WAL are endpoint-sensor components

Pavri launch coverage across framework and coding-agent environments. — **Text equivalent:** Launch coverage includes framework integration paths and coding-agent endpoint coverage. Each environment has specific observation, decision, and evidence boundaries.

Public status language

Coverage labels are plain-language and bounded.

Use available, available with requirements, observe only, optional, planned, and not inline. Avoid logo walls without detail.

Coverage detail

Endpoint operating-system detail and accessible coverage matrix.

Coding-agent endpoint detail

macOS coding-agent coverage detail
Observation source	Assistant, process, workspace, file, Git, network, browser, MCP, and local evidence sources where permissions allow.
Inline controls	Local MCP Broker controls configured MCP calls; endpoint controls vary by action and entitlement.
Deployment requirements	Managed endpoint enrollment, endpoint sensor, PolicyCache, and approved privacy configuration.

Windows coding-agent coverage detail
Observation source	Assistant, workspace, process, ETW-backed evidence, file, network, Git, MCP, and local event context where available.
Inline controls	Configured MCP calls can route through the Local MCP Broker. ETW is evidence and is not depicted as generic denial.
Deployment requirements	Managed endpoint enrollment, OS-specific sensor permissions, PolicyCache, and evidence upload configuration.

Linux coding-agent coverage detail
Observation source	Assistant, shell, process, workspace, file, Git, network, MCP, and local evidence sources where deployed.
Inline controls	Configured MCP calls can route through the Local MCP Broker; other enforcement varies by action path.
Deployment requirements	Managed endpoint enrollment, supported distribution profile, PolicyCache, and local evidence/WAL.

Coverage depth varies by OS, assistant, permissions, action type, and control point.

Next step

Validate coverage against your agent estate.

Map your frameworks, assistants, operating systems, MCP clients, and response systems to Pavri's current control points.

Book a coverage review Open integrations