Agent harnesses will move onto the shelf

The next useful abstraction for agents is not another chat box. It is the shelf.

Today, a serious agent is still something a team has to assemble: model, prompt, tools, MCP servers, runtime, permissions, secrets, memory, file system, cloud environment, evaluation loop, lifecycle rules, and a surface where the agent can be asked to work. That is a lot of scaffolding before the first useful task begins. It is also repetitive scaffolding. A "CMS and frontend agent using Next.js and PayloadCMS on DigitalOcean" should not need to be reinvented by every team that wants a site changed, migrated, audited, or extended.

The obvious next move is to rent the harness, not merely call the model. A team asks for a job to be done, and the user's main agent, perhaps Claude or ChatGPT sitting in Slack, acts as broker. It inspects the request, the repository, the permissions, the budget, and the desired outcome, then selects a specialized agent with the right harness already attached. The billing unit might be tokens, execution time, completed subtasks, or some blended meter; the more important shift is that the operational package becomes portable.

This is what the templatization of agent harnesses enables. Once an agent can be described as a stable bundle of instructions, skills, connectors, environment, policy, and quality gates, it can be versioned, compared, rented, improved, and swapped. The buyer does not want "access to a model." They want a known kind of work performed inside a known kind of runtime.

Anthropic's Managed Agents and OpenAI's Workspace Agents do not yet amount to a public bazaar of rentable specialists. But they make the shape visible. The harness is becoming a product boundary. Once that boundary hardens, agents stop looking like bespoke internal automations and start looking like labor units that can be put on a shelf.