Skip to main content

​
System Requirements

Before installing Enki, ensure you have the following dependencies:
All of these requirements are mandatory for Enki to function properly.
  • Git: Used for version control and managing task branches
  • Claude Code: The ACP agent that Enki orchestrates (see Claude Code documentation)
  • Node.js: Required to install and run the ACP agent runtime
  • Rust (if building from source): The Rust toolchain via rustup

​
Installation Methods

brew install korbindeman/tap/enki

​
Verify Installation

After installation, verify that Enki is available: 
enki --version
You should see output similar to: 
enki 2026.306.2

​
What Gets Installed

Enki installs a single binary (enki) that provides:
  • TUI Interface: Interactive terminal UI for managing agents and tasks
  • MCP Server: JSON-RPC stdio server for agent tool access (used internally)
  • Coordinator: Orchestration engine for spawning and managing ACP agents

​
Post-Installation Setup

Enki automatically initializes your project on first run. You don’t need to run any setup commands manually.
When you first run enki in a directory, it will:
  1. Create a .enki/ directory in your project
  2. Initialize the SQLite database for task tracking
  3. Set up the directory structure for worker isolation

​
Directory Structure

After initialization, your project will contain: 
.enki/
├── db.sqlite          # Task and execution state
├── roles/             # Project-specific role overrides (optional)
├── artifacts/         # Step outputs when using artifact mode
├── events/            # Signal files for cross-process communication
├── copies/            # Copy-on-write clones for worker isolation
└── logs/
    └── enki.log       # Main log file

​
Troubleshooting

​
Command Not Found

If you installed via Homebrew and get “command not found”: 
# Check that Homebrew's bin directory is in your PATH
echo $PATH | grep -q "$(brew --prefix)/bin" && echo "OK" || echo "Add $(brew --prefix)/bin to PATH"
If you installed via cargo and get “command not found”: 
# Ensure ~/.cargo/bin is in your PATH
export PATH="$HOME/.cargo/bin:$PATH"

# Add to your shell profile (~/.bashrc, ~/.zshrc, etc.)
echo 'export PATH="$HOME/.cargo/bin:$PATH"' >> ~/.zshrc

​
Build Errors (Source Installation)

If you encounter errors building from source: 
# Update Rust to the latest stable version
rustup update stable

# Ensure you're using Rust 2024 edition (requires Rust 1.85+)
rustc --version

​
Missing Dependencies

If Enki fails to start due to missing dependencies:
1

Install Git

# macOS
brew install git

# Ubuntu/Debian
sudo apt-get install git

# Verify
git --version
2

Install Node.js

# macOS
brew install node

# Ubuntu/Debian (using NodeSource)
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
sudo apt-get install -y nodejs

# Verify
node --version
npm --version
3

Set up Claude Code

Follow the official Claude Code setup guide to configure the ACP agent.

​
Next Steps

Now that Enki is installed, proceed to the Quickstart Guide to create your first multi-agent workflow.

Build docs developers (and LLMs) love

Get started for freeTalk to us