Stripe co-founder adds an improvements input box to his mini apps—making change requests almost like posting comments

Patrick Collison made a small move on X: he added an improvements input box to all the small apps he built with vibe coding. Users casually write a sentence about what they want changed, and the agent behind it implements it directly.

For readers without a development background, vibe coding can be understood as a way of quickly assembling small apps using natural language and AI. It significantly lowers the barrier to building a small tool, but Patrick's input box points to another thing: the cost of making a change is also falling.

Previously, proposing a requirement involved gathering, scheduling, evaluating, and persuading people why it was worth doing. Now a single sentence can trigger implementation. For people building small tools and content products, user feedback can directly become iteration itself. Some commenters found this experience delightful: write one sentence about what you want changed, and someone goes and changes it.

The trouble shifts to the other end. Once the requirements pool becomes a chat box, what is scarcest may not be implementation capacity, but the judgment of what should not be done. Just because an agent can write code does not mean the product knows its boundaries. Who blocks poorly thought-out requests, who sets priorities, and who writes acceptance criteria—these questions will surface faster than writing code.

Patrick's original post is here: https://x.com/ason_j19084/status/2116735191322345549