nanoclaw and clawe
One system provides an individual containerized AI agent with various messaging integrations and memory, while the other is a coordination system designed to manage and organize multiple instances of the first, making them **complements**.
About nanoclaw
qwibitai/nanoclaw
A lightweight alternative to OpenClaw that runs in containers for security. Connects to WhatsApp, Telegram, Slack, Discord, Gmail and other messaging apps,, has memory, scheduled jobs, and runs directly on Anthropic's Agents SDK
Implements per-group filesystem isolation and credential injection through OneCLI's Agent Vault, preventing agents from accessing raw API keys or other groups' data. Built as a single Node.js process with self-registering channel adapters that route messages through a per-group queue into containerized Claude agents via stdio transport. Designed for direct code modification over configuration—users fork the repo and ask Claude Code to customize behavior rather than manage sprawling config files.
About clawe
getclawe/clawe
Multi-agent coordination system: think Trello for OpenClaw agents.
Leverages Convex for persistent backend state and Anthropic/OpenAI for agent reasoning, with agents waking on cron schedules to process Kanban-style tasks through a CLI interface. Each agent maintains isolated workspaces with persona definitions (SOUL.md, HEARTBEAT.md) while sharing context through symlinked team state files. Real-time notifications and task updates flow through a dedicated watcher service that coordinates the multi-agent workflow across Docker-containerized squadhub gateway, backend, and web dashboard.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work