Why Feega is now one thing
We cut Feega from a canvas, a motion editor and an AI product to one extension that edits your source. What we dropped, what we kept, and what I got wrong.
On 19 and 20 November I deleted most of Feega. This is why, and what is left.
Where we started
The repo began in late August as an AI marketing product. Agents that analyse a brand, plan content and publish it. Chat, a calendar, an autopilot.
In September it turned into a canvas. The commit is called “Turn the workbench into the canvas”. Typed nodes for media, images and video you generate. Then a motion editor on top, so a frame could also be a video.
In October we wrote our own renderer in Rust on WebGPU, and gave the canvas a chat agent and an MCP server. Those two posts stay up as history: why we wrote the renderer in Rust and how the canvas got fast.
Social publishing went behind a flag on 8 October and was removed on 22 October. It was the first piece to go.
The problem
Each step added surface. None of them made Feega easier to explain.
Ask me on any day in October what Feega was and I would have given you a different sentence. Canvas, motion, AI, design tool, video tool. I could not say who it was for.
And I kept rebuilding the editor. A better canvas, a faster canvas, a Figma-grade canvas. Meanwhile almost nothing reached users in a shape they could try in five minutes.
What changed my mind
Developers already live in an editor with an agent next to it. Claude Code, Cursor. The code is the source of truth, and the agent edits it.
Design tools sit outside that loop. You draw in one place, then someone translates it into code, or an agent does, and details get lost on the way. Nudging padding by 4 pixels should not need a prompt.
So the idea became small. Click an element in your running app. Edit it like in a design tool. The change lands in your source, as a diff.
What we dropped
The canvas, the motion editor, the GPU renderer, the node graph, the chat agent, the MCP server and the old CLI. The “Remove the old product” pull request touched 11,267 files and deleted about a million lines.
The repo went from 15,115 tracked files and 238 MB to 3,922 files and 35 MB. A full archive of the old product exists as a git bundle, so nothing is lost. Your account data can still be exported from account settings.
The Rust renderer posts stay up. The work was real. It just is not Feega anymore.
What we kept
The account at oh.feega.app, sign-in for the editor, and billing for people who already subscribed. The database keeps its old tables untouched, because migrations are not something I want to delete.
What Feega is now
A free, open-source VS Code extension, Apache-2.0, also in Cursor, Windsurf and VSCodium. And npx feega for any browser.
You run your app through Feega and click an element. Size, spacing, colour, type, radius, shadow and layout are in a panel. Feega finds the file, line and column the element came from, and writes the change as a Tailwind class, your own token, or plain CSS. Every edit shows up in Changes. You can review it, undo it, revert it.
It supports SvelteKit, React with Vite, Next.js and Vue.
There is no AI in it. It does not need tokens. It sits next to the agent you already use: you design, your agent codes, same files.
Version 0.2.9 went out today. Since 0.2.0 on 19 November it gained:
- A Layers panel, with the structure of the page.
- Icons: change size, colour and stroke, or swap one from your icon library or an
.svgfile. - Link addresses, event handlers and simple click actions.
- Breakpoints: edit each responsive size on its own.
- States: hover, focus and the rest, edited like any other style.
- Themes: edit the light and dark variants.
- Text that comes from a loop or data points back to where the data is defined. Items generated by a loop still share one source line, so they cannot be moved one by one.
What is next
Feega Cloud: GitHub sync, collaboration, sections and templates. It will be paid. The editor stays free. The dashboard on the web app is a preview of it for now.
What I got wrong
I treated the editor as the product. It is the part that is fun to build, so I kept building it. A renderer that holds 90 fps is a good piece of engineering and I am proud of it. It did not tell me whether anyone needed the thing.
I also added before I removed. Every new surface looked like progress. Each was one more thing to explain, test and pay for.
The cut took two days.
Try it
Install it from the VS Code Marketplace, or Open VSX for Cursor, Windsurf and VSCodium. Or run:
npx feega
The docs cover setup per framework. The code is on GitHub. If something breaks, open an issue.