Figma Make adds local codebase editing in limited beta

• Figma said figma's launch post puts Make on top of a local codebase in a limited beta, moving the product from isolated generation toward edits on real production files.
• In figma's capability list, the company framed the new workflow in three steps: bring your codebase into Make, apply precise code edits, then branch, commit, and ship from the beta desktop app.
• figma's follow-up post tied the launch to Agentation and linked a beta signup page, while figma's later post pointed to a dedicated Make waitlist.
• The product framing is getting more explicit: zoink's post describes Figma's direction as freeform design, code-based prototyping, and production shipping inside one connected platform.

You can watch Figma's launch demo, join the beta signup, and check the separate Make waitlist. The clearest product shift is that Make now reaches past mockups into a local repo, and figma's rollout post says the desktop beta is where branching, commits, and shipping land first.

The new claim in figma's launch post is simple: Make can connect to local code instead of staying inside a generated sandbox. That changes the unit of work from a throwaway prototype to an existing codebase a team already ships.

zoink's platform framing makes the strategic direction plain. Figma is pitching design, coded prototypes, and production code as one continuous surface rather than separate handoff steps.

Figma's own feature list in this rollout post breaks the workflow into two distinct moves before shipping:

• Bring your codebase into Make.
• Edit code with precise changes.

That "precise changes" language matters because it suggests patch-style editing on top of existing files, not just regenerating an interface from a prompt. The launch materials do not describe supported frameworks or repo constraints, but they do frame the feature as visual editing tied to real local code.

The third step in figma's rollout post is the part that pushes Make closest to production workflows: branch, commit, ship.

Figma did not publish a long mechanics thread in the evidence set, but its wording implies Make is crossing from ideation into version-controlled changes. That is a much bigger promise than "generate a prototype," because the output now has to survive the same repo hygiene and shipping path as the rest of the product.

Access is still narrow. Figma's main post calls the rollout a limited beta starting now, the follow-up links a signup page, and a later official post points to a separate waitlist.

Figma's Agentation note also names Agentation as an influence "to push past the prompt," which is a useful clue about the product direction. Figma is not just adding another text box to design tooling, it is trying to make visual AI editing operate directly against the code teams already maintain.