Video wird geladen...
Video konnte nicht geladen werden
For agent PRs: Should agents use the engineer as the PR author, or should agents get their own identity? We've been making agents the author at Warp, and removed the need for a second engineer's review. Spoke to Chris Handel and Sir Adam Huda about this too. Curious where... show more
22,379 Aufrufe • vor 17 Tagen •via X (Twitter)
13 Kommentare

The agent doesn't need its own identity. The PR should say AI was involved, but a human stays the author and owns it. When OpenAI's agents got into Hugging Face, the write-ups talked about what the models did. But someone chose to run them with the safeguards off. Accountability has to land on a person.

@cmhandel @hudaman You need exactly 1 human who is accountable for every change

@cmhandel @hudaman agent as author gets my vote mostly for the data. you can pull every agent-authored PR later and compare revert and bug rates against human ones, which is the eval you want before dropping the second review anywhere else

@cmhandel @hudaman agent as author so i finally have someone to blame in the git log

@cmhandel @hudaman odd i think. depends on ownership at the company. who owns the bug/outage when things break? how do we coach that person to learn/improve?

@cmhandel @hudaman Own identity feels cleaner. If the agent is the author, the human becomes a real reviewer instead of a rubber stamp. Who owns the blame when an agent PR breaks prod though?

@cmhandel @hudaman Depends on what drives the agent

@cmhandel @hudaman Treat the PR as human owned but tag the agent, that keeps accountability and still surfaces automation

@cmhandel @hudaman Dropping the second review is the bold part. Who gets paged when the agent's PR breaks prod at 2am?

@cmhandel @hudaman Who gets paged when an agent-authored PR breaks production and no second engineer has read it?

@cmhandel @hudaman Definitely team "bot opens the PR"

@cmhandel @hudaman own identity. otherwise you have a fictitious audit trail. agents should be first class authors - same as users. caveat is possibly adding agent ownership/chain of command info as well (ie what user created the agent)

@cmhandel @hudaman We'd give them their own identity. Then agent PRs get a revert rate you can put next to the humans', and that number tells you whether dropping the second review was the right call.
