AI-DLC (AI-Driven Development Life Cycle) transforms AI coding assistants into structured, verifiable software-delivery workflows. This harness-neutral core runs natively in Claude Code, Kiro CLI, Kiro IDE, Codex CLI, Cursor, opencode, and GitHub Copilot. The Quick Start installs the latest stable AI-DLC release across macOS, Linux, WSL, or Windows via curl or PowerShell. The installer sets up the native aidlc command and every harness runtime without requiring Bun or Node.js. On Windows, it installs for the current account and registers the bin directory in User PATH. Run it from a normal PowerShell window; one opened with "Run as administrator" gets a warning and a prompt, since installing as administrator is less safe. Open a new terminal if another session cannot find aidlc. To skip both persistent and current-process PATH changes, use -No Modify Path. Windows uninstall removes only the User PATH entry recorded as installer-owned. On macOS, Linux, or WSL, follow the installer's PATH instruction if needed. Prefer to manage the project files yourself, or cannot install a native executable? The manual-copy path is the one place Bun is needed: install Bun, download aidlc-copy-runtime-X.Y.Z.tar.gz from the release, and copy the complete runtime/<harness>/ directory into your project. This path does not require the native aidlc command.
From the project root, select the harness you use: cd /path/to/your-project; aidlc config --harness claude; aidlc doctor. Replace claude with kiro, kiro-ide, codex, cursor, opencode, or copilot. Running aidlc config without --harness starts the interactive setup when a terminal is available. If you use Kiro IDE's own terminal in a project folder you have not trusted yet, Kiro first asks whether you trust it. Choose Trust Folder & Continue only for your own project or one you have checked, because trusting lets the folder's .kiro hooks run commands on your machine; otherwise choose Cancel and review the folder first (see First run).
Open your harness in the configured project and describe the work: /aidlc Build a REST API for inventory management. Codex CLI uses $aidlc instead of /aidlc. In Kiro IDE, first choose aidlc in the chat panel's agent picker. AI-DLC selects a workflow from the request, asks for missing decisions, and stops at approval gates before moving forward. For provider setup, trust prompts, and harness-specific prerequisites, use the guide in the table below. The complete walkthrough is in Getting Started. Pick your harness: Configure: Open: Invoke: Guide: Claude Code: aidlc config --harness claude; claude/aidlc; Getting Started. Kiro: Kiro IDE >= 1.1.70 / Kiro CLI >= 2.24.1 (v3): aidlc config --harness kiro-ide; Open the project in Kiro IDE and choose aidlc in the chat panel's agent picker, or run kiro-cli/aidlc; Kiro IDE. Kiro CLI (V2) >= 2.6: aidlc config --harness kiro; kiro-cli chat/aidlc; Kiro CLI. Codex CLI >= 0.145.0: aidlc config --harness codex; codex $aidlc; Codex CLI. Cursor: aidlc config --harness cursor; Open Cursor or run agent/aidlc; Cursor. opencode >= 1.17: aidlc config --harness opencode; opencode/aidlc; opencode. GitHub Copilot CLI >= 1.0.74 / VS Code >= 1.130: aidlc config --harness copilot; Copilot CLI or VS Code/aidlc; GitHub Copilot. Model-provider setup belongs to the harness. Shipped project configuration keeps the provider and model already selected by the user. aidlc config providers can apply Amazon Bedrock settings on supported project surfaces or record manual setup for other harnesses. Kiro CLI and Kiro IDE need no provider answer because model access comes with Kiro. For Kiro's v3 engine on Kiro CLI 2.24.1 or later, use kir...
Source: Hacker News · Summarized by HeadlinesBriefing