Every version, and what it changed for you.

Archis installs on older Linux again, and the site can say what it has saved.

Before you upgrade — On Linux, if 0.34.0 would not start: curl -fsSL https://archis.dev/install.sh | sh.

• NewPi is a supported agent, and the first one Archis reaches without the tool protocol, because Pi does not speak it: Archis arrives as the standing instructions Pi reads and the on-disk skill it loads on demand, and chi agents on pi writes both. chi agents now lists agents reached that way, so one Archis supports but cannot hand tools to is visible rather than missing from the command that answers whether Archis is connected.
• NewThe site now publishes how far Archis reaches and what it has saved, from the statistics opted-in installations already send. Every figure is a floor, not an estimate: measurements travel as ranges so no single installation is identifiable from them, and adding the bottom of each range understates by construction. Nothing new is collected from your machine for this.
• ImprovedThe server that answers your agent now reports the same anonymous statistics the CLI already did, having reported nothing before — so the sessions where Archis does its work were the ones nothing was recorded about. It covers the licence check, one roll-up of what the session read and saved, and a summary when the agent disconnects. chi telemetry preview shows the exact payload and chi telemetry off stops it, and an installation that has never signed in still collects nothing.
• FixedArchis installs and runs on older Linux distributions again. The 0.34.0 Linux builds were compiled against a newer system C library than most machines carry, so on Ubuntu 20.04, Debian 11 and anything of that vintage the install completed and the binary then would not start at all — and the installer's own guess, "wrong architecture?", pointed at the one thing that was correct. Both Linux builds now target a floor of glibc 2.28, which covers every distribution still receiving updates, and a release producing a binary that needs anything newer now fails instead of publishing it. The installer also keeps what the system actually said, so a mismatch names the version your machine has and the version the build wants. Re-run the install line to replace an affected binary.
• FixedBeing added to a Team by an administrator no longer looks like a refusal you cannot act on. Access is checked against a cached answer that refreshes on its own schedule, so for up to twelve hours after being added, a repository owned by your organization could still be refused — and the message only spoke to somebody who had upgraded their own plan. It now names your case and the one command, chi auth refresh, that picks the change up immediately.