The open-source, local Lovable alternative for Claude Code users
By Andrea Buttarelli, founder of Feega · checked 2026-11-22 · how we checked
Keep Lovable if you have no code yet. If you already work with Claude Code in a repo of your own, Lovable adds a second home for the app, and Feega adds none: Claude Code writes the page, and you adjust it by hand in the same files.
see it in action → The short version of this comparison, for Claude Code users.
Lovable, Claude Code and Feega at a glance
| Lovable | Feega | |
|---|---|---|
| Starts from | A prompt, or a ZIP upload | Your existing repo |
| GitHub | Sync creates a new repository | Edits your folder in place |
| Your coding agent | Claude Code works in your repo; the tool wants its own copy | Reads the project, writes the code, loads the Feega skill |
| Commit author | lovable-dev[bot], co-attributed to the member who triggered it | You |
| Branches | One synced branch at a time | Whatever branch you are on |
| Price | Free has 5 build credits a day, Pro is $25 a month | Free, Apache-2.0 |
Lovable, Claude Code and Feega side by side
| Lovable | Claude Code in your repo | Feega | |
|---|---|---|---|
| Where the code lives | In a Lovable project, synced to a new repository (Lovable GitHub integration) | In your repo, on your disk | In your repo, on your disk |
| Pricing model | Credits: Free has 5 daily build credits, Pro starts at $25 a month (Lovable plans, 22 November 2026) | Your Claude plan or API usage | Free, Apache-2.0, no credits |
| Export and git | Sync creates a repo; Upload code takes a ZIP | Plain git, any branch | Plain git. Feega writes files and never commits |
| Local or cloud | Hosted project | Runs in your terminal or editor (Claude Code: skills) | Runs on your machine, no account |
| Visual editing | Prompt, then preview | No canvas | Click an element and set its values |
| Fits | Starting an app from a prompt | Building and refactoring code | Nudging layout and type in an existing page |
Lovable wants the app inside Lovable
According to Lovable’s GitHub docs, sync always creates a new repository. To start from code you already have, you download a ZIP and upload it. After that, changes made in Lovable go to GitHub and commits pushed to the active branch come back, one branch at a time.
That is a reasonable arrangement for an app that began in Lovable. When the repo came first, it gives you a second copy of the product and a bot in the history of the one you have.
- Zip your project
- Upload it
- Prompt the change
- Sync a new repository
- Open your repo
- Click the element
- Set the value
- Commit yourself
A real edit, written to source
Here is what a hand edit leaves behind in src/routes/+page.svelte. Feega writes at the line of the element you clicked, as a Tailwind class or a rule in your own CSS, and nothing else in the file moves.
Claude Code has no canvas and Feega has no brain, so they cover each other. The diff is the same one your agent will read on its next turn, and the same one git will show in review.
.hero h1 { - font-size: 2.5rem; + font-size: 3.25rem; letter-spacing: -0.04em; }
Claude Code codes, you design, one set of files
Feega has no AI of its own. It sits next to Claude Code: Claude Code writes the component, you open the running page, click the element and set the padding or the type by hand. Both of you write to the same file, and git shows both as ordinary diffs.
Feega also reveals the selected element’s source in a text editor beside it, so Claude Code sees the line you picked. Right-click the element and choose Copy for agent to hand it the file, line, selector and preview width in one paste.

when to choose which
choose Lovable if
- You start from nothing and want a hosted app from a prompt.
- You want chat to be the only interface.
- You want hosting and the database included.
choose Feega if
- You already build with Claude Code in your own repo.
- You want the visual pass to cost no tokens.
- You want one codebase and your name on every commit.
what each one costs
Lovable’s free plan has 5 build credits a day and Pro is $25 a month, per its plans page when we checked on 22 November 2026. Credits run per build, so count how many your edits actually take.
Feega is free and open source under Apache-2.0, with no credits and no account. You still pay for your own agent and your own hosting, as you do now.
set up Claude Code once
Feega ships a skill for Claude Code. In Claude Code, install it as a plugin with /plugin install feega --marketplace andreabuttarelli/feega, or run npx skills add andreabuttarelli/feega in the project.
Per Anthropic’s docs, a skill is a SKILL.md file whose instructions load only when they are used, and a project skill lives in .claude/skills and can be committed. Facts that never change belong in CLAUDE.md, which Claude reads at the start of every session. The docs suggest keeping procedures in skills and facts in CLAUDE.md, so a good split is the skill for how, and one line in CLAUDE.md for the rule that class names stay literal.
The skill teaches Claude Code to add feega-source-map to a Next.js or Vite config, to start the editor with npx feega, and to write markup Feega can edit back.
if your app began in Lovable
If the project began in Lovable, you do not have to start over. Lovable’s docs say you can clone the synced repository and continue in your own IDE. Clone it, open the folder in your terminal, start Claude Code and run npx feega beside it.
Two things to know. Lovable only syncs one branch at a time, so to see a change back in Lovable, push to the branch it watches. And the earlier commits stay as they are, authored by lovable-dev[bot]. From here on, Claude Code’s changes and your Feega edits are written to the folder, and you commit them yourself.
Feega never talks to Lovable, so a hand edit spends no build credits.
what to ask Claude Code, and what to do by hand
Ask Claude Code for the structural work: a new section, a form, a data loop, a refactor. Ask it to write the markup so Feega can edit it back. That means literal Tailwind classes, visible words in the markup and icons from the supported libraries.
Do the small visual passes yourself in Feega. Spacing, radius, colour and type size are quick to set by eye and slow to describe, and a hand edit costs no tokens. When you are done, tell Claude Code to read the diff, so that its next change starts from the page you shaped.
where Lovable is still the better choice
Lovable turns a prompt into a hosted full-stack app, with nothing to install. If there is no code yet, or you want a working prototype to show someone this afternoon, it is hard to beat. Its GitHub sync also lets you clone the repository and keep working in your own tools.
Feega does none of that. It has no prompt-to-app builder and no hosting, and it only edits pages that already exist in your repo.
more on Lovable and your agent
This page covers Claude Code. The wider comparison is on Lovable alternatives. Other agents with the same question:
- Lovable alternative for OpenAI Codex
- Lovable alternative for Cursor
- Framer alternative for Claude Code
Feega is free. Download it or read the agents page in the docs.
what Lovable keeps, and what Claude Code keeps
Per Lovable GitHub integration, a Lovable project links to one repository, the sync covers one branch at a time, and you cannot switch branches while Lovable is editing. Claude Code has none of those limits because it works on a folder: any branch, any worktree, any commit you make yourself.
That difference decides where a visual tweak belongs. If the page already sits in your repo and Claude Code wrote it, opening it in Lovable first means a ZIP upload and a second copy. Opening it in Feega means clicking the element in the running page. The Lovable overview goes through the same trade-off without an agent in the picture.
A short session with both open
Say Claude Code has just built a pricing section. You open the page with Feega, click the card and see its file and line in the bar. The padding looks tight, so you change it in Properties and read the result in Changes as a one line diff. Nothing was prompted and nothing was billed.
Then you want a new FAQ block under the cards. That is structure, so it goes back to Claude Code, which reads the files you just changed. If you want it to start from the exact element, right-click it in Feega and choose Copy for agent, as described in the Feega docs: use Feega with AI agents. The pricing page lists what Feega itself costs.
Try Feega in two minutes: run npx feega in your project folder, or install the extension.
Download Feega →memory and skills decide how well it fits
Claude Code reads CLAUDE.md at the start of every session, per Claude Code: memory and CLAUDE.md, and a skill is a SKILL.md file whose body loads when it is used. Put the Feega rule in one of them: literal Tailwind classes, visible text in the markup, no class built by a function on elements people will tweak.
Lovable has its own prompt box and its own rules about what the builder may touch. With Claude Code, those rules sit in files you can commit and review. A teammate who clones the repo gets the same behavior, which is hard to promise for a hosted project. You can read how this idea started in Design in your codebase.
The agent guide shows each command and what the agent can see.
Read the agent docs →try Feega with Claude Code in five steps
- Install the skillRun /plugin install feega --marketplace andreabuttarelli/feega in Claude Code, or npx skills add andreabuttarelli/feega in the project.
- Ask for setupSay “set this project up for Feega”. Claude Code adds the source map where the framework needs it.
- Open the pageSay “start Feega”, or run npx feega in the app folder. The running page opens next to your layers.
- Click and setPick the element and change its values in the Properties bar. Copy for agent hands the element to Claude Code when you want it to take over.
- Review togetherRead the diff in Changes, then let Claude Code carry on from the new files. Commit with your own identity.
mistakes people make
Uploading a finished app to change one page. You end up with two copies to keep in step, and only one of them has your history.
Letting the agent write class names through cn() on every element. Feega refuses expressions it cannot trace to one line. Keep literal strings on the elements people tweak.
Describing a two-second drag to the agent. Spend the tokens on code, and set the spacing by hand.
questions
What does Lovable cost?
Free has 5 build credits a day. Pro is $25 a month, per its plans page.
How do I install the Feega skill in Claude Code?
Run /plugin install feega --marketplace andreabuttarelli/feega, or npx skills add andreabuttarelli/feega in the project.
Does Claude Code see what I select in Feega?
Feega reveals the selected element’s source beside it, and Claude Code is one of the agents that read the editor selection per the Feega docs.
Does Feega use Claude Code’s tokens?
No. Feega has no model behind it and sends nothing anywhere.
Does Feega replace Claude Code?
No. Claude Code writes code and Feega sets visual values in the same files.
how we checked
We make Feega, so read our column with that in mind. We read each product's public pages on 2026-11-22 and compared what they offer, not finished work. Something wrong? Write to hi@feega.app.
- Lovable GitHub integration
- Lovable plans
- Claude Code: skills
- Claude Code: memory and CLAUDE.md
- Feega docs: use Feega with AI agents
Feega is not affiliated with, endorsed by, sponsored by or connected to any company or product named on this page. All product names, logos and trademarks belong to their respective owners and are used only to identify those products. Information comes from their public pages on the date shown and may have changed since; check the source before you decide. This page is not legal, financial or purchasing advice.
Keep Lovable for a new app. Keep Claude Code and your repo for the one you have.
download for free →