Lovable

Plan

1. SupportsWork planning: Supports

   Work planning, supports. Plan mode investigates the project and writes a plan you edit and approve before any code changes. It plans one app and does not manage the team's backlog.

Build

1. Codebase context: Supports

   Codebase context, supports. Project and workspace knowledge (up to 10,000 characters each) carry rules and context into every request, scoped to code Lovable generated. Lovable cannot import an existing repository.

2. LovableCoreCoding: Core

   Coding, core. This is Lovable's primary stack role: Build mode writes and edits the whole app, frontend and backend, from chat, and paid plans can edit code directly in the browser.

3. Agent runtime: Core

   Agent runtime, core. The browser editor is where builders steer the agent through Chat, Plan, and Build modes and check results in the running app, with version history on every change.

4. Tool execution: Supports

   Tool execution, supports. Chat connectors and custom MCP servers bring outside context into a build, and app connectors such as Stripe and Databricks add integrations to the app itself.

Validate

1. Debugging: Supports

   Debugging, supports. Build mode can test in a browser, run frontend tests, and verify edge functions when asked, and Cloud logs show backend errors. Deep debugging moves to an IDE.

2. TouchesTesting: Touches

   Testing, touches. Verification tools run on request inside a build; Lovable does not maintain a test suite or gate publishing on tests.

3. Code review: Touches

   Code review, touches. Plan approval and the diffs in version history are the only review steps inside Lovable; pull request review happens in the team's Git provider once the code syncs.

4. Application security: Supports

   Application security, supports. A quick scan of row-level security, access rules, and npm dependencies runs on every publish, and a deep scan runs on request, but the docs say neither replaces a security review.

Ship

1. Source control: Supports

   Source control, supports. Two-way sync with GitHub, GitLab, or Bitbucket commits every change to one branch at a time, while the Git provider stays the system of record.

2. CI/CD: Supports

   CI/CD, supports. Lovable publishes and hosts the app on a lovable.app URL or a custom domain from a snapshot, but it runs no build pipeline, tests, or staged environments.

Operate

1. Observability: Touches

   Observability, touches. Cloud shows backend logs and usage for one app; production monitoring, alerting, and incident response need other tools.