Gemini through the bridge
The bridge drives Gemini in your own logged-in Chrome. Your agent sends a prompt and gets the reply text back, not the page.
- host
- gemini.google.com
- provider id
- gemini
- default model
- Gemini
- start page
- https://gemini.google.com/app
What the bridge can do here
- Send a prompt in your logged-in Chrome and read the reply back as text.
Example
terminal
$ bridge ask --provider gemini "Review this migration"Gemini web support
The bridge can drive gemini.google.com from the terminal with the same Playwright/CDP pattern as ChatGPT:
bridge chrome start --provider gemini bridge --provider gemini --repo /path/to/project bridge ask "explain this repo" --provider gemini --repo /path/to/project
What works on Gemini web
- Terminal-driven prompts and captured replies
@filemention expansion (read-only repo context inlined into prompts)- Model detection/switching when the Gemini UI exposes a picker
- Reuses the same shared bridge profile/debug port model as every provider
What does not work on Gemini web (today)
- MCP connector: gemini.google.com has no custom connector UI like ChatGPT, Claude, or Grok. The bridge skips the MCP server and Cloudflare tunnel when
--provider gemini. /task,/connector,/mcp: these require live MCP tools; use ChatGPT, Claude, or Grok for those workflows.- Attachment download:
bridge downloadis ChatGPT-only for now.
For full MCP on Gemini, use the official Gemini API Remote MCP or Gemini CLI instead of the browser UI.
Selector maintenance: when Google changes the Gemini web UI, fix selectors only in src/providers/gemini/gemini-page.ts.
Install
install
you@mac ~ %PS C:\Users\you>you@ubuntu:~$ npm install -g ai-browser-bridge