codex-chrome-linux

Bridge Linux Chrome to Codex for programmatic inspection, navigation, and control.

6|Updated Jul 9, 2019
One-click install
npx skills add https://github.com/sluongng/dotfiles --skill codex-chrome-linux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-chrome-linux
Source: https://github.com/sluongng/dotfiles/tree/main/config/codex/skills/codex-chrome-linux
Command: npx skills add https://github.com/sluongng/dotfiles --skill codex-chrome-linux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Inspect, instrument, and control Linux Google Chrome through the local Codex Chrome Extension native messaging bridge.

Core Features & Use Cases

  • Inspect and navigate Chrome tabs, history, and state via the native bridge.
  • Execute Chrome DevTools Protocol commands through the native host to automate browser workflows on Linux.
  • Troubleshoot the Chrome native messaging manifest and socket connections when debugging browser integrations on Linux.

Quick Start

Install and run the codex-linux-extension-host to connect to Chrome and begin browser control.

Frequently Asked Questions about codex-chrome-linux

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

FAQPage Schema
How do I control Chrome on Linux through a native messaging bridge?

You can control Linux Chrome by using a native messaging host that bridges Chrome to Codex, enabling programmatic inspection, navigation, and execution of DevTools Protocol commands via JSON-RPC.

How does the Chrome DevTools Protocol integrate with Linux Chrome for browser automation?

The Chrome DevTools Protocol integrates by routing commands through the local Codex Chrome Extension native messaging bridge, allowing you to automate browser workflows and manage tab states using JSON-RPC communication.

Can I execute Chrome DevTools Protocol commands to inspect tabs on Linux?

Yes, you can execute Chrome DevTools Protocol commands to inspect and navigate Chrome tabs, history, and state by connecting through the codex-linux-extension-host native bridge on Linux.

Do I need a specific extension host to automate browser workflows on Linux?

Yes, you need to install and run the codex-linux-extension-host to establish the native messaging connection with Chrome and begin programmatic browser control on Linux.

What is the best way to troubleshoot native messaging manifest issues with Linux Chrome?

To troubleshoot native messaging manifest and socket connection issues with Linux Chrome, use the native bridge to debug the browser integration and verify the fixed manifest configuration.

Why is my native messaging socket connection not working with Chrome on Linux?

Native messaging socket connections fail when the fixed manifest is misconfigured or the codex-linux-extension-host is not running, requiring you to debug the browser integration and verify the host setup.