§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.27.0

    A repository with no index yet is a reason to ask Archis first, not a reason to skip it.

    Before you upgrade — Nothing to change, and no reindex. After upgrading, repositories set up by an earlier release will say so — run chi init in the ones you are working in to pick up anything this release added.

    • NewArchis now tells you when a repository was set up by an older release than the one you are running. Upgrading the binary is not a migration: a release can add a hook, change the skill your agent is briefed with or extend what Archis writes into your instruction files, and none of that reaches a repository already on your machine until you run chi init there again. Your index was never the problem — it rebuilds itself — and nothing said the rest was out of step. Now three places do, each where you would see it: your agent is told at the start of a session (along with the fact that the index is current either way), chi doctor reports it with chi init as the fix, and chi update closes by naming which of your repositories an earlier release configured. It reports and stops there; chi init is what applies it, in the repository you are actually standing in.
    • FixedYour agent no longer walks away from Archis in a repository it has not indexed yet. The line Archis sends at the start of a session said the index was not built and that there was nothing to run by hand — accurate, and read by models as "Archis is no use here, I will use the shell instead". That is the one conclusion there is no way back from, because the index is built by asking: the first call indexes the repository and answers from it. So the session paid full price for every file it read, in exactly the repository where one Archis call would have covered all of them. The line is an instruction now. Nothing about the behaviour changed — automatic indexing has been on by default since 0.7.0 and your working tree has been re-checked before every answer since 0.14.2 — only the sentence your agent reads before its first decision.

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.