Skip to content
quoxcli

Read what a page says

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.3.1, checked 2026-10-15.

What does this page actually show?

Have Quox open a page in the governed browser and read it, then run the same read yourself.

What you get: the exact text a live page shows, read by a real browser, not guessed from the page source.

Ask Quox

Section titled “Ask Quox”

Say which page and what you want from it:

quox · talking to Quox

Open quox.ai in the governed browser inspector and tell me the exact text of the page's main h1 heading. Close the browser session when you are done.

▤ AOCL │ L1 identity complete · allowed · 0ms

▤ AOCL │ L3 policy gate complete · proceed · 2ms

◐ QLARITY │ open ✔ QLARITY │ open │ 200 status, 7 blocked · 5.9s

◐ QLARITY │ qlarity_inspect action=dom ✔ QLARITY │ qlarity_inspect action=dom │ Put AI agents to work. Keep proof of everything. · 2.9s

◐ QLARITY │ close ✔ QLARITY │ close │ ok · 800ms

⛓ AEE │ envelope opened · stream_success

The main h1 on quox.ai reads exactly:

Put AI agents to work. Keep proof of everything.

The inspector's h1 read returned only this one heading, and the page title is "Quox ·
Put AI agents to work, and keep proof of everything". The browser session is closed.

The sandbox's allowlist blocked a few external requests during the load: Google Tag
Manager, Google Fonts and  api.quox.ai . That doesn't affect the heading text. It does
mean the page was rendered without its web fonts and without whatever data the  
api.quox.ai  calls would have loaded.

45.7s · 3 tools · 0 approvals

A real turn on our own install (CLI 0.3.0, 15 Oct 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 15 Oct 2026 · test report mv8xh6

Quox opened the page in the governed browser, read the main heading, and closed the session. It also said which requests the browser was not allowed to make, so you know what the page was rendered without.

Do it yourself

Section titled “Do it yourself”

1. Read one element

Section titled “1. Read one element”

quox qlarity read opens the page, runs one named inspector, prints the result and closes:

one read 
quox qlarity read https://quox.ai --inspector text_content --selector h1🔍 QLARITY: https://quox.ai/ (200) Quox · Put AI agents to work, and keep proof of everything text_content:"Put AI agents to work. Keep proof of everything." blocked by egress policy (11):https://www.googletagmanager.com/gtag/js -> not_in_allowlist:www.googletagmanager.comhttps://api.quox.ai/api/brands -> not_in_allowlist:api.quox.ai
From a real run on our own install, against quox.ai. Two of the blocked requests are shown, one shortened.

2. Pick another inspector

Section titled “2. Pick another inspector”

text_content is one of several. computed_style reads a style, count counts matches, attribute reads an attribute, and bounding_box gives an element’s size and place. quox qlarity inspectors lists them all.

What just happened

Section titled “What just happened”

The page was opened in a browser on your Quox, isolated per organisation, and closed afterwards. Only allowed sites load: everything else is blocked and listed, so a missing font or call is visible instead of silent.

Check it yourself

Section titled “Check it yourself”

quox qlarity origins list shows which sites your organisation allows. Adding one is an admin action: quox qlarity origins add <origin>.

Undo

Section titled “Undo”

A read changes nothing on the page or on your Quox, so there is nothing to undo.

Next

Section titled “Next”