Quick Start¶
Important: LazyAI is Go-only. Install
lazyai-cliwithgo install; npm/npx distribution has been removed.
Install¶
Interactive setup¶
This launches a wizard where you choose:
- Scope:
project,global, orworkspace - Tools: OpenCode, Claude Code, GitHub Copilot
- Preset:
minimal,standard, orfull - Optional MCP servers: filesystem, ripgrep, memory, orchestrator, etc.
Non-interactive setup¶
Project scope (default)¶
lazyai-cli init \
--scope project \
--tools opencode,claude-code,copilot \
--enable-servers orchestrator \
--name my-app \
--preset standard \
--no-interactive
Global scope¶
lazyai-cli init \
--scope global \
--tools opencode,claude-code \
--name global \
--preset minimal \
--no-interactive
Workspace scope¶
lazyai-cli init \
--scope workspace \
--planning-repo ./planning-repo \
--repos ../app-one,../app-two \
--tools opencode,claude-code \
--name team-workspace \
--preset standard \
--no-interactive
What happens after init¶
- Creates canonical, tool-agnostic files under
.ai/ - Scaffolds specs, templates, rules, and infrastructure based on the selected preset
- Compiles root instructions for each selected tool
- Generates tool-native directories such as
.opencode/,.claude/,.github/, and.vscode/ - Writes
.ai-setup.jsonto track managed files, hashes, selections, and operations - Generates
.env.examplewhen enabled MCP servers require environment variables - Scaffolds
.ai/orchestration/when the optionalorchestratorMCP server is enabled
Verify the setup¶
Next steps¶
- Read How It Works to understand the canonical source model.
- Browse Scopes to choose the right setup mode.
- See MCP Integration to configure optional servers.