alt Hacker NewsSo I am likely coming from a completely different world because I use entirely self hosted models - but is it really common in your workflows to just wait for 12 minutes without any feedback? I am constantly watching my model and following the path it’s taking and cutting it off or steering it if it’s headed down a dead path. I was just curious if this is really common to just have no feedback for 12 minutes?
Replies
Usually, the longer the AI works on something the crappier its output because that means the context is getting filled up.
If my AI prompt takes more than 5 minutes to execute, I'm almost certain to stop it and break up the task or be more specific about what files it should look at or what subtask it should tackle first. The people who let it run for hours are absolutely not getting anything worth keeping in the end.
I have workflows that run for 8-10 hours unattended regularly. This is on frontier models though.
But if I were to look in on them they’d be giving feedback during that time, but they wouldn’t need steering.
I recently had GPT 5.6 work on something for 54 minutes while I went to sleep
K3 is relatively slow, but 12 minutes points to the harness not the model IMO.
I have Claude workflows that it takes 30+ minutes to get any feedback while it thinks
Well, to be clear, there was some feedback (e.g. it was calling subagents and printing some thinking messages).
That said, yes, it is pretty common for me to wait 10, 20 and sometimes even 30 minutes without steering the model or looking at what its doing. I usually write a pretty detailed prompt at the start that describes the issue, the usecases, the testing to do and the definition of success; then I sometimes ask it to draft a plan and give it a read, but after that I just press enter, let it run and come back when it's done.
In the end I do a manual review, both of the code and the functionality, but most of the time I get exactly what I wanted.