NanoClaw

Shipping NanoClaw Skills as npm Packages

NanoClaw wants capabilities as skills, not core PRs. The maintainers are busy, and skill PRs sit in a long queue. Here is how I ship npm packages that install skills into my fork, and keep install and uninstall idempotent.

Launching NanoClaw Agents on External Hosts

I use NanoClaw as my agent orchestration layer, but not only on local Docker. Here is why I implemented mailbox IO and agent container abstractions, and how these unlock Fly Machines, native process spawn, and the next agent container runtime without forking NanoClaw core.

Extending NanoClaw Without Forking the Host

NanoClaw keeps the trunk small on purpose. Here's how I add a local chat desk, live activity traces, and an admin API as installable skills, and why hosthooks is the extension layer underneath them.

Meet My NanoClaw Agent Team

Four specialized AI agents review PRs, file bugs, and ship code across BeakerStack, Skein, and the NanoClaw packages. Here is who they are, and the GitHub profiles where you can see the work.

Why I Chose NanoClaw Instead of OpenClaw

I wanted agents with real tools and a blast radius I could live with. NanoClaw puts isolation in the kernel, not in an allowlist, and that is why I run it.