HugAgentOS vs mateclaw
ZJU's self-hosted enterprise AgentOS on AgentScope 2.0: domain ontology as a control plane for agents, plus RAG, sub-agents, MCP, skills, sandbox, memory and approval-gated self-evolution. — versus — Self-hosted Java agent platform: ReAct plus plan-and-execute 'digital employees' with an LLM Wiki knowledge layer, skills/MCP/ACP tools, approval-gated actions and eight IM channels in one JAR.
mateclaw is the Java 'digital employees' platform with an LLM-wiki knowledge layer; HugAgentOS is the Python/AgentScope one with ontology as the knowledge layer.
| HugAgentOS | mateclaw | |
|---|---|---|
| Stars | 1.1k | 1.1k |
| Forks | 63 | 332 |
| Language | Python | Java |
| License | NOASSERTION | Apache-2.0 |
| Last activity | yesterday | 3 days ago |
| Topics | agents, knowledge-graphs, orchestration | agents, orchestration, memory |
| Curated connections | 5 | 6 |
HugAgentOS — the curator's take
Pick HugAgentOS when the pitch 'ontology as a machine-executable control plane' matters to you - governed concepts, relations, rules and action contracts feed the skill, memory and orchestration engines one shared business vocabulary, and self-evolution (memory, skills, orchestration) only lands after you approve it. One-command install with SQLite, Docker Compose for Postgres/Redis and a real sandbox. Caveats: the repo is a generated mirror of an upstream (`src/**` PRs not accepted), the licence is Apache-2.0 *plus* supplementary terms, and the Community Edition has no self-registration. If you don't care about ontology governance, maxkb or claraverse are more mature self-hosted workspaces; if you only want the ontology layer, context-ontology-accelerator or semantica are lighter.
mateclaw — the curator's take
Pick it when the buyer is an IT department rather than a hacker: multi-user workspaces, RBAC and approval gates on sensitive tool calls, audit trail, Spring Actuator health, per-channel error isolation, and provider failover across DashScope/OpenAI/Anthropic/Gemini/DeepSeek/Ollama when a vendor 401s mid-request. Underneath it's a real harness — StateGraph runtime, Team Runs with a durable runId, task DAGs, human approval — not a RAG call in a wrapper. The cost is weight and gravity: Java 21 + Spring Boot 3.5 + Vue, an enormous and fast-moving feature surface (workflows, triggers, Wiki transformations, Dream consolidation, skill mining), and a China-first channel set (DingTalk, Feishu, WeChat Work, QQ) whose value drops sharply outside that ecosystem. For a personal agent on a $5 VPS this is orders of magnitude too much machinery.