The meta-harness: orchestrating harnesses, not running one agent
One agent is a tool. A team with a boss is a harness. A boss of bosses is what he means by meta-harness.
Praful's personal timeline is the framing: prompting, then tools and gems, then agents, then teams, then harness, then meta-harness - 'it moved from tools to agents, to team, to harness, to a meta-harness.' The interface has become 'set it and forget it, obviously with all the guardrail possible', and the point is orchestration: 'we are not going to talk about just one agent, we are going to talk about orchestrated agents, and that is what the meta-harness is all about.' The roles are a film crew's: 'one of them will be building, one of them will be reviewing, one of them will be doing the Q&A, and one of them is going to check the security', coordinated because 'each of them cannot talk to each other, and that's where we need someone who's on top of it' - the orchestrator that 'plans, delegates, implements, reviews, tests', with 'a verifier... the human in the loop will be always there.' Stronger models do not retire the harness: 'stronger models do not make AgentGrid obsolete.'
Same architecture as Paul's own agent-team experiments: the orchestrator is the product, the workers are swappable.





