Skip to main content
Question

Figma Make Pushes to Github Blocked By Cloudflare

  • July 18, 2026
  • 2 replies
  • 20 views

John Stritzinger

I have been using the Figma Make Service for several months. And Up to Mid April it worked fine. I could push to both Github from inside the project, or from the Integration at the top right of the screen. But I am now getting Cloudflare errors in my project and neither work. I dont understand why or how to fix it.

 

And in general since Figma Make is using Claude Code instances(and a good implementation) I want the Claude Agent to push directly to github on occassion. This is possible but recently you started blocking it. Getting 500 errors.

2 replies

John Stritzinger

And BTW the Coding Agent is saying if it cant push directly it has to use the MCP integration which is horrible in my opinion. It doesnt support a full push, and I dont want to use my whole monthly subscription pushing one file at a time.


Tom Reem
Figmate
  • Figmate
  • July 18, 2026

Hey ​@John Stritzinger — welcome to Figma Forum, and thanks for flagging these details here.

I looked into this. The blocker is specific to pushing to GitHub directly from the coding agent (e.g. the agent running git push on its own). That route isn't supported right now, which is why those attempts come back as Cloudflare/500 errors.

The supported path is the built-in GitHub integration (Make settings → GitHub, top-right). Rather than the agent pushing on its own, it hands your project's code to Figma, and Figma pushes it to the repo for you — so it isn't affected by this, and it's a full push of your project, not a file-by-file flow. Steps and details here: Push from Figma Make to GitHub and Beyond the basics: Using Figma Make. If this isn’t matching up with your experience, please do let me know.

One thing I want to make sure I understand: You mentioned the built-in integration is also throwing Cloudflare errors. That path shouldn't be affected by this, so if it's still failing for you, could you try it once more and share a screenshot of the exact error? That'll help us dig into what's happening there specifically.

I can also see the Product Support team has your report under case: 2022322. If you haven't already, sharing view access to the affected file with support-share@figma.com will let them investigate the specifics.