Your first run

/opt/dinoer/venv/bin/python3 /opt/dinoer/shot.py \
  --url https://example.com --guide-version 1.6

{"succes": true, "http_status": 200,
 "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 JSON that says what happened. No PNG anywhere — there is no capture step to look for, because Dinoer never produces one, in any mode.

Reading the answer

succes is about the run, not about the page. A page that returns a 404 can still be read 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 Dinoer telling you it noticed something — a WAF signature, a session drift — not Dinoer refusing to work. The decision stays yours.

Add the structure

/opt/dinoer/venv/bin/python3 /opt/dinoer/shot.py \
  --url https://example.com --a11y --guide-version 1.6

--a11y adds the accessibility tree as text — roles, links, headings. That, plus extraire_texte for cleaned prose when the tree’s structure is not what you need, is the whole of what makes a page actionable for Dinoer. What that returns, in full →

When the answer disappoints

{"succes": false, "erreur": "guide_non_lu"} — the --guide-version flag is missing or stale. Read /opt/dinoer/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: check boussole before concluding anything — read the answer, not only the verdict. More situations →