As of 5 Oct 2026, Organization and Enterprise plans can connect more than one GitHub organization to the same Figma plan. I would do that before anyone prompts with the library on and expects the real components.
Code sources, which attach a repo or an npm package to the library, are still a closed beta. The multi-org connection is the part you can turn on now, if your plan is Organization or Enterprise. It does not, by itself, make the agent build from your package. It stops the "wrong org" excuse when the beta reaches you.
Name the package out loud
Write the package name into the guidelines file in the meantime. "Use @your-scope/ui" is a sentence. A demo kit with the same component names is how you teach the agent the wrong API.
I would put the connection, and the package name, on the same Q1 line. Design can see the library. Engineering can see the repo. The agent needs both, and a person still reviews the diff.
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.