internal/

Package browser holds the connection-layer logic for reaching Chrome over CDP: the DevToolsActivePort reader (Path B), the endpoint resolution, the vocabulary a probe answers in (WSState), and the connection-ladder decision.

Package chrome connects to Chrome over CDP (via chromedp) and exposes the Browser port the CLI commands drive.

Package chrometest provides a shared chrome.Browser test double.

Package cli builds chrome-cdp's cobra command tree and translates every command into the uniform result envelope + exit-code contract.

Package config loads optional persistent defaults from a TOML file and merges them with CHROME_CDP_* environment variables into the effective global-flag defaults.

Package daemon runs a background process that holds one CDP connection and serves Browser calls over a Unix socket.

Package encode turns captured frames into a shareable artifact: an animated GIF, a numbered PNG directory, or — when ffmpeg is on PATH — an MP4/WebM.

Package eventbuf provides the bounded, concurrency-safe ring buffers that retain the CDP events a held connection receives, per target.

Package mcp serves chrome-cdp's verbs to Model Context Protocol clients over stdio (RFC-0004).

Package policy bounds what chrome-cdp may drive: which origins it will act on, which verbs are permitted there, and which local paths may be uploaded.

Package probetest builds the stub debug endpoints that RFC-0013's tests run against: a port that accepts and stalls, one that completes the WebSocket upgrade (now or later), and one with nothing listening at all.

Package recipe loads, validates, and resolves recipes: saved `session` scripts with a small header.

Package result defines chrome-cdp's uniform output envelope and the stable exit-code contract that both humans and the Claude skill depend on.

Package state persists the sticky "current target" across CLI invocations, keyed per browser endpoint, under $XDG_STATE_HOME.

Package target resolves a <target> spec against the live set of Chrome tabs.