Developers and agents work together to ship code, but they're not always on the same page. An agent misses a design pattern your team takes for granted, or doesn't know the specific speed-versus-simplicity tradeoff your company makes every time.
Zenable learns those patterns from your codebase and from how your developers actually work, then proposes them as requirements, so your reviews and guardrails can hold every agent to them going forward.
Now you can review those proposals on a fully redesigned Insights page, built alongside our design partners to make it easier than ever to review, delegate, and approve. Every requirement in Zenable is attached to one or more scopes, which is how we segment context so only the right guardrails run at the right time, and proposed requirements now follow that same model. So you can browse them by the scope they belong to: a repository, a group of users, a file extension, a path pattern, and more.
Every proposal is also scored against a 6-point quality rubric before it reaches you. Use our recommended dimensions or bring your own; like everything in Zenable, it's batteries-included but fully configurable.
And reviewing doesn't have to happen in a browser. You can review and approve proposals straight from the zenable CLI or MCP server. And when a change needs a specific approval path, like a human in the loop or a particular role or teammate with the final say, you can wire that up with approval workflows on the Approvals page. More in the Insights docs.