Every version, and what it changed for you.

Setting a repository up is one command, and it finishes the job.

Before you upgrade — Run chi init in a repository you work in. It is safe to run on a repository that is already set up: it asks only what is still unanswered, and shows you the whole list before applying anything.

• Newchi init sets a repository up in one command, and asks how you want to answer before it asks anything else. A repository used to reach a working Archis install by accident: the index builds itself on the first call, so the graph was usually there — while the advice hook was not, the briefing was not, and nothing said so. Run it at a terminal and the first question is the shape of the rest: a checklist of every pending step to mark with x and apply together, yes to everything, every default, or the questions one at a time with their full explanations. --profile basic|full|custom picks one from a script, --yes is the alias for basic, and --check runs the closing report on its own and exits non-zero when something needs attention, which is what CI and pre-commit hooks need. Answers about your machine are remembered once per machine, answers about a repository once per repository, so the fortieth project does not re-ask you about this laptop.
• NewA reminder every tenth prompt, so a long session does not outlive its briefing. Archis introduces itself to a model once, before the first turn. Forty turns and a context compaction later that text is the oldest thing in the conversation, arguing against everything said since — and that is when an agent goes back to reading files whole. The reminder is three lines, on a slow cadence, and it is installed with the advice hook. If you already have the advice hook, chi init offers you the missing half once.
• Newchi hook strict makes the advice enforceable, and it is off unless you turn it on. Normally Archis names the cheaper call and never touches your permissions. With strict mode on, a session that has been handed the substitute call and keeps using the harness tool anyway has that call refused, with the Archis call to use written into the refusal. Shell commands are never refused: a read is often one stage of a pipeline, and breaking it would cost you more than the tokens. chi hook strict off at any time, licence or no licence.
• NewArchis's tools can stop asking permission, and your team can inherit the whole setup. A model learns whichever route does not interrupt it, and until now the cheap route was the interrupted one while grep ran unprompted — chi init offers to allow Archis's read-only tools outright. It also offers to commit Archis's hooks and that permission to the repository, so somebody who clones gets the briefing, the attribution and the advice from their first session without running anything. The committed entries are written so that a machine without Archis skips them silently instead of failing every session start.
• NewA skill that carries the method at length. Everything else Archis says to a model is prepended to every session, so every line is rationed down to the essentials. A skill costs one line until the model decides a task matches it, which makes it the first place the full method fits: which call answers which shape of question, when to batch, what a turn actually costs.
• Newchi eject --machine removes Archis from a machine the way chi eject removes it from a repository. Hooks, the briefing, the skill, the permission entry, strict mode and every agent registration, in one command that prints the plan first — previously five commands you had to know about. No repository is touched.
• Improvedchi dashboard opens the browser view by default. --tui keeps the terminal one, and --web still works and now means nothing.
• Fixed.chiignore no longer gains a copy of its own header every time you index. The header Archis writes and the one it wrote before 0.22 share a line, and the check for "did an older Archis write this" matched on it — so a file this version had just written looked like a file to migrate on the next run, and picked up another header. Files that already carry several copies keep them: they are ordinary comments, and Archis does not delete lines out of your files on an upgrade. Trim them by hand if they bother you.
• FixedWhat Archis writes into your repository can be taken back out. The .chi/ line in your git exclude file and the block Archis maintains in .chiignore had no inverse, so chi eject left them behind. Both come out now, and narrowly: the exclude line only where Archis's own comment is above it, since you may have written that line yourself, and the .chiignore file itself only when nothing but Archis's text was ever in it.