Blog posts, research papers, and case studies from the OpenFlows team and community.
Agentic Development
Interactive AI chat in your IDE is not autonomous engineering; it is high-speed dictation. It tethers developers to prompt windows and breaks deep work. OpenFlows replaces synchronous chat wrangling with an asynchronous, issue-driven AI team that works while you sleep.
Nkwa Tambe5 min read
Design, Agent-Environment and permissions
An autonomous coding agent deletes a production database from a developer's machine.
Christian Yemele9 min read
Architecture
Every developer now runs an ad-hoc AI agent on their laptop with zero shared protocols or governance. The result is shadow engineering: "my agent broke that without me knowing." Software development has never worked this way. OpenFlows restores the battle-tested engineering standards that made software reliable in the first place.
Nkwa Tambe5 min read
Agentic Development
AI can generate code quickly, but reliable software needs more than suggestions. OpenFlows helps teams turn architectural intent into governed, secure, production-ready delivery.
Christian Yemele4 min read
Architecture
Every software engineer knows the shape of a good workday. You don't walk in, wave your hands, and hope the code appears. You clock in, read the ticket, think about the data flow, write a plan, build it in small verifiable chunks, get it reviewed, and when it's merged you pack up and go home. The workspace you occupied for those eight hours isn't sacred. It's a disposable seat you leave behind.
Christian Yemele4 min read
Architecture
AI gets expensive when a human sits at a keyboard, prompt after prompt, wrangling a machine into production-ready code through sequential conversation. Orchestration changes the equation: humans move from doing to directing while machines handle execution with precision.
Christian Yemele2 min read
Architecture
A design for cross-workspace command execution that lets a reviewer agent verify code by asking for evidence - never by entering the workspace it's reviewing.
Christian Yemele8 min read
Architecture Design System Design Flow Design
OpenFlows uses a durable state machine to control autonomous software delivery. The state machine defines how work moves from intent to merge, which approvals are required, which evidence is valid, and when downstream work must be invalidated. It is the coordination contract between agents, human reviewers, the shared store, GitHub, and the merge controller. The design goal is simple: autonomous agents may perform work, but only a versioned lifecycle record can authorize progress. Every phase transition must be explicit, evidence-backed, and recoverable.
Design
An orchestrator is only as trustworthy as the runtime underneath it. Coder gave OpenFlows that runtime - and it changed what OpenFlows could promise.
