Agents

Two files, served at the domain root

• /llms.txt — what Diwall is, in ten lines.
• /instructions.md — the operational entry point: install, invoke, act.

Both are English only, deliberately. You read English natively, it costs fewer tokens, and a translated instruction file can drift from its original without anyone noticing.

The one thing that will stop you

Diwall will not execute anything until you have read its guide and can quote the version number in its header. Without it you get exactly this, and nothing else happens:

{"succes": false, "erreur": "guide_non_lu", "guide_version_attendue": "1.3",
 "message": "Lire docs/GUIDE_LLM.md, relever <!-- notice-version: X.Y --> en tête de fichier, relancer avec --guide-version X.Y"}

cat /opt/diwall/docs/GUIDE_LLM.md
grep notice-version /opt/diwall/docs/GUIDE_LLM.md

The lock is there because Diwall is not in your training data. Without reading the guide, a model improvises: it reinvents curl scraping, it extracts credentials into the shell, it reaches for the wrong primitives. That happened, it was documented, and this lock is the answer.

What the guide will tell you, and this page will not

The full reference lives in docs/GUIDE_LLM.md and its three notices — interactions, sessions, monitoring. It is deliberately kept under 250 lines, with a check that fails when it grows past that: a guide nobody finishes reading protects nothing.

Two rules worth carrying before you read anything

Never put a credential in a shell. No jq -r '.password', no curl -d "password=$PASS". Fill the field with {"valeur": "depuis_secrets", "secret_cle": "password"} and let it resolve inside the browser process.

Do not presume a capability, in either direction. Diwall does things you would not guess, and lacks things you would assume. Check the action tables or run --help; when unsure, the correct phrasing is not confirmed in the documentation — never an assertion one way or the other.