Update
Update the harness with rei init --update and the binary with rei update, including the Windows case.
When to use it
Use this guide when you want to check whether there is a new version of the binary, update it, or refresh the harness skeleton in a project that already has it initialized.
Requirements
- To update the binary, a connection to GitHub Releases and write permission on the executable.
- To update the harness, a project already initialized with
.rei/. - A backup or a clean commit before forcing changes to the documentation.
- Knowing the difference between updating the binary and updating the project skeleton.
Steps
- Check whether there is a new version with
rei update --check. It only reports the result: it does not download or write anything. - Update the binary with
rei update. It downloads the asset for your system and architecture, verifies its SHA-256 against checksums.txt and replaces the executable atomically. If the integrity check fails, it aborts without modifying the binary. - On Windows a running
.execannot be replaced:rei updatereports it and opens the releases page so you can download the archive by hand. - Update the harness skeleton with
rei init --update. It requires an REI project; it does not install from scratch and never touches.rei/specs/**or.rei/progress/**. - Review the warnings.
--updateis marker-aware: it updates the customization documents that still contain the pending marker and keeps those already customized. The rest of the files are updated only if the manifest confirms they were not modified. - Use
rei init --update --forceonly if you accept overwriting any file that differs, including customized or hand-edited ones. The result is reported as [NEW], [UPD], [OK] or [SKIP].
rei update --check
rei updaterei init --update
rei init --update --force
rei init statusVerification
rei version
rei init status
rei check
rei validaterei version confirms the binary version. rei init status tells you whether any documentation is still pending customization. rei check verifies the harness and the project checks, and rei validate reviews the consistency of a Work Item.
If the binary update fails because of the network, permissions or checksum, the previous executable is left intact. If the replacement fails after it has started, the original is restored.
Limits
rei init --updatedoes not install the harness from scratch: userei initfor that.--updatedoes not modify.rei/specs/**or.rei/progress/**: work in progress is not lost.- Customized documents are kept with a warning; only
--forceoverwrites them. --updateregenerates native subagents only if the project already has.opencode/or.claude/.- On Windows, the binary update is manual from the releases page.
Next step
After updating, run the checks again and, if the harness changed, review the command reference and the installation.
A human sign-off releases the sheet. Silence is not approval.