Add GitHub two-way sync to Client App Builder / Client Portal
E
Enoch Leffingwell
Please add GitHub two-way sync to Client App Builder / Client Portal, like AI Studio already has.
AI Studio syncs both ways with a GitHub repo — changes in the editor push to the repo, and pushes to the repo pull into the editor. Client App Builder has no such sync. The only way to edit it with an external AI tool is MCP, which is not a substitute: there is no repo, no version history or restore, no code review, and no owned copy of the work.
How this helps communication with clients: the client portal is where clients see their business — their dashboard, their links, their tools. When the agency can iterate on it quickly and safely, the portal improves faster and the client sees the improvement sooner, with fewer broken experiments in between.
Who benefits — every agency building client portals:
- Agencies that build portals with AI tools can work in their own editor and push, instead of being locked into one editing path.
- Teams that review each other's work get code review and version history before anything goes live.
- Agencies that manage many client portals can keep each portal's code in its own repo and roll back a bad change in seconds.
- Developers working alongside non-technical agency owners can collaborate on the same portal without overwriting each other.
- Anyone who has lost work to an accidental edit gets a restore point.
Why it benefits HighLevel: GitHub sync is already proven inside the platform — AI Studio has it, and agencies rely on it. Bringing the same capability to Client App Builder makes the portal product as safe and professional to build in as AI Studio, which keeps agencies building portals on HighLevel instead of in a separate tool, and it raises the quality of the portals clients actually see.
Log In