How It Works
A controlled path between an AI assistant and the Git repository you approve.
Secure Git Bridge is designed so the AI connection gets repository-specific capabilities instead of broad authority over the developer's computer.
1. Install Secure Git Bridge
Install the signed and notarized Apple silicon (arm64) macOS 13+ application from securegitbridge.com. The current package and SHA-256 digest are published on the Release Verification page.
2. Verify your customer identity
Before the first AI connection, sign in to the customer account with the email you registered or purchased with and activate this Mac. Existing paid access is restored automatically; first-time users receive Free. No credit card is required for Free, and repository setup remains available before verification.
3. Approve a repository
Select the local Git repository you want to expose. Repository approval is explicit; Secure Git Bridge does not turn an AI assistant loose on the rest of the filesystem.
4. Apply repository security rules
Protected-file rules block sensitive files and paths before the AI can read them. Each repository keeps its own boundary and connection state.
5. Connect an AI provider once; bind repository access in SSGB
ChatGPT, Claude Desktop, GitHub Copilot, Cursor, and Gemini each connect through Secure Git Bridge without receiving broad workstation authority. Provider setup is separate from repository authority: the human binds, moves, or unbinds repository access in Secure Git Bridge. Multiple repositories remain isolated rather than becoming one broad filesystem authority.
6. Read safely; propose changes
The AI can inspect approved code through Secure Git Bridge and prepare patch proposals. It does not receive direct authority to apply those patches to Git merely because it generated them.
7. Human review stays in the loop
You inspect the proposed change locally and decide whether to apply or reject it. Security decisions and activity remain visible in the local Secure Git Bridge workflow.
What leaves the Mac?
Repository content is not sent to Secure Git Bridge's commercial licensing or billing control plane. Content approved for an AI interaction can be sent to the AI provider the customer chooses, subject to that provider's terms and privacy practices.