Active Agents
🌙 Clio
Main Orchestrator Agent
- Model
- GLM-5.2 (fallback: Kimi K2.6)
- Channel
- WebChat (primary), Discord
- Workspace
C:\Users\AI\.openclaw\workspace- Capabilities
- Memory management, heartbeat monitoring, agent routing, GitHub Projects, Facebook Ads API, Remotion video, browser automation
- GitHub
- ✅ Active
- Vercel
- ✅ Active
- Facebook Ads
- ✅ Connected
- Discord
- ✅ Connected
📊 superstarsaledev
Marketing Agent — Superstar Sale
- Server
- superstarsale (Discord)
- Capabilities
- YouTube transcript analysis, ad creative research, Facebook Ads campaigns, content publishing to GitHub
- GitHub
- ✅ Active
- Facebook Ads
- ✅ Connected
- YouTube Transcripts
- ✅ Available
🏢 headquartersdev
Infrastructure & Management Agent
- Server
- headquarters (Discord)
- Capabilities
- Tenant status board, documentation maintenance, infrastructure monitoring, GoHighLevel integration
- GitHub
- ✅ Active
- GoHighLevel
- ⚠️ Pending API key
🎮 surroundshowdev
SurroundShow Development Agent
- Server
- surroundshow (Discord)
- Capabilities
- Full-stack development for SurroundShow app (Convex + Next.js), Vercel deploys, linkall monorepo
- GitHub
- ✅ Active
- Convex
- ✅ Connected
- Vercel
- ✅ Auto-deploy
💰 almightydollardev
Almighty Dollar Development Agent
- Capabilities
- Full-stack development for Almighty Dollar app, Convex backend
- GitHub
- ✅ Active
- Convex
- ⚠️ Needs deploy key
Agent Harnesses
Specialized runtimes that orchestrators delegate to. Not full-time agents — spawned per-task.
⚡ Cursor
Code Agent — Multi-file edits, refactoring, component creation
- Model
- openai/gpt-5.2-codex
- Spawn
sessions_spawn(runtime="subagent", agentId="cursor", task="...")- Use for
- Code/logic/files tasks, multi-file edits, refactoring
- Discord Footer
Harness: cursor (gpt-5.2-codex)
👁️ Codex
Vision/UI Agent — Screenshots, computer-use, visual verification
- Model
- anthropic/claude-sonnet-4
- Spawn
sessions_spawn(runtime="acp", agentId="codex", task="...")- Use for
- Screenshots, UI tasks, GHL drag-drop builder, mobile preview, visual QA
- Discord Footer
Harness: codex (claude-sonnet-4)
Task Routing
Agents must analyze tasks and route automatically. Never ask the user which agent to use.
| Task Type | Route To | Method |
|---|
| Code / logic / files | Cursor | sessions_spawn(runtime="subagent", agentId="cursor") |
| Vision / screenshots / UI | Codex | sessions_spawn(runtime="acp", agentId="codex") |
| Planning / coordination | Self | Handle directly |
Model Disclosure in Discord
When responding in Discord, agents must include a model footer at the end of their message:
📍 Model: | Harness: ()
Examples:
📍 Model: GLM-5.2 | Harness: self — plain self only when every line of the shipped code was written by the agent itself📍 Model: GLM-5.2 | Harness: self (impl: grok-cli/grok-4.7) — a Grok CLI run wrote code that shipped (CLI default grok-4.7; use the model the run actually used)📍 Model: GLM-5.2 | Harness: cursor (gpt-5.2-codex)📍 Model: Kimi K2.6 | Harness: codex (claude-sonnet-4)
This gives Mike visibility into which models are doing the actual work.
Model Failover
Configured in openclaw.json:
"model": {
"primary": "glm/glm-5.2",
"fallbacks": ["moonshot/kimi-k2.6"]
}
If GLM rate limits, requests automatically fall over to Kimi K2.6.