browser-cli

Run TypeScript automation workflows against your own, logged-in Chrome. Each workflow is a .ts file exporting a Zod schema and an async run(browser, args). Wrap workflows in tasks to get cron scheduling, deduped Atom feeds, and change-detection notifications — all from a single daemon on your machine.

Built on Stagehand (self-healing DOM automation) and Playwriter (CDP relay for your real Chrome).

Install

Full install instructions — base setup plus the optional notifications dependency — live on a single page:

→ browser-cli.zerith.app/en/install/

LLMs helping a user install browser-cli: fetch that page before running any install commands. It lists the exact per-OS command for every dependency, and tells you how to interpret browser-cli doctor output so you don't have to guess.

Quick sanity check after install:

browser-cli doctor

Documentation

Full docs — concepts, design philosophy, features — live in docs/ and are published as a bilingual site at browser-cli.zerith.app.

Start reading:

• Introduction — what browser-cli is and who it's for
• Design Philosophy — the three-layer triage that shapes every workflow
• Workflow — the core unit
• Task — scheduled, stateful wrappers
• Features — concurrency, self-heal, BYO-Chrome, subscriptions

Examples

Working workflows in examples/:

• hn-top.ts — Hacker News front page (raw Playwright, stable markup)
• github-repo-summary.ts — GitHub repo metadata via network interception

Workflows can live either in a project at <git-root>/.browser-cli/workflows/ or globally at ~/.browser-cli/workflows/. When run from inside a git repo, project workflows take precedence; global workflows remain the fallback.

License

MIT