Skip to main content
RapidDev - Software Development Agency
lovable-integrationsDeveloper Workflow

How to Integrate Lovable with Visual Studio Code

There is no Lovable VS Code extension. The correct workflow is Git-based: connect Lovable to GitHub, clone the repo locally, run npm run dev in your terminal, and edit the Vite+React+TypeScript project in VS Code with full IntelliSense, ESLint, Prettier, and Tailwind CSS IntelliSense. Push changes to GitHub and Lovable syncs them back automatically.

What you'll learn

  • Why there is no Lovable VS Code extension and what the real workflow is
  • How to connect Lovable to GitHub and clone your project locally
  • How to run the Lovable project locally with hot reload using npm run dev
  • Which VS Code extensions improve the Lovable development experience
  • How to push local edits back to Lovable via Git
Book a free consultation
4.9Clutch rating
600+Happy partners
17+Countries served
190+Team members
Beginner13 min read20 minutesDevOpsMarch 2026RapidDev Engineering Team
TL;DR

There is no Lovable VS Code extension. The correct workflow is Git-based: connect Lovable to GitHub, clone the repo locally, run npm run dev in your terminal, and edit the Vite+React+TypeScript project in VS Code with full IntelliSense, ESLint, Prettier, and Tailwind CSS IntelliSense. Push changes to GitHub and Lovable syncs them back automatically.

Using VS Code with Lovable: The Git-Based Local Development Workflow

Many developers search for a 'Lovable VS Code extension' expecting a direct IDE plugin, but Lovable does not offer a VS Code extension. Instead, Lovable's local development story runs entirely through GitHub. When you connect your Lovable project to a GitHub repository, every change in Lovable's browser editor automatically commits to the main branch in real time. That same repository becomes your bridge to VS Code: clone it, install dependencies, run the local dev server, and you have a fully functional development environment with all the tooling VS Code provides.

This Git-based approach is actually more powerful than a dedicated extension would be. You get access to the full VS Code extension marketplace — ESLint for code quality, Prettier for formatting, the official Tailwind CSS IntelliSense extension for autocomplete in className attributes, and the TypeScript language server for full type checking across the entire Vite+React codebase that Lovable generates. You can run the debugger, inspect network requests, and use breakpoints — none of which are possible in Lovable's browser-based editor.

The workflow is bidirectional. Edits you make in VS Code and push to GitHub appear in Lovable's editor automatically. Edits made in Lovable's chat interface commit to GitHub and appear in your local clone after a git pull. This means you can mix both workflows: use Lovable's AI chat for rapid scaffolding and feature generation, then switch to VS Code for fine-grained code editing, refactoring, and debugging.

Integration method

Developer Workflow

Lovable has no VS Code extension. Integration is entirely Git-based: Lovable connects to GitHub and provides bi-directional sync on the main branch. You clone that repo locally, open it in VS Code, and edit with all of VS Code's tooling. Pushing changes to GitHub automatically syncs them back into Lovable's browser editor.

Prerequisites

  • A Lovable account with an existing project (free or paid)
  • A GitHub account — Lovable requires GitHub for code export and sync
  • Visual Studio Code installed on your computer (download from code.visualstudio.com)
  • Node.js version 18 or higher installed — check by running node --version in your terminal
  • Git installed on your computer — check by running git --version in your terminal

Step-by-step guide

1

Connect your Lovable project to GitHub

Before you can open your Lovable project in VS Code, you need to export it to a GitHub repository. Open your Lovable project in the browser editor. Look for the GitHub icon in the top-right corner of the interface — it looks like the GitHub Octocat logo. Click it to open the GitHub integration panel. If you have not connected GitHub before, Lovable will prompt you to authenticate with your GitHub account via OAuth. Follow the prompts to authorize Lovable to create repositories in your account. Once authenticated, click 'Connect project' and choose whether to create a new repository or link to an existing one. Give the repository a name that matches your project and click 'Transfer anyway' to confirm. Lovable will push your entire project codebase — all React components, Supabase configurations, and Tailwind styles — to the new GitHub repository. This process takes about 30 seconds. Once complete, the GitHub icon turns green, indicating that Lovable is now syncing every change you make in the editor directly to the repository's main branch in real time. You will see the repository appear in your GitHub account immediately. Critical: never rename, move, or delete this repository after connecting — doing so permanently breaks the sync between Lovable and GitHub.

Pro tip: If the GitHub icon is already green when you open your project, your project is already connected to GitHub. Click it to find the repository URL.

Expected result: Your Lovable project is connected to a GitHub repository. The GitHub icon in the top-right shows green. You can see the repository at github.com/your-username/your-repo-name with all your project files.

2

Clone the repository to your local machine

With your project on GitHub, you can now clone it to your computer. Go to your repository on github.com. Click the green 'Code' button near the top right of the repository page. In the dropdown that appears, make sure 'HTTPS' is selected, then click the copy icon to copy the repository URL — it will look like https://github.com/your-username/your-project-name.git. Open your terminal (Terminal on macOS, Command Prompt or PowerShell on Windows) and navigate to the folder where you want to store the project. Run the command: git clone https://github.com/your-username/your-project-name.git. Git will download all the project files into a new folder named after your repository. Once the clone is complete, you will see a folder containing the project. The project structure follows the standard Lovable layout: src/ contains all your React components, pages, and shared utilities; supabase/ contains Edge Function code; and the root level contains configuration files like vite.config.ts, tailwind.config.ts, tsconfig.json, and package.json. Now open this folder in VS Code by running: code your-project-name from the terminal (if you have the VS Code CLI installed), or by opening VS Code manually and using File → Open Folder to navigate to the cloned directory.

Pro tip: On macOS, you can also drag the project folder directly onto the VS Code icon in your Dock to open it.

Expected result: VS Code opens with your Lovable project. You can see the file explorer on the left showing src/, supabase/, package.json, and other project files. VS Code may prompt you to install recommended extensions — click 'Install All'.

3

Install dependencies and run the local development server

Open the integrated terminal in VS Code by pressing Ctrl+` (backtick) on Windows/Linux or Cmd+` on macOS, or by going to View → Terminal in the menu bar. In the terminal, make sure you are in the root of your project folder (where package.json lives). Run the command npm install to install all the project dependencies — this downloads React, Vite, Tailwind CSS, shadcn/ui components, the Supabase client library, and all other packages listed in package.json. This may take one to three minutes depending on your internet speed. Once installation is complete, you need to set up your local environment variables. Create a new file in the project root called .env.local. This file is already listed in .gitignore by default, so it will never be committed to GitHub. Inside .env.local, add your Supabase credentials. You can find these in your Lovable project's Cloud tab (click the + icon next to the Preview button) or in your Supabase project settings. Add VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY to the file. Once the env file is saved, run npm run dev to start the Vite development server. Vite will start a local server, typically at http://localhost:5173. Open that URL in your browser to see your Lovable project running locally with hot module replacement — changes you make in VS Code appear in the browser instantly without a full page reload.

.env.local
1VITE_SUPABASE_URL=https://your-project-id.supabase.co
2VITE_SUPABASE_ANON_KEY=your-anon-key-here

Pro tip: Never commit .env.local to Git. It contains your Supabase anon key. The file should already be in .gitignore, but double-check before pushing.

Expected result: The terminal shows 'Local: http://localhost:5173/' and the project opens in your browser. Changes to React components appear in the browser within milliseconds. The app connects to your Supabase backend and all data operations work as expected.

4

Install recommended VS Code extensions for the Lovable tech stack

VS Code's extension ecosystem significantly improves the experience of working with Lovable's Vite+React+TypeScript+Tailwind codebase. Open the Extensions panel in VS Code by clicking the squares icon in the left sidebar or pressing Ctrl+Shift+X (Windows/Linux) or Cmd+Shift+X (macOS). Search for and install the following extensions that directly improve Lovable project development: 'ESLint' by Microsoft — highlights code quality issues inline as you type, enforcing consistent patterns across AI-generated code; 'Prettier - Code formatter' by Prettier — auto-formats TypeScript and JSX on save, keeping generated code consistent; 'Tailwind CSS IntelliSense' by Tailwind Labs — shows autocomplete suggestions for every Tailwind class inside className attributes, which is essential because Lovable uses Tailwind for all styling; 'ES7+ React/Redux/React-Native snippets' by dsznajder — provides shorthand snippets for React component boilerplate; 'Auto Rename Tag' by Jun Han — when you rename an HTML opening tag, the closing tag updates automatically; 'Pretty TypeScript Errors' by yoavbls — displays TypeScript type errors in a much more readable format than VS Code's default. To configure Prettier to format on save, press Ctrl+Shift+P (or Cmd+Shift+P on macOS), type 'Open User Settings JSON', and add these properties to your settings file: 'editor.formatOnSave': true and 'editor.defaultFormatter': 'esbenp.prettier-vscode'. Now every time you save a TypeScript or JSX file, Prettier formats it automatically.

.vscode/settings.json
1{
2 "editor.formatOnSave": true,
3 "editor.defaultFormatter": "esbenp.prettier-vscode",
4 "editor.tabSize": 2,
5 "typescript.preferences.importModuleSpecifier": "relative",
6 "tailwindCSS.includeLanguages": {
7 "typescript": "javascript",
8 "typescriptreact": "javascript"
9 }
10}

Pro tip: Create a .vscode/settings.json file in your project root to share these settings with your team. This file can be committed to GitHub so everyone gets the same VS Code configuration.

Expected result: Tailwind class names autocomplete as you type in className attributes. TypeScript errors appear inline in red. Files format automatically when saved. ESLint warnings appear as yellow squiggles.

5

Push local edits back to Lovable via GitHub

Any changes you make locally in VS Code need to be pushed to GitHub for Lovable to pick them up. VS Code has a built-in Git interface — click the Source Control icon in the left sidebar (it looks like a branching graph) or press Ctrl+Shift+G (Cmd+Shift+G on macOS). You will see a list of all files you have modified since the last commit. To stage changes, click the + icon next to each file you want to include, or click the + icon next to 'Changes' to stage everything. Type a commit message in the text box at the top of the Source Control panel describing what you changed — for example, 'Fix responsive layout on mobile dashboard'. Click the blue 'Commit' button to create the commit locally, then click 'Sync Changes' (or 'Push') to push it to GitHub. Within a few seconds of your push arriving on GitHub, Lovable detects the new commit on the main branch and syncs the changes into the Lovable editor automatically. You can verify this by opening your Lovable project in the browser — the files in the Code panel will reflect your local edits. The sync is one-directional from GitHub to Lovable: Lovable reads whatever is on main and updates its internal representation. Important: only push to the main branch. Creating feature branches is fine for your own workflow, but Lovable only syncs from main, so merge your branch back to main when you are ready for Lovable to reflect the changes.

Pro tip: If Lovable made changes in the browser editor while you were working locally, run git pull before pushing to avoid merge conflicts. Lovable commits directly to main, so conflicts can occur if both sides edited the same file.

Expected result: Your local changes appear in the Lovable browser editor within seconds of the GitHub push. The Code panel in Lovable shows the updated file contents. Other team members can also pull the changes from GitHub to their local VS Code environments.

Common use cases

Refactor AI-generated code with full TypeScript checking

After building a feature with Lovable's AI chat, clone the project locally in VS Code to review and refactor the generated TypeScript code. VS Code's TypeScript language server catches type errors, unused imports, and logic issues that the browser editor misses.

Lovable Prompt

Connect my Lovable project to GitHub so I can clone it and edit the code locally in VS Code.

Copy this prompt to try it in Lovable

Add ESLint and Prettier configuration to a Lovable project

Lovable generates clean code, but enforcing consistent formatting and lint rules across a team requires ESLint and Prettier config files. Open the cloned project in VS Code, add .eslintrc and .prettierrc files, and push them to GitHub so all future Lovable-generated code passes the same rules.

Lovable Prompt

Add an ESLint configuration and Prettier config to this project with rules appropriate for a React TypeScript Vite app. Use the Airbnb style guide as the base.

Copy this prompt to try it in Lovable

Debug API calls and Supabase queries locally

When a Supabase query or Edge Function call behaves unexpectedly, VS Code's built-in debugger lets you set breakpoints in React components and step through API response handling. Clone the project, create a .env.local file with your Supabase keys, run npm run dev, and debug with the browser DevTools or VS Code's JavaScript debugger.

Lovable Prompt

What environment variables do I need in my .env.local file to run this Lovable project locally and connect to Supabase?

Copy this prompt to try it in Lovable

Troubleshooting

npm run dev fails with 'Cannot find module' or dependency errors

Cause: The node_modules folder was not installed, or the installed versions are incompatible with the current Node.js version on your machine.

Solution: Delete the node_modules folder and the package-lock.json file, then run npm install again. Make sure you are running Node.js 18 or higher — run node --version to check. Lovable generates projects expecting Node 22.

The app loads but shows blank pages or Supabase errors like 'Invalid API key'

Cause: The .env.local file is missing, has incorrect variable names, or the Supabase credentials are wrong.

Solution: Open the .env.local file in your project root and verify that VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY are spelled exactly right, including the VITE_ prefix. Copy the values fresh from your Lovable Cloud tab or Supabase project settings. Restart the dev server after saving .env.local — Vite does not hot-reload environment variable changes.

Lovable is not syncing changes pushed to GitHub — the browser editor shows old code

Cause: The GitHub repository connection may have been broken, or you pushed to a branch other than main.

Solution: In Lovable, click the GitHub icon in the top-right. If it shows a warning or disconnected state, click 'Reconnect' and re-authorize. Make sure your local changes were pushed to the main branch, not a feature branch. Check your git remote with git remote -v to confirm it points to the correct repository URL that Lovable is connected to.

Tailwind CSS IntelliSense is not showing autocomplete suggestions in className attributes

Cause: VS Code does not know the file uses Tailwind, or the extension has not detected the tailwind.config.ts file.

Solution: Make sure the Tailwind CSS IntelliSense extension is installed and enabled. Open the Command Palette (Cmd/Ctrl+Shift+P) and run 'Tailwind CSS: Show Output' to see if the extension found the config file. If not, create a .vscode/settings.json file with the tailwindCSS.includeLanguages configuration shown in Step 4.

Best practices

  • Always run git pull before starting a VS Code editing session to get the latest changes Lovable committed to GitHub during any AI chat sessions.
  • Never rename or delete the GitHub repository that Lovable is connected to — this permanently breaks the sync and requires reconnecting from scratch.
  • Keep your .env.local file out of Git by double-checking that .gitignore includes .env.local and .env*.local before your first push.
  • Use VS Code's built-in TypeScript checking to review AI-generated code quality — hover over variables to see inferred types and catch potential runtime errors before they reach production.
  • Create a .vscode/settings.json file with team-wide settings and commit it to GitHub so every developer who clones the project gets consistent formatting and extension behavior.
  • Use separate git branches for experimental local changes and only merge to main when ready — Lovable only syncs from main, so branches give you a safe scratch space.
  • Install the 'GitLens' VS Code extension to see who made each change and view Lovable's AI-generated commits inline in the editor, making it easier to understand what the AI built.
  • When debugging Supabase issues locally, open the Supabase dashboard alongside VS Code — Edge Function logs and database query analysis there are more detailed than what Lovable's Cloud tab shows.

Alternatives

Frequently asked questions

Is there a Lovable VS Code extension?

No, there is no official Lovable VS Code extension as of March 2026. The integration between Lovable and VS Code is entirely Git-based. You connect Lovable to a GitHub repository, clone that repository locally, and open it in VS Code. There is no plugin or direct IDE connection.

Can I edit code in VS Code and have it appear in Lovable?

Yes. When you push commits to the main branch of the GitHub repository connected to Lovable, Lovable automatically syncs those changes into its browser editor within a few seconds. The sync is triggered by any push to the main branch, regardless of whether it came from VS Code, GitHub's web editor, or any other Git client.

Will Lovable's AI edits overwrite my VS Code changes?

They can, if both you and the Lovable AI edit the same file at the same time without pulling first. When Lovable's AI makes changes in the browser editor, it commits them to GitHub. If you then try to push local VS Code edits without first running git pull, you will get a merge conflict. The solution is to always git pull before starting a local editing session.

Do I need to install Node.js to run a Lovable project locally?

Yes. Lovable generates Vite+React+TypeScript projects that require Node.js to run the development server. Install Node.js version 18 or higher from nodejs.org. Lovable's generated projects are configured for Node 22, so using a recent LTS version is recommended.

Can I use the VS Code Dev Containers extension to run the Lovable project in a container?

Yes, this is an advanced option. You can create a .devcontainer/devcontainer.json file in your project root that specifies a Node.js 22 container image. VS Code will then offer to reopen the project inside a container with all dependencies isolated from your local machine. This is particularly useful if you also want to use Docker for deployment, as it keeps your local environment consistent.

RapidDev

Talk to an Expert

Our team has built 600+ apps. Get personalized help with your project.

Book a free consultation

Need help with your project?

Our experts have built 600+ apps and can accelerate your development. Book a free consultation — no strings attached.

Book a free consultation

We put the rapid in RapidDev

Need a dedicated strategic tech and growth partner? Discover what RapidDev can do for your business! Book a call with our team to schedule a free, no-obligation consultation. We'll discuss your project and provide a custom quote at no cost.