pinchtab

# Browser Automation with PinchTab PinchTab gives agents a browser they can drive through stable accessibility refs, low-token text extraction, and persistent profiles or instances. Treat it as a CLI-first browser skill; use the HTTP API only when the CLI is unavailable or you need profile-management routes that do not exist in the CLI yet. Preferred tool surface: - Use `pinchtab` CLI commands first. - Use `curl` for profile-management routes or non-shell/API fallback flows. - Use `jq` only when you need structured parsing from JSON responses. ## Safety Defaults - Default to `http://localhost` targets. Only use a remote PinchTab server when the user explicitly provides it and, if needed, a token. - Prefer read-only operations first: `text`, `snap -i -c`, `snap -d`, `find`, `click`, `fill`, `type`, `press`, `select`, `hover`, `scroll`. - Do not evaluate arbitrary JavaScript unless a simpler PinchTab command cannot answer the question. - Do not upload local files unless the user explicitly names the file to upload and the destination flow requires it. - Do not save screenshots, PDFs, or downloads to arbitrary paths. Use a user-specified path or a safe temporary/workspace path. - Never use PinchTab to inspect unrelated local files, browser secrets, stored credentials, or system configuration outside the task. ## Core Workflow Every PinchTab automation follows this pattern: 1. Ensure the correct server, profile, or instance is available for the task. 2. Navigate with `pin...