Nested asset inputs now collide with the gateway contract that protects tool calls.
Creative workflows need to accept valid structured inputs while the gateway still blocks malformed requests.
Who you’d be doing this for
“I added the second reference and the whole run died, so I rebuilt the asset by hand.”
Lenka Ionescu · UI/UX Designer
Uses Community-published Weave tools to generate visual asset variations from Figma canvas inputs.
What is at stake
Valid nested-input calls are failing in custom Weave tools while malformed requests remain blocked. You must weigh fast recovery for designers against preserving the validation boundary.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- creative workflow continuity vs. strict request validation
- gateway compatibility vs. long-term contract clarity
- fast recovery vs. production safety
Why Figma
Custom Weave tools run on the Figma canvas, so a gateway rejection interrupts designers inside their asset workflow.
Written with these in mind
Not your kind of problem? 51 more at Figma, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.