setup
Skill1 starsChanged 9 months agoMITView on GitHub
Run initial NanoClaw setup. Use when user wants to install dependencies, authenticate WhatsApp, register their main channel, or start the background services. Triggers on "setup", "install", "configure nanoclaw", or first-time setup requests.
- Reads credentials
- Deletes or force-pushes
- Installs packages
192 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- openstory-so/openstorytheir own version, first seen Nov 16, 2026
- furkandvrc/conductortheir own version, first seen Nov 16, 2026
- futorio/red-greentheir own version, first seen Nov 16, 2026
- JCodesMore/jobs-for-ai-agentstheir own version, first seen Nov 16, 2026
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
Used with
Projects with it also use add-atomic-chat-tool, add-dashboard and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkilladd-atomic-chat-tool
Add Atomic Chat MCP server so the container agent can call local models served by the Atomic Chat desktop app via its OpenAI-compatible API.
Also in 8 projects that use this
MicrosoftSkilladd-dashboard
Add a monitoring dashboard to NanoClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.
Also in 8 projects that use this
- +10 more from microsoft
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- gavrielc/nanoclaw★ 31k22% same
- nanocoai/nanoclaw★ 31k22% same
- qwibitai/nanoclaw★ 31k22% same
- Runchuan-BU/BioClaw★ 40595% same
- microsoft/amplifier-app-nanoclaw★ 522% same
- 0-CYBERDYNE-SYSTEMS-0/FFT_nano★ 456% same
Wrote their own version · 186
- anthropics/knowledge-work-plugins★ 36ksame name
- garrytan/gbrain★ 33ksame name
- Q00/ouroboros★ 6.4ksame name
- pytorch/executorch★ 5.2ksame name
- aws/agent-toolkit-for-aws★ 3.5ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
- skyllwt/OmegaWiki★ 1.7ksame name
- DAIR-AutoResearch/AutoSci★ 1.7ksame name
- PKU-DAIR/AutoSci★ 1.7ksame name
176 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-gmailSkill
- add-mcp-skeletonSkill
- add-parallelSkill
- add-telegramSkill
- add-telegram-swarmSkill
- add-voice-transcriptionSkill
- convert-to-dockerSkill
- customizeSkill
- debugSkill
- pr-reviewSkill
- setup-macmini-24x7Skill
- setup-minimaxSkill
- x-integrationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
35 rules. 0 are common, 14 are distinctive, and 21 are very specific to this project.
0
Common
Most of the 169 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
21
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 8
Run all commands automatically.
- Very specific: line 10
UX Note: When asking the user questions, prefer using the AskUserQuestion tool instead of just outputting text.
- Distinctive: line 41
If Apple Container is NOT installed: Ask the user:
- Distinctive: line 60
Wait for user confirmation, then verify:
- Very specific: line 92
If they give you the token, add it to .env.
- Distinctive: line 100
Ask if they have an existing key to copy or need to create one.
- Distinctive: line 130
Verify the build succeeded by running a simple test (this auto-detects which runtime you're using):
- Very specific: line 171
Run this with run_in_background: true.
- Very specific: line 179
If already_authenticated, skip to the next step.
- Distinctive: line 181
If QR data is ready, generate the QR as SVG and inject it into the HTML template:
- Very specific: line 214
If authenticated, success — clean up with rm -f store/qr-auth.html and continue.
- Very specific: line 215
If failed:qr_timeout, offer to retry (re-run the auth and regenerate the HTML page).
- Very specific: line 216
If failed:logged_out, delete store/auth/ and retry.
- Very specific: line 220
Ask the user for their phone number (with country code, no + or spaces, e.g.
- Very specific: line 252
If authenticated or already_authenticated, success — continue to next step.
- Very specific: line 254
If failed:515 or timeout, the 515 reconnect should handle this automatically.
- Distinctive: line 268
Wait for the user to confirm authentication succeeded, then continue to the next step.
- Distinctive: line 306
If they choose option 4, ask a follow-up:
- Very specific: line 338
Ask the user for the phone number (with country code, no + or spaces, e.g.
- Very specific: line 372
Write to the database directly by creating a temporary registration script, or write data/registered_groups.json which will be …
- Very specific: line 380
If the user chose a name other than Andy, also update:
- Distinctive: line 384
Ensure the groups folder exists:
- Distinctive: line 398
If no, create an empty allowlist to make this explicit:
- Distinctive: line 414
If yes, ask follow-up questions:
- Distinctive: line 442
Create the allowlist file based on their answers:
- Distinctive: line 552
Verify it's running:
- Very specific: line 573
Service not starting: Check logs/nanoclaw.error.log
- Distinctive: line 576
Ensure the container runtime is running:
- Very specific: line 579
Check container logs: cat groups/main/logs/container-*.log | tail -50
- Very specific: line 582
Verify the trigger pattern matches (e.g., @AssistantName at start of message)
- Very specific: line 585
Check that the chat JID is in the database: sqlite3 store/messages.db "SELECT * FROM registered_groups"
- Very specific: line 586
Check logs/nanoclaw.log for errors
- Very specific: line 590
Check logs for Translated LID to phone JID — if missing, the LID isn't being resolved
- Very specific: line 592
Verify the registered JID doesn't have a device suffix (should be number@s.whatsapp.net, not number:0@s.whatsapp.net)
- Very specific: line 596
Run npm run auth to re-authenticate
“Common” is measured: kept by at least 6 in 10 of the 169 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
NanoClaw Setup
Run all commands automatically. Only pause when user action is required (WhatsApp authentication, configuration choices).
UX Note: When asking the user questions, prefer using the AskUserQuestion tool instead of just outputting text. This integrates with Claude's built-in question/answer system for a better experience.
1. Install Dependencies
npm install2. Install Container Runtime
First, detect the platform and check what's available:
echo "Platform: $(uname -s)"
which container && echo "Apple Container: installed" || echo "Apple Container: not installed"
which docker && docker info >/dev/null 2>&1 && echo "Docker: installed and running" || echo "Docker: not installed or not running"If NOT on macOS (Linux, etc.)
Apple Container is macOS-only. Use Docker instead.
Tell the user:
You're on Linux, so we'll use Docker for container isolation. Let me set that up now.
Use the /convert-to-docker skill to convert the codebase to Docker, then continue to Section 3.
If on macOS
If Apple Container is already installed: Continue to Section 3.
If Apple Container is NOT installed: Ask the user:
NanoClaw needs a container runtime for isolated agent execution. You have two options:
- Apple Container (default) - macOS-native, lightweight, designed for Apple silicon
- Docker - Cross-platform, widely used, works on macOS and Linux
Which would you prefer?
Option A: Apple Container
Tell the user:
Apple Container is required for running agents in isolated environments.
- Download the latest
.pkgfrom https://github.com/apple/container/releases- Double-click to install
- Run
container system startto start the serviceLet me know when you've completed these steps.
Wait for user confirmation, then verify:
container system start
container --versionNote: NanoClaw automatically starts the Apple Container system when it launches, so you don't need to start it manually after reboots.
Option B: Docker
Tell the user:
You've chosen Docker. Let me set that up now.
Use the /convert-to-docker skill to convert the codebase to Docker, then continue to Section 3.
3. Configure Claude Authentication
Ask the user:
Do you want to use your Claude subscription (Pro/Max) or an Anthropic API key?
Option 1: Claude Subscription (Recommended)
Tell the user:
Open another terminal window and run:
claude setup-tokenA browser window will open for you to log in. Once authenticated, the token will be displayed in your terminal. Either:
- Paste it here and I'll add it to
.envfor you, or- Add it to
.envyourself asCLAUDE_CODE_OAUTH_TOKEN=<your-token>
If they give you the token, add it to .env. Never echo the full token in commands or output — use the Write tool to write the .env file directly, or tell the user to add it themselves:
echo "CLAUDE_CODE_OAUTH_TOKEN=<token>" > .envOption 2: API Key
Ask if they have an existing key to copy or need to create one.
Copy existing:
grep "^ANTHROPIC_API_KEY=" /path/to/source/.env > .envCreate new:
echo 'ANTHROPIC_API_KEY=' > .envTell the user to add their key from https://console.anthropic.com/
Verify:
KEY=$(grep "^ANTHROPIC_API_KEY=" .env | cut -d= -f2)
[ -n "$KEY" ] && echo "API key configured: ${KEY:0:7}..." || echo "Missing"4. Build Container Image
Build the NanoClaw agent container:
./container/build.shThis creates the nanoclaw-agent:latest image with Node.js, Chromium, Claude Code CLI, and agent-browser.
Verify the build succeeded by running a simple test (this auto-detects which runtime you're using):
if which docker >/dev/null 2>&1 && docker info >/dev/null 2>&1; then
echo '{}' | docker run -i --entrypoint /bin/echo nanoclaw-agent:latest "Container OK" || echo "Container build failed"
else
echo '{}' | container run -i --entrypoint /bin/echo nanoclaw-agent:latest "Container OK" || echo "Container build failed"
fi5. WhatsApp Authentication
USER ACTION REQUIRED
The auth script supports two methods: QR code scanning and pairing code (phone number). Ask the user which they prefer.
The auth script writes status to store/auth-status.txt:
already_authenticated— credentials already existpairing_code:<CODE>— pairing code generated, waiting for user to enter itauthenticated— successfully authenticatedfailed:<reason>— authentication failed
The script automatically handles error 515 (stream error after pairing) by reconnecting — this is normal and expected during pairing code auth.
Ask the user which method to use
How would you like to authenticate WhatsApp?
- QR code in browser (Recommended) — Opens a page with the QR code to scan
- Pairing code — Enter a numeric code on your phone, no camera needed
- QR code in terminal — Run the auth command yourself in another terminal
Option A: QR Code in Browser (Recommended)
Clean any stale auth state and start auth in background:
rm -rf store/auth store/qr-data.txt store/auth-status.txt
npm run authRun this with run_in_background: true.
Poll for QR data (up to 15 seconds):
for i in $(seq 1 15); do if [ -f store/qr-data.txt ]; then echo "qr_ready"; exit 0; fi; STATUS=$(cat store/auth-status.txt 2>/dev/null || echo "waiting"); if [ "$STATUS" = "already_authenticated" ]; then echo "$STATUS"; exit 0; fi; sleep 1; done; echo "timeout"If already_authenticated, skip to the next step.
If QR data is ready, generate the QR as SVG and inject it into the HTML template:
node -e "
const QR = require('qrcode');
const fs = require('fs');
const qrData = fs.readFileSync('store/qr-data.txt', 'utf8');
QR.toString(qrData, { type: 'svg' }, (err, svg) => {
if (err) process.exit(1);
const template = fs.readFileSync('.claude/skills/setup/qr-auth.html', 'utf8');
fs.writeFileSync('store/qr-auth.html', template.replace('{{QR_SVG}}', svg));
console.log('done');
});
"Then open it:
open store/qr-auth.htmlTell the user:
A browser window should have opened with the QR code. It expires in about 60 seconds.
Scan it with WhatsApp: Settings → Linked Devices → Link a Device
Then poll for completion (up to 120 seconds):
for i in $(seq 1 60); do STATUS=$(cat store/auth-status.txt 2>/dev/null || echo "waiting"); if [ "$STATUS" = "authenticated" ] || [ "$STATUS" = "already_authenticated" ]; then echo "$STATUS"; exit 0; elif echo "$STATUS" | grep -q "^failed:"; then echo "$STATUS"; exit 0; fi; sleep 2; done; echo "timeout"- If
authenticated, success — clean up withrm -f store/qr-auth.htmland continue. - If
failed:qr_timeout, offer to retry (re-run the auth and regenerate the HTML page). - If
failed:logged_out, deletestore/auth/and retry.
Option B: Pairing Code
Ask the user for their phone number (with country code, no + or spaces, e.g. 14155551234).
Clean any stale auth state and start:
rm -rf store/auth store/qr-data.txt store/auth-status.txt
npx tsx src/whatsapp-auth.ts --pairing-code --phone PHONE_NUMBERRun this with run_in_background: true.
Poll for the pairing code (up to 15 seconds):
for i in $(seq 1 15); do STATUS=$(cat store/auth-status.txt 2>/dev/null || echo "waiting"); if echo "$STATUS" | grep -q "^pairing_code:"; then echo "$STATUS"; exit 0; elif [ "$STATUS" = "authenticated" ] || [ "$STATUS" = "already_authenticated" ]; then echo "$STATUS"; exit 0; elif echo "$STATUS" | grep -q "^failed:"; then echo "$STATUS"; exit 0; fi; sleep 1; done; echo "timeout"Extract the code from the status (e.g. pairing_code:ABC12DEF → ABC12DEF) and tell the user:
Your pairing code: CODE_HERE
- Open WhatsApp on your phone
- Tap Settings → Linked Devices → Link a Device
- Tap "Link with phone number instead"
- Enter the code: CODE_HERE
Then poll for completion (up to 120 seconds):
for i in $(seq 1 60); do STATUS=$(cat store/auth-status.txt 2>/dev/null || echo "waiting"); if [ "$STATUS" = "authenticated" ] || [ "$STATUS" = "already_authenticated" ]; then echo "$STATUS"; exit 0; elif echo "$STATUS" | grep -q "^failed:"; then echo "$STATUS"; exit 0; fi; sleep 2; done; echo "timeout"- If
authenticatedoralready_authenticated, success — continue to next step. - If
failed:logged_out, deletestore/auth/and retry. - If
failed:515or timeout, the 515 reconnect should handle this automatically. If it persists, the user may need to temporarily stop other WhatsApp-connected apps on the same device.
Option C: QR Code in Terminal
Tell the user to run the auth command in another terminal window:
Open another terminal and run:
cd PROJECT_PATH && npm run authScan the QR code that appears, then let me know when it says "Successfully authenticated".
Replace PROJECT_PATH with the actual project path (use pwd).
Wait for the user to confirm authentication succeeded, then continue to the next step.
6. Configure Assistant Name and Main Channel
This step configures three things at once: the trigger word, the main channel type, and the main channel selection.
6a. Ask for trigger word
Ask the user:
What trigger word do you want to use? (default:
Andy)In group chats, messages starting with
@TriggerWordwill be sent to Claude. In your main channel (and optionally solo chats), no prefix is needed — all messages are processed.
Store their choice for use in the steps below.
6b. Explain security model and ask about main channel type
Use the AskUserQuestion tool to present this:
Important: Your "main" channel is your admin control portal.
The main channel has elevated privileges:
- Can see messages from ALL other registered groups
- Can manage and delete tasks across all groups
- Can write to global memory that all groups can read
- Has read-write access to the entire NanoClaw project
Recommendation: Use your personal "Message Yourself" chat or a solo WhatsApp group as your main channel. This ensures only you have admin control.
Question: Which setup will you use for your main channel?
Options:
- Personal chat (Message Yourself) - Recommended
- DM with a specific phone number (e.g. your other phone)
- Solo WhatsApp group (just me)
- Group with other people (I understand the security implications)
If they choose option 4, ask a follow-up:
You've chosen a group with other people. This means everyone in that group will have admin privileges over NanoClaw.
Are you sure you want to proceed? The other members will be able to:
- Read messages from your other registered chats
- Schedule and manage tasks
- Access any directories you've mounted
Options:
- Yes, I understand and want to proceed
- No, let me use a personal chat or solo group instead
6c. Register the main channel
First build, then start the app briefly to connect to WhatsApp and sync group metadata. Use the Bash tool's timeout parameter (15000ms) — do NOT use the timeout shell command (it's not available on macOS). The app will be killed when the timeout fires, which is expected.
npm run buildThen run briefly (set Bash tool timeout to 15000ms):
npm run devFor personal chat (they chose option 1):
Personal chats are NOT synced to the database on startup — only groups are. The JID for "Message Yourself" is the bot's own number. Use the number from the WhatsApp auth step and construct the JID as {number}@s.whatsapp.net.
For DM with a specific number (they chose option 2):
Ask the user for the phone number (with country code, no + or spaces, e.g. 14155551234), then construct the JID as {number}@s.whatsapp.net.
For group (they chose option 3 or 4):
Groups are synced on startup via groupFetchAllParticipating. Query the database for recent groups:
sqlite3 store/messages.db "SELECT jid, name FROM chats WHERE jid LIKE '%@g.us' AND jid != '__group_sync__' ORDER BY last_message_time DESC LIMIT 40"Show only the 10 most recent group names to the user and ask them to pick one. If they say their group isn't in the list, show the next batch from the results you already have. If they tell you the group name directly, look it up:
sqlite3 store/messages.db "SELECT jid, name FROM chats WHERE name LIKE '%GROUP_NAME%' AND jid LIKE '%@g.us'"6d. Write the configuration
Once you have the JID, configure it. Use the assistant name from step 6a.
For personal chats (solo, no prefix needed), set requiresTrigger to false:
{
"JID_HERE": {
"name": "main",
"folder": "main",
"trigger": "@ASSISTANT_NAME",
"added_at": "CURRENT_ISO_TIMESTAMP",
"requiresTrigger": false
}
}For groups, keep requiresTrigger as true (default).
Write to the database directly by creating a temporary registration script, or write data/registered_groups.json which will be auto-migrated on first run:
mkdir -p dataThen write data/registered_groups.json with the correct JID, trigger, and timestamp.
If the user chose a name other than Andy, also update:
groups/global/CLAUDE.md- Change "# Andy" and "You are Andy" to the new namegroups/main/CLAUDE.md- Same changes at the top
Ensure the groups folder exists:
mkdir -p groups/main/logs7. Configure External Directory Access (Mount Allowlist)
Ask the user:
Do you want the agent to be able to access any directories outside the NanoClaw project?
Examples: Git repositories, project folders, documents you want Claude to work on.
Note: This is optional. Without configuration, agents can only access their own group folders.
If no, create an empty allowlist to make this explicit:
mkdir -p ~/.config/nanoclaw
cat > ~/.config/nanoclaw/mount-allowlist.json << 'EOF'
{
"allowedRoots": [],
"blockedPatterns": [],
"nonMainReadOnly": true
}
EOF
echo "Mount allowlist created - no external directories allowed"Skip to the next step.
If yes, ask follow-up questions:
7a. Collect Directory Paths
Ask the user:
Which directories do you want to allow access to?
You can specify:
- A parent folder like
~/projects(allows access to anything inside)- Specific paths like
~/repos/my-appList them one per line, or give me a comma-separated list.
For each directory they provide, ask:
Should
[directory]be read-write (agents can modify files) or read-only?Read-write is needed for: code changes, creating files, git commits Read-only is safer for: reference docs, config examples, templates
7b. Configure Non-Main Group Access
Ask the user:
Should non-main groups (other WhatsApp chats you add later) be restricted to read-only access even if read-write is allowed for the directory?
Recommended: Yes - this prevents other groups from modifying files even if you grant them access to a directory.
7c. Create the Allowlist
Create the allowlist file based on their answers:
mkdir -p ~/.config/nanoclawThen write the JSON file. Example for a user who wants ~/projects (read-write) and ~/docs (read-only) with non-main read-only:
cat > ~/.config/nanoclaw/mount-allowlist.json << 'EOF'
{
"allowedRoots": [
{
"path": "~/projects",
"allowReadWrite": true,
"description": "Development projects"
},
{
"path": "~/docs",
"allowReadWrite": false,
"description": "Reference documents"
}
],
"blockedPatterns": [],
"nonMainReadOnly": true
}
EOFVerify the file:
cat ~/.config/nanoclaw/mount-allowlist.jsonTell the user:
Mount allowlist configured. The following directories are now accessible:
~/projects(read-write)~/docs(read-only)Security notes:
- Sensitive paths (
.ssh,.gnupg,.aws, credentials) are always blocked- This config file is stored outside the project, so agents cannot modify it
- Changes require restarting the NanoClaw service
To grant a group access to a directory, add it to their config in
data/registered_groups.json:"containerConfig": { "additionalMounts": [ { "hostPath": "~/projects/my-app" } ] }The folder appears inside the container at
/workspace/extra/<folder-name>(derived from the last segment of the path). Add"readonly": falsefor write access, or"containerPath": "custom-name"to override the default name.
8. Configure launchd Service
Generate the plist file with correct paths automatically:
NODE_PATH=$(which node)
PROJECT_PATH=$(pwd)
HOME_PATH=$HOME
cat > ~/Library/LaunchAgents/com.nanoclaw.plist << EOF
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.nanoclaw</string>
<key>ProgramArguments</key>
<array>
<string>${NODE_PATH}</string>
<string>${PROJECT_PATH}/dist/index.js</string>
</array>
<key>WorkingDirectory</key>
<string>${PROJECT_PATH}</string>
<key>RunAtLoad</key>
<true/>
<key>KeepAlive</key>
<true/>
<key>EnvironmentVariables</key>
<dict>
<key>PATH</key>
<string>/usr/local/bin:/usr/bin:/bin:${HOME_PATH}/.local/bin</string>
<key>HOME</key>
<string>${HOME_PATH}</string>
</dict>
<key>StandardOutPath</key>
<string>${PROJECT_PATH}/logs/nanoclaw.log</string>
<key>StandardErrorPath</key>
<string>${PROJECT_PATH}/logs/nanoclaw.error.log</string>
</dict>
</plist>
EOF
echo "Created launchd plist with:"
echo " Node: ${NODE_PATH}"
echo " Project: ${PROJECT_PATH}"Build and start the service:
npm run build
mkdir -p logs
launchctl load ~/Library/LaunchAgents/com.nanoclaw.plistVerify it's running:
launchctl list | grep nanoclaw9. Test
Tell the user (using the assistant name they configured):
Send
@ASSISTANT_NAME helloin your registered chat.Tip: In your main channel, you don't need the
@prefix — just sendhelloand the agent will respond.
Check the logs:
tail -f logs/nanoclaw.logThe user should receive a response in WhatsApp.
Troubleshooting
Service not starting: Check logs/nanoclaw.error.log
Container agent fails with "Claude Code process exited with code 1":
- Ensure the container runtime is running:
- Apple Container:
container system start - Docker:
docker info(start Docker Desktop on macOS, orsudo systemctl start dockeron Linux)
- Apple Container:
- Check container logs:
cat groups/main/logs/container-*.log | tail -50
No response to messages:
- Verify the trigger pattern matches (e.g.,
@AssistantNameat start of message) - Main channel doesn't require a prefix — all messages are processed
- Personal/solo chats with
requiresTrigger: falsealso don't need a prefix - Check that the chat JID is in the database:
sqlite3 store/messages.db "SELECT * FROM registered_groups" - Check
logs/nanoclaw.logfor errors
Messages sent but not received by NanoClaw (DMs):
- WhatsApp may use LID (Linked Identity) JIDs for DMs instead of phone numbers
- Check logs for
Translated LID to phone JID— if missing, the LID isn't being resolved - The
translateJidmethod insrc/channels/whatsapp.tsusessock.signalRepository.lidMapping.getPNForLID()to resolve LIDs - Verify the registered JID doesn't have a device suffix (should be
number@s.whatsapp.net, notnumber:0@s.whatsapp.net)
WhatsApp disconnected:
- The service will show a macOS notification
- Run
npm run authto re-authenticate - Restart the service:
launchctl kickstart -k gui/$(id -u)/com.nanoclaw
Unload service:
launchctl unload ~/Library/LaunchAgents/com.nanoclaw.plistDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

