install

Additional install commands

macOS

Homebrewverified · 100%

brew install chrome-cli

local Homebrew formula metadata

MacPortsverified · 94%

sudo port install chrome-cli

MacPorts ports tree · www/chrome-cli/Portfile · source: api.github.com

overview

Package summary

Control Google Chrome from the command-line

Project links

Commands and aliases

arc-cli
brave-cli
chrome-canary-cli
chrome-cli
chromium-cli
edge-cli
vivaldi-cli

history

Project history and usage

chrome-cli is a macOS command-line utility for controlling Google Chrome-compatible browsers through Apple's Scripting Bridge.

Project history

The GitHub repository was created in February 2014. The README describes chrome-cli as a native OS X/macOS binary for controlling Chrome-compatible browsers from the command line.

The early 1.1.0 tag dates to February 2014, with later releases continuing through 1.11.0 in September 2025.

Adoption history

Homebrew packages chrome-cli and installs companion wrapper commands for Chrome Canary, Chromium, Brave, Vivaldi, Edge, and Arc. The supplied package-manager facts also list MacPorts.

Homebrew's formula API reports stable version 1.11.0 and ongoing installs, while the README documents Homebrew as the installation path.

How it is used

The tool lists windows, tabs, and links; opens URLs; activates, closes, reloads, resizes, and positions browser windows; prints tab information or source; executes JavaScript; and can emit JSON output with `OUTPUT_FORMAT=json`.

For JavaScript execution and source viewing, the README documents the Chrome setting needed for JavaScript from Apple Events. Browser selection can be changed with the `CHROME_BUNDLE_IDENTIFIER` environment variable or the installed wrapper scripts.

Why package nerds care

chrome-cli is significant as a small macOS automation package that exposes Apple Events/Scripting Bridge browser control as ordinary shell commands. It is especially useful in scripts, launchers, tests, and tab-management workflows where a full browser automation framework would be excessive.

Timeline

2014: Repository created and early 1.1.0 tag appears.
2018: 1.6.0 release line reached.
2021: 1.7.x releases published.
2022: 1.8.0 release published.
2023: 1.9.x releases published.
2024: 1.10.0 release published.
2025: 1.11.0 release published; Homebrew stable version reports 1.11.0.

Related projects

Related browser targets include Chrome, Chrome Canary, Chromium, Brave, Vivaldi, Edge, and Arc. The README also points to Chromium's AppleScript documentation for enabling JavaScript execution through Apple Events.

Sources

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

narrow executable package without higher-risk signals

Signals

metadata:no-higher-risk-signals

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 6 platform targets.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

Command	Kind	Exposure
`arc-cli`	cli	global executable
`brave-cli`	cli	global executable
`chrome-canary-cli`	cli	global executable
`chrome-cli`	cli	global executable
`chromium-cli`	cli	global executable
`edge-cli`	cli	global executable
`vivaldi-cli`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08

manager version1.11.0

manager updated

local dataok

upstreamcurrent

latest detected1.11.0

https://github.com/prasmussen/chrome-cli

infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package key	brew:chrome-cli
Version	1.11.0
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/chrome-cli
Homepage	https://github.com/prasmussen/chrome-cli
Repository	https://github.com/prasmussen/chrome-cli
Upstream docs	https://github.com/prasmussen/chrome-cli#readme
License	MIT
Source archive	https://github.com/prasmussen/chrome-cli/archive/refs/tags/1.11.0.tar.gz
Bottle	available (on arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	chrome-cli
Version Scheme	0
Revision	0
Head Version	HEAD
Requirements	macos xcode
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

MacPorts95%

chrome-cli

sudo port install chrome-cli

normalized package name match
Matched by: Chrome Cli

MacPorts ports tree · api.github.com · MacPorts ports tree: www/chrome-cli/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/chrome-cli.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Install chrome-cli with Homebrew, MacPorts