Bridge to every model
Use Claude-only connectors, such as your claude.ai Gmail, from a Codex or Gemini chat: your own Claude does the task, read-only unless you allow actions.
Updated 2026-10-20
Bridge lets Codex or Gemini ask your own Claude on this computer to use a connector, then passes Claude's answer back to the chat. For example, Codex can ask Claude to summarize messages through your Claude account's Gmail connection.
Before you start
You need Claude Code, Claude's terminal app, installed and signed in with your Claude account on this computer. The connector must also work in Claude.
Bridge runs as your Claude account, uses your Claude plan and is slower than using a connector directly. Your Codex or Gemini conversation still uses its own AI connection as usual. See Connect an AI model for sign-in help.
You can bridge:
- Connectors linked to your Claude account.
- Servers set up through Claude Code.
You cannot bridge ChatGPT apps, Codex servers or Gemini servers and extensions with this feature. Claude in Chrome is also excluded: it controls your real browser, where clicking or typing can change something, so there is no safe read-only version for Bridge.
Read the action limit first
Bridge starts read-only and blocks actions it recognises as sending, creating, changing or deleting. Granular recognises these actions by their names, such as send, create, delete and similar words. An action with an unusual name might not be recognised.
Only bridge connectors you trust, and check what the agent did. Read-only is a safeguard, not a guarantee that an unfamiliar connector cannot make changes.
Turn on Bridge
- Open Settings.
- Open Connectors.
- Select This computer.
- Open the Claude connector you want to use.
- Make sure On for Claude is on.
- Under Bridge to every model, turn on Bridge.
- The first time, read Bridge this connector to every model? and click Turn on Bridge. Choose Not now to cancel.
The confirmation explains that Bridge uses your Claude account and plan, takes longer than a direct connection, and starts read-only. You only see this initial confirmation once, rather than for every connector.
In a Codex or Gemini chat, ask for a complete task, such as “Summarize my five most important unread emails.” One complete request usually makes more sense than many small requests because each Bridge task asks Claude to work separately.
Allow actions
Leave Allow actions (send, edit, delete) off if you only want to search and read.
To let Claude request permission for recognised actions:
- Open the connector's details with Bridge on.
- Turn on Allow actions (send, edit, delete).
- In Let bridged models take actions?, click Allow actions. Choose Keep read-only to cancel.
The mode reads Bridge on · actions need your OK. For each action Granular recognises as a change, the chat shows an approval card. Click Allow to approve that action or Decline to deny it. Settings calls this an Allow / Deny card.
The card names the action, but does not show all its details, such as a full email body or recipient list. Check those details before choosing Allow.
The name-based limit still applies with actions enabled: an unusually named action might not be recognised and might not show a permission card. Only use trusted connectors and review the result.
If the app is set read-only through another matching connection, Bridge stays read-only and its actions switch is unavailable. The strictest setting takes priority. See App permissions.
What you'll see
A bridged call appears as Bridge to Claude · Gmail, or the name of the app you used. The card shows Claude's current step and whether it completed.
Expand the card to see the request sent to Claude, its steps, short summaries of tool calls and results, and its answer. Some details are shortened or hidden to protect secrets, so this is not a full record of everything the app returned.
Claude's answer is then available to Codex or Gemini in the same conversation. You do not need to switch the chat's model to read it.
Change or turn off Bridge
Turn off Allow actions (send, edit, delete) to return the connector to read-only mode. Turn off Bridge to stop offering that connector through Claude to Codex and Gemini.
Keep On for Claude on if you still want Claude chats to use the connector directly. Turning that switch off also prevents Bridge from offering it.
These settings apply across your chats. Turning a switch off does not undo an action already taken.
If you used Gmail (via Claude)
Bridge replaces the older Gmail (via Claude) connector. When Granular finds Gmail in your Claude account's connectors, it removes the older connector. If the older connection was enabled when first moved over, Bridge is turned on for Gmail.
Open Gmail under This computer to check its Bridge settings. If Gmail has not been found yet, the older connector stays available. The controls described in this article belong to Bridge, so check that you are using the Gmail connector's Bridge settings.
Limits
- Bridge supports Codex and Gemini using Claude account connectors or Claude Code servers. It does not make every connection available to every model.
- Recognised changes are blocked in read-only mode or sent for approval with actions enabled. Unusual action names can escape that check.
- Bridge needs a working Claude sign-in and connector. Being signed in to Codex or Gemini is not enough.
- It uses your Claude plan and adds another AI request, so it takes longer than a direct connection.
- Two Claude accounts with the same connector currently share its Bridge and action switches. You cannot set those controls independently for each account.
- A Claude email shown with a connector identifies the Claude login, not necessarily the account inside the connected app.
- Turning Bridge off does not undo completed work. Check the connected app if a task stops partway through.
Troubleshooting
If you see Sign in to Claude to use the bridge
Sign in to Claude on this computer, then try again. Bridge needs your Claude account even when your main chat is using Codex or Gemini. See Connect an AI model.
If you see Sign in to this connector in Claude first.
For a Claude account connector, open claude.ai → Settings → Connectors and reconnect the app. For a server set up through Claude Code, open your session's Terminal tab, type claude mcp and press Enter to see its management options.
If you see an app needs signing in again in Claude
For example: Gmail needs signing in again in Claude (claude.ai → Settings → Connectors).
Reconnect it through the place it came from. Claude account connectors are managed on claude.ai under Settings → Connectors; Claude Code servers are managed through claude mcp in your session's Terminal tab. Then retry the task.
If you see Couldn’t start Claude on this computer. Is Claude Code installed?
Check that Claude Code is installed and can start on this computer. In your session's Terminal tab, type claude and press Enter. Complete its sign-in if asked, then retry Bridge.
If you see an app through Claude took too long
For example: Gmail through Claude took too long - try a smaller task.
Ask for a smaller task, such as summarizing fewer messages.
If you see Claude couldn’t reach the app right now
For example: Claude couldn’t reach Gmail right now (its connectors didn’t load). Try again in a moment.
Wait a moment and try again. If it keeps happening, check that the connector works in Claude and that its sign-in is current.
If you see Claude stopped early
The message reads Claude stopped early (exit …)., with an exit number or question mark in place of the dots.
Retry the task. If it keeps stopping, check Claude's sign-in and whether the connector works in Claude.
If you see Couldn’t set up action approvals, so nothing was run.
Retry after returning to the chat. Bridge did not start that task because it could not set up the approval step.
If you see that the connector is bridged read-only
The message reads Refused: this connector is bridged read-only. Writing, sending or deleting is switched off.
Leave it read-only for searches and reading. If you want it to request permission for changes, enable Allow actions (send, edit, delete). If the switch is unavailable because the app is read-only elsewhere, review App permissions.