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

    Archis now searches the code of every repository on your CAVS DB Server, even ones you have never checked out, and you sign in to the server with your Archis account.

    Before you upgrade — Update, then reopen your agent window so it starts the new version. Your existing indexes are kept. Federation needs a Team or Enterprise plan; the self-hosted server needs Enterprise.

    • NewCode from repositories that live only on the server: published repositories now carry their file content, so chi workspace context returns lines and not just paths for a repository you have no checkout of. Every repository in the workspace is searched under a shared budget, and anything left unread is reported. chi repo mode chooses how much each repository publishes.
    • NewYour agent can ask across repositories too: the new federation_context tool answers a task over the whole workspace that contains the current repository, and chi_context points to it when a task names another repository.
    • NewSign in to your organization’s CAVS DB Server with your Archis account: chi registry server login gets a personal token, keeps it with your Archis credentials and renews it when due; chi registry server status shows what it reaches. Tokens in an environment variable still work, so CI is unchanged. The portal can issue the same token.
    • Newchi repo attach --all registers every repository the server gives you access to, and sync, publish and attach --all run in parallel (--jobs). One repository failing no longer stops the rest; the run ends with a summary.

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.