§00Changelog

Every version, and what it changed for you.

63 releases since 25 Jul 2026. Breaking changes say what to do about them, and a version that rebuilds your index says so at the top.

Archis updates itself: chi update checks what is published, verifies the release hash before writing anything, and puts the previous binary back if the new one does not start. chi update --check installs nothing.

  1. 0.28.0

    Taking Archis back off a machine is one command now, not one command per repository.

    Before you upgrade — Nothing to change, and no reindex. If you are removing Archis, use the uninstaller rather than deleting the binaries — run it with --dry-run first to see the plan.

    • NewAn uninstaller, served beside the installer: curl -fsSL https://archis.dev/uninstall.sh | sh -s -- --yes. Removing Archis used to mean visiting every repository it had indexed and running chi eject in each, which is how most of them got left behind — and the ones left behind are the ones that keep an index directory, hook entries in your agent settings and a paragraph in a committed instruction file for as long as the machine lives. Deleting the two binaries first made all of it unreachable, because chi is the only thing that knows where any of it is. So the order is the whole design: every repository, then the machine-wide setup, then the sign-out, and the binaries last. --dry-run prints the plan and changes nothing, --keep-sessions keeps each repository working history, --keep-repos limits it to the machine setup and the binaries, and --purge also deletes the state directory. A step that fails is reported without stranding the rest.
    • Newchi eject --all does the same removal in every repository Archis has indexed on this machine, in one pass and with one question. It tells you what it is not doing rather than implying a sweep: a repository on a disk that is not mounted right now is named and left alone instead of counted as done, and a repository Archis was never pointed at was never on the list, so the output says which is which. Combine it with --machine to leave nothing behind. --machine also works beside --keep-sessions now — finished with Archis, keeping the working histories, is a real thing to want.
    • ImprovedNeither of these needs a valid licence, and the documentation now says so where the question comes up. Whatever Archis puts on a machine has to come back off a machine whose licence has lapsed, and a lapsed plan is the most likely moment to want exactly that. A lapsed licence has never deleted anything of yours either — blocking is reversible and deleting is not.

Run the current release

Archis Free is the whole local engine, with no card. Everything semantic runs on your machine — there is no endpoint that accepts source.