nanoclaw-codex

Add iMessage as an optional channel skill for NanoClaw using a single-file local-macos-first implementation. Phase 1 keeps BlueBubbles as a config seam.

Add new capabilities or modify NanoClaw behavior. Use when user wants to add channels (iMessage, Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.

Run initial NanoClaw setup. Use when user wants to install dependencies, authenticate messaging channels, register their main channel, or start the background services. Triggers on "setup", "install", "configure nanoclaw", or first-time setup requests.

Add Gmail integration to NanoClaw. Can be configured as a tool (agent reads/sends emails when triggered from WhatsApp) or as a full channel (emails can trigger the agent, schedule tasks, and receive replies). Guides through GCP OAuth setup and implements the integration.

Add a local Ollama MCP server so the Codex worker can call local models for cheaper/faster summarization, translation, or general helper tasks.

Add Slack as a channel. Can replace WhatsApp entirely or run alongside it. Uses Socket Mode (no public URL needed).

Add Telegram as a channel. Can replace WhatsApp entirely or run alongside it. Also configurable as a control-only channel (triggers actions) or passive channel (receives notifications only).

Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use $add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.

Add WhatsApp as a channel. Can replace other channels entirely or run alongside them. Uses QR code or pairing code for authentication.

Historical migration skill for the old Docker/Apple Container runtime. Current NanoClaw uses a local Codex worker and does not require Apple Container.

Efficiently bring upstream NanoClaw updates into a customized install, with preview, selective cherry-pick, and low token usage.

X (Twitter) integration for NanoClaw. Post tweets, like, reply, retweet, and quote. Use for setup, testing, or troubleshooting X functionality. Triggers on "setup x", "x integration", "twitter", "post tweet", "tweet".

Configure, verify, and troubleshoot NanoClaw structured session memory, `MEMORY_REFRESH`, and sliding-window compaction. Use when enabling `~/.config/nanoclaw/context-config.json`, checking `context_turns` or `group_memory_state`, or debugging summary updates, bootstrap behavior, and resumed-session refreshes.

Debug NanoClaw runtime issues. Use when worker runs fail, channel auth breaks, context memory behaves unexpectedly, WebSocket sources stop, or to inspect logs, IPC, sessions, and sandbox layout.

Work with Home Assistant's REST API for state inspection, service calls, template rendering, custom events, synthetic states, history, and REST authentication/debugging. Use when the user asks to query or control Home Assistant through `/api/*`, build a REST client, or troubleshoot 400/401/404/405 responses.