Workflow Agents with Persistent Backlogs
Filip Kozera, CEO of Wordware, on the rise of vibe doing
This is really a claim about product shape, not just infrastructure. A cloud first agent can keep a live work queue running after the user walks away, watch inboxes and docs for changes, create new tasks on its own, and hand back a review pile in the morning. That makes Sauna look less like a chat app and more like an always on chief of staff, which is a much bigger behavior change than speeding up one prompt at a time.
-
The architectural burden comes from persistence. In coding, the job can end when code is merged. In knowledge work, the working state is the inbox, calendar, files, relationships, and active projects themselves, so the system has to keep sandboxes alive, remember context, and react quickly when a new email or message changes the task.
-
That is why Kozera compares Sauna less to a coding copilot and more to mission control. The product is a kanban with to do, working, and review, plus proactive task generation. Cloud execution matters because the useful work is the unattended middle step, not the final chat response.
-
The contrast with developer agents is narrowing fast. Claude Code began as a terminal tool tied to a developer machine, while OpenAI now positions Codex as cloud based and built for background parallel work. That means Sauna's edge is not simply being in the cloud, it is applying persistent cloud execution to messy business workflows like email, scheduling, hiring, and document handling.
The category is moving toward agents that own an ongoing backlog instead of waiting for prompts. The winners are likely to be the products that can stay on all day, act safely across many business systems, and package the results into a clean review loop. In that market, cloud persistence becomes table stakes, and workflow judgment becomes the real moat.