Best for
- Developers and teams who want to monitor and command AI coding agents from anywhere.
- Users who need to run multiple long-running tasks with automatic crash recovery.
- Users who prefer Telegram or Discord as their control interface.
A
30FMRS · D
AgEnD offers a powerful multi-agent management solution, but be aware of its maintenance mode and security risks. Suitable for experienced users to significantly boost remote development efficiency.
AgEnD (Agent Engineering Daemon) turns your Telegram or Discord into a command center for AI coding agents. One bot, multiple CLI backends, unlimited projects — each running as an independent session with crash recovery and zero babysitting. It supports backends like Claude Code, Gemini CLI, Codex, OpenCode, and Kiro CLI, and allows agents to collaborate peer-to-peer via MCP tools. Note: the project is in maintenance mode; active development has moved to the Rust rewrite agend-terminal.
Tools
The tool list has not been reviewed yet.
Setup
One-liner (macOS/Linux):
curl -fsSL https://suzuke.github.io/AgEnD/install.sh | bashOr install manually:
npm install -g @suzuke/agend
agend quickstart
agend fleet startRequires Node.js >= 20, tmux, at least one supported AI coding CLI, and a Telegram or Discord bot token.
Fit and risk
Not for
- Users looking for an officially maintained MCP server (AgEnD is not an official product).
- Users who need native Windows support (only macOS and Linux are supported).
- Users who want new features without breaking changes (new features are in pre-alpha agend-terminal).
Required permissions
- All CLI backends run with --dangerously-skip-permissions (or equivalent), meaning agents can execute arbitrary code.
- Access to the file system, network, and command execution is required.
- Optional: Groq API key for voice message transcription.
Risks and side effects
- Agents run with full permissions, posing security risks from mistakes or malicious instructions.
- Cost risk: Without daily spending limits, agents might incur unexpected charges.
- The project is in maintenance mode, so new features are not developed and vulnerabilities may remain unfixed.
Troubleshooting
- Ensure Node.js >= 20 and tmux are installed.
- Check that the Telegram bot token is correct and the bot is added to the desired chat.
- If using WSL, set appendWindowsPath=false in /etc/wsl.conf and restart WSL.
- Check logs with `agend logs` or inspect system service status.
Use cases
Remotely manage multiple AI coding projects from your phone.
Isolate sessions via Telegram forum topics for parallel development.
Enable multiple agents to collaborate on complex tasks via MCP tools.
Supported clients
Supported clients have not been confirmed yet.