connect-chrome

Launch and control a real Chrome instance with real-time Side Panel visibility.

1|2|Updated Jan 4, 2024
One-click install
npx skills add https://github.com/NaKMiers/Port4lio --skill connect-chrome-nakmiers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connect-chrome
Source: https://github.com/NaKMiers/Port4lio/tree/main/.agents/skills/connect-chrome
Command: npx skills add https://github.com/NaKMiers/Port4lio --skill connect-chrome-nakmiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connect Codex to a real Chrome window, exposing every action in real time through the Side Panel extension.

Core Features & Use Cases

  • Launch a real Chrome window with the gstack extension auto-loaded.
  • Observe every click, navigation, and action in real time via the Side Panel feed.
  • Use for live demos, debugging browser interactions, and end-to-end automation workflows.

Quick Start

Run the preflight cleanup, then execute the connect step to launch Chrome and verify the Side Panel is visible.

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 instance for live debugging and automation?

You can control a real Chrome instance for live debugging by connecting Codex to launch a browser with the gstack extension, exposing every click and navigation in real time through a Side Panel feed for observation.

Can I observe browser interactions in real time during end-to-end automation?

Yes, observing browser interactions in real time during end-to-end automation is possible by launching Chrome with the gstack extension auto-loaded, which surfaces every action through the Side Panel feed as it happens.

What do I need to launch Chrome from Codex with the gstack extension?

To launch Chrome from Codex you need the gstack browser setup installed, bun available for installation, and all preflight checks to pass before executing the connect step to verify the Side Panel is visible.

How do I set up a live demo of browser automation using Chrome?

To set up a live demo of browser automation, run the preflight cleanup step first, then execute the connect step to launch a real Chrome window with the gstack extension loaded and verify the Side Panel is visible.

Does this Chrome automation approach work without headless mode for demonstrations?

Yes, this approach launches a real, visible Chrome window rather than a headless instance, making it suitable for live demonstrations where you need to visually debug browser interactions and end-to-end workflows.