Agentic development feels like magic to some teams and overhyped to others. Harnesses like Claude Code or Codex have been built around the local loop, the way things have always been done: a single developer changing code before opening a PR. Inside real organizations, agents hit walls: repo boundaries that demand human attention, a lack of episodic memory across sessions and unresolved questions around trust and permissions.Fixing this requires a higher level of abstraction: the *meta-harness*. Just as meta-frameworks like Next.js or Remix let React stay simple while giving developers what they need to ship, a meta-harness keeps the agent CLI focused on its job while bringing the components teams need to be effective: cross-repo orchestration, testing, and change tracking for greater autonomy,session memory that understands decisions and extracts tribal knowledge,collaboration features for easier handoffs, reviews, shareable sessions andsecurity primitives like sandboxes, remote execution, and clearly scoped agent permissions.This talk argues that the meta-harness - a layer above any single lab or agent - is the missing piece for integrating agents into how we build software across the stack.
