Installation
Viben CLI is the command-line interface for Agent Swarm x Code Evolution - orchestrating AI agent swarms for continuous code improvement through FileEvo, intelligent task management, and idea generation.
Install globally via npm/pnpm, or build from source for development.
Quick Installation
Using npm
npm install -g @viben/cli
Using pnpm
pnpm add -g @viben/cli
Using npx (No Installation Required)
Run directly without installing:
npx @viben/cli --help
System Requirements
| Requirement | Version |
|---|---|
| Node.js | 18.0 or higher |
| npm | 9.0 or higher (or pnpm 8.0+) |
Check Environment
# Check Node.js version
node --version
# Check npm version
npm --version
Verify Installation
After installation, verify that Viben CLI is correctly installed:
viben --help
You should see output similar to:
Usage: viben <command> [options]
Bootstrap CLI for Viben - Configure apps, manage services, and query status.
Commands:
init Initialize workspace in current directory
config Configuration management (git-style)
service Manage background services
gateway Start Gateway
executor Discover and view executors
agent Manage agent instances and templates
provider Manage API providers
model Manage models, aliases, and fallback chains
mcp Manage MCP servers
skill Manage skills
channel Manage chat channels
cron Manage scheduled tasks
team Team collaboration workspace management
workspace Workspace operations
version Show version information
help Show help
Options:
--json Output JSON
--global, -g Use global configuration
--workspace Use workspace configuration
-n, --name <id> Specify agent name/ID
--verbose, -v Verbose output
--quiet, -q Suppress non-essential output
--help, -h Show help
Check version:
viben version
Install from Source (Development)
For developers who want to modify the CLI or contribute code:
1. Clone Repository
git clone https://github.com/LinXueyuanStdio/viben.git
cd viben
2. Install Dependencies
pnpm install
3. Build CLI
pnpm build --filter=@viben/cli
4. Link for Local Development
cd apps/cli
pnpm link --global
Now you can use the viben command globally, and changes will take effect after rebuilding.
5. Development Mode
For active development with automatic rebuilding:
cd apps/cli
pnpm dev
Configuration Location
After installation, Viben CLI stores its configuration in:
| Platform | Location |
|---|---|
| macOS/Linux | ~/.viben/ |
| Windows | %USERPROFILE%\.viben\ |
The configuration directory is automatically created on first use.
Directory Structure
~/.viben/
├── config.yaml # Global configuration
├── providers.yaml # API provider configuration
├── models.yaml # Model configuration
├── channels.yaml # Channel configuration
├── cron.yaml # Scheduled task configuration
├── agents/ # Agent instances
├── mcp/ # Shared MCP servers
└── skills/ # Shared skills
Updating
npm
npm update -g @viben/cli
pnpm
pnpm update -g @viben/cli
From Source
cd viben
git pull
pnpm install
pnpm build --filter=@viben/cli
Uninstalling
npm
npm uninstall -g @viben/cli
pnpm
pnpm remove -g @viben/cli
Clean Up Configuration (Optional)
To remove all configuration and data:
# macOS/Linux
rm -rf ~/.viben
# Windows (PowerShell)
Remove-Item -Recurse -Force $env:USERPROFILE\.viben
Removing the .viben directory will delete all agent configurations, memory, and sessions. Make sure to backup important data first.
Troubleshooting
Command Not Found
If the viben command is not found after installation:
-
Check PATH: Ensure npm global bin directory is in your PATH
# Find npm global bin directorynpm bin -g# Add to PATH (bash/zsh)export PATH="$(npm bin -g):$PATH" -
Restart Terminal: Close and reopen terminal after installation
-
Reinstall: Try reinstalling with verbose output
npm install -g @viben/cli --verbose
Permission Errors
On macOS/Linux, if you encounter permission errors:
# Option 1: Use sudo (not recommended)
sudo npm install -g @viben/cli
# Option 2: Fix npm permissions (recommended)
mkdir -p ~/.npm-global
npm config set prefix '~/.npm-global'
export PATH=~/.npm-global/bin:$PATH
npm install -g @viben/cli
Version Conflicts
If you have multiple Node.js versions, use a version manager:
# Using nvm
nvm use 18
npm install -g @viben/cli
Next Steps
- Quick Start - Initialize and configure your first workspace