From 6 Oct 2026, Figma moved the agent in Figma Design and Weave tools from open beta to general availability. During beta, agent runs didn't touch your AI credit balance. From GA, they draw from the same shared Figma AI credit pool as tools like Figma Make. If you already burn Make, image AI, or cleanup tools against that seat bucket, the agent is now another line on the same meter.
For Figma AI agent freelancers the decision is small. Try it on a non-client draft this week if you already pay for a Professional (or Org/Enterprise) Full seat and have a repeatable design-system, cleanup, or docs job. Skip for now if you're on Starter's monthly cap, mid-deadline with Make already eating the pool, or stuck on Dev/Collab when you need edits in shared team files. Wait if you want clearer per-action credit tables before client use. Budget / buy credits only after a measured dry run — never from a launch post. This isn't a generator shoot-out. That one is our live Canva Magic Studio vs Adobe Firefly comparison.
Affiliate disclosure: some tool or platform links may later be affiliate or referral links. Product facts below come from Figma's AI credit updates FAQ, the Figma agent help article, the How AI credits work page, Figma's pricing page, and Figma's design-systems agent blog post, as of 7 Oct 2026 (SAST). Re-check seat allotments, credit wording, and seat permissions before you put client files through the agent. Not legal advice. Not a guarantee of clients, savings, or income.
What the Figma agent actually is
The Figma agent is a canvas agent inside Figma Design. You describe a goal in plain language — document a component, audit a screen for library adherence, rename tokens — and it takes actions on the file. It runs in the desktop app or the web browser. It isn't a new image model, and it isn't Weave.com as a standalone site. Weave tools inside Figma are a related GA surface that also meters Figma AI credits; they share the Design agent's budget with Make.
Figma's design-systems blog post names the jobs it wants you to try: document components (do's/don'ts, variants, handoff APIs); audit screens for library adherence; bulk replace components or tokens; standardize naming; check token adoption. Skills can package repeatable workflows. Treat those as product examples, not a promise that your library cleanup will finish in one prompt.
What changed on 6 Oct
Per Figma's AI credit updates FAQ:
- The agent in Figma Design and Weave tools moved from open beta to general availability on 6 October 2026.
- Usage during the beta period didn't consume any AI credits. Crediting started at GA.
- Weave tools and the Design agent now draw from the same credit budget as other GA AI tools like Figma Make.
- Agent usage varies by prompt complexity, actions taken, and context (connected libraries, attached files) — like other agentic features such as Make. Figma does not publish a fixed per-prompt burn for the agent, so we won't invent one.
- Weave tools have set credit costs per tool, listed in the How AI credits work consumption table. Re-check that table in Admin before a big batch.
The meter mindset is the same one we used for Firefly AI Assistant: one small non-client dry run, watch the balance, then decide. Different vendor, same habit.
Seat math for freelancers
Every seat includes monthly seat credits. From figma.com/pricing and the credit FAQ (as of research on 7 Oct 2026):
- Professional Full: $16/mo + 3,000 AI credits/mo
- Professional Dev: $12/mo + 500
- Professional Collab: $3/mo + 500
- Starter: free, with 150 AI credits/day, up to 500 AI credits/mo
- Organization Full: 3,500/mo; Enterprise Full: 4,250/mo; other seats on paid plans 500/mo
Seat credits aren't changing as part of the 25 Aug 2026 add-on package update. That update gave AI credit add-ons more credits at the same cost (2× for Pro; 1.6× for Org/Enterprise). Seat allotments stayed put.
When you hit zero, limits reset monthly. Admins can purchase additional credits (subscription and/or pay-as-you-go). For current add-on package prices, open Admin → AI credits — we won't invent a USD package table or convert anything to ZAR. If you already budget API meters, the discipline in our API cost guide for freelancers applies. Don't carry those numbers over to Figma.
Who can edit vs chat
Per Figma's blog and the Work with the Figma agent help article:
- Full seat users on Professional, Organization, Enterprise, and some Education plans can use the agent. Availability on Starter is limited.
- Full seat + edit access: chat and ask for edits on the file.
- View, Dev, or Collab seats (or view-only access): chat without making edits to the shared file.
- Anyone can chat and ask for edits in Draft files.
- Collab, Dev, and View seats can use the agent in their drafts.
So a Dev or Collab teammate is not locked out of the agent — but on a shared team file they may be chat-only. If your workflow needs the agent to rename tokens or swap components in a live library file, that needs Full + edit access (or a Draft where anyone can ask for edits).
A freelancer workflow on paper
This is a test plan built from Figma's docs, not a hands-on credit log.
- Duplicate a throwaway frame into a Draft — never a live client library.
- Ask the agent to audit that frame for out-of-system buttons or components that aren't from your library.
- Watch AI Balance before and after. Write the delta down. Don't guess the burn from a launch video.
- On a second Draft, ask it to draft do's/don'ts or variant notes for one component you already own.
- Reject any step you wouldn't bill a client for. Course-correct in plain words.
- Compare the time you would have spent manually against the credit delta and the quality of the notes.
One row of that log tells you more than any GA announcement. If the dry run is useful and repeatable, you have a case for budgeting more credits. If Make already owns the monthly pool, you've learned that without burning a client week.
Try / Skip / Wait / Budget sheet
Try if you already pay for a Professional (or Org/Enterprise) Full seat, you have a repeatable design-system / cleanup / docs job this week, and you can spare seat credits on a non-client draft while watching the AI Balance menu.
Skip for now if you live on Starter's 500/mo cap, you're mid-deadline with Make already eating the pool, clients refuse Figma logins, or you only have Dev/Collab and need edits in shared team files (chat-only outside drafts). Stay on manual library work and existing Make budget discipline. If your clients live in Canva anyway, the Canva vs Firefly comparison is the better next read than an agent dry run.
Wait if you only need the agent once Figma publishes clearer per-action credit tables you can meter, or you're waiting for admin-bought subscription credits before client use.
Budget / buy credits only after a measured dry run shows agent workflows you'll repeat monthly — using Figma's own Admin add-on or pay-as-you-go paths. We won't name a package that "pays for itself." Nobody has measured that for your work.
| Situation | Try | Skip | Wait | Budget / buy credits |
|---|---|---|---|---|
| Professional Full solo ($16 + 3,000/mo) | Yes: one non-client Draft, Balance watched | If you never open Design AI tools | If mid-deadline | Only after a logged monthly pattern |
| Starter (150/day, 500/mo cap) | Tiny test only if agent is offered | Yes for client weeks — cap is tight | — | Only after a plan change you already planned |
| Dev or Collab seat, shared team file | Chat in Drafts; edits there only | Yes if you need edits on the team file | For a Full seat upgrade decision | Talk to the seat admin, not a launch post |
| Make-heavy month already | Not on the live client file | Yes until Make cools off | Yes: protect the shared pool | Only if agent + Make both prove monthly |
| Org/Enterprise Full (3,500–4,250/mo) | Yes: same dry-run habit | If policy blocks AI edits | If admin hasn't enabled credits | Admin add-on / PAYG only after the log |
The Joburg reality check
Run the dry run on a non-client Draft over fibre you trust, not mobile data during load-shedding, and not on a paid brief. Export a version history snapshot or a PDF handoff before you let the agent touch anything you'd bill for. Keep the manual library habit as the backup. That's how we'd run it from a Joburg desk. It works the same anywhere.
FAQ
Does the agent cost credits now?
Yes. From GA on 6 Oct 2026, the Design agent and Weave tools consume Figma AI credits. Beta usage didn't. Cost varies by prompt complexity, actions, and context — Figma doesn't publish a fixed per-prompt number for the agent.
Can I use it on a Collab seat?
Yes in Drafts (chat and edits). On shared team files, Collab, Dev, and View seats can chat without making edits. Full + edit access is what you need for edits on those files.
Do Make and the agent share one pool?
Yes. Weave tools and the Design agent draw from the same credit budget as other GA AI tools like Figma Make.
What happens at 0 credits?
Limits reset monthly. Admins can purchase additional credits via subscription and/or pay-as-you-go. Check Admin → AI credits for current package prices — we won't invent them here.
Sources: AI credit updates FAQ (Figma Help), How to lighten design system upkeep with the Figma agent (Figma Blog, 6 Oct 2026), Figma Pricing, Work with the Figma agent in design files (Figma Help), How AI credits work (Figma Help). Re-check seat allotments, credit wording, and permissions at paste time.