iriai-build

library0.6.6jsnpmunverified

Iriai Build (version 0.6.6) is an AI agent orchestration Command Line Interface (CLI) designed for planning, implementing, and shipping software features. It streamlines the development workflow by managing multi-agent pipelines directly from the terminal or via a Slack bridge. The tool integrates with the `claude` CLI as its underlying execution engine, allowing for sequential planning phases (PM, Designer, Architect, Plan Compiler) and parallel implementation across multiple teams. Key differentiators include its state-machine driven feature lifecycle, signal-based agent communication via the filesystem, multi-team coordination capabilities, and flexible budget tiers for controlling model usage and concurrency. It offers both interactive terminal and asynchronous Slack modes for user decisions and updates. As a pre-1.0 tool, its release cadence is likely agile, with ongoing feature development and potential for breaking changes.

llm-agents devops workflow aws

npm install iriai-build

package ↗

INSTALL

IMPORT

SIG · IRIAI-BUILD

iriai-build

llm-agentsjavascriptv0.6.6

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

iriai-build (CLI executable)

✓ npm install -g iriai-build iriai-build [command] [options]

✗ import { iriaiBuild } from 'iriai-build'

This package is a global CLI tool designed for command-line execution, not for programmatic `import` into a JavaScript/TypeScript project. Interactions occur via its subcommands after global installation.

iriai-build launch (subcommand)

✓ iriai-build launch "Implement user login feature"

✗ import { launch } from 'iriai-build'

CLI subcommands are the primary interaction points. Attempting to import them as functions or objects in code will result in an error as they are not exposed programmatically.

iriai-build setup (subcommand)

✓ iriai-build setup

✗ const config = require('iriai-build').setup();

Configuration is managed interactively through the CLI's `setup` command, which writes to `~/.iriai/config.json`. There is no programmatic API for setup.

Demonstrates the global installation of iriai-build, interactive configuration, and launching a complete AI-driven feature development cycle via the `launch` command.

#!/bin/bash # --- Prerequisites --- # Ensure Node.js >= 18 is installed. # Ensure 'claude' CLI is installed globally and configured (e.g., with API key). # If 'claude' is an npm package, install it: npm install -g claude # Otherwise, follow its specific installation instructions. # --- Installation --- npm install -g iriai-build # --- Configuration --- # Run interactive setup for tokens, tool paths, budget tier, and preferences. # This will save configuration to ~/.iriai/config.json iriai-build setup # --- Launching a Feature --- # Define a simple feature description for the AI agents. FEATURE_DESCRIPTION="Add a 'Privacy Policy' page with standard legal text and a contact email link." # Launch the full feature development cycle using the 'launch' command. # This will initiate planning, implementation, and review gates interactively. # Be prepared for a potentially long-running process with multiple prompts. # Ensure you are in your project's root directory when running for a real project. iriai-build launch "$FEATURE_DESCRIPTION" echo "Iriai-build launched for feature: '$FEATURE_DESCRIPTION'." echo "Follow the interactive prompts in your terminal to guide the agents."

iriai-build --version

Debug

Known issues

breakingThis package is pre-1.0 (currently 0.6.6) and is subject to frequent breaking changes in its API, command structure, and configuration schemas. Users should expect to review release notes for each update.

fix

Always check the latest README and release notes when upgrading. Consider pinning minor versions (e.g., `^0.6.0`) or specific patch versions if stability is critical for your workflow.

affects: >=0.1.0

gotchaIriai Build requires the `claude` CLI to be installed globally and available in the system PATH, or its path must be explicitly configured via the `CLAUDE_BIN` environment variable or during `iriai-build setup`. Without it, agent execution will fail.

fix

Install the `claude` CLI (e.g., `npm install -g claude` if it's an npm package, or follow its specific installation instructions) and ensure it's accessible. Run `which claude` to confirm its path, then configure `CLAUDE_BIN` or run `iriai-build setup`.

affects: >=0.1.0

gotchaThe default budget tier is `unrestricted`, which can incur significant API costs due to extensive Opus model usage and parallel agent execution. Monitor your Claude API usage closely.

fix

Configure a stricter budget tier using `--budget econ` or `--budget budget` when running commands, or set it persistently via `iriai-build setup` or the `IRIAI_BUDGET` environment variable.

affects: >=0.1.0

gotchaFeatures initiated and progressing in terminal mode do not automatically sync to Slack for asynchronous collaboration. To transition a terminal-initiated feature to Slack, the `transfer-to-slack` command is required.

fix

Use `iriai-build transfer-to-slack` for existing features. Ensure `slack_app_token` and `slack_bot_token` are configured via `iriai-build setup` or corresponding environment variables before attempting Slack operations.

affects: >=0.1.0

gotchaNode.js version 18 or higher is a mandatory prerequisite. Using older Node.js versions may lead to runtime errors, compatibility issues, or unexpected behavior.

fix

Upgrade your Node.js installation to version 18 or higher. Tools like `nvm` (Node Version Manager) can facilitate easy switching and management of Node.js versions (e.g., `nvm install 18 && nvm use 18`).

affects: <18.0.0

Errors

Common errors & fixes

Command 'claude' not found

The `claude` CLI executable is not installed, not in the system's PATH, or `CLAUDE_BIN` environment variable is incorrectly set.

fix

Install the `claude` CLI (refer to its documentation for specific instructions). Verify its accessibility by running `which claude`. If needed, configure the `CLAUDE_BIN` environment variable or run `iriai-build setup` to explicitly set its path.

Node.js version 16.x detected. Iriai Build requires Node.js >= 18.

The system's active Node.js version is older than the minimum requirement of 18.

fix

Upgrade your Node.js installation to version 18 or newer. If using `nvm`, run `nvm install 18 && nvm use 18`.

Slack tokens are not configured. Cannot launch Slack bridge.

Attempting to use Slack-related commands (`slack`, `transfer-to-slack`) without providing the necessary `slack_app_token` and `slack_bot_token`.

fix

Run `iriai-build setup` interactively and provide the required Slack App and Bot tokens. Alternatively, set the `SLACK_APP_TOKEN` and `SLACK_BOT_TOKEN` environment variables before running the commands.

Permission denied: access to ~/.iriai/config.json

The user executing `iriai-build` commands lacks sufficient write permissions for the `~/.iriai` directory or the `config.json` file within it.

fix

Check the file permissions for the `~/.iriai` directory and `~/.iriai/config.json`. Ensure the user has read and write access (e.g., `chmod 700 ~/.iriai` and `chmod 600 ~/.iriai/config.json`).

Upgrade

Version history

0.6.6latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

15 hits · last 30 days

node

OpenAI (training)

Resources

packagehttps://www.npmjs.com/package/iriai-build ↗