Understanding Trigger Words
NanoClaw uses a trigger word (default:@Andy) to know when you’re talking to it. Messages must start with the trigger word.
Customizing the Trigger Word
You can change the trigger word anytime:ASSISTANT_NAME environment variable:
.env
Registering Groups
Main Channel (Self-Chat)
Your main channel is your private self-chat on your messaging platform. The/setup command automatically registers this as your main control channel.
The main channel has special privileges:
- Can write to global memory (shared across all groups)
- Can manage all groups and scheduled tasks
- Can configure directory mounts for any group
- Has access to all tools (same as other groups)
In the main channel, you don’t need the trigger word for most commands - the assistant processes all messages by default.
Adding New Groups
From your main channel, you can register additional chats:Get the group/chat name
Find the exact name of the WhatsApp group, Telegram chat, Discord channel, or Slack channel you want to add.
Register from main channel
In your main channel (self-chat), send:Replace
"Family Chat" with your group’s exact name.Managing Groups
From the main channel:Basic Commands
In Any Group
Main Channel Only
Real Examples
Example 1: Scheduled Reporting
- Create a scheduled task with cron expression
0 9 * * 1-5 - Every weekday at 9am, run as a full agent with access to your mounted Obsidian folder
- Read tasks, prioritize them, and send you a message
Example 2: Git History Review
- Schedule a weekly task
- Run
git logfor the past week - Compare with README.md
- If there’s drift, update the README and commit the changes
Example 3: Dynamic Reminders
- Detect the time-sensitive mention
- Automatically create a reminder
- Send you a reminder on Monday morning
Example 4: Web Research
- Search Hacker News and TechCrunch
- Filter for AI-related articles from the past week
- Summarize the most important developments
- Send you a formatted briefing
Conversation Catch-Up
NanoClaw’s conversation catch-up feature means the agent sees all messages since its last interaction, even if it wasn’t mentioned. Example:Understanding Sessions
NanoClaw uses sessions to maintain conversation continuity:- Each group has its own session
- Sessions persist across restarts
- The assistant remembers what you talked about
- Session transcripts are stored in
data/sessions/{group}/.claude/
Memory Hierarchy
NanoClaw has a three-level memory system:Global Memory
Location:
groups/CLAUDE.md- Read by all groups
- Written by main channel only
- Contains preferences, facts, and context shared everywhere
Group Memory
Location:
groups/{channel}_{group-name}/CLAUDE.md- Read by that group only
- Written by that group
- Contains group-specific conversation context
Container Isolation
Every agent runs in an isolated Linux container with:- Filesystem isolation: Only sees mounted directories
- Safe Bash access: Commands run inside container, not on your host
- Per-group context: Each group has its own container with its own working directory
- Process isolation: Container processes can’t affect your system
This means you can safely let the assistant run bash commands, install packages, or experiment - it’s all sandboxed.
What Agents Can Access
- Default Mounts
- Additional Mounts
- Mount Security
Every agent has access to:
groups/{name}/→ Working directory with CLAUDE.md and filesgroups/CLAUDE.md→ Global memory (read-only for non-main)data/sessions/{group}/.claude/→ Session transcripts
Advanced Usage
Agent Swarms
NanoClaw is the first personal assistant to support agent swarms - teams of specialized agents that collaborate:Custom Skills
You can add capabilities with Claude Code skills:Debugging
Ask Claude Code to debug issues:Next Steps
Scheduled Tasks
Create recurring jobs and reminders
Proactive Agent
Enable morning check-ins and dynamic reminders
Memory System
Deep dive into how memory works
Security
Understand container isolation and safety