Looking for a feature that you want but not seeing it? Let us know! We've got a public roadmap - take a look, submit something new, and vote for features you'd like to see at zenable.io/feedback
If you follow us anywhere you've probably heard us talk about requirements. They sure seem important to us since they are, you know... required. Our goal is to make it as easy as possible to write and manage requirements for your coding agents. That's why we're adding support for yet another method of creating and managing review contexts... AGENTS.md! AGENTS.md are an open, standard, simple way to...
Greg Brockman (President & Co-Founder at OpenAI) put it simply: “Say no to slop. Managing AI generated code at scale is an emerging problem, and will require new processes and conventions to keep code quality high.” We agree. every time you write a requirement in Zenable, we generate guardrails. But...
Today we're announcing Adaptive Guardrails; the Zenable Guardrails that automatically learn from you. Because if there’s one thing we keep hearing, it’s this: You DO know what you want You DON'T want to spend your life manually writing it all out And you know what, we agree...
Boris Cherny (creator of Claude Code at Anthropic) says to "Ruthlessly edit your CLAUDE.md over time. Keep iterating until Claude's mistake rate measurably drops." We totally agree. Now you can put your context hygiene on autopilot with our new automated context management...
When you're reviewing a change, sometimes you just don't have all of the information you need. That's why we built Pull Request Research, a set of code base searching and exploration tools that are available to our Pull and Merge Request bots...
IDEs are one of the most powerful Zenable integrations. That's why we stay on top of all of the newest features, shipping support within hours of their release, not months.This time we're here to let you know that we've added support for Cursor and Windsurf's hooks. Following in Claude Code and Kiro's footsteps, hooks are ways where you can bring determinsitic behavior to agentic work. Just run `uvx zenable-mcp install hook` and our CLI tool will auto detect which of these you've got installed, and configure them properly to ensure that your guardrails are in place and requirements are being followed, as soon as code is being written.
Everyone expects something from their software. But not everyone has gotten a chance to write it down yet. If that's you, we've got you covered! You don't need to have written requirements in order to have AI guardrails. Just by signing up with Zenable you get access to our marketplace, where you'll automatically get access to thousands of different possible guardrails, common requirements, frameworks, and other expectations. And if you don't like our out-of-the-box guardrails? No problem. Everything in the Zenable stack can be fully customized including disabling guardrails, pinning your environment to a specific version, or extending what we've provided to add context, specific to your environment. Check it out today on https://www.zenable.app/requirements
If there's one thing we know well, is that every team in a company is not the same. That's why customization is at the core of everything that Zenable does. And although we talk a lot about guardrails and requirements, we know that's not all that matters. So, if you want to have your code reviewers to be direct and to the point, or elaborative and give examples, we can do that! If you want it to talk like a cowboy, Dwight Schrute, or your favorite Ninja Turtle... That's all fine with us too. Just share your preference at zenable.app/context and you're all set. And the best part is that this is available at all subscription levels, even the free tier! Give it a shot today and let us know what you think
Real businesses don’t have “one size fits all” requirements. A guideline becomes a policy. A policy becomes a contract clause. Then you ship a new product, add an integration, or carve out an exception, and suddenly the same requirement applies to some codepaths but absolutely not all of them. That’s why we built Scopes...
If you've worked on a large software project, you know that requirements don't always apply. Sometimes it's only for certain teams, certain software, or even certain runtime environments. That's why we're releasing scopes. Now you can choose when a requirement applies, like only for certain users, repositories, and more. And along with that we are releasing our new advanced rule builder engine. So you can say that a requirement applies IF it is user A in repository A, OR if it's repository B, regardless of which user. That, and a whole lot more, are available at https://www.zenable.app/contexts?tab=scopes