ACP Setup

🤖 AionUi Multi-Agent Mode Configuration Tutorial

This tutorial will detail how to configure and use Multi-Agent Mode in AionUi, including integration with external CLI tools like Claude Code, Qwen Code, CodeX, iFlow CLI, etc. These external tools are integrated through ACP (Agent Communication Protocol) for unified interface management.

English | 简体中文

🎯 Multi-Agent Mode Overview

Multi-Agent Mode is an optional feature that allows you to integrate external CLI tools you already have installed. If you already use Claude Code, Codex, or Qwen Code, AionUi auto-detects them and lets you Cowork with all of them — alongside the built-in agent. These external CLI tools are integrated through ACP (Agent Communication Protocol) with the following characteristics:

• Auto Detection: Automatically recognizes installed CLI tools
• Unified Interface: One Cowork platform for all your AI agents
• Automated Task Execution: AI agents can independently execute tasks, run scripts, read/write files, and operate tools automatically
• Workflow Automation: Complete workflow automation capabilities with file system operations and task completion
• Independent Functionality: Each agent maintains its original features and capabilities
• Protocol Standardization: Standardized communication through ACP protocol
• Flexible Extension: Supports integration of more CLI tools that comply with ACP protocol

Supported External Agents

Agent	CLI Command	Status
Claude Code	claude	✅ Supported
Qwen Code	qwen	✅ Supported
CodeX	codex	✅ Supported
iFlow CLI	iflow	✅ Supported
Goose	goose	✅ Supported
Augment Code	auggie	✅ Supported
Kimi CLI	kimi	✅ Supported
OpenCode	opencode	✅ Supported
Factory Droid	droid	✅ Supported
CodeBuddy	codebuddy	✅ Supported
GitHub Copilot	copilot	✅ Supported
Qoder CLI	qodercli	✅ Supported
Mistral Vibe	vibe-acp	✅ Supported
Nano Bot	nanobot	✅ Supported
OpenClaw	openclaw	✅ Supported
Built-in Agent	Built into AionUi	✅ Enabled by default

💡 Tip: AionUi also supports Custom Agents, allowing you to configure any CLI tool that complies with the ACP protocol in the settings.

Multi-Agent Mode vs Built-in Agent Mode

Feature	Built-in Agent Mode	Multi-Agent Mode
Installation Requirements	Built into AionUi, users get it by default after installation	Requires users to download and install CLI tools themselves, then AionUi auto-detects and integrates
Technical Architecture	AionUi built-in Agent engine	External CLI tools integrated via ACP protocol
Feature Completeness	Complete features (image generation, tool scheduling, multi-API key rotation, etc.)	Currently relatively simple, mainly GUI management of conversations and workspaces
Configuration Integration	Direct access to all AionUi configuration features	Currently cannot directly use AionUi's LLM configuration, image generation, and other built-in features
Future Development	Most complete functionality, continuous optimization	ACP-integrated tools will gradually catch up, unified management features planned
Use Cases	Daily use, complete AI functionality experience	Professional users, specific CLI tool requirements

---

🚀 Step 1: Install CLI Tools

Before configuring Multi-Agent Mode, you need to install the corresponding CLI tools first.

Claude Code Installation

1. Install Claude CLI

   # Install globally with npm
   npm install -g @anthropic-ai/claude-code

2. Verify Installation

   claude --version

3. Authentication Configuration

   # Login to Claude account
   claude login

📖 Official Documentation: Claude Code GitHub

Qwen Code Installation

1. Install Qwen CLI

   # Install globally with npm
   npm install -g @qwen-code/qwen-code

2. Verify Installation

   qwen --version

3. Authentication Configuration

   # Login to Qwen account
   qwen login

📖 Official Documentation: Qwen Code GitHub

CodeX Installation

1. Install CodeX CLI

   # Install globally with npm
   npm install -g @openai/codex

2. Verify Installation

   # Check version
   codex --version

3. Authentication Configuration

   # Login to OpenAI account
   codex login

📖 Official Documentation: OpenAI Codex CLI

iFlow CLI Installation

1. Install iFlow CLI

   # Install globally with npm
   npm install -g @iflow-ai/iflow-cli

2. Verify Installation

   iflow --version

3. Authentication Configuration

   # Login to iFlow account
   iflow login

📖 Official Documentation: iFlow CLI GitHub

Goose Installation

1. Install Goose CLI

   # macOS using Homebrew
   brew install block/tap/goose
   
   # Or using pipx
   pipx install goose-ai

2. Verify Installation

   goose --version

3. ACP Mode

   # Goose uses subcommand for ACP
   goose acp

📖 Official Documentation: Goose GitHub

Augment Code Installation

1. Install Augment Code CLI

   # Install globally with npm
   npm install -g @anthropic-ai/augment-code

2. Verify Installation

   auggie --version

3. ACP Mode

   # Auggie uses --acp flag
   auggie --acp

📖 Official Documentation: Augment Code

Kimi CLI Installation

1. Install Kimi CLI

   # Install globally with npm
   npm install -g @anthropic-ai/kimi-cli

2. Verify Installation

   kimi --version

3. ACP Mode

   # Kimi uses --acp flag
   kimi --acp

📖 Official Documentation: Kimi CLI (Moonshot)

OpenCode Installation

1. Install OpenCode CLI

   # Install with Go
   go install github.com/opencode-ai/opencode@latest

2. Verify Installation

   opencode --version

3. ACP Mode

   # OpenCode uses subcommand for ACP
   opencode acp

📖 Official Documentation: OpenCode GitHub

Factory Droid Installation

1. Install Factory Droid CLI

   # Refer to Factory official documentation for installation
   # Requires FACTORY_API_KEY environment variable

2. Verify Installation

   droid --version

3. ACP Mode

   # Droid uses special exec command format
   droid exec --output-format acp

📖 Official Documentation: Factory Droid

CodeBuddy Installation

1. Install CodeBuddy CLI

   # Install globally with npm
   npm install -g @tencent-ai/codebuddy-code
   
   # Or use npx (no global installation required)
   npx @tencent-ai/codebuddy-code

2. Verify Installation

   codebuddy --version

3. ACP Mode

   # CodeBuddy uses --acp flag
   codebuddy --acp

📖 Official Documentation: CodeBuddy GitHub

GitHub Copilot Installation

1. Install GitHub Copilot CLI

   # Install globally with npm
   npm install -g @github/copilot-cli

2. Verify Installation

   copilot --version

3. ACP Mode

   # GitHub Copilot uses --acp --stdio flags
   copilot --acp --stdio

📖 Official Documentation: GitHub Copilot CLI

Qoder CLI Installation

1. Install Qoder CLI

   # Install globally with npm
   npm install -g @qoder-ai/qoder-cli

2. Verify Installation

   qodercli --version

3. ACP Mode

   # Qoder uses --acp flag
   qodercli --acp

📖 Official Documentation: Qoder CLI GitHub

Mistral Vibe Installation

1. Install Mistral Vibe CLI

   # Install with pip
   pip install vibe-acp
   
   # Or use pipx (recommended)
   pipx install vibe-acp

2. Verify Installation

   vibe-acp --version

3. ACP Mode

   # Mistral Vibe runs directly with vibe-acp command
   vibe-acp

📖 Official Documentation: Mistral Vibe

Nanobot Installation

1. Install Nanobot CLI

   # Install globally with npm
   npm install -g nanobot

2. Verify Installation

   nanobot --version

3. ACP Mode

   # Nanobot runs directly
   nanobot

📖 Official Documentation: Nanobot GitHub

OpenClaw Installation

1. Install OpenClaw CLI

   # Install globally with npm
   npm install -g @openclaw/cli

2. Verify Installation

   openclaw --version

3. Gateway Mode

   # OpenClaw uses gateway subcommand
   openclaw gateway

📖 Official Documentation: OpenClaw GitHub

💡 Tip: OpenClaw can also be configured through AionUi's built-in assistant. See OpenClaw Setup Assistant for details.

---

💬 Step 2: Using Multi-Agent Mode

Create Multi-Agent Conversation

1. Select Agent

   • Choose the external agent to use on the welcome interface
   • System will display detected available agents (integrated via ACP protocol)

2. Create Conversation

   • Enter message content
   • Select working directory (optional)
   • Click send to start conversation

Conversation Features

1. Real-time Connection Status

   • Shows agent connection status
   • Automatic reconnection mechanism
   • Connection error prompts

2. Permission Management

   • CLI tools will request file operation permissions
   • Confirm or deny permission requests in AionUi
   • Supports one-time or permanent authorization

3. Tool Calling

   • Supports CLI tool's native functionality
   • File read/write operations
   • Code execution and debugging

---

❓ Common Questions

Q: What's the difference between Multi-Agent Mode and Built-in Agent mode?

A: Main differences:

• Built-in Agent Mode: AionUi's built-in core functionality, users get it by default after installation, supports image generation, tool scheduling and other complete features - no CLI tools to install
• Multi-Agent Mode: If you already have external CLI tools installed, AionUi auto-detects and integrates them through ACP protocol, currently relatively simple functionality, will develop MCP settings functionality to enhance integration in the future

Q: When to choose Multi-Agent Mode?

A: Selection recommendations:

• Daily Use: Recommend Built-in Agent mode, most complete functionality, ready to use out of the box - no setup required
• Professional Needs: If you already have specific CLI tools installed (like Claude Code, Qwen Code, etc.), you can use Multi-Agent Mode to integrate them
• Future Planning: MCP functionality will let Multi-Agent Mode enjoy more unified features

Q: How to know if Multi-Agent Mode is working properly?

A: Check methods:

• Can see agent options on welcome interface
• Can connect normally when creating conversations
• Can receive replies when sending messages
• Permission requests display normally

Q: What features does Multi-Agent Mode support?

A: Current features:

• Basic conversation functionality
• File operation permission management
• CLI tool's native functionality
• Working directory management

---

🔧 Troubleshooting

Q: Multi-Agent Mode not detected?

A: Check steps:

1. Confirm CLI tool is properly installed

   # macOS/Linux
   which claude
   which qwen
   which iflow
   which goose
   which auggie
   which kimi
   which opencode
   which droid
   which codebuddy
   which copilot
   which qodercli
   which vibe-acp
   which nanobot
   which openclaw
   
   # Windows
   where claude
   where qwen
   where iflow
   where goose
   where auggie
   where kimi
   where opencode
   where droid
   where codebuddy
   where copilot
   where qodercli
   where vibe-acp
   where nanobot
   where openclaw

2. Verify CLI is in system PATH

   • Ensure CLI tools are in system environment variable PATH
   • Restart terminal or command line window

3. Check CLI tool version

   claude --version
   qwen --version
   iflow --version
   goose --version
   auggie --version
   kimi --version
   opencode --version
   droid --version
   codebuddy --version
   copilot --version
   qodercli --version
   vibe-acp --version
   nanobot --version
   openclaw --version

4. Restart AionUi to re-detect

   • AionUi automatically scans system PATH on startup
   • Detects installed external CLI tools
   • Shows available Multi-Agent options on welcome interface

Q: Authentication failed?

A: Solutions:

1. Run claude login or qwen login in terminal
2. Complete CLI tool authentication process
3. Restart AionUi to reconnect

Q: Connection timeout?

A: Possible reasons:

1. Network connection issues
2. CLI tool service unavailable
3. Firewall blocking connection
4. CLI tool version too old

Q: Permission requests not showing?

A: Check configuration:

1. Confirm Multi-Agent Mode is properly connected
2. Check AionUi permission settings
3. Restart conversation to re-establish connection

---

📚 Related Documentation

• Quick Start: Getting Started
• LLM Configuration: LLM Configuration
• Image Generation Configuration: Image Generation Setup
• Common Questions: FAQ

---

Need Help?

• 🐛 Report Issues
• 💬 Community Discussions
• 📖 Complete Documentation

Multi-Agent Mode lets you enjoy the powerful functionality of multiple AI tools in AionUi!