Workflows have defined points where the agent stops and someone decides. Not a notification. A real gate the agent can't pass without approval.
Every engineer is running a coding agent locally. The prompt, the plan, and the approach live in a session nobody else can see.
Nothing reaches the team until the work is done. Intent, scope, and approach were all settled hours ago, in private.
Code review shows what the agent wrote. It doesn't show what it was asked to do, what it decided on its own, or whether anyone agreed to that before it started.
Changing a button color and changing how taxes get reported arrive the same way: a pull request, whoever's around, an approve button.
Switch human approval on or off per repository for workflows that have a human step by default. Base the call on how complex that codebase is, not a one-size-fits-all setting.
Human gates make sure a person reviews the step, whoever is available on your team at the time.
An agent completes its step and the workflow pauses. Nothing moves forward on its own.
The gate routes to a human, in the tools they already use. No agent can bypass a human approval.
Approve, reject, or send it back with feedback. The choice is always a person's to make.
What was approved, who approved it, and when, were logged permanently against that run.
Approval doesn't depend on one person being online. Anyone on your Dispatch team can pick up a pending gate.
Toggle approval on for the steps that need a human, and off for the ones that don't. You decide once, per workflow, when you set it up.
As a workflow proves itself reliable, its gates can be loosened, deliberately, not by default.
Every gate decision is logged, giving compliance and audit teams a clear answer to "who approved this, and why."
Approvals happen in the tools your team already uses, alongside a dedicated view in Upsun Dispatch when you need it.
A gate that's on stays on until someone explicitly says yes. There's no silent default to "approved."