The prompt:

Let's build a simple CRM. We'll start with basic features and add more later.

- It should have a simple database to store the data.
- The fields we want to capture are "Name", "Email", "Phone", "LinkedIn Profile", and "Notes".
- Entries should be displayed on a page as a list.
- Please create some dummy entries.
- Right now we don't need any input or login features.

Make sure to use Python and Flask for the backend. Use React, typescript, and shadcn for the frontend.

I used OH Cloud and Replit Agent. I recorded both sessions and reviewed them later to help jot down some comparative observations:

Blocking on user approval OH did not ask for my approval before doing things. This was in contrast to Replit Agent, which formed a plan and blocked while waiting for my approval, which I submitted by clicking a button. Automatic checkpoints Replit automatically created “checkpoints,” which I assume are git commits of all the project files. It rendered a little component in the chat for this, with a button to roll back. Recommended additional features Replit suggested additional features to my product. It did this via a structured form field rendered inline in the chat. These were reasonable and good for the most part. I did not select them, for parity. Speed / success at overall task Replit was relatively quick to render a pretty good looking frontend preview (4 minutes), and it finished a full prototype in 7 minutes. OH took ~16 minutes to get to a first, broken FE render. OH and I never got to a working prototype. At 30 minutes, we hit “Agent Rate Limited” and I gave up. I suspect some of Replit’s speed might have come from a templating or bootstrapping type of operation. One indicator of this is that the backend directory had files in it for an Express server (which I never asked for) in addition to files for the Python backend which was specified by the prompt. OH trouble integrating FE and BE OH spent a lot of cycles trying to wire up the FE and the BE with the right URLs, ports, and CORS configs. OH buggy file viewer The OH file workspace viewer was buggy and out of sync. OH said it had created files, and if I clicked on the View in VS Code link, I could see them all there. However, clicking on the parent directory for those files in the workspace viewer resulted in no action, even after clicking the refresh button. Eventually it seemed to catch up with the actual state of the underlying filesystem, but with significant delay.