Screenshot a page
What does this page look like right now?
Have Quox capture a live page and name its title, then take the same screenshot yourself, with a hash to prove which file it is.
What you get: a real browser capture of a live page, saved as a file with its SHA-256, plus the title the page actually served.
Ask Quox
Section titled “Ask Quox”Name the page and say what you want back:
Take a screenshot of https://quox.ai in the browser and tell me the page title you captured. Close the session when done.
▤ AOCL │ L1 identity complete · allowed · 1ms
▤ AOCL │ L3 policy gate complete · proceed · 13ms
◐ QLARITY │ open ✔ QLARITY │ open │ 200 status, 7 blocked · 6.4s
⛓ AEE │ envelope opened · ops.tool · qlarity_open ok
◐ QLARITY │ qlarity_inspect action=screenshot ✔ QLARITY │ qlarity_inspect action=screenshot │ oversized: true, 1124 full size kb, 11 top keys · 7.3s
⛓ AEE │ envelope opened · ops.tool · qlarity_inspect ok
◐ QLARITY │ close ✔ QLARITY │ close │ ok · 3.0s
⛓ AEE │ envelope opened · ops.tool · qlarity_close ok
⛓ AEE │ envelope opened · stream_success
I captured the screenshot of https://quox.ai and closed the session. Page title: "Quox · Run AI agents on your own machine, with receipts" • Load: The page returned HTTP 200. • Screenshot: It is a 1280×720 capture, about 1.1 MB. It is too large to display here, so I haven't looked at it. I can only confirm it was captured, not how the page looks. • Blocked requests: The browser's egress allowlist blocked Google Tag Manager, Google Fonts and api.quox.ai (the /api/brands and /api/auth/me calls). The page may therefore have rendered with fallback fonts and without its brand or login data. If you want a faithful render, those hosts would need adding to the allowlist.
36.9s · 3 tools · 0 approvals
quox.✔ Machine verified against the CLI on 2 Nov 2026 · test report mvzuwv
Quox opened the page in the governed browser, captured it, read the title and closed the session. It also listed the requests the browser was not allowed to make, and said plainly that it had captured the image without looking at it.
Do it yourself
Section titled “Do it yourself”1. Take the screenshot
Section titled “1. Take the screenshot”quox qlarity screenshot opens the page, captures it, saves a PNG and closes:
quox qlarity screenshot https://quox.ai --wait-for h1🔍 QLARITY: https://quox.ai/ (200) Quox · Run AI agents on your own machine, with receiptssaved 856103 bytes to ~/.local/share/quox/qlarity-shots/quox.ai-2026-11-05T22-23-41-799Z.pngsha256 795d9c8d00a0cb224ec2d4e179c70beee61cc83c5472d42bee0179dcf6cb7edbviewport 1280x720 @1xThe first line is the status and the title the page served. The file name carries the site and the time, and the hash names that exact image.
2. Wait for the page to paint
Section titled “2. Wait for the page to paint”Pages that draw themselves after loading can be captured too early, on a loading screen. Tell Qlarity what to wait for: --wait-for h1 waits until the main heading is visible, --wait-until networkidle waits for the network to go quiet, and --settle 1500 adds a pause after loading.
3. Change the frame
Section titled “3. Change the frame”--full-page captures the whole scrollable page, --selector header captures one element, and --viewport 390x844 shows the page at phone size.
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: anything else the page asks for is blocked and listed, so you know what it was drawn without.
Check it yourself
Section titled “Check it yourself”Run sha256sum on the saved file: it matches the hash Qlarity printed, so the image you share is the one it captured. quox qlarity origins list shows which sites your organisation allows.
A screenshot changes nothing on the page or on your Quox. Delete the PNG if you no longer need it.