Skip to main content
toolsSource-backed
NanoClaw logo

NanoClaw

Open-source platform that runs Claude agents in isolated per-session containers, connects them to messaging channels, keeps per-agent memory and scheduled tasks, and routes credentials through a vault so keys never enter containers.

by nanocoai · submitted by JPette1783·added 2026-06-05·
HarnessCLI
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://docs.nanoclaw.dev, https://github.com/nanocoai/nanoclaw, https://nanoclaw.dev
Brand
NanoClaw
Brand domain
nanoclaw.dev
Brand asset source
brandfetch
Safety notes
Agents run in OS-level container isolation (Docker or Apple Container) with explicit filesystem mounts; bash commands execute inside containers, not on the host., Each agent group gets its own container, isolated CLAUDE.md memory, and selective mounts, limiting what a single agent can reach., Scheduled tasks run Claude on a recurring basis and can message users automatically; review schedules and message permissions., Messaging channels are installed on demand and can send outbound messages on your behalf, so scope which channels and agents are enabled.
Privacy notes
API keys never enter containers; outbound requests route through OneCLI's Agent Vault, which enforces per-agent policies and rate limits., Messages flow through inbound/outbound SQLite databases rather than shared memory, and each agent group only accesses explicitly mounted directories., Channels can be configured for full per-channel privacy, unified memory with separate conversations, or a single shared session; choose the mode that matches your privacy needs., Running Claude through the Anthropic Agent SDK sends conversation context to Anthropic's API.
Author
nanocoai
Submitted by
JPette1783
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

4 prerequisites to line up before setup.

0/4 ready
Install & runtime2General2

Safety & privacy surface

Safety & privacy surface

4 safety and 4 privacy notes across 6 risk areas. Review closely: credentials & tokens, permissions & scopes, network access.

6 areas
  • SafetyLocal filesAgents run in OS-level container isolation (Docker or Apple Container) with explicit filesystem mounts; bash commands execute inside containers, not on the host.
  • SafetyGeneralEach agent group gets its own container, isolated CLAUDE.md memory, and selective mounts, limiting what a single agent can reach.
  • SafetyPermissions & scopesScheduled tasks run Claude on a recurring basis and can message users automatically; review schedules and message permissions.
  • SafetyPermissions & scopesMessaging channels are installed on demand and can send outbound messages on your behalf, so scope which channels and agents are enabled.
  • PrivacyCredentials & tokensAPI keys never enter containers; outbound requests route through OneCLI's Agent Vault, which enforces per-agent policies and rate limits.
  • PrivacyNetwork accessMessages flow through inbound/outbound SQLite databases rather than shared memory, and each agent group only accesses explicitly mounted directories.
  • PrivacyCredentials & tokensChannels can be configured for full per-channel privacy, unified memory with separate conversations, or a single shared session; choose the mode that matches your privacy needs.
  • PrivacyExecution & processesRunning Claude through the Anthropic Agent SDK sends conversation context to Anthropic's API.

Disclosure: editorial

Safety notes

  • Agents run in OS-level container isolation (Docker or Apple Container) with explicit filesystem mounts; bash commands execute inside containers, not on the host.
  • Each agent group gets its own container, isolated CLAUDE.md memory, and selective mounts, limiting what a single agent can reach.
  • Scheduled tasks run Claude on a recurring basis and can message users automatically; review schedules and message permissions.
  • Messaging channels are installed on demand and can send outbound messages on your behalf, so scope which channels and agents are enabled.

Privacy notes

  • API keys never enter containers; outbound requests route through OneCLI's Agent Vault, which enforces per-agent policies and rate limits.
  • Messages flow through inbound/outbound SQLite databases rather than shared memory, and each agent group only accesses explicitly mounted directories.
  • Channels can be configured for full per-channel privacy, unified memory with separate conversations, or a single shared session; choose the mode that matches your privacy needs.
  • Running Claude through the Anthropic Agent SDK sends conversation context to Anthropic's API.

Prerequisites

  • macOS or Linux, or Windows via WSL2.
  • Node.js 20+ and pnpm 10+.
  • Docker Desktop or Engine (or Apple Container on macOS) for container isolation.
  • Claude Code for skills and customization, plus Anthropic Agent SDK access.

Schema details

Install type
copy
Troubleshooting
No
Source repository stats
Scope
Source repo
Tool listing metadata
Pricing
open-source
Disclosure
editorial
Application category
DeveloperApplication
Operating system
macOS, Windows, Linux
Full copyable content
git clone https://github.com/nanocoai/nanoclaw.git nanoclaw-v2
cd nanoclaw-v2
bash nanoclaw.sh

About this resource

Overview

NanoClaw is a lightweight, open-source platform for running Claude agents safely. It orchestrates per-session agent containers that receive incoming messages, run Claude through Anthropic's Agent SDK, and deliver responses back through messaging channels. It is positioned as a security-focused alternative that gives agents only the access they explicitly need.

It is released under the MIT license and is primarily TypeScript, running on Node.js with Docker (or Apple Container on macOS) for isolation and SQLite for message storage.

Features

  • Per-session agent containers with OS-level isolation and selective mounts.
  • Multi-channel messaging: WhatsApp, Telegram, Discord, Slack, Teams, iMessage, Matrix, Gmail, and more, installed on demand.
  • Per-agent workspace with isolated CLAUDE.md memory.
  • Scheduled, recurring tasks that can run Claude and message users.
  • Web search and fetch from within agents.
  • Credential security: API keys never enter containers, routed via a vault.

Use Cases

  • Run Claude-powered assistants across messaging platforms with isolation.
  • Give each agent group its own sandboxed memory and filesystem scope.
  • Schedule recurring agent jobs that can notify users.
  • Keep credentials out of agent containers while still calling external APIs.

Installation

Clone the repository and run the setup script:

git clone https://github.com/nanocoai/nanoclaw.git nanoclaw-v2
cd nanoclaw-v2
bash nanoclaw.sh

Disclosure

Editorial listing. No paid placement or affiliate relationship. NanoClaw is open source under the MIT license.

Source citations

Add this badge to your README

Show that NanoClaw is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/tools/nanoclaw.svg)](https://heyclau.de/entry/tools/nanoclaw)

How it compares

NanoClaw side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Open-source platform that runs Claude agents in isolated per-session containers, connects them to messaging channels, keeps per-agent memory and scheduled tasks, and routes credentials through a vault so keys never enter containers.

Open dossier

Open-source infrastructure for securely running AI-generated code in isolated sandboxes that start in milliseconds, with SDKs for Python, TypeScript, and other languages, persistent snapshots, and an optional managed cloud.

Open dossier

Open-source infrastructure for running AI-generated code in secure, isolated cloud sandboxes, with Python and JavaScript SDKs, a Code Interpreter package, and self-hosting options.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backed
SubmitterJPette1783JPette1783JPette1783
Install riskReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandNanoClaw logoNanoClawDaytona logoDaytonaE2B logoE2B
Categorytoolstoolstools
SourceSource-backedSource-backedSource-backed
AuthornanocoaiDaytonaE2B
Added2026-06-052026-06-052026-06-05
Platforms
Harness
Source repo
Safety notesAgents run in OS-level container isolation (Docker or Apple Container) with explicit filesystem mounts; bash commands execute inside containers, not on the host. Each agent group gets its own container, isolated CLAUDE.md memory, and selective mounts, limiting what a single agent can reach. Scheduled tasks run Claude on a recurring basis and can message users automatically; review schedules and message permissions. Messaging channels are installed on demand and can send outbound messages on your behalf, so scope which channels and agents are enabled.Daytona is purpose-built to execute arbitrary, AI-generated code; only run untrusted code inside its isolated sandboxes, never on the host. Each sandbox has its own kernel, filesystem, and network stack, but sandboxes can make outbound network requests unless network limits are configured. Sandboxes support computer use, Git operations, and command execution; scope what an agent can do and review declarative builder configurations before use. Self-hosting runs runner compute nodes and Docker services that need elevated host privileges; isolate the deployment from production systems. Persistent snapshots retain sandbox filesystem state across sessions, which can preserve secrets or sensitive files written during execution.E2B is built to execute arbitrary, AI-generated code; run such code only inside its isolated cloud sandboxes, never directly on a developer machine. Sandbox network and filesystem access depend on configuration; review and restrict sandbox capabilities before running untrusted code. Generated code can still perform destructive or unexpected actions within a sandbox, so treat sandbox outputs and side effects with caution. Self-hosting deploys cloud infrastructure via Terraform that you are responsible for securing, patching, and isolating from production systems.
Privacy notesAPI keys never enter containers; outbound requests route through OneCLI's Agent Vault, which enforces per-agent policies and rate limits. Messages flow through inbound/outbound SQLite databases rather than shared memory, and each agent group only accesses explicitly mounted directories. Channels can be configured for full per-channel privacy, unified memory with separate conversations, or a single shared session; choose the mode that matches your privacy needs. Running Claude through the Anthropic Agent SDK sends conversation context to Anthropic's API.Using the managed cloud sends your code, files, and execution data to Daytona-operated infrastructure; review their terms before processing sensitive data. The platform emits OpenTelemetry metrics, log streaming, and audit logs that can capture command output and activity. API keys grant access to your sandboxes and organization; store them as secrets and never commit them to source control. Self-hosting keeps execution data on your own infrastructure but you become responsible for log retention, access control, and isolation.On the managed cloud, your code and execution data are sent to and run on E2B-operated infrastructure; review their privacy terms before processing sensitive data. API keys grant access to your sandboxes; store them in environment variables or a secrets manager and never commit them to source control. Data passed into a sandbox (files, inputs, environment variables) lives in that sandbox for its lifetime; avoid sending secrets you do not need there. Self-hosting keeps execution data on your own infrastructure, making log retention, access control, and isolation your responsibility.
Prerequisites
  • macOS or Linux, or Windows via WSL2.
  • Node.js 20+ and pnpm 10+.
  • Docker Desktop or Engine (or Apple Container on macOS) for container isolation.
  • Claude Code for skills and customization, plus Anthropic Agent SDK access.
  • A Daytona Cloud account and API key for the managed service, or self-hosted infrastructure for the open-source platform.
  • Python 3.8+ for the `daytona` SDK or Node.js 18+ for the `@daytona/sdk` TypeScript SDK.
  • Docker and Docker Compose to run supporting services (PostgreSQL, Redis) when self-hosting.
  • Nix with flakes enabled or a devcontainer-compatible editor for local development of the platform itself.
  • An E2B account and API key from the dashboard, set as the `E2B_API_KEY` environment variable, for the managed cloud.
  • Python 3.8+ for the `e2b` / `e2b-code-interpreter` SDK, or Node.js 18+ for the `e2b` / `@e2b/code-interpreter` SDK.
  • Self-hosting requires Terraform and a supported cloud provider to deploy the sandbox infrastructure.
Install
Config
Citations
ClaimUnclaimedUnclaimedUnclaimed
Open 3 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.