Journal

Figma's latest updates: code layers credits, GitHub cloning and what to check now

Figma's free code layers window ran through November 4, and recent updates change GitHub cloning, connectors and AI credit controls. Here is what to check.

Figma's latest updates: code layers credits, GitHub cloning and what to check now

Figma has shipped a run of small updates over the past few weeks, and most are easy to miss if you only read the big launch posts. Taken together, they change a few things that affect budgets, permissions and everyday work. One date also just passed: Figma said that creating and editing in code layers would be free on paid plans through November 4, 2026.

This roundup covers what changed according to Figma's release notes and what we would check as a result. We have kept Figma's announcements separate from our own suggestions, so you can tell which is which. Availability and rollout timing can vary, so check your own file and plan before changing a process.

The code layers free window has reached its end date

Code layers entered open beta at Config India in October. Figma's announcement said the feature "will use AI credits", with creating and editing free on paid plans through November 4, 2026. The notes we reviewed did not mention an extension or describe in detail what changes after that date.

If your team tried code layers during that window, this is a good moment to look at how much you used it. We would do three things:

  • Check your current AI credit usage in your Figma plan's settings.
  • Try one typical code layer task and see what it costs before you build it into a client workflow.
  • If you quote fixed-price projects, decide how you will account for AI credits in your estimates.

Code layers now read your prototype connections

In a November 3 update, Figma said that when you create a code layer from design frames, the agent now reads the prototype connections and interactions between them. The stated goal is less prompting for the complex parts of a flow, with more time left for refining the prototype and finding edge cases.

In practice, this gives you a reason to keep prototype links tidy before you convert a flow. A broken or outdated connection is now context that the agent may use, so we would review those links first, especially in older files.

GitHub cloning is on by default for new connections

This is the update we would flag to your admin. Figma says cloning will be enabled by default for new GitHub repository connections, so teams can import code into Figma without an extra admin approval step. It is rolling out to all plans. Admins can disable cloning for individual repositories at any time, and settings for existing connections stay the same.

That removes friction, but it also removes a checkpoint. If your organisation or a client has rules about where source code can go, it is worth reviewing the process now:

  1. List which repositories are connected to Figma today.
  2. Decide which future connections should allow cloning.
  3. Tell whoever connects repositories what the new default is.
  4. Check your client contracts if you work with their private code.

Connectors are now available on all plans

On October 30, Figma announced a Google Drive connector for the Figma agent and Make. It can bring existing file context into Figma and create new Drive files from within your file. Figma's examples include summarising research insights, referencing real data and pulling in assets to edit on the canvas. It also said connectors are now available on all plans, including Starter. You add them from the plus menu in the prompt box.

This could cut down on copying and pasting research into prompts. Before you connect anything, though, think about what a shared file might expose. We would start with a project folder rather than a broad drive, particularly on client work.

Shaders are generally available, with higher resolution exports

Figma says shaders are now generally available to all users and can render and export at up to 4096px. You can also include them when you turn a design into a code layer with "build this with code". They render properly when the code layer is set to Play, although Figma notes this is only available in the browser through Chrome version 157, which was rolling out at the time of the note.

The higher limit matters if you were avoiding shaders for large hero images or print-sized exports. If a shader will be part of a code layer, test it in the required browser before you show it to a client.

Weave models are reachable through the Figma MCP

On October 26, Figma said all video and image models in Figma Weave can be used from your AI agent through the Figma MCP, including models like Seedance, Kling and Nano Banana. You need a Weave account connected to your Figma account, and generations consume Weave credits.

That last detail is worth remembering. Weave credits are a separate thing to watch alongside your Figma AI credits, and an agent can use them quickly if it generates several options in a row.

New Enterprise controls and device presets

Two smaller updates round out the period. For Enterprise plans, Figma announced on October 22 that admins can:

  • Set default access to paid AI credits at the organisation and billing group levels.
  • Manage AI credit access and limits through SCIM for SCIM-managed users.
  • Stop team members from creating Starter or Professional plans with company email addresses.
  • Use new admin REST APIs to manage teams, folders and files.

Meanwhile, frame presets for iPhone Duo and iPhone 18 arrived on October 23, including in the properties panel, prototype settings and the Make preview device picker. If you maintain device templates, you can check them against the new presets.

None of these updates requires urgent action on its own. The two we would act on this week are AI credit usage now that the code layers date has passed, and the GitHub cloning default if your team connects private repositories. Figma's release notes change often, so it is worth adding a quick read to your weekly routine.

Oybek Ruziev

Designer & Framer developer · AidanCreates

Keep reading

All posts