# Lovable — How we built Lovable, and why we keep rebuilding it

- Company: Lovable (lovable.dev)
- Announced: 2026-11-04T12:30:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://lovable.dev/blog/how-we-built-lovable-and-why-we-keep-rebuilding-it
- Record: https://forck.live/items/31552-how-we-built-lovable-and-why-we-keep-rebuilding-it
- Subject: Lovable / AI app builder

Lovable's co-founder explains how the company repeatedly rebuilt its AI app builder, narrowing the problem and constraining the agent to keep it dependable. The team chose greenfield projects and an opinionated stack, giving it control over libraries, code structure and the environment the generated code ran in. An async agent design that let the agent create tasks and delegate to subagents got stuck in technical rabbit holes, so the team deleted almost all agent code and returned to one request producing a predictable chain of tools. By late 2024 the main editing flow was a single response of file changes, with the model wrapping code in XML-like tags such as <lov-write> because native tool calling was not reliable enough. Instead of the fine-tuning the 2023 plan called for, engineers read chat logs from broken apps and wrote short knowledge files, which a retrieval step added to the model's context. The company says that work was critical to its late-2024 take-off, and an early version of Lovable Stack Overflow cut the rate at which users got stuck by 5%.

## Evidence

Verbatim from https://lovable.dev/blog/how-we-built-lovable-and-why-we-keep-rebuilding-it:

> Making Lovable simple and dependable has meant repeatedly rethinking how it works. As the technical landscape keeps changing, engineering choices that once helped can start holding you back. Many teams building AI-powered products face the same question: what should you keep, and what should you rebuild?
> 
> In the spring of 2023, I put an open-source project called GPT Engineer on GitHub. You described the software you wanted, it asked clarifying questions, and then it wrote the whole codebase. Later that year I wrote down the plan for Lovable : people who couldn’t code would create, deploy, and improve software through chat and instantly see the result. More than 100,000 pull requests in our codebase later, my co-founder Fabian and our team of engineers, designers, and product managers have turned that plan into Lovable, and our users have created more than 70 million projects on the platform to date.
> 
> I recently reread my original plan, and it's eerily similar to what we ended up building. What I didn’t anticipate was how many times we would reinvent the way we get there.

---

Record: https://forck.live/items/31552-how-we-built-lovable-and-why-we-keep-rebuilding-it
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md