Every version, and what it changed for you.

Your agent is told Archis is there, even when Archis cannot hook it.

Before you upgrade — If your agent is anything other than Claude Code, run chi brief on after upgrading — nothing else tells it Archis is there before its first turn. Restart the agent afterwards so it re-reads its configuration.

• Newchi brief on writes Archis's briefing into the instructions file your agent already reads — CLAUDE.md, AGENTS.md, GEMINI.md or .goosehints, whichever ones you have. Only one of the seven supported agents has a hook Archis can register itself with, so for the other six the only thing that had ever told a model Archis exists arrived once, inside a tool roster, at connect time. This is one block between two markers: nothing outside them is touched, the file is backed up first, a second run replaces the block rather than adding another, and chi brief off puts the file back exactly as it was. It writes your own configuration by default; --project writes the repository's file, which is usually committed. chi brief status prints the resolved path for every agent, so you can see which file it chose before you trust it.
• Newchi hook install --intercept names the cheaper Archis call *before* a Read, Grep or Glob runs, with the path or pattern your agent just typed already substituted into it. This is the one moment where advice can still change what a session costs — after the tool has run, the tokens are already bought. It is opt-in, it never denies or approves the call, and your agent's own permission flow is untouched: the call goes ahead exactly as it would have. Said once per tool per session, because the same paragraph forty times is forty times the cost for one time the effect.
• Newchi doctor now answers whether anything is actually asking Archis. A valid licence, a fresh index and an agent that never calls the server was not a visible failure anywhere. The report adds which coding agents are installed, whether the session briefing is registered, which instructions files are still unbriefed, and what share of this repository's recorded file touches went through Archis rather than around it. chi doctor agents asks each agent about its own configuration as well, which takes a few seconds longer.
• FixedThe setup wizard asks again when you install a coding agent after Archis. Answering the question with one agent on the machine and then installing a second left an agent Archis had never offered to connect and never would, while chi setup --list reported the step as done. It now comes back for the new agent, and only for that one; an agent you *uninstall* changes nothing, and an answer you gave before this release stays settled.
• FixedThe dashboard shows a session that is open. Three separate omissions on the same path, each enough on its own to empty the view: a session was first noticed when it read or wrote a file, so one that spent its first hour in other commands was absent rather than late; a recorded file touch never marked the session as still working, so every hook-driven session read as idle from the minute it was created and "0 active now" was structural; and a repository you indexed by hand had nowhere to record what happened in it, so an afternoon of work showed as no history at all.
• FixedThe .chiignore Archis writes at your repository root is in English. It is a file meant to be committed and read by whoever picks the project up, and its header and its block markers were in the language of the people who wrote Archis rather than the language of everything else it prints. A file written by 0.21 or earlier is recognised and rewritten the next time you index — markers included, which matters for more than tidiness: a marker Archis no longer knew would have claimed every entry inside it as yours and left a second, empty block underneath. Your own rules on either side of the block are untouched.