automating-chrome
Automates Google Chrome and Chromium-based browsers via JXA with AppleScript dictionary discovery. Use when asked to "automate Chrome tabs", "control browser with JXA", "Chrome AppleScript automation", "Chromium browser scripting", or "browser tab management". Covers windows, tabs, execute(), tunneling patterns, and permissions.
What this skill does
# Automating Chrome / Chromium Browsers (JXA-first, AppleScript discovery)
## Technology Status
JXA/AppleScript browser automation is legacy. JavaScript injection is disabled by default in modern Chrome. Modern alternatives: Selenium/ChromeDriver, Puppeteer, PyXA.
**Related Skills**: `web-browser-automation`, `automating-mac-apps`
**PyXA Installation:** See `automating-mac-apps` skill (PyXA Installation section).
## Contents
- [Scope](#scope)
- [Core framing](#core-framing)
- [Workflow (default)](#workflow-default)
- [Quick Examples](#quick-examples)
- [Modern Alternatives](#modern-alternatives)
- [What to load](#what-to-load)
## Scope
- Primary target: Google Chrome (bundle ID: com.google.Chrome).
- Chromium-based variants (Brave: com.brave.Browser, Edge: com.microsoft.edgemac, Arc: company.thebrowser.Browser) often expose similar dictionaries but may differ by bundle name and permissions.
- Always verify dictionary availability in Script Editor for target browser before automation.
**Security Note**: JavaScript injection via AppleScript is disabled by default in Chrome. Enable via: View → Developer → Allow JavaScript from Apple Events (not recommended for production use).
## Core framing
- AppleScript dictionaries define the automation surface.
- JXA provides logic and data handling.
- `execute()` runs JavaScript in page context but doesn't reliably return values—use tunneling patterns (save to clipboard/localStorage) for data extraction instead.
**⚠️ Security Warning**: The tunneling approach (clipboard/localStorage) can expose sensitive data. Use modern APIs for production automation.
- **Tunneling Patterns Explained:** Since `execute()` doesn't return JavaScript results directly, work around this by having your injected script save data to accessible locations like the system clipboard (`navigator.clipboard.writeText()`) or localStorage (`localStorage.setItem()`). Then retrieve the data in your JXA script using system commands or by reading back from localStorage via another `execute()` call.
## Workflow (default)
1) Discover dictionary terms in Script Editor (Chrome or target browser).
2) Prototype minimal AppleScript commands in target browser.
3) Port to JXA and add defensive checks:
- Wrap operations in try/catch blocks
- Check browser process status: `chrome.running()`
- Verify window/tab indices exist before access
- Handle permission dialogs programmatically when possible
4) Use batch URL reads and reverse-order deletes for tab operations.
5) Use tunneling patterns for DOM data extraction.
6) Validate results: Log tab counts, URLs, or extracted data to confirm operations succeeded.
## Quick Examples
**Open new tab and navigate:**
```javascript
const chrome = Application('Google Chrome');
chrome.windows[0].tabs.push(chrome.Tab());
chrome.windows[0].tabs[chrome.windows[0].tabs.length - 1].url = 'https://example.com';
```
**Execute JavaScript in current tab:**
```javascript
const result = chrome.execute({javascript: 'document.title'});
// Note: execute() runs JS but doesn't reliably return values
```
**Batch close tabs (reverse order):**
```javascript
const tabs = chrome.windows[0].tabs;
for (let i = tabs.length - 1; i >= 0; i--) {
if (tabs[i].url().includes('unwanted')) {
tabs[i].close();
}
}
```
**Extract page data via tunneling:**
```javascript
// Inject script to save title to localStorage
chrome.execute({javascript: 'localStorage.setItem("pageTitle", document.title)'});
// Retrieve via another execute call
chrome.execute({javascript: 'console.log(localStorage.getItem("pageTitle"))'});
```
**Check browser permissions:**
```javascript
try {
const chrome = Application('Google Chrome');
chrome.windows[0].tabs[0].url(); // Test access
console.log('Permissions OK');
} catch (error) {
console.log('Permission error:', error.message);
}
```
## Modern Alternatives
For production Chrome automation, see the `web-browser-automation` skill for comprehensive guides covering:
- **PyXA**: macOS-native Chrome automation with full integration
- **Selenium**: Cross-platform automation with automatic ChromeDriver management
- **Puppeteer**: Node.js automation with bundled Chrome
- **Multi-browser workflows**: Chrome, Edge, Brave, and Arc coordination
**Quick PyXA Example** (see web-browser-automation skill for details):
```python
import PyXA
# Launch Chrome and navigate
chrome = PyXA.Application("Google Chrome")
chrome.activate()
chrome.open_location("https://example.com")
# Get current tab info
current_tab = chrome.current_tab()
print(f"Page title: {current_tab.title()}")
print(f"Current URL: {current_tab.url()}")
```
### PyObjC with Selenium (Cross-Platform with macOS Integration)
```python
from selenium import webdriver
from selenium.webdriver.chrome.options import Options
from AppKit import NSWorkspace
# Configure Chrome options
options = Options()
options.add_argument("--remote-debugging-port=9222")
options.add_argument('--headless=new') # Modern headless mode
# Launch Chrome with Selenium (automatic ChromeDriver management)
driver = webdriver.Chrome(options=options)
driver.get('https://example.com')
# macOS integration via PyObjC
workspace = NSWorkspace.sharedWorkspace()
frontmost_app = workspace.frontmostApplication()
print(f"Frontmost app: {frontmost_app.localizedName()}")
print(f"Page title: {driver.title}")
driver.quit()
```
### Selenium with ChromeDriver (Recommended for Cross-Platform)
```bash
# Install Selenium (latest: 4.38.0)
pip install selenium
# ChromeDriver is automatically managed by Selenium Manager (v4.11+)
# No manual download needed - compatible version downloaded automatically
# Basic Python example
from selenium import webdriver
driver = webdriver.Chrome() # Automatic ChromeDriver management
driver.get('https://example.com')
print(driver.title)
driver.quit()
```
**Advanced Configuration:**
```python
from selenium.webdriver.chrome.options import Options
options = Options()
options.add_argument('--headless=new') # Modern headless mode (required)
options.add_argument('--no-sandbox')
options.add_argument('--disable-dev-shm-usage')
driver = webdriver.Chrome(options=options)
driver.get('https://example.com')
print(f"Page title: {driver.title}")
driver.quit()
```
**Manual ChromeDriver Setup (for specific versions):**
```python
from selenium.webdriver.chrome.service import Service
from selenium.webdriver.chrome.options import Options
# Download from https://googlechromelabs.github.io/chromedriver/
# Match major version with your Chrome installation
service = Service(executable_path='/path/to/chromedriver')
options = Options()
driver = webdriver.Chrome(service=service, options=options)
```
**Note**: Selenium 4.11+ automatically downloads compatible ChromeDriver. Manual setup only needed for specific version requirements or CI/CD environments.
### Puppeteer (Recommended for Node.js)
```bash
# Install Puppeteer (latest: 24.35.0)
npm install puppeteer
# Bundles compatible Chrome automatically
```
```javascript
const puppeteer = require('puppeteer');
(async () => {
const browser = await puppeteer.launch({
headless: 'new' // Modern headless mode (required in v24+)
});
const page = await browser.newPage();
await page.goto('https://example.com');
const title = await page.title();
console.log(title);
await browser.close();
})();
```
**Advanced Puppeteer Configuration:**
```javascript
const puppeteer = require('puppeteer');
(async () => {
const browser = await puppeteer.launch({
headless: 'new',
args: ['--no-sandbox', '--disable-dev-shm-usage']
});
const page = await browser.newPage();
// Set viewport
await page.setViewport({ width: 1280, height: 720 });
await page.goto('https://example.com');
// Wait for element and interact
await page.waitForSelector('h1');
const title = await page.title();
console.log(`Page title: ${title}`);
await browser.close();
})();
```
### Chrome DevTools Protocol (Advanced)
```javascript
// WebSRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.