Guides
Install it, run it, launch a research campaign, write your own scenarios, set up the encrypted directory. Everything here is a command you can type.
Two installation channels: the .deb package to use Dinoer as-is, a Git
clone if you intend to modify it. See Install for both,
in detail.
The one thing that will stop you
Dinoer refuses to run for a model that cannot quote the version number of its own guide. Skip the flag and you get this — real output, from a real run:
{"succes": false, "erreur": "guide_non_lu", "guide_version_attendue": "1.6"}
It is the only place where Dinoer imposes something rather than offering it, and it exists because of a documented incident in the project this one forked from: a model drove the tool across several sessions without reading its guide and produced a string of errors the guide warns about explicitly.
The lock is cooperative by design: it makes skipping the guide a deliberate act rather than an accident. It does not stop someone determined to deceive it.
Credentials never pass through your shell
The pattern below is not a convenience — it is the reason the encrypted directory exists.
{"type": "remplir", "selecteur": "input[name=\"password\"]",
"valeur": "depuis_secrets", "secret_cle": "password"}
Where passwords live, and the one mistake that writes them in clear text →
Where to start
Never run it before: Install, then First run. That pair takes a few minutes and ends with a real, readable answer from your own machine.
Have a research question, not a single page: Running a research campaign is the guide to read next.
Already running it and want to automate a multi-step task: Writing a scenario.
Something is broken rather than missing: you want Recipes instead — that section is organised by symptom.