Design → code → canvas → feedback → repeat. The Figma MCP server is now bidirectional. GitHub Copilot users can pull design context into code and push working UI back to the Figma canvas, all from Visual Studio Code . No handoffs or context switching. Just flow.

@figma @github @code it's all so exhausting...

@figma @github @code for us that never was the problem, The problem was iteration between Make <->design. design->code always left Make and code out of sync and then design was overwhelmed to keep up.

I tried it yesterday on a project (Webapp for mobile devixes). I started by coding and then created a Figma design. However, if I’ve already built my screens using HTML and CSS, why should I revert to Figma? I don’t see the actual benefit. In the past, designing with Figma and making iterations was quicker. However, now I’m much faster working directly with Codex or Claude on Live Code. I See Instant the result, can Test in a real Browser etc. Maybe anyone has a good use case for Code -> figma -> Code?

@figma @github @code Finally, I can break my designer's carefully crafted auto-layout with my cursed CSS right from VS Code! 😅 Sounds amazing, but I can't wait for our first 'merge conflict' directly on the Figma canvas. 🍿

@code @figma @github Bidirectional flow is a big step. But the real source of truth still isn’t defined. Design describes structure. Code describes implementation. What’s missing is the behaviour model both compile from.

@figma @github @code Fraud didnt tell u it cant even group elements in figma yet alone attach tokens from brand sd. Ai slopers are now “engeners and designers” 🤣🤣🤣

@figma @github @code the overlooked part is how 'working ui' pushed back to figma actually looks. is it clean auto-layout components or just a static frame? that makes all the difference for actual design flow.

@figma @github @code Does copilot put into consideration the frames, autolayout and groups in the design screen on figma?

@figma @github @code The frame you show that had been generated back into figma was not the 'related' tab you asked it to do

@figma @github @code This is new, yes?

@figma @github @code When I can figma can accurately bring in my UI into figma make I’ll trust this. The design context is still just as strong as bringing in an image of my work into Claude rn in my opinion.

@figma @github @code What terrible way

@figma @github @code Bidirectional is the unlock. Next step: the design agent dynamically discovering a deployment or QA agent it wasn't pre-configured for — closing the loop across tools, not just between two.

@zoink @figma @github @code Not good enough. Started using pencil and it’s the future of how design will work. Literally plugged into cursor 🤯

@figma @github @code I saw this cake on a YouTube video made by Figma. That cake gets around.

@figma @github @code no handoffs is the right framing. every project slows down at the design→code→feedback boundary. this just collapses it.

@figma @github @code Bidirectional MCP closes the loop most design tools miss. Not just 'design → code' but 'code changes → update design file.' That's version control, not a one-way export. The feedback loop compresses from days to seconds.

@figma @github @code Count me in—can’t wait

@figma @github @code Why the back and forth? Why do designers need to be in Figma anymore?

@figma @github @code Building nice figma designs is hard for me