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

    Archis works where your editor starts it, tells you when something needs you, and edits a graph twice as fast.

    • Newchi init treats signing in as the next step instead of saying nothing about it. On a machine without an account it used to index your repository, silently skip everything that needs one, and announce that Archis was set up. It now opens by saying where you stand, closes with what is waiting, and offers to sign in.
    • ImprovedEditing a file, keeping history and switching branch are substantially faster on the CAVS backend. Measured on three repositories, median of three runs: a one-file edit 40–52% faster, a ten-file edit 51–63%, revision history 47–53%, and switching branch 95–98%. Reading a symbol for the first time in a process went from 48.6 to 1.8 microseconds, because what a process has read now stays read.
    • FixedArchis works when your editor starts its MCP servers in the background. A client that spawns a server without setting a working directory left Archis resolving your repository to the filesystem root and failing with what looked like a database error — while the same server started from a terminal worked perfectly, so it looked like Archis was broken and it was not. Archis now asks your client which project it was opened for, which needs no configuration at all; CHI_BASE_DIR covers a client that cannot answer; and where neither works it says exactly that, with the three ways out.
    • FixedSigning in over SSH no longer hangs. The browser flow can only be finished by a browser on the same machine as the CLI, so on a remote shell the one-time code went to your laptop and the terminal waited out its full ten minutes. Archis now notices a remote session and shows a verification code instead, and says why. If a redirect is lost anyway it asks for the code rather than waiting.
    • FixedConnecting one coding agent no longer configures a different one. Asked about a single agent, Archis was writing another vendor's hooks and skill, briefing two more, and telling you to restart a product you had not mentioned. Every file it touches and every line it prints is now about the agent you named — and disconnecting one no longer removes what told the others Archis is there.
    • FixedA repository nobody has indexed yet says so. cannot open the index read as a broken server, and a model that saw it quietly stopped using Archis for the rest of the session without telling you. The message now names the command that fixes it and asks the agent to tell you rather than give up in silence.
    • FixedWhat a new release adds to your instruction files now reaches machines that already have them. A briefing block written by an older release stayed exactly as it was and reported itself as finished, so a machine set up months ago went on telling every model what Archis said back then. Blocks Archis already wrote are brought up to date; one it never wrote is still your 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.