Base44: GitHub 2-Way Sync for Shared Workspaces
Base44Base44 extended its GitHub 2-way sync to apps hosted in shared workspaces, enabling team environments to connect a repository and keep cloud and local code in sync. The feature requires the Builder plan or higher and enforces that only the app owner can establish the initial connection. This release makes GitHub-based collaboration viable for multi-user Base44 projects.
Sources & Mentions
3 external resources covering this update
Overview
Base44 expanded its GitHub 2-way sync feature to cover apps in shared workspaces. Previously limited to single-owner apps, the integration now supports team environments where multiple collaborators need to contribute code through a connected Git repository.
How the Sync Works
Once connected, the GitHub integration keeps the Base44 cloud environment and a local repository synchronized in both directions. Developers can write code locally in their preferred IDE — using tools like Cursor, VS Code, or any editor — and sync changes back to the Base44 cloud by merging them to the main branch of the connected repository.
Sync is automatic after a merge; no manual push to Base44 is required beyond the standard Git merge operation. A subsequent publish action within Base44 makes the updated code live for end users.
Access Controls and Restrictions
Several important permission controls govern the shared workspace integration. GitHub integration requires the Builder plan or higher. Only the app owner can establish the initial GitHub connection. Changes must be merged to a branch named main — Base44 does not currently support other default branch names. GitHub sync is permanent: once an app is connected, it cannot be disconnected.
Developer Impact
Team-Scale Vibe Coding
This feature closes a gap that made Base44 difficult to use for team projects. Without shared workspace GitHub sync, teams had to rely entirely on Base44's in-product version history, which lacks branching and pull request workflows. With repository sync enabled for shared workspaces, teams can apply standard Git collaboration practices while still using Base44's AI builder for rapid iteration.
Limitations Compared to Full Local Development
The GitHub sync integration still has constraints compared to fully ejecting an app. It requires main as the branch name, does not support feature branch workflows from within Base44, and is permanent once enabled. Teams that need more flexibility in their Git workflow should consider the eject command instead.