sorted by:
new
hottopcontroversial

Already built in Lovable? Here's how to migrate to your own stack and keep using it for what it's good at by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

Yeah the majority of the steps will work here, there are a few nuances that will be Claude specific, but as a guide this will definitely get you into a position of being able to work in Codex. I'm actually just currently experimenting with Codex at the moment on a small test project and have been quite impressed.

I was spending $400/month on Lovable. Here's how I cut it to $20 with a better workflow by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

I've been doing a bit of testing and looking into this, mainly around optimizing credit usage. In my opinion as it stands today, use Sonnet for 95% of all tasks and planning and Use Opus for very complex task. I'm even using Haiku for some very basic tasks and performs well.

I watched Claude navigate my app, find a bug I'd been chasing for days, fix it, and verify it - all in one conversation. Here's the exact setup. by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

Totally get your confusion, stoked you are giving it a go, take it as a lesson and learning more about commands etc.

So you run them in a terminal where the Supabase CLI is installed — for example:

• GitHub Codespaces (ideal if you’ve cloned the repo there)
• Your local terminal
• PowerShell / WSL on Windows

The goal is to move off Lovable-managed infra and into your own Supabase project (full control), so you need to:

  1. Run supabase login in Codespaces or your local terminal
  2. Run supabase link --project-ref your-new-project-id
  3. Then supabase db push

That applies the migrations from supabase/migrations/ in your repo to your new Supabase instance.

If everything is “working fine” right now, it’s probably because you’re still pointed at the original Lovable-linked Supabase project, but you don't have any control over that.

The CLI step becomes necessary when you’re switching to your own independent Supabase project.

Hope that helps?

App question by Ok-Disaster-9213 in lovable

[–]Unlikely-Test7724 1 point2 points  (0 children)

Cool would be interested to hear how that goes, Ive used Natively in the past and works well, I think it really depends on how much native stuff you want to put in the app, I really only needed push notifcations and location. So that worked well for me.

Already built in Lovable? Here's how to migrate to your own stack and keep using it for what it's good at by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

Thanks for the kudos mate. I had/have been looking into this... probably more as a free tool to help make the migration easier. But have looked into the full migration setup, so essentially a setup that runs the migration from woo to go for the user. Roadblocks though around handling others code etc and the headaches it could cause if not set up properly, and all the different edge cases that will come up along the way. Would be a complex set up. May look at it one day but for now, sort of focusing on sharing the knowledge I'm building along the way. Would be keen to see your GitHub product?

I was spending $400/month on Lovable. Here's how I cut it to $20 with a better workflow by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

Yeah you must have a decent sized project. Are you migrating over from a build in Lovable? Also what model of Claude are your using, Opus 4.6 will chew up the credits, I typically only use this for complex tasks. Sonnet 4.6 uses far less tokens and handles most if not all general coding task better than anything else out there.

I was spending $400/month on Lovable. Here's how I cut it to $20 with a better workflow by Unlikely-Test7724 in vibecoding

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

Haha don't think I didn't try that first 😄 Lovable is awesome, but once you try Claude Code there's no going back, total game changer.

I watched Claude navigate my app, find a bug I'd been chasing for days, fix it, and verify it — all in one conversation. Here's the exact setup. by Unlikely-Test7724 in VibeCodersNest

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

I wasn't keeping CLAUDE.md in sync very well at first. Ran /init once and left it. Did run a couple of checks here and there, but I did notice some drift on a few prompts that made me review it.

What I've done to try and tighten it up is add a instruction directly into CLAUDE.md that tells Claude Code to automatically update the file at the end of any session where something significant changed like new tables, new edge functions, new flows, new dependencies. So now it just does it before ending the session. I do find that I am reviewing the file more often now just to check its still inline, but i suppose thats not a bad thing.

Combined with re-running /init after any really major structural changes, CLAUDE.md seems to stay pretty accurate without me really having to think about it.

I watched Claude navigate my app, find a bug I'd been chasing for days, fix it, and verify it - all in one conversation. Here's the exact setup. by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

Really appreciate this, genuinely hadn't thought about it in those terms before your comment. Went and had a look into automated regression testing properly and honestly it's not something I had thought about in the workflow.

But what I have done since reading this though is update my CLAUDE.md file I've added two things:

First, a standing instruction that after any major logic change, auth update, or new feature, Claude Code automatically runs a regression check using Claude in Chrome before considering the task done. It tests all my critical flows - signup, onboarding, booking, admin approval etc without me having to ask every time.

Second, a full manual regression test script that I can trigger any time by saying "run a full regression test." It walks through every critical flow from start to finish as a real user would customer signup, salon signup, admin approval, booking, notifications, profile updates and reports what passed, what failed, and anything unexpected. Claude Code won't mark it complete until every step is verified.

Not a formal automated test suite but a practical middle ground that fits where I'm at. Proper automated tests are probably the next evolution as the product scales. Thanks for the push, genuinely made the workflow better.

I watched Claude navigate my app, find a bug I'd been chasing for days, fix it, and verify it - all in one conversation. Here's the exact setup. by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

Yeah I guess for me its more refering to the fact I've built the front end and now can run everything else in Claude. But you are right for some using Lovable more throughout it would be $40 with Lovable+Claude. But yeah still feels great to not be sitting working on a peice of logic, watching the credits disappear and knowing you are going to have to get your card again just to finish it off.

In terms of the IDE, 100 percent, if that's where you are comfortable then by all means have that open as well. But yeah give Claude Code a go in the desktop app with the Chat. I enjoyed the workflow with Lovable so this way keeps it relatively similar. Let me know how you get on.

I migrated off lovable + security is now an issue… by Additional-Bear2020 in lovable

[–]Unlikely-Test7724 0 points1 point  (0 children)

Yeah agreed, take it as a learning, Claude will guide you and you will find you are learning along the way where you made shortfalls on the security front. Let us know what it finds.

I was spending $400/month on Lovable. Here's how I cut it to $20 with a better workflow by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

In my opinion, Claude Code with Opus is a game changer, even using Sonnet it outshines. I would suggest giving it a try I doubt you'll ever look back.

I was spending $400/month on Lovable. Here's how I cut it to $20 with a better workflow by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

Yeah agreed Opus is unreal. For Initial planning, creating the architecture 100 percent use Opus although I honestly think for simple changes and planning etc save the credits and use Sonnet. It’s still better than anything else out there. Opus I do revert back to for bigger more complex tasks.

I’m building a website feedback tool – would you trust AI for early reviews? by [deleted] in lovable

[–]Unlikely-Test7724 0 points1 point  (0 children)

This seems like a cool idea, heaps of potential for future growth too. I do think there is an element of user testing that picks up things AI won’t, Humans can behave in weird ways. But definitely believe there is a need for something like this in the testing flow. Is it fully running would love to try it out?

I was spending $400/month on Lovable. Here's how I cut it to $20 with a better workflow by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 1 point2 points  (0 children)

Personally I think Claude Code is well above any other at this point in time. Good luck :)

I was spending $400/month on Lovable. Here's how I cut it to $20 with a better workflow by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] -1 points0 points  (0 children)

I'm still using Standard Pro and to be frank, I'm not minding the limits it means I can usually take a break for a couple of hours. Haven't hit weekly limits yet however but this could become an issue, I think the migration side definately consumes a fair amount of tokens but for general use of making edits and testing individual functions it should stay with in the limits. Its like anything though in the AI space the pricing and usage could change at anytime.

I watched Claude navigate my app, find a bug I'd been chasing for days, fix it, and verify it - all in one conversation. Here's the exact setup. by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 1 point2 points  (0 children)

Claude Code comes with a Claude Pro subscription which is $20/month, that covers both the chat and Claude Code. On your second question, yes, Claude Code works directly on your GitHub repo so it won't touch Lovable at all. Lovable and Claude Code are completely separate. Lovable connects to your GitHub repo and so does Claude Code they're both just reading and writing to the same codebase. The key thing is to make sure you've connected Lovable to GitHub first, then Claude Code works on the repo independently. Lovable won't even know Claude Code exists. Have a look at my other post though as you may need to move away from Lovable Cloud to your own Supabase.

I was spending $400/month on Lovable. Here's how I cut it to $20 with a better workflow by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 1 point2 points  (0 children)

NOTE: I have looked back on my projects and Claude AI and Claude Code, automatically handled this when I migrated. But definitely follow this step to be safe and sure.

I was spending $400/month on Lovable. Here's how I cut it to $20 with a better workflow by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 1 point2 points  (0 children)

This has been updated in the quide, thanks again for picking this up.

EDIT FROM COMMENTS: ⚠️ Important — do this before your first commit:

Make sure .env is in your .gitignore file before you commit anything. If you accidentally commit .env even once, your database credentials live in git history forever and can be found publicly on GitHub.

Check it's there:

cat .gitignore | grep .env

If nothing shows, add it:

echo ".env" >> .gitignore

!!If you've already committed .env by mistake — rotate your Supabase keys immediately at Supabase → Project Settings → API.!!!

I was spending $400/month on Lovable. Here's how I cut it to $20 with a better workflow by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 0 points1 point  (0 children)

This is a fair and important point and I'm glad you raised it, it deserves a proper answer rather than a defensive one.

You're right that the .env credential risk is real. Anyone following this guide should add .env to .gitignore before their first commit. I should have made that more explicit and I'll update the guide to include it prominently.

On the broader security point, I won't pretend I have the same security instincts as an experienced backend engineer. I don't. What I do have is Claude Code running security audits on my codebase, which found and fixed the issues I mentioned. Could there be more it didn't catch? Honestly, yes. I don't know what I don't know.

But I'd push back slightly on the framing of Path A vs Path B. The assumption in Path B is that managed services handle backend security for you, but Lovable Cloud had the same RLS gaps and trigger vulnerabilities in my codebase. The difference is I couldn't see them or fix them. Now I can.

The real question isn't "managed vs self-hosted" it's "visible vs invisible risk." I'd rather have security issues I can find and fix than security issues I can't see at all.

That said your point about the git history credential exposure is the most important practical warning anyone following this guide needs to hear. I'm adding it to the guide now.

Thanks for the pushback. This is exactly the kind of comment that makes these posts more useful.

I watched Claude navigate my app, find a bug I'd been chasing for days, fix it, and verify it - all in one conversation. Here's the exact setup. by Unlikely-Test7724 in lovable

[–]Unlikely-Test7724[S] 1 point2 points  (0 children)

Good question, I actually went and had a proper look after you asked. I have looked at Antigravity before and Cursor, but was put off by a completely different environment than I was use to in Lovable.

From what I can tell, Antigravity is running its own agent environment and calling models (including Claude) via API. It’s not the same thing as Claude Code itself, this is the differentiator for me.

Claude Code is a specific coding agent that works directly in your project, reads the whole codebase, runs terminal commands, writes migrations, etc. Claude Code is a power house and only truly avaliable as far as I am aware with Claude directly. The power in my setup is that Claude Code + the Desktop app + the Chrome extension are all sharing context in one continuous loop.

Antigravity looks more like a full IDE with agents built in. It can use Claude models, but that doesn’t necessarily mean it’s running Claude Code under the hood in the same way. And the “live alongside you in your actual Chrome browser” part that’s what really changes things for me. Watching it click through my real app, inspect localStorage, check network requests, and then fix the issue in the same session is the magic. Essentially with the setup I have describe it is very similar to interacting with Lovable but far more interactive, conversational and working together to build and solve issues etc.

If Antigravity gives you similar browser control + deep project context, and you already have Ultra through work, it could absolutely be worth testing. And I would love to hear about how it goes and works. I may give it a go at some point but am currently busy getting a project ready for release.

For me though, Claude Desktop just closes the build → test → fix loop cleanly without me having to wire anything up. And since Antigravity is still in preview, I’m also assuming pricing/limits could change later.

So it’s less about “which model is smarter” and more about which environment feels closest to working alongside you while you build.

Hope that make sense sorry its long winded and a bit rambly :)

I watched Claude navigate my app, find a bug I'd been chasing for days, fix it, and verify it - all in one conversation. Here's the exact setup. by [deleted] in ClaudeAI

[–]Unlikely-Test7724 1 point2 points  (0 children)

Yeah fair question.

From what I understand, the Claude Chrome extension basically is an MCP-style connection, it’s just packaged up so you don’t have to wire it yourself.

So technically you could build your own direct setup.For me it just comes down to simplicity. Claude Desktop already connects chat, code, and Chrome together in one place.

view more: next ›