Guides

Two installation channels, and they are mutually exclusive on one machine: the package for your system if you intend to use Diwall, a Git clone if you intend to change it. Pick one.

sudo apt install ./diwall_1.24.4-1_all.deb   # Debian 13, Ubuntu 24.04, Ubuntu 26.04
sudo dnf install ./diwall-1.24.4-1.fc44.noarch.rpm   # Fedora 44
sudo zypper install --allow-unsigned-rpm ./diwall-1.24.4-1.leap160.noarch.rpm   # openSUSE Leap 16.0
sudo pacman -U ./diwall-1.24.4-1-any.pkg.tar.zst   # Arch Linux

The package creates the system user and installs six diwall-* commands and manual pages in four languages. During installation it builds an isolated Python environment and downloads its dependencies and Chromium, so network access is required at that moment. Debian 13, Ubuntu 24.04 and 26.04, Fedora 44, openSUSE Leap 16.0 and Arch Linux only; other systems are not supported, which is a statement about what has actually been tested rather than a matter of principle.

The one thing that will stop you

Diwall refuses to run for a model that cannot quote the version number of its own guide. Skip the flag and you get this, and nothing else happens:

{"succes": false, "erreur": "guide_non_lu"}

It is the only place where Diwall imposes something rather than offering it, and it exists because of a dated incident. On 3 July 2026, a model drove Diwall across several sessions without reading the guide and produced a string of errors the guide warns about explicitly — including an environment error described on its first page.

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_som", "id": 2, "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 capture on your own screen.

Already running it and want to automate something: Writing a scenario.

Something is broken rather than missing: you want Recipes instead — that section is organised by symptom.