Sandboxing for Agent Governance
Beta New You can now see whether your developers run AI coding agents inside a sandbox. The new Sandboxing tab in Agent Governance inventory gives each user a sandbox coverage status: fully sandboxed, partially sandboxed, not sandboxed, or unknown. It also names the sandbox each session used, such as Docker, Seatbelt, or nono, and shows the policy outcomes for each user. You can export the usage data. The new Sandbox Gap widget on the Agent Governance overview counts the users whose sandbox coverage is not 100%, so you can see who to follow up with. Session policies can also match a session’s sandbox posture, and two new built-in policies alert on or block unsandboxed sessions. Both are off by default. For more information, see Sandboxing and Match on sandbox posture.License notice reports
Beta New You can now generate a license notice report that lists the open source dependencies in your projects and packages, along with their license texts and copyright notices. Use it to meet attribution obligations when you distribute software built on open source. For more information, see Create a license notice report and Generate a license notice report for a project.Configurable fail-open and fail-closed behavior
New Package Firewall now lets you decide what happens when it cannot complete a policy check, such as when the malware feed or an upstream registry is unreachable. Choose Warn (Fail-open) to allow the package and record the event, or Block (Fail-close) to reject it. You can set the action once at your root namespace, send Slack notifications for these events, and filter the logs by the Package not evaluated reason. For more information, see Action when a policy cannot be evaluated.Grok Build support for the MCP server
Enhancement You can now use the Endor Labs MCP server in Grok Build. Grok Build loads MCP servers from.cursor/mcp.json, so the server you configure in Cursor is also available in Grok Build. Scan dependencies, detect vulnerabilities, find leaked secrets, and review code for security issues.
For more information, see Endor Labs MCP server in Cursor.
Enterprise policy option for VS Code extensions
Enhancement You can now route VS Code through Package Firewall with VS Code’s enterprise policy, alongside or instead of patching VS Code’sproduct.json. The MDM scripts no longer enable either method by default, so select at least one when you generate the scripts. Scripts that are already deployed keep working until you replace them.
See Choose a method to compare the patch method and the enterprise policy.