Player profile
NanoClaw
An MIT-licensed personal AI assistant that runs Claude agents in isolated containers, connects to chat channels, keeps memory, schedules work, and uses skills as git branches.
Profile
Where it fits
NanoClaw is a lightweight personal Claude assistant that runs agents in their own Linux containers, connects to Telegram, Discord, WhatsApp, Slack, Gmail, and local CLI channels, keeps persistent conversation memory, and supports scheduled tasks.
It belongs in Open Orchestrators because it takes the OpenClaw-style personal assistant shape and makes the control surface smaller, more inspectable, and more isolation-first: one process, explicit mounts, containerized agent execution, and skills distributed as git branches.
Builder web analytics
Measure projects built with NanoClaw
NanoClaw can run scheduled and chat-driven agent work from a small, container-isolated assistant. Agent Analytics gives those workflows user-facing outcome data after the agent ships changes.
Install Agent Analytics around the project surface NanoClaw changes first. Agent Analytics measures the website, docs, app, or funnel outcomes; it does not replace NanoClaw memory, container logs, or chat history.
First loop to measure
- a NanoClaw assistant ships a website, docs, onboarding, support, or install-flow change
- the changed surface reports visits, sources, CTA clicks, signup, activation, retention, or task-completion events to Agent Analytics
- a scheduled NanoClaw task fetches the Agent Analytics results
- the assistant reports what moved users toward value and proposes the next container-isolated improvement
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including NanoClaw-managed page, traffic source, CTA click, signup, activation event, retention signal, or scheduled workflow outcome. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which NanoClaw-managed page, traffic source, CTA click, signup, activation event, retention signal, or scheduled workflow outcome moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.Related