Skip to content

lerim init

Interactive setup wizard for first-time Lerim configuration.

Overview

Run this once after installing Lerim. It detects installed native trace sources, lets you select which to connect, and writes the initial config to ~/.lerim/config.toml.

Host-only command

This command runs on the host machine. It does not require a running Lerim server.

Syntax

lerim init

What it does

  1. Scans for installed native trace sources (Claude Code, Codex CLI, Cursor, OpenCode, pi)
  2. Prompts you to select which sources to connect
  3. Writes the initial config to ~/.lerim/config.toml
  4. Checks for Docker availability
  5. Prints next steps

Example

lerim init

Output:

Welcome to Lerim.

Which native trace sources do you use?
  claude (detected) [Y/n]: y
  cursor (detected) [Y/n]: y
  codex (not found) [y/N]: n
  opencode (not found) [y/N]: n

Config written to ~/.lerim/config.toml
Agents: claude, cursor

Docker: found

Next steps:
  lerim project add /path/to/repo   # register a project
  lerim up                           # start the Docker service

Notes

  • Running lerim init again overwrites the existing config
  • API keys are not stored in config — they come from environment variables
  • You can manually edit ~/.lerim/config.toml after init
  • Non-coding workflows can be added after init with custom trace folders, source profiles, or MCP trace submission.