← All IntelClip / AI AgentsTask horizon decides which product surface works
From Claude for Long-Horizon Tasks — Lance Martin, Anthropic · ≈0:55
Explains why autocomplete/chat fit the 10-20 minute era, local coding agents fit the 1-hour era, and async only becomes usable once horizons stretch further.
What’s in it
- Explains why autocomplete/chat fit the 10-20 minute era, local coding agents fit the 1-hour era, and async only becomes usable once horizons stretch further.
Clip transcript
model kind of shifts. And we've seen this over the past few years. So, I'm plotting here different Claude models and their task horizon. So, how much autonomous work can they do over time? And you might recall back in like the Opus 3 days, this was kind of like 2024, models could only do, you know, maybe 10 to 20 minutes of autonomous work. This is measured by meter. And in that regime, only certain product surfaces made sense. Things like autocomplete, things like chat, where your human is very in the loop cuz the model's really only doing a very short amount of work before you're steering it. Now, the past year we saw the rise of synchronous coding agents like Claude code. And this is, you know, a kind of a shift because then models could do maybe an hour of work. So, it made sense to have them run, but typically locally, where you could still steer them easily. And it's kind of interesting because during this regime, I remember efforts and I was involved in some efforts to build kind of async agents. But when models can only do like an hour of work, async as an experience is kind of bad. Um the model goes off and it like hits an error and it comes back to you over a short period of time. In order to really unlock async, we needed longer task horizons.
Comments
Sign in to comment.
Loading comments…