From GPT Engineer to Today: The Complete Lovable Journey in 6 Theses

What this is about

In June 2023, Anton Osika pushed a small Python repo to GitHub over a weekend: GPT Engineer (launch post, June 18, 2023). Top-trending worldwide within days, today over 55,000 stars (GitHub: AntonOsika/gpt-engineer). The open-source experiment became the commercial Lovable platform in November 2024 (Lovable launch post on LinkedIn), the first major release in April 2025 – and Lovable 2.0 in February 2026 with Workspaces, Multiplayer and Dev Mode. In the four months since, we got: Beyond Apps, Skills, Vent Tool, Mobile App, Google Workspace connectors, Gemini Enterprise, Opus 4.7 as default – and on May 27, 2026, subagents.

Read each launch in isolation and you see features. Read them together – from GitHub repo to agent framework – and you see a product strategy. Here are five theses, followed by the full timeline.

Prequel: From open-source repo to platform

Three phases everyone needs to understand before the five theses make sense.

2023 – GPT Engineer: The proof of concept

Key takeaway: Natural-language-to-codebase works – and the world was ready for it.

• June 2023: Anton Osika pushes GPT Engineer v0.0.1 to GitHub over a weekend (launch post) – a CLI tool that turns a prompt into a full code tree.
• Within days top-trending on GitHub worldwide (THE DECODER, June 24, 2023), today over 55,000 stars (repo).
• The open-source experiment becomes the blueprint for everything that follows – and turns Anton Osika into the figurehead of the codegen scene.

2024 – Lovable AB: From CLI to platform

Key takeaway: The experiment becomes a product – after two failed attempts.

• Anton Osika and Fabian Hedin found Lovable AB in Stockholm and turn the CLI into a web platform with live preview and iterative chat mode.
• Two quiet launches flop – Anton works through the reasons publicly himself (LinkedIn post, Nov 2024).
• November 2024: The third attempt sticks – templates, feedback portal, GitHub sync (launch announcement).

2025 – Hypergrowth & Lovable 1.x: From toy to tool

Key takeaway: In eight months, Lovable becomes Europe's fastest-growing SaaS – and production-ready at the same time.

• Feb 2025: USD 10M ARR (36kr). July 2025: USD 100M ARR in eight months (EU-Startups) and USD 200M Series A from Accel (TechCrunch, Accel statement).
• April 2025 – Lovable 1.x: Chat Mode Agent, Security Scan, Visual Edits, Dev Mode in beta.
• The platform shifts from "prompt-to-demo" toy to productive tool – the foundation that makes Lovable 2.0 make sense in the first place.

Only with this prequel does the February 2026 release "Lovable 2.0" become the logical next step – not a product reboot.

Thesis 1: Lovable is no longer an app builder

Until early 2026, the answer to "what does Lovable do?" was simple: web apps from prompts. With the Beyond Apps update in March, that definition collapsed.

Since then, Lovable analyzes CSV files, builds pitch decks, generates images and videos and processes PDFs – in the same chat where apps are built. The platform made the same jump ChatGPT made with Code Interpreter and Canvas: from single-purpose tool to general-purpose workspace.

The question is no longer "which tool for which task?" but "which task do I still outsource at all?".

Thesis 2: Building goes async

The April 27 mobile launch wasn't an "app version" of the web UI. It's the logical consequence of two preceding updates:

• The "Build more. Manage less." release made the agent more autonomous and tasks longer.
• Skills reduced the need to repeat conventions over and over.

If the agent can work autonomously for hours, you don't have to sit next to it. The mobile app turns the synchronous browser tab into a prompt queue with push notification. Drop ideas on the go, let builds run, review at the next coffee break.

That changes more than workflow – it changes how teams plan capacity. Vibe coding becomes available in time slots where coding was previously unthinkable.

Thesis 3: From solo builder to team tool

Lovable 2.0 shipped three features with one shared subtext: Workspaces, Multiplayer, Dev Mode. Lovable stopped being a tool for individuals.

• Workspaces cleanly separate projects by context.
• Multiplayer lets several people build at the same time.
• Dev Mode opens the platform for developers who want to work in code.

This is the prerequisite for agencies like us to use Lovable productively for client work – and the reason the entire industry needs to be re-sorted.

Thesis 4: Enterprise is no longer an add-on, it's the default

Three releases, one shared vector:

• Lovable Cloud (managed backend with built-in auth, DB, functions)
• Google Workspace connectors (Gmail, Calendar, Sheets, Drive connected directly)
• Gemini Enterprise as a data source for internal apps

What sounds like an integrations list is a strategic statement: Lovable wants to become the default layer for internal tools in companies that already run Google Workspace. That puts Lovable in direct competition with Retool, Glide and home-built Streamlit apps – at a far lower build threshold.

Thesis 5: Lovable is on its way to being an agent framework

The most important – and least noticed – release: the Vent Tool and self-improving loop. Lovable Stack Overflow (LSO) collects errors from builds, and the Vent Tool automatically generates PRs against the agent itself.

Combined with Skills (reusable instructions), Opus 4.7 (default model with better tool-use reliability) and the subagents announced on May 27, 2026, it becomes clear: Lovable is no longer just building apps – it's building the framework in which agents build. Subagents bring true parallelism to the build process for the first time – a head agent orchestrates, several read-only subagents research codebase and web simultaneously, each with its own context window (Lovable announcement). The shift from "vibe coding with one model" to "agent system with memory, skills, self-healing and orchestration" is underway.

Thesis 6: Lovable is the new WordPress

Probably our boldest thesis – and the one with the clearest evidence: Lovable won't stop at "AI app builder". Lovable will become the default layer for next-generation websites, the way WordPress was for two decades of the old web. Four reasons:

• Websites need constant updates – a perfect token use case. Every content change, every new landing page, every campaign launch is a prompt. Unlike apps that often sit untouched for years after launch, websites are a continuous build. Exactly what Lovable's pricing is built for.
• Lovable becomes the interface for marketing. Marketing teams today need a dev ticket for every change beyond the CMS. With Lovable the prompt becomes the interface – marketing builds, dev reviews in Dev Mode. The role WordPress Admin held for two decades.
• Headless CMS integration is trivial. Lovable + Sanity / Contentful / Strapi / Storyblok works out of the box. Content in the CMS, frontend in Lovable, deploy on Vercel. That cleanly resolves the old WordPress dilemma "editor vs. performance".
• Websites become interactive and fun again. Instead of SEO-driven text deserts, the exciting sites today are interactive experiences – see our view on immersive web design. Lovable + Framer Motion + React Three Fiber drops the threshold for such sites from "custom dev project" to "weekend prompt".

Consequence: The next 12 months decide whether Lovable actively addresses the web market (own templates, CMS integrations, SEO features) or whether others fill that gap. We're betting on option 1 – and we're already building our clients' websites exactly that way.

What this means in practice

For teams using Lovable productively, four consequences follow:

1. Rebuild your workflow. If you still use Lovable like an editor, you're leaving 70% of the value on the table. Queue-based, async work is the new default.
2. Invest in skills early. Every repeated convention belongs in a skill – it saves tokens and friction on every build.
3. Check the connectors. If your stack is Google Workspace, the new connectors make custom integrations unnecessary.
4. Prepare the enterprise conversation. With Cloud, Gemini Enterprise and Workspace, Lovable is now an answer to "what do you build internal tools with?".

The full timeline

What comes next

Four bets that follow from the pattern:

• Voice-first workflows. Mobile + Skills + longer autonomous tasks → voice prompts become standard input by Q3.
• Native agent marketplaces. Skills are the format. A marketplace is the obvious next step.
• Enterprise SSO + audit logs. Once Workspace connectors land, compliance features follow automatically.
• Lovable for websites. Templates, CMS connectors and marketing workflows as a dedicated pillar – see Thesis 6.

We track this continuously. To stay up to date: all Lovable resources at a glance.

Sources

• Anton Osika: GPT Engineer launch post (Substack, June 18, 2023)
• GitHub: AntonOsika/gpt-engineer
• THE DECODER: Developers fall in love with GPT-Engineer (June 24, 2023)
• Anton Osika on LinkedIn: GPT-Engineer launch & postmortem (Nov 2024)
• Lovable: "Building products takes too long" – launch post (Nov 2024)
• 36kr: Lovable Secures $200M Series A After ARR Exceeds $100M in Eight Months
• EU-Startups: Sweden's Lovable becomes fastest growing software company ever (July 17, 2025)
• TechCrunch: Lovable becomes a unicorn with $200M Series A (July 17, 2025)
• Accel: $200M Series A in Lovable – Enabling the Last 99%
• Lovable: Introducing subagents (May 27, 2026)