From 78e01627a1d1e940e3292df3f1787eaa3934d9f1 Mon Sep 17 00:00:00 2001 From: Pinkesh Date: Fri, 1 May 2026 11:11:13 +0530 Subject: [PATCH 1/4] FF MCP: update to mention branching support --- docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md b/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md index 39be2e48..e5253a66 100644 --- a/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md +++ b/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md @@ -227,6 +227,8 @@ From that point on, the same rules apply as when [editing an existing project](# :::info[Prerequisite] Have your **project ID** ready. Open the project in the FlutterFlow editor. The project ID is the path segment after `/project/` in the URL. + +**To work on any branch of the project**, open that branch in the FlutterFlow editor and copy the project ID from URL. ::: Editing an existing project follows the same flow as [creating a new one](#setup-workspace) — you run `flutterflow ai init` to scaffold a workspace, then drive changes from your agent. The only difference is one step in the wizard: when it asks for an **existing project ID**, paste yours instead of pressing Enter: From 588cd17c8e93b099f8172185f7d9d0ed754e86e6 Mon Sep 17 00:00:00 2001 From: Pinkesh Date: Fri, 1 May 2026 12:13:13 +0530 Subject: [PATCH 2/4] moved to branching section --- .../ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md b/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md index e5253a66..90a9fa88 100644 --- a/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md +++ b/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md @@ -227,8 +227,6 @@ From that point on, the same rules apply as when [editing an existing project](# :::info[Prerequisite] Have your **project ID** ready. Open the project in the FlutterFlow editor. The project ID is the path segment after `/project/` in the URL. - -**To work on any branch of the project**, open that branch in the FlutterFlow editor and copy the project ID from URL. ::: Editing an existing project follows the same flow as [creating a new one](#setup-workspace) — you run `flutterflow ai init` to scaffold a workspace, then drive changes from your agent. The only difference is one step in the wizard: when it asks for an **existing project ID**, paste yours instead of pressing Enter: @@ -299,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. -::: +Workspaces can target any branch of a FlutterFlow project. To work on a branch, open that branch in the FlutterFlow editor, copy the project ID from the URL, and paste it when `flutterflow ai init` asks 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. From 79147847b5867b1ea49f546801216c05304e27c4 Mon Sep 17 00:00:00 2001 From: pinkeshmars <71133091+pinkeshmars@users.noreply.github.com> Date: Fri, 1 May 2026 13:51:31 +0530 Subject: [PATCH 3/4] Update docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md Co-authored-by: Pooja Bhaumik --- docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md b/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md index 90a9fa88..113c4189 100644 --- a/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md +++ b/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md @@ -297,7 +297,7 @@ See [MCP tools](#mcp-tools) for the full command list. ## Branches and Rollback -Workspaces can target any branch of a FlutterFlow project. To work on a branch, open that branch in the FlutterFlow editor, copy the project ID from the URL, and paste it when `flutterflow ai init` asks for an **existing project ID**. +The CLI can target any branch of a FlutterFlow project. To work on a branch, open that branch in the FlutterFlow editor, copy the project ID from the URL, and paste it when `flutterflow ai init` asks 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. From cc9e09eff9a64f4c992f3c469be4a19197fca90e Mon Sep 17 00:00:00 2001 From: Pinkesh Date: Fri, 1 May 2026 13:57:16 +0530 Subject: [PATCH 4/4] Clarify instructions for targeting branches --- docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md b/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md index 113c4189..e3ddc731 100644 --- a/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md +++ b/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md @@ -297,7 +297,7 @@ See [MCP tools](#mcp-tools) for the full command list. ## Branches and Rollback -The CLI can target any branch of a FlutterFlow project. To work on a branch, open that branch in the FlutterFlow editor, copy the project ID from the URL, and paste it when `flutterflow ai init` asks for an **existing project ID**. +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.