Secure Git BridgeSecure AI repository access
Connect. Work.
Secure.
Secure Git Bridge quick start
Install the Mac app, approve a real Git repository, connect ChatGPT, and bind the conversation you want to that repository. Secure Git Bridge keeps repository authority local and human-controlled.
Follow these steps in order. Most of the work happens once; connecting another conversation later is much faster.
System requirement: Apple silicon Mac (arm64) running macOS 13 or later. The current commercial package does not support Intel Macs.
Open the downloaded macOS package, install Secure Git Bridge, then launch the app.
If macOS asks you to confirm access or permissions, follow the system prompt. Secure Git Bridge must be able to read the repository you explicitly approve.
Before the first AI connection, open the Secure Git Bridge customer account and use the email you registered or purchased with. Existing paid purchases are restored automatically; first-time users receive a verified Free account. Then choose Activate this Mac. Free does not require a credit card and verification does not enroll you in marketing.
You can add and inspect repositories before verification; the verified account is required only when you start AI access.
Click Add Repository and choose the repository's Git root — the folder Git itself recognizes as the repository.
Secure Git Bridge supports ChatGPT, Claude Desktop, GitHub Copilot, Cursor, and Gemini. Provider setup is separate from repository access.
ChatGPT uses the published Secure Git Bridge connector and the conversation-binding flow below. Claude Desktop, GitHub Copilot/VS Code, Cursor, and Gemini each receive one provider connector setup. After that, select a repository in Secure Git Bridge and use Bind, Move, or Unbind; you do not reinstall the provider for every repository.
Secure Git Bridge copies a short-lived connection message containing a one-time code.
The conversation is then pinned to the repository you selected in Secure Git Bridge.
ChatGPT becomes connected after the confirmed conversation starts using Secure Git Bridge. Named local providers show Bound after SSGB grants a repository route and Active only after live provider MCP traffic. You can now inspect allowed code or create patch proposals through Secure Git Bridge.
Once provider setup is complete, repository access is managed inside Secure Git Bridge. ChatGPT conversations can be bound independently, while Claude Desktop, GitHub Copilot, Cursor, and Gemini keep their one-time provider connectors and move between approved repositories without reinstalling.
Select the repository, click Connect to AI, then paste the new one-time message into the intended ChatGPT conversation using @Secure Git Bridge.
Different ChatGPT conversations can be bound to different approved repositories. A conversation does not gain authority over another repository just because it is saved in the same app.
When ChatGPT proposes a patch, review it locally in Secure Git Bridge before applying anything to your repository.
Use the repository disconnect control when you want to revoke AI access for that repository. The global disconnect control stops all AI access.
You selected a normal folder instead of a Git repository root. Choose the folder that Git recognizes as the repository.
If this installation already has a working ChatGPT tunnel, choose Use existing tunnel and reuse it. Do not create a separate tunnel just because you added another repository.
Return to Secure Git Bridge and click Connect to AI again to generate a fresh connection message.
That is expected security behavior. Secure Git Bridge intentionally prevents AI access to protected files and secret paths.