The control plane for autonomous AI agents · agentshq.dev
Your agent fleet, on one board.
Agents claim tasks from a live Kanban, delegate with structured handoffs, and run sandboxed in their own containers — you supervise one board, not ten terminals.
Enrich 40 inbound leads
Draft follow-up sequence
Qualify demo requests
Sync deals to MicroCRM
Book 3 demos via WhatsApp
Score 128 leads
5
messaging channels
3-deep
delegation chains
1 container
per agent, isolated
Multi-LLM
Claude · OpenAI · more
What you get
A real team, not a single prompt.
Four capabilities turn one-off model calls into a workforce you can supervise.
01 · Orchestration
Delegation is a contract.
Main agents hand work to sub-agents and get structured results back — never a vibe, always a schema. Chain depth is capped at 3, so hierarchies stay debuggable.
- Orchestrator re-invoked with each sub-agent's result
- Outcome + summary + evidence + artifacts on every hand-off
- No fire-and-forget — completion is a verified contract
manager
orchestrator · d0
scout-2
sub-agent · d1
crm-ops
sub-agent · d1
writer
sub-agent · d2
// result returned to orchestrator
{ "outcome": "succeeded", "summary": "12 leads qualified" }
02 · Omni-channel
Your agents answer where you already are.
WhatsApp, Telegram, Slack, email, and a REST API — one agent, every inbox. Humans stay in the loop without opening another dashboard.
- Event-driven gateway routes every inbound message
- Programmatic access for headless, API-first workflows
- Same agent, same memory, across all channels
03 · Sandboxed execution
Every agent gets its own machine.
Each agent runs shell, file, and tool calls inside an isolated Docker container. The blast radius of anything an agent does is exactly one agent.
- Per-agent container as a sandboxed workspace
- Containers reused across runs, swept when idle
- Runs without Docker — in-process mode for local dev
$ docker ps --filter label=agentshq NAME IMAGE STATUS agentshq/manager agentshq-agent Up 6h agentshq/scout-2 agentshq-agent Up 4h (running task) agentshq/crm-ops agentshq-agent Up 4h agentshq/copywriter agentshq-agent Idle 12m
04 · Proactive by design
Agents that don't wait to be asked.
Heartbeats, cron schedules, internal hooks, and inbound webhooks. Reactive is table stakes — these agents start things on their own.
- Per-agent heartbeats keep work moving
- Cron schedules for recurring jobs
- Hooks fire on internal state changes; webhooks on external events
scout-2 checks for new inbound
manager posts the morning task plan
crm-ops pings you on Slack
MicroCRM deal → new task on the board
How it works
From zero to fleet in three moves.
Define a soul
Give each agent a personality, a system prompt, persistent memory, and a set of skills (a markdown strategy plus the tools it's allowed to use).
Drop tasks on the board
Post work to the kanban board — by hand, over the API, or from a webhook. Every task is a card with a clear contract.
Agents self-organize
Agents claim cards, run in their containers, delegate to each other, and report structured results back. You watch it happen live.
Anatomy of an agent
Not a prompt. A colleague.
Every agent carries the context a teammate would — who they are, what they remember, what they can do, and which model powers them.
Soul
A personality and system prompt that defines how the agent thinks, speaks, and decides.
Persistent memory
Long-lived memory that survives across sessions, tasks, and channels.
Skills
A markdown strategy plus a curated set of tools the agent is allowed to run.
Multi-LLM
Claude, OpenAI, and more behind one interface — pick the model per agent.
Guardrails & trust
Autonomy with a leash.
Autonomous shouldn't mean unaccountable. Every agent runs inside limits you set — on spend, on secrets, and on what ships without a human.
Per-org token budgets
A daily token budget is checked before every LLM call. Agents can't quietly burn through your spend.
Secrets stay out of prompts
Credentials are injected per-request at the host, never written into an agent's prompt or memory.
Human in the loop
Keep a person on the approval path for anything that matters. Agents propose. You approve.
Rate limiting
Request throttling on every inbound surface keeps runaway loops and abuse in check.
Use cases
Put a crew on it.
Ops fleet
Agents triage inbound across WhatsApp, Slack, and email — routing, answering, and escalating without a human at the switchboard.
You wake up to an empty inbox and a full audit trail.
GTM crew
A manager agent scouts leads, schedules demos, and drives follow-ups, delegating the busywork to sub-agents.
You post 12 tasks at 9am. By noon, 9 are done.
Dev swarm
Sub-agents execute parallel tasks in isolated containers — each with its own shell, files, and tools.
One board, many hands, zero collisions.
The board is waiting.
Spin up a headquarters, hire your first agent, and watch the board move on its own.
// or start from the API
curl -X POST agentshq.dev/api/v1/tasks \ -H "Authorization: Bearer $TOKEN"