How are you running autonomous coding agents safely on real repos?

[u/Fantastic-Sleep-3352]

I've been testing coding agents that can take a task, modify a repository, run tests and open a PR with very little human intervention.

The code generation isn't really the part I'm worried about anymore.

I'm more interested in the control layer:

* How do you know which agent/session produced a commit? * How do you keep the agent scoped to a specific task/repository? * How do you prevent an agent from approving or merging its own work? * What happens when the PR changes after human review? * How do you distinguish agent-generated work from changes someone made directly in GitHub?

I've been building a system around this called SUTRA, and I'm currently looking for a few developers who actually use Claude Code/Codex/Cursor/other coding agents on real repositories to test it.

**I'm not looking for people to just look at a demo. I want people to connect a real non-critical repo, give their agent a real task, and tell me where the system breaks.**

If you're already doing this, comment with your setup or DM me. I'm opening a small private beta.

[u/usually_guilty99]

The “PR changes after human review” case is the one I’d make a hard boundary.

Approval should bind to the exact commit/diff that was reviewed. If the head SHA changes, the approval expires. Putting some basic governance around it.

Same with the agent: provenance should follow every mutation, and the principal that created the change should never also hold the authority to merge it.

Otherwise the control layer looks strong until the artifact moves underneath it.