What’s interesting here is that Routines and Managed Agents quietly change the unit of software from “app” to “ongoing obligation.” Most SaaS tools still assume a user shows up, clicks around, and initiates work. But a routine is basically a promise: “this thing will keep happening, with context, unless something breaks.” That sounds small, but it creates a very different product surface.
Amodei is credible precisely because he has skin in the game on both sides. The question isn't whether to take it seriously — it's what the 1-5 year window actually means for people in transition now. Retraining programs historically take 3-7 years to mature. The timing gap is the real problem.
How are you handling state management between agent handoffs in these routines? That's consistently been the breaking point in my setups: the model loses critical context at exactly the wrong moment mid-task. Curious whether Managed Agents changes that or just moves the problem upstream.
What’s interesting here is that Routines and Managed Agents quietly change the unit of software from “app” to “ongoing obligation.” Most SaaS tools still assume a user shows up, clicks around, and initiates work. But a routine is basically a promise: “this thing will keep happening, with context, unless something breaks.” That sounds small, but it creates a very different product surface.
Amodei is credible precisely because he has skin in the game on both sides. The question isn't whether to take it seriously — it's what the 1-5 year window actually means for people in transition now. Retraining programs historically take 3-7 years to mature. The timing gap is the real problem.
How are you handling state management between agent handoffs in these routines? That's consistently been the breaking point in my setups: the model loses critical context at exactly the wrong moment mid-task. Curious whether Managed Agents changes that or just moves the problem upstream.