away from lovable

Stage 2 · Bring in your agent

Your edge function changed on GitHub, but Lovable still runs the old one?

Lovable does not deploy a changed edge function, or run a new migration file, when your commits sync from GitHub. Ask Lovable's chat to deploy the function, then check it is really the new code. The dashboard can look up to date when it is not.

Checked against Lovable’s, Vercel’s and Supabase’s own documentation on 29 September 2026.

What is going on

When Claude Code, Codex or you change server code outside Lovable, the files reach Lovable through the GitHub sync and stop there. Lovable’s docs say so directly: in a Lovable Cloud project the repository holds “Edge Functions under supabase/functions/ and the migration files under supabase/migrations/ … Lovable does not deploy a changed Edge Function or run a new migration file when your commits sync” (Lovable docs).

Publish does not cover it either. Publish puts your screens live; the functions and the database are separate.

Owners describe it the same way:

“i push my changes and i can see my commit in lovable and i publish it but the functions are not deployed.” (r/lovable, December 2025)

“My functions read ‘Last updated 2 days ago’ — i.e. current — while newer code was already synced from GitHub.” (r/lovable, July 2026)

The fix

  1. Edge functions: after the commit has synced, ask Lovable in the project chat to deploy the function, then check it under More → Cloud → Edge functions (Lovable docs). Name every function that changed and ask it to deploy them from the current code in the repository, even if they look up to date.
  2. Database changes (migrations): ask Lovable in the project chat to apply them, or run the SQL yourself in Lovable’s SQL editor (Lovable docs).
  3. Prove it. Because the dashboard can look current, check with a request that only the newest code would answer. One owner put the fix as “explicitly ask the agent to force-redeploy all edge functions from current source” and the check as “Fire a live request that only your newest code would satisfy” (r/lovable, July 2026).

A message you can paste into Lovable’s chat, with your own function and file names:

Deploy these Supabase edge functions from the current code in the repository, even if they look up to date: send-invoice. Apply these migrations from supabase/migrations to the database, in this order, if they are not applied yet: 20260921093000_add_due_date.sql. Do not change any code. When you are done, list each function you deployed and each migration you applied.

What it costs

That chat message is build usage, and build usage costs Lovable credits; Build mode messages cost more the more work they involve (Lovable docs). Lovable does not publish what a deploy request costs. Running a migration’s SQL yourself in the SQL editor is the route that needs no chat message.

Which apps this touches

Every Lovable project whose server code you change outside Lovable: on Lovable Cloud, and on your own Supabase while Lovable is connected to it (the July 2026 report above was an own-Supabase project). Lovable’s docs add that apps built before May 2026 are the ones most tied to edge functions, “since newer apps don’t depend on Edge Functions” (Lovable docs); new projects have used TanStack Start since 13 May 2026 (Lovable docs).

When it stops being your problem

Once the database is your own Supabase project, Supabase’s GitHub integration can do this job: with Deploy to production switched on, every push or merge to your production branch applies new migrations and deploys the edge functions declared in config.toml (Supabase docs). Lovable’s chat is then no longer in the loop. That is stage 5, move the data. Until then, the routine is: push, Publish, and one chat message for any server change.

Where this fits

This is part of stage 2, bring in your agent. Other short answers:

Not sure which stage your app is in?

The free check asks five questions about your app and gives you the path, what usually breaks on it, and what it costs. It asks; it does not look at your app. About a minute, no email.

If you would rather have your AI agent do the work with you, the kit is $19, one payment: the full guide, an agent skill that runs each stage, guardrails and checks.

Take the free checkGet the kit for $19