Lovable

Connectors are documented in a single catalog with Lovable handling authentication, credentials and requests, offering three connection types: app connectors, chat connectors and app user connectors where each person using the published app connects their own account, with each connector's page stating which types it supports.

Roughly ninety integrations are individually documented, spanning Salesforce, HubSpot, Pipedrive and Zoho CRM, Snowflake, BigQuery, Databricks, Redshift, ClickHouse and Microsoft Fabric, Shopify, WooCommerce, PrestaShop and Lightspeed, Stripe, Chargebee, QuickBooks and Xero, Slack, Twilio, Telegram and Resend, Workday and Ashby, Aikido and Wiz, Notion, Airtable and Contentful, and AWS S3. An any-API route, a create-connector path, custom MCP servers and MCP registries cover anything unlisted.

Sourcedocs.lovable.dev integrations introduction, app-connectors, chat-connectors, app-user-connectors, any-api, create-connector and integration catalogread 2026-08-31

Build mode, previously Agent mode, is documented as the autonomous execution mode that takes ownership of a task end to end, understanding intent, exploring the codebase for context, applying changes across files and resolving issues during development, with visible tasks showing progress and results reviewed before moving on.

Plan mode handles decision-making and the two are switchable at any time. Subagents are documented as a distinct feature, and cross-project referencing allows one project to draw on another. Skills apply reusable instructions, code mode and the project editor expose generated files for direct editing, and drafts and project history support iteration.

Sourcedocs.lovable.dev agent-mode, plan-mode, subagents, cross-project-referencing, skills, code-mode, projects/editor, drafts and projects/history pagesread 2026-08-31

Knowledge is documented as persistent instructions and context for the agent, defined once and always included in context, at two levels: workspace knowledge holding shared rules across all projects such as coding standards, preferred libraries and naming conventions, and project knowledge holding application purpose, database schema, architecture decisions and domain terminology. Workspace knowledge is described as a text field, and the vendor contrasts it with Skills, which load on demand.

The vendor's FAQ states that project and workspace knowledge plus the customer's code and components are the primary context sources and does not describe reading instruction files from the repository or external sources. Design systems are Lovable projects that export reusable components, colors, fonts and styling rules, which other projects connect to and inherit, with immediate propagation, precedence ordering across multiple connected systems, and no versioning. Cross-project referencing and roughly ninety integrations supply further per-request material.

Sourcedocs.lovable.dev features/knowledge, design systems FAQ and knowledge context-sources FAQread 2026-08-31

Plan mode investigates the project and writes a plan the user reviews, edits and approves before any code is written, and Lovable states Plan mode never modifies code. It is one of three modes the user picks, and Build mode implements changes directly, so the approval sits in an optional mode rather than in the build path; project monitoring findings are fixed only when the user asks. Workspace admin controls, integration admin controls, groups and project visibility settings constrain who can do what.

Sourcedocs.lovable.dev plan-mode and project-monitoring pagesread 2026-09-29

Documented platform controls include a trust center, SAML single sign-on, SCIM provisioning, two-factor authentication, workspace identity and identity reuse, groups and people access controls, integration admin controls, project visibility settings, and Enterprise audit logs. Enterprise materials describe centralized identity, granular access controls and workspace-wide security oversight.

A data opt-out setting is documented at Business tier, and secrets and build secrets are managed separately from generated code. Security scanning of the generated application is documented separately through a security center, security insights, sensitive-data scanning and Aikido and Wiz integrations.

Sourcedocs.lovable.dev trust-center, saml-sso, business/sso, business/scim, two-factor-authentication, workspace-identity, groups, people, admin-controls, business/data-opt-out and secrets pagesread 2026-08-31

Enterprise audit logs record actions taken by workspace members and, since 24 August 2026, which client each action came from across Web, Desktop, iOS and Android, filterable by client or by individual member, with earlier entries marked Unknown. Dedicated pages cover project monitoring, logs, project usage, analytics and security insights. Build mode surfaces visible tasks as work proceeds, and project history records changes to a project. Audit logs are documented among Enterprise workspace capabilities alongside workspace-wide security oversight.

Sourcedocs.lovable.dev audit-logs, project-monitoring, logs, project-usage, analytics and security-insights pages, changelog and lovable-for-enterpriseread 2026-08-31

Projects are durable objects with a documented history page recording changes, drafts persist unfinished work, and project chat is a documented persistent surface. A Knowledge feature holds project configuration, and cross-project referencing allows one project to draw on another. Build mode is documented as exploring the codebase for context when given a task rather than carrying forward learning between tasks, and skills apply reusable instructions authored by the customer with no documented agent-side updating.

Sourcedocs.lovable.dev projects/history, drafts, projects/chat, knowledge, cross-project-referencing, agent-mode and skills pagesread 2026-08-31

A default hosting region is set from Settings, Security and compliance, Privacy and security, choosing Americas, Europe or Asia Pacific. On Business and Enterprise workspaces admins can set a required default region for every new project, after which members cannot choose a different region; the setting applies only to new projects and existing projects keep their original region.

Country-specific regions including Germany, Japan and United States East are available on Enterprise by request. Enterprise materials list regional code hosting. Lovable Cloud provides hosting with custom, verified and transferable domains, and two-way GitHub sync plus external deployment guidance allow hosting the application elsewhere.

Sourcedocs.lovable.dev privacy-and-security-settings, cloud, hosting, custom-domain, github and external-deployment-hosting pages, lovable-for-enterpriseread 2026-08-31

Design templates are documented as a Business-tier capability, alongside a managed registry, a remix path for starting from an existing project, a prompting library, skills carrying reusable instructions, and design systems supplying customer components. Video tutorials and an idea-to-app guide cover getting started. No catalog of ready-made finished applications published by the vendor appears in the complete documentation inventory.

Sourcedocs.lovable.dev business/design-templates, managed-registry, projects/remix, prompting-library, skills and design-systems pagesread 2026-08-31

Lovable documents project monitoring in which it checks a project on a schedule, daily or weekly at a chosen time and optionally only after a minimum number of edits, reviewing the app code for broken functionality and recent visitor errors, then alerting by email and surfacing findings to fix in the project chat. That is an autonomous scheduled wake of the builder agent. Other routes are the web chat, a Slack app, mobile and desktop apps, a Telegram route, the Lovable API and the Lovable MCP server. Monitoring is in beta, on Pro, Business and Enterprise.

Sourcedocs.lovable.dev project-monitoring page and llms.txt indexread 2026-09-29

No model selection, model picker, bring-your-own-key or provider configuration for the builder appears anywhere in the complete documentation inventory covering roughly two hundred pages, including advanced settings, workspace admin settings and account settings. Model-related integrations that do appear, namely Fireworks, Replicate, Perplexity and Gemini Enterprise, together with an AI feature documented among the Cloud backend pages, provide model access to the application being built rather than choice over the model powering Lovable itself.

Sourcedocs.lovable.dev sitemap inventory, advanced-settings, workspace-admin-settings, lovable-account-settings and features/ai pagesread 2026-08-31

A Lovable API and a Lovable MCP server are documented as first-party integration surfaces. Agent integrations turn a published Lovable app into an MCP server consumable by ChatGPT, Claude and other assistants, with configurable tools, sign-in, permissions and access. Custom MCP servers and MCP registries are separately documented, alongside a create-connector path and an any-API route for arbitrary services. Two-way Git sync with GitHub and GitLab, including self-managed and dedicated GitLab, exports the full codebase, and desktop, mobile and Slack surfaces extend access to the platform.

Sourcedocs.lovable.dev lovable-api, lovable-mcp-server, agent-integrations, custom-mcp, mcp-registries, create-connector, any-api and git-sync-overview pagesread 2026-08-31

Browser testing is documented as the platform interacting with the customer's application in a real browser running in a virtual environment, clicking buttons, filling forms, navigating pages and verifying real user behavior with screenshots across different screen sizes.

It returns a verdict rather than a trace: a Details view shows the steps taken and summarizes what worked and what did not, and the documented pattern is reproduce, fix, then verify. Where the test and live environments feature is enabled it runs against the project preview in the test environment, so the evaluation happens before the change reaches anyone. A criterion applied by Lovable's mechanism to the customer's artifact, ahead of release, is Full.

Sourcedocs.lovable.dev browser-testing page and test-and-live-environments documentationread 2026-08-31

Browser testing and the preview toolbar exercise and display the application the agent has generated, which is verification of the agent's own output rather than operation of third-party software. Firecrawl and Apify integrations retrieve web content over HTTP, which is scraping rather than computer use.

All external action is documented as running through connectors, the any-API route, custom MCP servers or MCP registries, all of which are programmatic interfaces. No browser navigation, form filling, screen control or computer-use capability appears anywhere in the complete documentation inventory.

Sourcedocs.lovable.dev browser-testing, preview-toolbar, projects/preview, firecrawl and apify pages plus sitemap inventoryread 2026-08-31