gemini-research-browser-use

Automate Gemini web queries via Chrome DevTools Protocol.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/tkmh04/CoffeeHouse-Management-System --skill gemini-research-browser-use
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gemini-research-browser-use
Source: https://github.com/tkmh04/CoffeeHouse-Management-System/tree/main/.agents/skills/gemini-research-browser-use
Command: npx skills add https://github.com/tkmh04/CoffeeHouse-Management-System --skill gemini-research-browser-use

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow enables AI to research or ask Gemini by driving the Gemini web UI through the Chrome DevTools Protocol, leveraging the user's active Chrome session to bypass API limits and maintain authentication.

Core Features & Use Cases

  • Drive the Gemini web interface via the Chrome DevTools Protocol to input queries, submit, and read responses.
  • Automate repeated Gemini research tasks while preserving login state and session data.
  • Use cases include rapid literature-style queries, data checks, or complex reasoning tasks wired to Gemini's UI.

Quick Start

Launch Chrome with remote debugging enabled on port 9222 using a non-default profile, open https://gemini.google.com/, ensure you are logged in, and run the provided script to send a query.

Frequently Asked Questions about gemini-research-browser-use

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Gemini web research using Chrome DevTools Protocol?

Automating Gemini web research via Chrome DevTools Protocol involves driving the Gemini web UI through a live remote-debugging-port to input queries, trigger submission, and extract responses. This requires Python with websockets and a cloned user-data-dir.

Can I bypass Gemini API limits by automating the web interface?

Yes, you can bypass API limits by driving the Gemini web interface through the Chrome DevTools Protocol. This leverages your active Chrome session and authentication state instead of making direct API calls.

What do I need to set up Chrome remote debugging for browser automation?

Chrome remote debugging requires launching Chrome with a non-default user profile, a live remote-debugging-port like 9222, and a cloned user-data-dir. You also need Python with websockets installed to execute the automation script.

How does a Python script extract Gemini responses through Chrome CDP?

A Python script uses the websockets library to connect to the Chrome DevTools Protocol remote-debugging-port, drives the Gemini web UI to input queries, waits for submission, and reads the extracted response text from the page DOM.

Why does Gemini browser automation require a non-default Chrome profile?

Gemini browser automation requires a non-default Chrome profile because remote debugging needs a cloned user-data-dir to establish a separate active session. This isolates the automation process while preserving your login state and session data.