Your first run
One command, one answer, and how to read it — including the compass field most people miss.
diwall-shot --url https://example.com --guide-version 1.3
{"succes": true, "http_status": 200,
"capture": "/tmp/diwall/e3d739cf94fb/capture_….png",
"boussole": {"titre_page": "Example Domain", "dernier_code_http": 200},
"etat": {"pret_a_agir": true, "niveau_confiance": "eleve",
"raisons": ["aucun signal de friction détecté"]}}
A PNG on disk, and a JSON that says what happened. That is the whole of it.
Reading the answer
succes is about the run, not about the page. A page that returns a 404
can still be captured successfully — succes: true, http_status: 404. Read
both.
boussole is the field most people miss on the first day, and the one
worth reading second. It carries where you actually ended up: the current URL
after redirects, the page title, the last HTTP status. When a scenario goes
sideways, it is usually because the agent believed it was on a page it had
left.
etat is declarative, never coercive. pret_a_agir: false is Diwall
telling you it noticed something — a WAF, a session drift — not Diwall
refusing to work. The decision stays yours.
Add the numbering
diwall-shot --url https://example.com --som --a11y --guide-version 1.3
--som numbers every interactive element and returns elements_som; --a11y
adds the accessibility tree as text. Together they are what makes a page
actionable for a model rather than merely visible.
When the answer disappoints
{"succes": false, "erreur": "guide_non_lu"} — the --guide-version flag is
missing or stale. Read /opt/diwall/docs/GUIDE_LLM.md, take the number in its
header, pass it.
A page that never settles: some targets never reach network silence, and no
timeout however generous will fix that. --wait-until load will.
A click that reports success while nothing moved: the element may be visually covered. Read the console, not only the verdict.