Pagerunner vs agent-browser
agent-browser is well-built and fast-growing. The core difference: Pagerunner compounds knowledge across sessions. agent-browser resets every time.
Feature comparison
| Feature | Pagerunner | agent-browser |
|---|---|---|
| Site intelligence | Adapters, API discovery | Resets |
| PII anonymization | Local ONNX NER | None |
| Accessibility snapshots | DOM-based | Semantic locators |
| Annotated screenshots | Not available | Element refs overlay |
| Cloud mode | Local only | Remote sessions |
| Cloudflare tunneling | Not available | Expose local servers |
| Session checkpoints | Full state + scroll | Cookies/localStorage |
| Profile organization | Named, personal/agent | Flat --session-name |
| Encrypted state | AES-256-GCM | Auth Vault |
| Audit log | Built-in | None |
| Domain allowlisting | Per-profile | None |
| Token efficiency | Standard DOM | Accessibility snapshots |
| Price | Free (Apache-2.0) | Free |
Where Pagerunner wins
- Site intelligence compounds. Adapters and API discovery mean repeated visits to the same site get faster and more reliable.
- PII anonymization. Local NER ensures sensitive data never reaches any LLM, not even in transit.
- Encrypted state. AES-256-GCM encryption stored in your system Keychain, not a flat file.
- Audit log. Every action is logged for compliance and debugging.
- Domain allowlisting. Control exactly which sites each profile can access.
Where agent-browser wins
- Accessibility snapshots. Token-efficient page representation that can reduce LLM costs.
- Cloud mode. Supports remote browser sessions without local Chrome.
When to use which
Use Pagerunner when
Your workflows need to learn from repeated use, when privacy matters, or when you need security controls like domain allowlisting and audit logging.
Use agent-browser when
You need cloud execution, accessibility snapshots for token efficiency, or Cloudflare tunneling for local development.