HiClaw

Open-source Agent Teams system that deploys coordinated AI agent teams within 5 minutes. A Manager Agent orchestrates Worker agents with all communication visible in Matrix IM. Workers never hold real API keys — the Higress MCP Gateway manages credentials separately for security.

Evaluated Mar 08, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ AI & Machine Learning agent-teams multi-agent matrix mcp-gateway human-in-the-loop docker orchestration
⚙ Agent Friendliness
62
/ 100
Can an agent use this?
🔒 Security
71
/ 100
Is it safe for agents?
⚡ Reliability
45
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
62
Documentation
72
Error Messages
55
Auth Simplicity
70
Rate Limits
45

🔒 Security

TLS Enforcement
65
Auth Strength
75
Scope Granularity
70
Dep. Hygiene
60
Secret Handling
80

Good credential isolation model. Workers use consumer tokens, gateway holds real keys. Self-hosted Docker. New project — limited security track record.

⚡ Reliability

Uptime/SLA
40
Version Stability
50
Breaking Changes
40
Error Recovery
50
AF Security Reliability

Best When

You need a multi-agent system with built-in communication, human oversight, and secure credential management — and want it running in under 5 minutes with Docker.

Avoid When

You need a lightweight single-agent setup, or your organization requires Slack/Teams integration rather than Matrix.

Use Cases

  • Deploying multi-agent teams with human-in-the-loop oversight via instant messaging
  • Running coordinated AI workflows where agents need access to external services (GitHub, etc.) through secure gateway
  • Setting up agent infrastructure with built-in credential isolation — workers only carry consumer tokens
  • Enabling non-technical stakeholders to observe and interact with agent activities via Matrix clients

Not For

  • Single-agent use cases where orchestration overhead is unnecessary
  • Environments without Docker (requires Docker Desktop/Engine)
  • Teams already invested in Slack/Teams bot infrastructure (uses Matrix instead)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: api_key
OAuth: No Scopes: No

Admin credentials generated during installation. Workers receive consumer tokens from Manager Agent — never real API keys. MCP Gateway handles actual service credentials.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Apache 2.0 licensed. Self-hosted. Requires Docker infrastructure.

Agent Metadata

Idempotent
Unknown
Retry Guidance
Not documented

Known Gotchas

  • Very new project (Feb 2026) — expect rapid changes and potential instability
  • Requires Docker with 2 CPU cores and 4GB RAM minimum (8GB recommended)
  • Uses Matrix for communication instead of Slack/Teams — may not integrate with existing workflows
  • MCP access is through Higress Gateway — adds infrastructure complexity
  • 53 open issues suggest active development but also unresolved problems

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for HiClaw.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-08.

6961
Packages Evaluated
25669
Need Evaluation
173
Need Re-evaluation
Community Powered