Workflow

I spent last week running agent pipelines the old way — prompt, wait, scroll through a terminal buffer looking for the one line that tells me whether the research task finished before the timeout killed it. It works. Barely. When something goes wrong, good luck figuring out which agent step caused the mess. But agent chat logs are a special kind of black box. You can’t code review them. Plus, you can’t version-control the flow. But debugging is copy-paste-and-pray. After enough rounds of that, you start wondering: why are we treating AI agent orchestration like a conversation when every other piece of software is written as code? ...