diff --git a/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md b/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md
index 39be2e48..e3ddc731 100644
--- a/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md
+++ b/docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md
@@ -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.