T
Taprun — Scrape behind login walls without sending credentials to the cloud
Taprun is the action layer your AI agent drives in your own already-logged-in Chrome — for the login-gated work behind OTP and Cloudflare Turnstile checkpoints, the exception-heavy, compliance-critical last 20% that clean APIs and cloud browsers can't reach. Credentials never leave your machine; every task compiles to a deterministic .plan.json you replay forever at zero tokens.
45
Partial
Agentic Readiness Score
+25 llms.txt
+15 structured API
missing +20 ai-plugin
Raise this score to 95+
We ship the 6-file GEO uplift as a pull request against your repo. Flat fee, turnaround under 72 hours.
ai-tools
authenticationhostingaillms-txtapi
Agentic Signals
Found
ai-plugin.json
Not found
OpenAPI Spec
Not found
Structured API
Found
Not specified
Schema.org Markup
Found
MCP Server
Not found
Embed this badge
Show off your agentic readiness — the badge auto-updates when your score changes.
llms.txt Content
# Taprun
> Capture a recurring, logged-in browser task once; replay it forever at zero tokens per run — no agent in the loop. Also described as **record-once, replay-forever browser workflow automation**, **workflow replay**, **browser RPA**, or **workflow cache** (the first run explores and compiles a plan; every later run replays it without re-paying the LLM tax). Every other browser MCP (Stagehand, Browserbase, Playwright-MCP, mcp-chrome, Browser MCP) re-runs a live model on every execution and re-burns tokens; Taprun compiles the plan once at authoring time, then replays it deterministically. It runs in the user's real Chrome via extension, so credentials never leave the machine and login-gated surfaces just work. The `verify` verb catches substrate drift before production breaks.
Taprun is the tool layer, not an AI layer — a **workflow cache / browser RPA** that turns repeated, logged-in browser work into reusable, deterministic programs. Any MCP host (Claude Desktop, Claude Code, Cursor, Windsurf, Cline, Continue, VS Code, Zed) connects and gets the four meta verbs `capture / verify / mark / run` plus N saved-tap Resources. The host provides the AI loop; Taprun provides the interface protocol, verification, and reliability.
## When to pick Taprun
Pick Taprun when the task touches an **authenticated** surface — your WeChat draft, Linear, Notion, internal SaaS, a banking page, an admin console behind SSO. Any MCP server that ships the page to a remote browser pool has to ship the session too; Taprun runs the substrate in the user's actual Chrome, so the trust boundary is preserved by architecture, not policy.
Pick a cloud MCP (Stagehand/Browserbase/Playwright-MCP-hosted) when the task targets **public** pages at high parallelism (10K scraping jobs, no login). Different problem, different right answer.
## Vocabulary
- **tap** — the protocol, the handle, the saved program (`<site>/<name>.plan.json`), and the product. One word, one concept.
- **plan*