Connect Gemini once. Control repository access in Secure Git Bridge.

1. Install Secure Git Bridge once

Add the Git repositories you want Secure Git Bridge to protect. Each repository keeps its own isolated helper, rotating broker capability, protected-file policy, audit chain, and patch proposal store.

2. Connect Gemini once

Open Gemini in Secure Git Bridge and choose Connect Gemini. Secure Git Bridge copies the one-time Gemini CLI user-scope MCP setup command and opens Terminal. Paste the command once. Secure Git Bridge does not execute the shell command and does not place repository credentials in it.

The provider connector contains no repository path, repository ID, or repository broker credential. Provider setup and repository authority are separate.

3. Bind Gemini to a repository in Secure Git Bridge

Select the approved repository in Secure Git Bridge and choose Bind to this repository. Secure Git Bridge creates the internal route only after that human action. Gemini cannot enumerate, choose, or switch repositories through its connector.

If you later choose Move, Secure Git Bridge closes the previous provider session and moves the same installed connector to the newly selected repository. No reinstall is required.

4. Work through the Secure Git Bridge tools

• Read only policy-permitted repository content.
• Protected files and path escapes remain blocked.
• Git status, log, and diff remain repository-scoped.
• The AI may create patch proposals for local review.
• There is no Secure Git Bridge shell, repository picker, approval, rejection, or Apply tool for the AI.

Apply remains human-only inside Secure Git Bridge.

The one-time Gemini command configures only Gemini's provider-router identity. Repository authority is added later inside Secure Git Bridge.

Disconnect without reinstalling

Unbind removes Gemini's repository route while leaving the provider connector configured. Disconnect This Repository revokes every AI route to that repository. Disconnect All AI Access revokes all repository routes. Provider connectors can remain installed and be rebound later.

What “Connected,” “Bound,” and “Active” mean

Connector ready means the one-time provider setup has been handed off and no repository authority is implied. Bound means Secure Git Bridge has authorized one repository route. Active is shown only after Secure Git Bridge sees a live provider MCP session.

Provider account and data flow

Your Gemini account, plan, usage, retention, and provider-side privacy terms remain with the provider. Repository content you intentionally authorize the AI to inspect can be transmitted to that provider through the normal AI interaction. Secure Git Bridge controls the local repository boundary and records access; it does not claim provider-side data handling.

Next steps

Download Secure Git Bridge Open the quick start

For the trust boundary and release model, see Security and How It Works.