Push to GitHub

Push to GitHub sends a version of your prototype to a repository as a ready-to-run project, the same files you get when you download the project. Each push is one commit, so developers can keep building on top while you keep designing in Phluffle.

Good to know Pushing to GitHub is free for everyone and uses no credits. You need edit access to the prototype.

#Connect your GitHub account

You connect GitHub once, then push from any prototype you can edit.

1. Open a finished version and open Take it to code (from the rail, ☰ Tools, or the Share menu).
2. In Push to GitHub, click Connect GitHub.
3. GitHub asks you to give Phluffle access to your repositories. Approve it.

You come back to the dialog, connected. You can also connect from Settings → Connections.

Note One GitHub account can belong to only one Phluffle account. If you see "That GitHub account signs in to another Phluffle account", use a different GitHub account, or sign in to Phluffle with that one.

#Push a prototype for the first time

The first time you push a prototype, Phluffle creates a new repo for it.

1. In Take it to code, check the New repo name. It starts as your prototype's name; change it if you like. Names can use letters, numbers, dots, dashes and underscores.
2. Leave Private repo ticked to keep it private, or untick it to make it public.
3. Click Create and push.

When it's done you'll see a confirmation with a View the commit link. The repo is now linked to this prototype.

#Push a new version

Once a repo is linked, the dialog shows it under Linked repo, with when you last pushed.

1. Open the version you want to push and open Take it to code.
2. Check the Branch. It's main by default, or the branch you used last time.
3. Click Push vN.

If the branch doesn't exist yet, Phluffle creates it from the repo's default branch. That's a simple way to push design updates to a separate branch for review.

To start over in a fresh repo, open Push to a new repo instead, name it and click Create and push.

#What each push does

• One commit per push, on top of the branch, with the message "Phluffle vN:" followed by that version's summary.
• Phluffle's files are replaced with this version: index.html, AGENTS.md, the phluffle/ scripts and the other project files.
• Files developers added stay. New components, config, tests and anything else that isn't one of Phluffle's files are left alone.

Heads up If a developer edited one of Phluffle's own files, such as index.html, the next push replaces it with your version. Agree with your team on which files Phluffle owns, or push to a separate branch.

#Hand the repo to a coding agent

The project includes AGENTS.md and CLAUDE.md, so a coding agent knows how the prototype is built before it changes anything. Clone the repo, open it in Claude Code, Cursor or Codex, and say what to build next, for example: "Read AGENTS.md, then turn this prototype into a Next.js app. Keep the design and the screens."

Want the agent's work to come back to Phluffle as new versions instead? See Connect coding agents (MCP).

#Disconnect GitHub

1. Open Settings → Connections.
2. Next to GitHub, click Disconnect.

To fully remove access, also revoke Phluffle in GitHub under Settings → Applications.

Connecting GitHub also links it as a way to sign in. Disconnecting stops pushes, but you can still use Continue with GitHub to sign in. See Your account and signing in.

#If a push doesn't work

• "GitHub signed you out. Connect your account again in Settings." Your GitHub access was revoked or expired. Connect again.
• "GitHub wouldn't let us…" Your GitHub account can't write to that repo. Check your access in GitHub.
• "You already have a repo called …" Pick another name, or push to the repo you linked before.

#Related

• Download the project (take it to code)
• Connect coding agents (MCP)
• Versions, restore and retry