Skip to content

FF MCP: update to mention branching support #509

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PoojaB26 merged 4 commits into from
May 1, 2026
+1 −3
Merged

FF MCP: update to mention branching support #509

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
78e0162
FF MCP: update to mention branching support
pinkeshmars May 1, 2026
588cd17
moved to branching section
pinkeshmars May 1, 2026
7914784
Update docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md
pinkeshmars May 1, 2026
cc9e09e
Clarify instructions for targeting branches
pinkeshmars May 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -297,9 +297,7 @@ See [MCP tools](#mcp-tools) for the full command list.

## Branches and Rollback

:::warning[Agents commit to main]
Workspaces always target the project's **main branch**. There's no flag to point them at a feature branch. Every successful push creates a commit on main, so for high-stakes projects, work on a clone, make sure version history is enabled, or coordinate with your team before letting an agent run.
:::
The CLI can point to any branch of a FlutterFlow project. Since each branch is accessed through its own URL, it has its own project ID. To work on a specific branch, open it in the FlutterFlow editor, copy the project ID from the URL, and paste it when `flutterflow ai init` prompts for an existing project ID.

To roll back, use FlutterFlow's project version history in the visual builder — the same mechanism you'd use for visual edits. Each agent push lands as a commit there with whatever commit message the agent supplied.

Expand Down
Loading