Today, general-purpose agents and first-party agents are at odds, competing over the interface and user relationship (e.g. Amazon blocking Muse). But the better model is clearly one where they complement each other. - External general-purpose agents are natural aggregators, but weak at execution for most tasks. - First-party specialists agents are weak aggregators, but have a structural execution advantage via controlling the data, systems and permissions required to complete tasks on their platforms The more complex and high-stakes the task, the larger this structural advantage becomes. Without a model that combines them, we risk a hitting capability and adoption ceiling. Agents with distribution will be limited to a relatively small set of low value tasks, and specialist agents will struggle to gain adoption. The better model is clearly one that combines them -- general-purpose agents aggregate intent and delegate to specialist agents to execute the job on their own platforms. Aggregators will compete interface quality and the surface area of useful work they can facilitate reliably. Specialist agents expand that surface area for aggregators, and compete on discovery and execution quality, much like they do already today. This model results in a number of win win outcomes for users, aggregators, and merchants/services: 1) Merchants and services retain what they care most about — owning the user’s account and control over execution, including checkout and fulfillment 2) Aggregators expand the range of jobs they can reliably complete, including high-stakes tasks users would only trust the underlying service, eg their bank, to execute directly 3) As a byproduct, the liability problem is solved for all sides. Assuming the merchant agent can verify delegated intent, it can stand behind executing that instruction correctly. This is a huge improvement versus today, where all liability is dumped onto the external agent’s user

Vertical personal agents and account ownership I don't buy that there will be one general-purpose personal agent. I think there will be specific agents for: •productivity / work •food and grocery •money •health Each of these will be owned by whoever controls the system of record and the right to act. Take money. The money agent should be your bank account and execute transactions on your behalf. It has the ledger, the license, the fraud models, and the liability when something goes wrong. A general agent that "logs into" your bank is a screen scraper with ambition. The bank that becomes an agent is the agent. The same pattern repeats: •Food and grocery: Whoever owns the cart, the inventory, and the last mile. The agent knows what's in your fridge because it put it there. •Health: Whoever holds your records, your labs, and a relationship with a licensed provider. Advice without the chart is a guess. Action without a license is a lawsuit. •Productivity / work: Whoever owns your calendar, inbox, and docs. Context is the moat, and it already lives somewhere. Agents win on three things: data, permission, and accountability. A horizontal agent can borrow the first, beg for the second, and has none of the third. Trust isn't general either. I'll let an agent book my dinner without asking. I won't let the same agent wire $50K or change my medication. Each domain has its own risk tolerance, its own regulation, and its own definition of "done." One agent can't hold all of those thresholds at once. The general-purpose agent doesn't disappear. It becomes the router. It's the front desk that knows which specialist to call. That's a real product, but it's thin. Routers commoditize, and the specialists capture the value. The question isn't "who builds the best assistant?" It's "who owns the account the assistant acts on?" The incumbents with licenses and ledgers have a bigger head start than they realize. The startups that win will either become the system of record in a vertical or make themselves impossible to route around. The future isn't one agent that does everything. It's a handful of agents that each own something.