Skip to main content
relai init registers an agent project and generates simulator support.
relai init
relai init can take a while for larger or more complex agents because RELAI inspects the project and generates a simulator harness for it.

Before you run it

Run it from the root of a git-tracked agent repository. The project should satisfy the project requirements, and relai setup should already have RELAI API credentials. relai init has no CLI flags. Interactive runs may ask for RELAI credentials, agent metadata, generation choices, and whether to commit generated files.

What it creates

  • project registration with the RELAI backend.
  • simulator files under .relai/simulator/.
  • runtime and mock manifests.
  • .relai/learning-env-context.json.
  • .relai/simulator.env.example.
  • optional dependency file changes when simulator installation updates project files.
  • suggested or performed git commits for generated artifacts.

Example

git status --short
relai init

Common failures

  • not running inside a git repository.
  • missing RELAI credentials.
  • missing required local tools.
  • backend generation or validation failure.
  • tracked generated paths already have local changes.
  • the project cannot expose a runnable local simulator surface.
This command writes files. Review generated files before committing them.