Changelog: Control the Autopilot

AI is writing more code than ever, which means more dependencies, more findings, and more triage than any security team can keep up with by hand. Automation is the only way to stay ahead, but handing a pipeline the keys with no say in what it does is its own kind of risk. This release puts you in the driver’s seat. You decide, per severity, exactly how much of the vulnerability workflow Chainloop runs on its own, and where it stops and asks. Around that sit a GitOps-ready chainloop apply, alternative material groups in contracts, and one Slack workspace that can serve many organizations.

Vulnerability Automation, on Your Terms

A new Vulnerability Automation section in organization settings gives you a severity-by-action matrix. For each severity level, you toggle whether Chainloop auto-assesses new findings, auto-approves high-confidence AI verdicts, and automatically opens fix pull requests for approved, fixable assessments. Existing organizations keep the previous behavior, auto-assess Critical and High and nothing else, until you opt in. The dial goes from fully hands-on to fully autonomous, and every step in between is yours to set.

Worst-first. Auto-assessment and remediation now run in severity order, so a Critical finding jumps ahead of queued lower-severity work and gets assessed and fixed soonest.

Traceable remediation PRs. Pull requests opened by the remediation agent deep-link back to the risk assessment that triggered the fix, so a reviewer can trace every PR to its evidence.

Debounced Slack digests. Bursts of activity, new findings, reviews, remediation PRs, are bundled into one Slack digest per channel instead of a message per event.

A GitOps-Ready chainloop apply

chainloop apply keeps growing into the single declarative entry point for your Chainloop resources, and now that includes your own workflow templates.

Organization workflow templates. Define your own WorkflowTemplate resources with chainloop apply, embedding a contract inline or referencing an existing one by name. Your templates then show up across the UI, ready to pick when you create a workflow or onboard a project.

Point it at your repo. chainloop apply -f ./ no longer fails on YAML that is not a Chainloop resource. GitHub Actions workflows, Helm values, and friends are skipped and reported in a new “Skipped” section, and a --exclude glob flag plus a .chainloopignore file let you opt files out explicitly. That makes apply practical to run straight from a repo in GitOps and CI.

”At Least One Of” Material Groups

Workflow contracts can now express alternatives between materials. Assign materials to a named group, and the attestation is satisfied when at least one member of the group is provided, for example accept either a CycloneDX or an SPDX SBOM. The CLI surfaces each group’s rule and its satisfaction status as the attestation runs, so contributors see exactly what counts.

One Slack Workspace, Many Organizations

Multiple Chainloop organizations can now share a single Slack workspace. Outbound notifications stay correctly scoped per organization, and Ask Chainloop routes each question by your live organization membership. If you belong to several connected organizations, Slack shows an org picker, remembers your choice, and offers a switch-org affordance, so a consultancy or a multi-org enterprise can run everything from one workspace.

Full changelog at docs.chainloop.dev/changelog.

Let’s Talk

We will be at Black Hat USA 2026 in Las Vegas, booth #5810, on August 5 and 6. If AI-driven code volume is outrunning your triage, come talk through where to set the dial for your team.

• Chainloop at Black Hat USA 2026

• Request a demo: chainloop.dev/book-a-demo

• Documentation: docs.chainloop.dev

• Open source: github.com/chainloop-dev/chainloop

• Follow us on LinkedIn