Viewer
Open rei view, read its views, control its lifecycle and respect its read-only limits.
When to use it
Open the viewer when you want to review a Work Item with its documents rendered, its table of contents, validation, session, diff and FICHA on a single page. It is a local tool for reading and checking, not for deciding.
Requirements
- A project initialized with
.rei/and the rei binary available. - An active session or the identifier of the Work Item you want to see.
- A local browser; the viewer serves HTTP on your machine and deploys nothing.
- A free port, which the viewer itself picks and reports at startup.
Steps
- Run
rei viewwithout an identifier to open the Work Item of the active session. If there is no session, pass one withrei view <id>. - If you do not want to block the terminal, use
rei view --open: it starts or reuses the server in the background and opens the browser. The--open,--stop,--enableand--disablemodes are mutually exclusive. - Review the planning and progress documents, the TOC, validation, session, diff and FICHA. The FICHA shows issue, base and epic when
links.jsonexists. - Leave the tab open if you want to follow the state: the badge and the FICHA refresh live over SSE when they change on disk.
- Close the server with
rei view --stop, with Ctrl+C, or by waiting for the idle timeout. In the background it also closes shortly after showing «finished» when the Work Item reaches done. - Turn automatic opening on ready on or off with
rei view --enableorrei view --disable. It only changesviewer.autoOpenOnReadyin.rei/config.json.
rei view
rei view 2026-10-27_01-54__mi-feature --open
rei view --stop
rei view --enable
rei view --disableVerification
rei item show 2026-10-27_01-54__mi-feature
rei validate 2026-10-27_01-54__mi-featureCheck that the viewer's state and FICHA match the CLI card and links.json, and that the diff corresponds to the real changes of the Work Item. If the viewer shows an old state, refresh the page: the refresh depends on the SSE connection.
Limits
- It is read-only: it does not approve and does not modify documents,
meta.jsonor the state of the Work Item. - It does not replace the human answer in the chat or the terminal, nor the CLI, nor the git history.
- It loads no third-party JavaScript, CSS or fonts: its assets are embedded in the binary.
- It exposes no approval route or button that changes the state.
Next step
After reviewing the viewer, the next control is the project verification. The checks guide explains which commands run and how to interpret their result.
A human sign-off releases the sheet. Silence is not approval.