Navigate and interact
Click, type, fill forms, select options, scroll. Element finding by description with DOM fallback strategies, not brittle selectors. Cookie banners are dismissed automatically on the objective path.
Act · Browser-Q · web automation
The web automation agent that learns.
Navigate, interact, extract and monitor, with vault-injected credentials and fallback element finding. Browser-Q does what you do in a browser, but autonomously.
Browser tools 49Price $10 / monthExtraction tools 6Fallback strategies 4
The animation below is a simulation of a typical run, not a live session. In real runs, navigation, login and cookie actions are logged and critical objective steps are witnessed on the chain.
Browser-Q · autonomous
In plain words
What it is, where it lives, when to reach for it
- What is it
- A web automation agent in the QuoxCORE dashboard that signs in, clicks, fills forms and downloads files for you.
- Where do I use it
- On the Browser-Q view in your dashboard, with every run listed under its Runs tab.
- When would I use it
- When a task means logging into a site, filling a form, or fetching a file again and again.
- How do I use it
- Open Browser-Q in the dashboard and type the task in plain language, or start from a suggested chip.
QuoxCORE is the free, self-hosted platform underneath this. What is QuoxCORE
The problem
Most of the systems you need to automate have no API.
Invoice portals. Government forms. Legacy ERPs. Vendor dashboards. Insurance claim systems. They all require a human clicking through a browser. You can wait for the API that will never come, or you can let Browser-Q do the clicking for you.
No API available
Browser-Q navigates the UI
Site redesigns break bots
DOM fallbacks find the element
Credentials exposed in scripts
Vault injects, the agent never sees
No audit trail
Logged steps, critical ones witnessed
How it runs
Anatomy of a governed session.
The simulation above shows the shape of a typical Browser-Q run. Five things happen, in order.
01You describe the outcome
“Fetch March’s invoice from the vendor portal.” No recording, no scripting, no selectors. Browser-Q plans the steps from your description and you approve the plan before it runs. The setup is the chat.
02The agent reads the page
Elements are found by description with DOM fallback strategies, not brittle selectors. On the objective path, cookie banners are dismissed automatically. Browser-Q keeps per-organisation site memory of login flows and quirks for return visits.
03The login is leased, not handed over
The credential is injected from the vault at runtime and the agent never sees it. Login approval can be enforced as an optional mode (by default the lease is advisory: it is logged and does not block), and MFA pause-and-resume is built in.
vault JIT injection · optional enforced approval · MFA pause-and-resume04The task completes under watch
A live view refreshes from screenshots about every 5 seconds, so you can follow what the agent is doing. You can Cancel a run from the automation wizard; it is a cancel, not an instant kill switch.
05The evidence outlives the session
Navigation, login and cookie actions are written to the audit log, screenshots are taken on screenshot steps, and critical objective steps are witnessed on the WARD chain. Screen video capture is available as an opt-in tool.
audit log · WARD witnessed critical steps · opt-in videoCore capabilities
Six core capabilities.
Everything you need to automate any website. No recording, no selectors, no scripts.
Act
Read
Extract data
Pull structured data from any page using schemas. Tables, lists, product catalogues, invoice line items. Export as JSON, CSV, or push directly into Action-Q.
Repeat
Record and replay
Save automation sequences and replay them later. When a selector breaks, the element finder tries fallback strategies before giving up.
Watch
Visual monitoring
Schedule visual diffs on any URL. When a page changes beyond your threshold, Browser-Q creates an alert with the diff.
Guard
Secure authentication
Vault-injected credentials. The agent never sees raw passwords. Login approval can be enforced per organisation. MFA pause-and-resume built in.
Prove
Session recording
Automations produce a step-by-step timeline, with screenshots on screenshot steps and opt-in video capture. Evidence for debugging failures.
When a selector breaks, the finder tries again.
Shipped today
49 browser tools, one governed agent.
This is the tool surface Browser-Q exposes inside QuoxCORE right now, straight from the agent registry. Not a roadmap: every group below is callable today.
navigate & capture 6 navigate · screenshot · click · type · wait · scroll extraction 6 extract · table · schema · template · links · metadata forms 4 fill form · select · find element · analyse forms files & audit 3 pdf · download · lighthouse tabs 3 new tab · switch · list auth & sessions 3 login · save cookies · restore cookies record & replay 7 record start/stop · replay · saved sequences ×4 video capture 4 start · stop · list · delete visual monitoring 4 create · list · check · delete objectives 9 create · plan · execute · run · approve step · cancel · list · get · save sequence
Counts taken from the Browser-Q entry in the QuoxCORE agent registry. Multi-step objectives include an approve-step action.
What makes it different
Seven capabilities, built on the platform.
Built on QuoxCORE platform intelligence: the memory, governance and evidence layers the rest of the platform already runs on.
01Site memoryPer-organisation, learned
Browser-Q keeps per-organisation site memory of login flows, navigation patterns and quirks, so return visits start with what it already learned.
02Live session viewerWatch the agent work
A live view that refreshes from screenshots about every 5 seconds. Cancel a run from the automation wizard when needed.
03Conversational setupNo recording, no scripting
Describe the outcome in plain language. Browser-Q plans the steps and you approve the plan before it runs. The setup is the chat.
04Step timelineSee what the run did
A step-by-step timeline of the run, with screenshots on screenshot steps. A page can also be saved as a PDF.
05Extraction templatesPre-built schemas
Common patterns ready to go: product catalogues, invoice line items, job listings, table data.
06Visual change detectionSpot page changes
Visual monitoring compares a page against its earlier capture and raises an alert with the diff when the change passes your threshold.
07Fallback element findingSelectors break. The finder tries again.
When a selector breaks, the finder tries a CSS selector, exact and partial text matches, then aria-label, placeholder and title attributes. Four fallback strategies before it gives up.
Security
Credentials stay in the vault.
Browser automation with credentials is a serious trust boundary. Credentials are vault-injected at runtime and never shown to the agent. Login approval can be enforced per organisation. Navigation, login and cookie actions are written to the audit log.
AOCL governedWARD witnessed
- Vault JIT injection. The agent never sees raw credentials.
- Login approval. An optional enforced mode per organisation. By default the lease is advisory: it is logged and does not block.
- AOCL governance. Configurable policies per action type.
- WARD witnessing. Critical objective steps get hash chain entries.
- Isolated context. Each run uses its own browser context.
- Cancel. Cancel a run from the automation wizard.
requestportal login needs acme-portal · lease requested, not the secret
hitlapproval requested · when enforced mode is on
leaselse_07c4 · scoped to this agent, this session
injectresolved server-side · the agent never sees it
sealcontext destroyed · lease revoked · witnessed on the chain
Use cases
Built for every team.
Browser-Q works wherever a human currently clicks through a web UI.
Operations
- Download invoices from vendor portals
- Data entry into legacy ERPs (SAP, Coupa)
- Government form filing: tax, compliance, licences
- HR onboarding across multiple web portals
DevOps
- Dashboard monitoring and screenshot capture
- Visual regression detection on deployments
- Certificate and DNS verification via web UIs
- Multi-cloud console operations (AWS, Hetzner, Cloudflare)
Sales and marketing
- Competitive pricing monitoring
- Lead enrichment from directories
- Review and brand monitoring
- SEO rank tracking and SERP analysis
Research
- Dataset collection and enrichment
- Market research across hundreds of sources
- Regulatory filing monitoring
- Academic paper and patent tracking
Pricing
One price. Everything included.
No tiers, no feature gates. Browser-Q is a QuoxCORE plugin billed monthly: install it from the store and every capability on this page is in the box, for as long as the subscription runs.
Browser-Q
$10 / month
No tiers. No feature gates.
- Navigate and interact
- Extract structured data
- Record and replay
- Visual monitoring
- Secure vault auth
- Session recording
- Site memory
- Fallback element finding
AssistantQ bundle
Not a SKU yet
The four-agent bundle has no store row today. Browser-Q is the one that ships, at $10 a month; the other three are listed here as the intended set, not as something you can buy.
- Action-Q ($5)
- Browser-Q ($10 a month)
- Calendar-Q ($19)
- Inbox-Q (see the store)
- All features included
- Shared vault credentials
- Unified evidence trail
Browser-Q runs inside QuoxCORE. Install the plugin from the store, describe what you want automated, and the agent handles the rest. Browse the store →
Where it stands
What's proven, what's still beta.
The animation above is simulated. This is what the product does and does not cover today.
Live and proven
- 49 browser tools across 10 groups are real and callable today, straight from the agent registry, not a roadmap
- Vault-injected login is a real Beta consumer of the credential-decrypt and lease-gate path: the agent never sees the raw password
- Element-level fallback finding is real: four fallback strategies, a CSS selector, then exact and partial text matches, then aria-label, placeholder and title attributes, run before a broken selector gives up
Beta and partial
- Vault-injected login (web_login) and the TOTP 2FA path are Beta, not Stable, per the platform vault status doc
- Any ScreenCap container still holding an old on-disk cookie file from before the encrypted session-state migration is a leftover until rebuilt; this has not been re-verified live
Known gaps
- Browser-Q is a step executor, not a browser agent: it runs a pre-planned list of steps in order, and there is no LLM watching the page after each step to decide what happens next
- Cookie banners are auto-dismissed on the objective path, and login success is checked; there is still no LLM watching the page after each step to decide what happens next, so the fallback finding covers locating an element, not reasoning about the page
- Browser-Q runs its own separate objective engine, not the tasks-service objectives engine the rest of QuoxCORE uses; a browser run does not show up on the main Objectives page
browser tools49loginsvault injectedevidenceaudit log + WARDprice$10 / month
Hands off the mouse
Stop clicking. Start automating.
Browser-Q runs inside QuoxCORE. Install the plugin, describe what you want automated, and let the agent handle the rest. Vault-injected credentials, an audit log and witnessed critical steps.
$10 a month · audit-logged · critical steps witnessed