Appearance
Command-Line Help for rein
This document contains the help content for the rein command-line program.
Command Overview:
rein↴rein check↴rein run↴rein eval↴rein step↴rein describe↴rein graph↴rein debug↴rein watch↴rein list↴rein show↴rein serve↴rein agent-context↴rein hook↴rein install↴rein uninstall↴rein update↴rein lsp↴rein dap↴
rein
A small language for agent decision flows
Usage: rein <COMMAND>
Subcommands:
check— Check a project directory, or one .rein file, and print diagnosticsrun— Run a flow as a live process. Writes one step per line, reads one answer per line on stdineval— Evaluate one function, for debugging. Agents userein runorrein stepstep— Step the whole flow frommain. This is the agent-facing interface: answer one key per calldescribe— Print a function's schema as JSONgraph— Print the program graph: functions, questions, branches, outcomes, and hand-offs. With answers, mark the path the flow takes. The graph shows functions, not calls: a function called several times withawaitis marked with the answers of its first calldebug— Debug a program in the browser: set inputs and answers, step through, and watch the path the flow takeswatch— Show the agents that use rein now: their programs, answers and the step each run waits on, in a browser page. The flow graph shows functions, not calls: a function called several times withawaitis marked with the answers of its first calllist— List the programs visible from here, aslslists files: names, or-lfor details. Operands are name globsshow— Print a program's source: its manifest and every .rein fileserve— Serve the agent interface. Holds live runs in memoryagent-context— Print the block an agent needs to use the visible flowshook— The agent hook entry point. Reads one event on stdin. Run by the agent, not by handinstall— Install a program package: runspnpm addwith these argumentsuninstall— Remove an installed program package: runspnpm removewith these arguments.-gpicks the user folderupdate— Update installed program packages: runspnpm update --ignore-scriptswith these arguments.-gpicks the user folderlsp— Run the language server on stdiodap— Run the debug adapter on stdio (Debug Adapter Protocol). The VS Code extension starts it