Install
From zero to a running daemon in under five minutes.
Prerequisites
- Node.js 20+ —
node --version - Claude Code CLI (for
claude-codetier agents) — install guide. Other providers (OpenAI, Ollama) don't require it. - A channel credential: a Telegram bot token from @BotFather, a Discord bot token, a GitLab API token, or a WhatsApp session. Telegram is the fastest to get started.
1. Install the CLI
bash
npm install -g agentix-cli
agentx --versionPackage name
The npm package is agentix-cli; the CLI binary is agentx.
2. Initialize a workspace
bash
mkdir my-agentx && cd my-agentx
agentx initThis creates:
agentx.json— the main config file.env— template for secrets (loaded automatically at startup).agentx/— runtime data directory (sessions, wiki, cron logs — gitignored)
3. Add your first agent
bash
agentx agent addYou'll be asked for:
| Prompt | What it means |
|---|---|
| ID | Short slug, e.g. support |
| Name | Display name, e.g. Support Assistant |
| Workspace | Directory for this agent's CLAUDE.md, skills, MCP config. Defaults to ./agents/<id> |
| Tier | claude-code uses the claude CLI (subscription); sdk uses the Claude Agent SDK (API key); orchestrator uses AgentX's built-in loop with any LLM provider |
| Model | e.g. claude-sonnet-4-6, claude-haiku-4-5 |
| Mentions | Handles that route to this agent, e.g. @support_bot, @support |
An agent is just a directory with configuration files. No code required.
4. Add a channel
bash
agentx channel addPick one:
text
- Account name (free label): default
- Bot token: <from @BotFather>
- Bind to agent: <your agent>text
- Bot token: <from Discord Developer Portal>
- Bind to agent: <your agent>text
- GitLab host: https://gitlab.com (or self-hosted)
- API token: <personal access token>
- Webhook port: 18811
- Secret: <random string>
- Project routes: <project_id>:<agent_id>text
- Default agent: <your agent>
- Session dir: .agentx/whatsapp-sessions
- First run prints a QR code — scan with WhatsApp on your phone5. Start the daemon
bash
agentx daemon startYou'll see each channel come up, each agent register, and (if configured) mesh peers health-check.
Watch it live
In a second terminal:
bash
agentx daemon watchColor-coded activity feed:
text
10:31:08 → Routing [telegram/You] -> "Support": Hello!
10:31:08 ▶ [support] executing task (1/2)
10:31:15 ✓ [support] completed in 7234ms6. Verify
bash
agentx daemon status # PID, channels, agents, crons, mesh peers
agentx config check # Validate agentx.json + workspaces
agentx config show # Print resolved configurationDM your Telegram bot — the reply should arrive within a couple of seconds.
Run in the background
bash
agentx daemon start --detachFor auto-start on boot, use systemd (Linux) or launchd (macOS). A minimal systemd unit:
ini
[Unit]
Description=AgentX Daemon
After=network.target
[Service]
Type=simple
User=your-user
WorkingDirectory=/path/to/your/agentx
ExecStart=/usr/bin/node /path/to/agentx/dist/cli.js daemon start
Restart=always
RestartSec=5
[Install]
WantedBy=multi-user.target