Figma is testing code sources in a closed beta. You attach a GitHub repo or an npm package to a design library, then publish the library once. Teammates turn that library on and prompt. They do not import the package themselves. The agent is meant to build and edit components and code layers from that code.
A Figma component and a React component with the same name are not the same component until the props match. This is the feature that tries to close that gap. Figma says the beta is a small group. Assume you are not in it until the control shows up.
If you are in it, and if you are not
If you are in it, connect the package the app actually installs. A demo kit will teach the agent the wrong API.
If you are not in it, write the prop names into the guidelines file now. Guidelines can carry the list today. Code sources can enforce it later. Organization and Enterprise plans can also connect more than one GitHub organization to the same Figma plan, as of 5 Oct. That matters when the system lives in one org and the product code lives in another.
Which component in your library has a Figma API and a code API that disagree? Start there. One component, both names written down, is a better Q1 item than a rollout of a beta you cannot open.
I checked the Figma release notes and the Config India 2026 help article on 18 Oct 2026. Plans, betas, and the 4 Nov credit window come from those pages. If your admin console disagrees, trust the console.