We should not try to make AI agents into something more complex than they are. Technically speaking, an agent is a workflow. Many agents are crons, of which workflows are a superset. Because agents are workflows, we’ve seen a renaissance of workflow builders: Zapier, n8n, etc Whether you build an agent visually or with code, underpinning the workflow there must be an engine and infrastructure that makes it reliable. A workflow is a different kind of software than a web server. It’s not request-response. It consists of many steps, can fail a lot and is expected to recover, it can run for a very long time. This is why we’re so excited about @WorkflowDevKit. An agent is just “𝚞𝚜𝚎 𝚠𝚘𝚛𝚔𝚏𝚕𝚘𝚠”. Pair it with @aisdk (where each tool call is an “𝚞𝚜𝚎 𝚜𝚝𝚎𝚙”), AI Gateway for token reliability, and Fluid for efficient compute… and you have all you need to build the future of software.