Every version, and what it changed for you.

Your agent can tell you what Archis saved it, and your documentation is part of the graph.

Before you upgrade — Your index rebuilds itself the first time you open it after upgrading. macOS and Linux: curl -fsSL https://archis.dev/install.sh | sh. This release has no Windows build — 0.35.0 remains the newest one for Windows.

• NewAn agent can now close a task by saying what Archis cost and what it saved. session_report takes no arguments and returns the calls it answered, the tokens it served, and what those stood in for — the source the agent never had to read. It also reports what it could not measure and what you read in full anyway despite asking Archis first, so the figure is one you can check rather than one you have to trust.
• NewWhen subagents did some of the work, that report breaks down per agent as well as in total. Each subagent is counted as itself instead of being folded into the harness that spawned it, so "which of my agents is reading past Archis" has an answer. With the harness hooks installed (chi agents on --hooks) the summary is emitted at the end of a turn on its own, without the agent having to remember.
• NewYour documentation is in the graph beside your code. Markdown files declare relationships, headings form a tree, and a name written in backticks inside a document links to the thing it names — so asking about a design decision finds the document that made it. Specifications under specs/ are stored whole, chi specs list and chi specs check inventory them, and documentation is searchable by its own prose rather than only by its headings.
• Newchi channel chooses which releases this machine follows: stable by default, or beta to take pre-releases early. A machine on beta returns to stable by itself when the real release lands.
• FixedOne agent could destroy another agent's index. A repository being read by two Archis processes at once — which is what a harness running subagents is — could have its index deleted out from under a process still using it, on nothing worse than a moment of contention, producing the corruption the deletion was meant to cure. Archis now discards an index only when it is genuinely unusable, and serialises the work that cannot run twice at once. If you run subagents, this is the fix to upgrade for.
• FixedA damaged index no longer poisons the rest of the session: the server repairs it and retries the call once, instead of failing every request until you restart. chi doctor also now tells you when .chi has been committed to git, and the exclusion is written correctly in a worktree or a submodule — the layout agents most often run in, and the one that was missing it. An edited README or specification is re-read on the next index instead of answering from the previous version.