Install and uninstall quietly: no service, no root, no leftovers

20131 is local-first by construction, and that should show in how it lands on your machine — and how it leaves. This page states the footprint contract for each platform; the step-by-step guides are on the <a href="/en/docs/install/">install guide</a>, and the what-gets-recorded side is on <a href="/en/docs/agent-behavior-events/">the events page</a>.

What "quiet" means here, property by property

• No installer on Windows: unzip the .exe and run it — user-mode observation needs no admin rights
• No service, no scheduled task, no startup entry on any platform: the collector runs because you ran it
• No root: the Linux binary reads procfs in user mode; the macOS path is zero-privilege polling in the shipped build
• No network I/O from the collector: the audit surface stays on your machine; the dependency closure is machine-checked in CI
• Read-only control surface: status, audit-tail and timeline render what is already on disk

The one-script route and its stated safety properties

For macOS and Linux, install.sh does the download-and-verify dance with the rules published up front: it fetches exactly one release asset over HTTPS, verifies it against the release checksums before unpacking anything, refuses on a mismatch, never uses root, never installs services or scheduled tasks, and never pipes remote code into a shell. It is a plain-text file — reading it first is encouraged.

curl -fsSL https://20131.com/install -o install.sh
DRYRUN=1 bash install.sh                 # print the chosen URL, download nothing
bash install.sh                          # agent-collector into ./20131-install

On Windows the script stops by design and prints the zip link plus the SmartScreen path instead of trying to be clever.

Uninstall is deletion

• Linux: delete the binary and the audit log — nothing else was written to your system; the tar.gz itself carries a CHECKSUM.txt covering its own contents
• macOS: delete the binary and its log; the ad-hoc signature and the Gatekeeper "Open Anyway" exception concern launch approval, not persistent system state
• Windows: delete the folder — there is no installer database, no service to remove, no registry setup to unwind
• The audit log itself is owner-only readable and rotates by size and day; if you delete it, that is a choice, not a malfunction

Platform capability rows (including honest degradations) are defined in depth on <a href="/en/docs/supported-os-matrix/">the OS capability matrix</a>. Questions before you install: the <a href="/en/support/">support page</a> states what Early Access support means today.