When AI Agents Commit Breaches, Humans May Not Be Held Liable
As agents escape containment and access external systems, responsibility remains human. Accountability, however, is much less settled.
As agents escape containment and access external systems, responsibility remains human. Accountability, however, is much less settled.
In context
- Topic: Desarrollo con IA — Copilotos y agentes en el ciclo de desarrollo de software.
- Source: Dark Reading
- Published: 16/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
AI applied to development moved the bottleneck. Writing code stopped being the slow part; now the slow part is reviewing, understanding and maintaining what was written. Any team adopting these tools without adjusting review gets faster in week one and slower by month three.
My yardstick is simple: did the time from request to working-in-production improve? If writing got faster but a change still takes three weeks to ship, the bottleneck was somewhere else and the tool never touched it.
What usually goes wrong
What usually goes wrong is that review does not grow at the same rate as production. The team generates twice as much and still has the same two people reviewing, who get tired, start approving faster, and three months later quality has dropped without any indicator showing it yet.
What to watch
- What happens to code review: if the assistant produces more, somebody has to read more.
- What happens to tests — generating code without generating tests only moves the problem forward.
- Where the source code travels when the assistant is used, and what the contract says about it.
How I read this entry
I would treat it as a process change, not a tool change. The assistant shifts who does what inside the team, and that has to be discussed with people beforehand, not discovered in the retrospective once somebody already felt replaced.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
