Agent ownership

Jonah Turnquist, chief technology officer of the property-planning software company PropCode, organises his AI coding agents like an engineering team, and finds that his own review time becomes the limit.

Engineering leader Jared Smith argues that when AI agents write the code, a person must still own how the changes fit together, which a better model will not fix.

An Amazon Web Services engineer argues that once an AI agent can change live systems, teams must prove separately who approved a change, what ran and whether it worked.

A Salesforce team built AI agents that design and test teams of other agents, aiming to cut hours to minutes, with an engineer approving every design.

Dan Graves, chief product officer at WitnessAI, has seven people on his team manage AI agents like junior hires, with a person approving work before it moves on.

Jakob Nielsen shows that most users keep whatever setting a product ships, and argues that AI agents hide their defaults in instruction files that need an owner.

Researchers held a workshop with 40 staff at a large embedded-software company and turned their views on AI agents into a roadmap for reorganising the company around them.

Pedro Franceschi, chief executive of Brex, says each AI agent should be set up like a new employee, with one job, written instructions, a human manager and a budget.