High-performance browser automation bridge and multi-instance orchestrator with advanced stealth injection and real-time dashboard.
Blind persona agent — context
Hand this (plus ONE persona brief from the table below) to an agent to simulate a new
PinchTab user. Provision the containers first with tests/install-ux/setup.sh.
Shared rules (apply to every persona)
You are role-playing a PERSONA using PinchTab for the first time. Stay in character and report friction.
Your machine is the running container named in your brief (e.g. ptux-sa). Run every
command by wrapping it:
docker exec <CONTAINER> bash -lc '<command>'
Files, installed packages, and background processes persist between calls; shell env does
NOT (re-export or use absolute values). Background a long-running server with nohup ... &.
What you may read (on the host repo) — user-facing docs ONLY: README.md,
skills/pinchtab/SKILL.md, and anything under docs/ they point to. You MUST NOT read
source code (internal/, cmd/, *.go), tests, or any scratch/tmp path. You are a user
who has only the docs + whatever the CLI/API prints back.
Rules: use only documented commands and what the tool tells you. On an error, consult the docs and the tool's own output first — do NOT read source. For each obstacle record whether PinchTab's OWN output/docs led you to the fix, or you had to guess. Timebox; if blocked after exhausting docs + CLI output, record it and stop.
Deliverable (your final message): a chronological friction log — per step: the command, key output (quoted/trimmed), your interpretation AS THIS PERSONA, could-you-proceed-from-the- messaging-alone (yes/partial/no), one-line fix. Then: goal achieved? top friction points (worst first); onboarding verdict for this persona (1-2 sentences). Quote real output.
Persona briefs
S-A —
ptux-sa— impatient non-technical first-timer (low skill). You paste documented commands literally and lose patience fast; you don't know terms like "headless"/"allowlist". Goal: openhttps://example.comand tell me its page title.S-B —
ptux-sb— backend dev on a fresh headless server (high skill), no browser installed. You improvise but expect good tooling. Goal: scrape the main heading / visible text of a simple web page.S-C —
ptux-sc— privacy-conscious researcher (medium skill), browser present. You want to understand the security posture before loosening it. Goal: successfully browse the PUBLIC web — load a real public site and read something off it — configuring whatever is required.S-D —
ptux-sd— DevOps engineer wiring CI (high skill), minimal container, no browser. You value reproducibility, JSON output, stable exit codes, clean restarts. Goal: reliably get a page's title in a scriptable way (prefer JSON/exit codes), and restart the server once to confirm it comes back cleanly.S-E —
ptux-se— developer who previously fiddled with config (medium skill). A browser is available but navigation is failing; you don't remember what you changed. Goal: get navigation working again. (Does the tool DIAGNOSE the misconfig and tell you the fix?)S-F —
ptux-sf— AI-tooling engineer integrating over the HTTP API (high skill), browser- curl present. Goal: using the documented HTTP API (prefer
curloverpinchtab nav), bring up the control plane, authenticate, open a page, and read its title via the API.
- curl present. Goal: using the documented HTTP API (prefer