Menu

Product

How it worksDecision LayerFeaturesPerformanceCloud or self-host

Agents

Connect any agentInstall a pluginGuardrails

Zuppo

PricingDocsBlog
Start free
All posts
Product12 Nov 20266 min read

Why we built Merge on green

People shouldn't have to approve every typo fix. Here's how small, safe changes land on their own, and why you stay in charge.

The Zuppo team

Agents now open more handoffs than any team can read. If every one waits for a person, review becomes the bottleneck and people start skimming. Skimming is worse than not reviewing at all, because it looks like a review.

Green means more than a passing build

A handoff can merge on green only when it's small, low-risk and outside the paths you protect. Then every requirement has to pass:

  • Every required Stove check on the latest commit
  • No high findings from your code review steps
  • Merge readiness at or above your Decision Layer threshold
  • An agent safety review: secrets, destructive changes, writes outside the workspace, dependencies, tests and public APIs

People stay in charge

You decide what qualifies, in .zuppo/merge.yml, reviewed like any other change. A sample of what lands goes to My work for a spot-check, and if main breaks within an hour the change is reverted automatically.

The goal isn't to remove people. It's to stop spending them on changes that don't need them.

Turn it on in Settings → Merge on green, start with low-risk only, and watch the revert rate in Insights before you widen it.

Keep reading

Ship with people and agents.