connect-chrome

Launch real Chrome controlled by gstack with the Side Panel extension auto-loaded.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/deveshkumars/Intentra --skill connect-chrome
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connect-chrome
Source: https://github.com/deveshkumars/Intentra/tree/main/connect-chrome
Command: npx skills add https://github.com/deveshkumars/Intentra --skill connect-chrome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Launch real Chrome controlled by gstack with the Side Panel extension auto-loaded. You can watch every action in real time as Claude interacts with a visible browser.

Core Features & Use Cases

  • Real-time visibility of browser actions in a headed Chrome window with the Side Panel live feed.
  • Auto-loaded Side Panel extension for live activity tracking and command execution.
  • Quick setup and guided workflow to connect Claude to a visible browser for demonstrations.

Quick Start

Run the connect-chrome command to launch a real Chrome window controlled by gstack.

Frequently Asked Questions about connect-chrome

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

FAQPage Schema
How do I control a real Chrome browser with Claude for live debugging?

Control a real Chrome browser by launching a headed window with gstack and an auto-loaded Side Panel extension, providing real-time visibility of browser actions and a live activity feed for debugging.

What is the best way to watch browser automation actions in real time?

Watch browser automation actions in real time by running the connect-chrome command to launch a visible Chrome window, which displays a live activity feed directly within the Side Panel extension.

Can I use the Side Panel extension to track browser commands during a demo?

Yes, the Side Panel extension is auto-loaded specifically for live activity tracking and command execution, allowing you to monitor every browser action during guided demonstrations.

How do I set up a visible Chrome window for browser automation demonstrations?

Set up a visible Chrome window by coordinating the preflight setup and browser connection via gstack, which provides guided Side Panel access to enable seamless live browser demonstrations.

Does the connect-chrome workflow require any external dependencies?

No external dependencies are required for the connect-chrome workflow; it handles preflight setup, browser connection, and Side Panel access directly through the gstack scripts.

Why use a headed Chrome window instead of headless mode for QA testing?

Use a headed Chrome window to gain real-time visibility of browser actions and a live feed from the Side Panel, which is essential for interactive debugging and visual demonstrations that headless mode cannot provide.