Skip to main content

​
Machine & setup

See setup or report for flags and examples.

​
The learning loop

The core cycle — see The learning loop for how these stages fit together.

​
Authoring

​
Project inputs

Use a root-level .relaiignore file to keep selected project files out of RELAI backend generation inputs and optimizer worktrees. See Controlling project inputs with .relaiignore for scope, examples, and explicit-path failure behavior.

​
Getting help

Use --help at any level for command-specific flags, and --version for the installed version.

​
Diagnostic logs

Each relai invocation writes a bounded, structured diagnostic log to ~/.relai/logs/. Logs record command lifecycle, safe high-level actions, validation and repair attempts, backend outcomes, warnings, and failures. CLI arguments are represented by flag names only, paths are project-relative, and subprocesses retain only operation, attempt, status, outcome, and duration. Logs intentionally exclude credentials, option values, authorization headers, request bodies, generated source, and all subprocess output. Each invocation is limited to 500 events or 256 KiB. Logs older than 30 days are removed, and the directory is pruned to 100 MiB. When asking for support, share only the relevant log after reviewing it for project names or other information you do not want to disclose.