mateclaw vs Octop
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. — versus — Tencent Cloud's self-hosted, multi-user AI assistant: per-user expert agents, AgentTeams, memory, RAG and connectors, served as one process to a web dashboard, CLI and 8+ IM channels.
Closest twin: both are self-hosted 'digital employee' platforms with a knowledge layer, skills/MCP/ACP tools, approval-gated actions and many IM channels in one deployable. MateClaw is a single Java JAR; Octop is Python with multi-user isolation and a Tencent connector suite.
| mateclaw | Octop | |
|---|---|---|
| Stars | 1.2k | 12k |
| Forks | 357 | 1.6k |
| Language | Java | Python |
| License | Apache-2.0 | MIT |
| Last activity | yesterday | yesterday |
| Topics | agents, orchestration, memory | agents, orchestration |
| Curated connections | 8 | 4 |
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.
Octop — the curator's take
Built for a household or small team that wants one box everyone talks to: JWT-isolated users, an expert library to switch specialists per task, and reach through Feishu, DingTalk, QQ, WeChat, WeCom, Telegram or Discord without wiring each bot. Strongest fit inside the China IM/Tencent ecosystem (Docs, Meeting connectors); the extras — browser sessions, remote desktop, ACP delegation to Claude Code/OpenCode — make it a personal ops console, not just chat. Skip it if you want a library to build agents with (it is a product), if you only need one user on one channel (a single-binary bot is lighter), or if beta AgentTeams orchestration is your main reason to adopt.