AI agents can now receive Slack messages and route them to containerized OpenClaw instances
A new agent system lets users create AI agents through a setup form, configure messaging platforms like Slack, and have messages automatically routed to containerized OpenClaw instances running on a VPS. A status dashboard provides real-time visibility into agent health and execution history.
This PR introduces an AI agent platform that runs on existing infrastructure. Users can now create agents through a setup form at /agents/setup, selecting their model (Claude or GPT), messaging platform (Slack, Discord, or Telegram), and enabling specific tools like web search, code execution, or API calls.
The system stores agent configuration in the database and routes incoming Slack messages to containerized OpenClaw instances. When a Slack message arrives at the webhook endpoint, it's matched to an agent based on workspace ID and then forwarded to the appropriate container running at a specific IP and port. The agent's response is then sent back to Slack via webhook.
A status dashboard at /agents/{agentId}/status shows configuration details, recent executions with timing data, and health check history. The provisioning system assigns ports starting at 8001 and tracks container metadata.
This work includes a significant brand transition from Trigger.dev to AirTrigger, with updated logos, email templates, UI copy, and domain references. The visual design has also shifted from a dark charcoal theme to a lighter gray palette.
View Original GitHub Description
Summary
Build Phase 1 MVP for AI agent platform:
- Users create agents through setup form (/agents/setup)
- Agents stored in database with configuration (model, platform, tools)
- Slack webhook receives messages and routes to containers on VPS
- Status dashboard shows agent health and execution history
- Database models: AgentConfig, AgentExecution, AgentHealthCheck
Key Features
- Agent Setup: Configure model, messaging platform, tools, Slack integration
- Webhook Handler: Receives Slack events, routes to OpenClaw containers at 178.128.150.129:{port}
- Provisioning: Assigns container ports (8001+), stores metadata
- Status Dashboard: Real-time visibility into agent health and recent executions
- Health Monitoring: Tracks container status and response times
Known Limitations
- Docker provisioning not yet implemented (currently stores port assignments only)
- Actual container startup will require SSH to VPS + docker run commands
- Need to verify OpenClaw /api/message endpoint format
Files Changed
- Database: Added AgentConfig, AgentExecution, AgentHealthCheck models
- Routes: agents.setup.tsx, agents.$agentId.status.tsx, api.agents.provision.ts, webhooks.slack.ts
- Fixes: VPS IP routing, removed axios dependency, proper fetch API usage