Persistent by design
Cookies, localStorage and IndexedDB live in independent profile directories. Close the agent. Resume the session.
Persistent identities. Your proxies. Compact page context. Browser infrastructure built for agents that do real work.
Self-hosted · No GPU required · Your sessions stay on your server
# persistent session / p01 → navigate /register 200 · page ready → get_text interactive_only=true input:email "Email" [ref=s1e0] input:password "Password" [ref=s1e1] button "Register" [ref=s1e2] → fill_form data={ email, password } ok · 2 fields → run_scenario register · p02 ok · workflow replayed
Move from screenshots and fragile scripts to structured observations and reusable browser actions.
Cookies, localStorage and IndexedDB live in independent profile directories. Close the agent. Resume the session.
Bind each profile to a corporate or dedicated proxy. Local bridges handle SOCKS5 authentication without exposing credentials to the model.
Compact ARIA and interactive targets. Fill an entire form in one call. Ask for screenshots only when you need them.
Record parameterized workflows and run them across profiles. The model handles exceptions instead of rediscovering every field.
Streamable HTTP MCP, CLI and JS/Python clients. A single validated tool contract across every interface.
Audit outcomes, inspect errors and measure performance. Detection, solver tokens and site acceptance remain distinct states.
OpenCode or another tool-calling client sends a structured action.
Authenticated calls enter a bounded, per-session action queue.
A persistent Chromium context uses its assigned proxy bridge.
Return text, refs and outcomes. Keep heavy artifacts out of the prompt.
Structured actions are independent of the model vendor. Save repeated actions as a workflow and give the agent only the result.
// POST /v1/tools/fill_form { "session": "p01", "form_selector": "#register", "data": { "email": "[email protected]", "password": "${password}" }, "submit": false } // one compact response { "ok": true, "filled_fields": ["email", "password"], "unfilled_fields": [] }
Pentest2Bot is our Telegram entry point for security tooling and project updates. Follow development, discuss a use case, or talk to the team about integration.
The public repository contains the MIT specification, schemas and examples. The server implementation is distributed separately.
No. Detection, token solving and site acceptance are different operations. There is no universal bypass promise or fabricated success rate.
Yes, ordinary forms and JavaScript pages run in headless Chromium on CPU. Workload capacity depends on CPU, memory and the target applications.
The public specification and examples are MIT. The implementation is separate; its release licensing and distribution are being finalized.
Registry packages have not been released yet. Follow the official repository for verified installation instructions.