durable workflows for agents

Everyone is building "agent workflow" libraries right now. Many of them optimize the easiest part. It is not that hard to wire: model calls tool calls retries fallback models structured outputs Give that task to a strong model and you can get a surprisingly decent orchestration layer very quickly. I am not saying those abstractions are useless. I am saying they are usually not the real problem. The real problem begins when your workflow lasts longer than the HTTP request that created it. That is where agent systems stop being a prompt-engineering exercise and start becoming a systems problem. The solution is to employ durable workflows from Runner: https://runner.bluelibs.com/guide/durable-workflows The Real Problem Is Time Real agent workflows often span minutes, hours, or days. They wait for: human approval revised input compliance review a webhook from another system a scheduled retry window a sub-workflow to finish somewhere else And while they wait, life happens: your server resta