Approval gates: keeping AI agent changes off your branches until a human signs off
Roles, per-repository permissions and an approval step before any agent push. How enterprise teams run agents without giving up control.
Autonomy is what makes agents useful, and what makes them risky. Amoeba separates the two: agents can try anything inside a session, but nothing reaches a shared branch without approval.
Admins set owner, admin and member roles, with permissions per repository. When an agent is ready to push, the request appears for whoever holds approval rights, with the full diff attached.
The gate is a single place to see everything agents want to land, instead of finding out in a pull request.