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. **Prefer a dedicated skill** — If a skill covers the request, invoke it instead of editing core by hand: - Channels: `/add-telegram`, `/add-slack`, `/add-discord`, `/add-whatsapp`, `/add-signal`, `/add-imessage`, and the rest of the `/add-<channel>` family. - Wiring channels to agents and isolation levels: `/manage-channels`. - Container directory access: `/manage-mounts`. - Agent providers (non-default): `/add-opencode`, `/add-codex`, `/add-ollama-provider`. - Integrations as MCP tools: `/add-gmail-tool`, `/add-gcal-tool`, `/add-ollama-tool`, etc. 3. **Plan the changes** — Identify the v2 surface the change belongs to (entity model in the central DB, per-agent-group container config, per-group `CLAUDE.md`, or core code). 4. **Implement** — Make the change on the right surface. 5. **Test guidance** — Tell the user how to verify. ## Entity Model Customizations route through the v2 entity model: users → messaging groups → agent groups → sessions. A messaging group is one chat/channel on one platform; an agent group holds the workspace, personality, and container config; a wiring links a messaging group to an agent group with a session mode and trigger rules. Inspect and edit all of this with the `ncl` admin CLI. See `docs/isolation-...