Merge Is the Bottleneck - Prasanna Sankar, Vorflux

A customer call ended with a bug, and an agent found the unfinished task in the transcript and screen recording. In Prasanna Sankar's account, it asked for permission to investigate, involved the responsible engineer, produced a pull request and drafted the customer followup after the fix shipped. That example captures where Vorflux's engineering work led: once agents can complete longer tasks, coordinating and starting the right work becomes its own bottleneck. Prasanna traces the progression from cloud coding sessions to persistent bots with a goal, an owner and a shared channel. The foundation is six practical problems: reproducing a working development environment, investing more effort in planning, dividing tasks with dependencies, testing without returning to a laptop, reviewing from multiple angles, and keeping changes mergeable as the base branch moves. Browser tests, recordings and staging links give people something concrete to inspect. The second half shifts from those coding workflows to on call, CI and project management bots that respond to signals already present in the company. Prasanna also describes the failure mode of indiscriminate automation: noisy alerts, unwanted pull requests and growing token bills. His proposed controls are budgets, visible work, named ownership and increasing responsibility as results justify it. These are lessons and examples from building Vorflux, with a clear acknowledgment that the bots remain fallible and some responsibilities still belong with people. Speaker info: Prasanna Sankar, Vorflux - https://www.linkedin.com/in/myprasanna/ - https://vorflux.com/ Timestamps: 0:00 - Prasanna's background and the move to longer agent tasks 3:46 - Reproducing the development environment in the cloud 5:10 - Planning effort and dependency aware orchestration 6:41 - Browser tests, recordings and staging links 7:44 - Independent reviews and the merge queue 8:48 - The bottleneck moves to project management 10:39 - Starting work from existing signals 12:58 - Why indiscriminate automation fails 14:17 - Autobots, ownership and a customer support example 16:56 - Orchestration, operating limits and the next bottleneck