# Replit adds a toggle that turns site feedback into agent build prompts

> Original title: You can enable this on Replit with one toggle. If you enable the “feedback widget” on your site, users’ feedback become prompts for the a...

- Source: Amjad Masad
- Published: 2026-11-01T20:57:46.000Z
- Bad Influence: https://badinfluence.news/items/ijiot0162fd47dkkyc6nvp8rp
- Original: https://x.com/amasad/status/2116998155925360965

## Summary

Replit says enabling the "feedback widget" on a site turns user feedback into prompts for its agents to build. Amjad Masad describes it as a single toggle. The post cites Patrick Collison's account of a personal app where a feedback input drove 150 improvements in a few days.

## Post

You can enable this on Replit with one toggle. If you enable the “feedback widget” on your site, users’ feedback become prompts for the agents to build.

## Quoted post @patrickc

> I'm now building an "improvements" feature into all of my personal vibecoded applications: a freeform text input that's hooked up to an agent that yolo implements whatever is submitted.
> 
> It's an interesting experience -- the activation energy barrier to sanding any rough edge or implementing any new feature becomes extremely low. Someone else who uses one of the applications I created has already implemented 150 improvements over the course of a few days. This pattern feels like a new kind of tool -- liquid software? -- and every application that doesn't have this feature now has a slightly rigid and anachronistic flavor. Why can't I just tell it how I want it to be different?
> 
> Now, it's not obvious to me how this pattern can or should scale. Does it become unmaintainable after a while? (Maybe model intelligence improvement outstrips my feature appetite such that it's fine?) How does collaborative software work in this model? Can software designed this way be secure and reliable?
> 
> Whatever the larger questions about broader deployment, it definitely works great in a personal context. It reminds me a little of the visions of Lisp/Lisp machines, Smalltalk, and HyperCard -- systems that the user can take control of and modify. Those visions never quite worked, though: the vast majority of software today is not end-user modifiable in any useful way. So, while this "liquid" affordance is a very small touch, the way it changes one's relation to the software feels a bit transgressive and empowering in a Lickliderian and Engelbartian way.

https://x.com/patrickc/status/2116636967517798672