Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nanoclaw.dev/llms.txt

Use this file to discover all available pages before exploring further.

NanoClaw trunk ships the registry and infrastructure. Channel adapters and alternative AI providers are installed on demand through setup flows and /add-<name> skills. This keeps your fork lean and your code legible: nothing you didn’t ask for.

​
Two kinds of integration

Channels

Where messages come from: Telegram, Discord, WhatsApp, Signal, Slack, Teams, iMessage, email, the terminal, and more

Providers

Which AI runs the agent: Claude (default), OpenAI Codex, OpenCode (OpenRouter/Google/DeepSeek), Ollama (local). Configurable per agent group.

​
Channels

Install through bash nanoclaw.sh during first setup, or with a skill invocation in Claude Code later. Channel flows install the adapter, collect platform-specific auth, register the first messaging group, and restart the service when needed.

​
Documented channels

WhatsApp

/add-whatsapp (Baileys, WhatsApp Web API) or /add-whatsapp-cloud (Cloud API, DMs only)

Telegram

/add-telegram — grammy framework, BotFather token

Discord

/add-discord — discord.js, bot application token

Slack

/add-slack — Slack app credentials plus a public events URL

Signal

/add-signal — signal-cli linked-device flow

​
Also available on the channels branch

SkillPlatformNotes
/add-teamsMicrosoft TeamsBot Framework
/add-imessageApple iMessagemacOS-only; uses AppleScript bridge
/add-matrixMatrixFederated; supports Element and self-hosted homeservers
/add-gchatGoogle ChatWorkspace accounts
/add-webexCisco WebexBot token
/add-linearLinearIssue comments, triage workflows
/add-githubGitHubPR comments, issue reactions, webhooks
/add-wechatWeChatWeChat Work API
/add-emacsEmacsTalk to your agent from inside your editor
/add-resendEmail (outbound)Transactional sends via Resend
/clawLocal terminalTalk to your agent from a CLI — no platform account required
Documentation for these is rolling out post-v2 launch. The skill itself is self-documenting via SKILL.md — ask Claude Code to walk you through any of them.

​
Providers

By default, NanoClaw uses Claude via the official Claude Agent SDK. Other providers drop in as skills from the providers branch and can be configured per agent group:
SkillProviderUse case
/add-codexOpenAI CodexChatGPT subscription or OpenAI API key
/add-opencodeOpenCodeOpenRouter, Google, DeepSeek, and more via OpenCode
/add-ollama-providerOllamaLocal open-weight models — no cloud calls
/add-ollama-toolOllama (tool mode)Use local Ollama as a tool inside Claude agents
agent_provider is a column on agent_groups in the central database — each agent group can run a different provider. Mix and match in the same install.

​
How channel skills work

  1. Skill or setup invocation — you pick a channel in bash nanoclaw.sh or run /add-<channel> later from Claude Code
  2. Adapter install — the flow adds the channel adapter and any platform package dependencies
  3. Platform auth — the flow prompts for tokens, OAuth flows, QR pairing, or linked-device setup
  4. First messaging group — the flow registers your first chat/channel/group from that platform so you can test immediately
  5. Verify — a round-trip test confirms inbound + outbound work before the flow exits
To pick up channel installer improvements, rerun the relevant /add-<channel> workflow. The installer fetches the current channels branch and updates the files it owns. To remove a channel, revert the commit that installed it: 
git revert <skill-commit-sha>

​
Running multiple channels

Channels are peers — none is privileged. Run one, or run Telegram + Discord + GitHub + a local CLI all at once. For each channel you add, decide how it relates to existing agents:
  • Separate agent groups — each channel has its own workspace, memory, and personality
  • Same agent, separate sessions — one workspace; per-channel conversation threads
  • Shared session — multiple channels feed one conversation (webhook + chat is the classic case)
The choice is per channel, configurable via /manage-channels. See Channel isolation model for details.

​
Next steps

Skills system

How skills work, how to update, and how to author your own

Customization

Trigger words, timeouts, engage modes, sender scope

Security

Sender policies, user roles, OneCLI credentials

Channel isolation

Decide how channels relate to agent groups
Last modified on April 28, 2026