mercury-agent vs nanoclaw
Self-hosted AI assistants compared
mercury-agent and nanoclaw are self-hosted TypeScript assistants that connect agents to messaging and scheduled tasks. mercury-agent offers a broad set of interfaces and built-in tools, while nanoclaw emphasizes container isolation and customization through code and skills.

mercury-agent: Run a Permission-Aware AI Agent Across Channels
Mercury is a self-hosted AI agent for CLI, Telegram, and web use, with permission prompts, persistent memory, token budgets, and scheduled tasks. It suits people who want an always-on assistant they can configure and operate locally.

nanoclaw: Run Claude Agents in Isolated Containers
NanoClaw is a lightweight, customizable AI assistant built on Anthropic’s Claude Agent SDK. It runs agents in isolated containers and connects them to messaging apps on macOS, Linux, or Windows via WSL2.
| mercury-agent | nanoclaw | |
|---|---|---|
| Language | TypeScript | TypeScript |
| License | MIT | MIT |
| Stars | 3.2k | 31.1k |
| Forks | 341 | 12.7k |
| Last analyzed | Oct 3, 2026 | Nov 2, 2026 |
Key differences
- mercury-agent provides CLI, Telegram, and a local web dashboard; nanoclaw routes messages through supported channels to agent sessions.
- mercury-agent includes approval controls, folder-level permissions, token budgets, and built-in tools; nanoclaw runs agents in Docker containers with explicitly mounted files and credentials kept outside containers.
- mercury-agent includes persistent memory, scheduling, and Kanban task boards; nanoclaw focuses on per-agent memory, scheduled tasks, and channel-to-agent arrangements.
- mercury-agent supports Node.js 20 or later for npm installation and offers standalone installers; nanoclaw expects Node.js 22 or newer and Docker support for containerized agents.
- mercury-agent has 3.2k stars and 341 forks; nanoclaw has 30.9k stars and 12.8k forks, and its listed latest release is a prerelease.
- mercury-agent is suited to users configuring a feature-rich assistant; nanoclaw is aimed at technically comfortable users who prefer adapting code over relying on extensive configuration. Both use TypeScript and the MIT license.
Choose mercury-agent if you…
- need CLI, Telegram, and a local web dashboard for one assistant.
- want built-in approval controls, token budgets, and a choice of tools including shell, Git, and scheduling.
- prefer a configurable assistant with persistent memory and Kanban task boards.
Choose nanoclaw if you…
- want agents isolated in Docker containers with explicitly allowed file mounts.
- prefer customizing the project directly in code and adding installable skills.
- need separate agent workspaces and memories, or scheduled tasks delivered through messaging channels.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.