Why it matters
Sam Bhagwat frames an agent harness as context engineering combined with coding-agent capabilities, then argues that competitive harnesses tend to acquire persistent execution, tools, heartbeats, and cloud hosting until they resemble always-on “claws.” The talk presents that evolution as a product and infrastructure trend rather than a settled architectural requirement.
My takeaway: Adding persistence changes a developer tool into an operational principal. Before a harness becomes always-on, define its identity, permissions, budgets, wake-up conditions, audit trail, shutdown path, and ownership; otherwise a convenient context layer quietly becomes an unbounded automation service.