pinchtab

High-performance browser automation bridge and multi-instance orchestrator with advanced stealth injection and real-time dashboard.

Runssource: GitHubGoMITcommit 83666d227100

Go, MIT licensed. The project labels itself: browser automation, cdp, golang, headless chrome, orchestrator, stealth and web scraping.

pinchtab runs. An Argusic agent installed it in 11 minutes and hit 6 errors on a clean machine with no GPU, and the whole session was recorded.

A source-built PinchTab server (binary reports pinchtab dev) is running on 127.0.0.1:9867 with a responsive always-on headless instance and answered authenticated health, navigate, snapshot, text, title, and screenshot API calls with HTTP 200, while the full Go unit suite (9166 passed, 18 skipped) and scripts/check.sh pass;

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 94.3 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
94.3 / 100
cost of the verifying run
$0.25 (measured)
recorded runs
2
last tested
stars
10,585
forks
789
open issues
21
watchers
38
size
39 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing pinchtab, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Dashboard vite build fails typecheck in src/components/molecules/TabsChart.tsx against [email protected] (TooltipContentProps assignment, TS2322)3 minutes
  • No Go toolchain in container2 minutes
  • No Chrome/Chromium browser in container2 minutes
  • ./dev doctor could not find golangci-lint; scripts/doctor.sh and scripts/check.sh only probed PATH and $GOPATH/bin though doctor installs into .tools/bin2 minutes
  • npm global install into /usr/local failed with EACCES (rootless container)1 minute
  • internal/activity TestQuerySourcesNarrowsFileWalkAndSkipsUnrequestedSource failed: hard-coded 2026-09-12 event date fell outside the 7-day retention window on 2026-11-04, so its own data was pruned1 minute
Install time
11 minutes
Cold machine to finish
19 minutes
Errors hit and fixed
6 hit, 5 fixed with no human help
How the result was proved
curl -sS -H 'Authorization: Bearer <token>' http://127.0.0.1:9867/health returned 200 with status ok and defaultInstance running/responsive; POST /navigate to http://127.0.0.1:18080/index.html returned 200 with title PinchTab Benchmark - Home; /snapshot, /text, /title returned 200; /screenshot returned 200 and decoded base64 JPEG passed 'ffmpeg -v error -i FILE -f null -' (1280x720); go test -count=1 ./... exited 0 (9166 pass, 18 skip)
Model tokens used
738,388
Exact commit tested
83666d227100
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- Dashboard build type error in `TabsChart.tsx` with `[email protected]` — not fixed — 3 minutes.
**Report**
exec
/usr/bin/bash -c "cat <<'EOF'
EOF" in /work/repo
 succeeded in 0ms:
Done. One line as requested:
2026-11-04T14:39:17.182543Z ERROR codex_core::session: failed to record rollout items: thread 01a1a…
2026-11-04T14:39:17.182718Z ERROR codex_core::session: failed to record rollout items: thread 01a1a…
tokens used
738,388
Done. One line as requested:

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 11 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.
  • Hit 6 errors during setup, 1 of which were not solved.

Of the 13 browser-automation projects Argusic has installed and timed, pinchtab was the 9th fastest to reach a running state, and 12 of 13 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs96.670.25
Argusic Runner1/3Runs with mocks92.000.27

Topics (from GitHub)

browser-automationcdpgolangheadless-chromeorchestratorstealthweb-scraping

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/pinchtab.svg)](https://argusic.com/subject/pinchtab)

Questions

Does pinchtab run?
Yes. pinchtab runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test pinchtab?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 83666d227100. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test pinchtab?
The run that produced this verdict cost $0.25: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does pinchtab take to install?
11 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does pinchtab need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing pinchtab?
6 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does pinchtab compare with the alternatives?
Of the 13 browser-automation projects Argusic has installed and timed, pinchtab was the 9th fastest to reach a running state, and 12 of 13 reached one at all.
Where is the evidence for pinchtab?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion