customize

NanoClaw Customization

This skill helps users add capabilities or modify behavior. Use AskUserQuestion to understand what they want before making changes.

Workflow

1. Understand the request - Ask clarifying questions
2. Plan the changes - Identify files to modify. If a skill exists for the request (e.g., /add-telegram for adding Telegram), invoke it instead of implementing manually.
3. Implement - Make changes directly to the code
4. Test guidance - Tell user how to verify

Key Files

File	Purpose
src/index.ts	Orchestrator: state, message loop, agent invocation
src/channels/whatsapp.ts	WhatsApp connection, auth, send/receive
src/ipc.ts	IPC watcher and task processing
src/router.ts	Message formatting and outbound routing
src/types.ts	TypeScript interfaces (includes Channel)
src/config.ts	Assistant name, trigger pattern, directories
src/db.ts	Database initialization and queries
src/whatsapp-auth.ts	Standalone WhatsApp authentication script
groups/CLAUDE.md	Global memory/persona

Common Customization Patterns

Adding a New Input Channel (e.g., Telegram, Slack, Email)

Questions to ask:

• Which channel? (Telegram, Slack, Discord, email, SMS, etc.)
• Same trigger word or different?
• Same memory hierarchy or separate?
• Should messages from this channel go to existing groups or new ones?

Implementation pattern:

1. Create src/channels/{name}.ts implementing the Channel interface from src/types.ts (see src/channels/whatsapp.ts for reference)
2. Add the channel instance to main() in src/index.ts and wire callbacks (onMessage, onChatMetadata)
3. Messages are stored via the onMessage callback; routing is automatic via ownsJid()

Adding a New MCP Integration

Questions to ask:

• What service? (Calendar, Notion, database, etc.)
• What operations needed? (read, write, both)
• Which groups should have access?

Implementation:

1. Add MCP server config to the container settings (see src/container-runner.ts for how MCP servers are mounted)
2. Document available tools in groups/CLAUDE.md