add-imessage
Add iMessage Channel
Adds iMessage support via the Chat SDK bridge. Two modes: local (macOS with Full Disk Access) or remote (Photon API).
Install
NanoClaw doesn't ship channels in trunk. This skill copies the iMessage adapter in from the channels branch.
Pre-flight (idempotent)
Skip to Credentials if all of these are already in place:
src/channels/imessage.tsexistssrc/channels/index.tscontainsimport './imessage.js';chat-adapter-imessageis listed inpackage.jsondependencies
Otherwise continue. Every step below is safe to re-run.
1. Fetch the channels branch
git fetch origin channels
2. Copy the adapter
git show origin/channels:src/channels/imessage.ts > src/channels/imessage.ts
3. Append the self-registration import
Append to src/channels/index.ts (skip if the line is already present):
import './imessage.js';
4. Install the adapter package (pinned)
pnpm install chat-adapter-imessage@0.1.1
5. Build
pnpm run build
Credentials
Local Mode (macOS)
Requirements: macOS with Full Disk Access granted to the Node.js binary.
The Node binary path is buried deep (e.g. ~/.nvm/versions/node/v22.x.x/bin/node). To make it easy, open the folder in Finder so the user can drag the file into System Settings:
open "$(dirname "$(which node)")"
Then tell the user:
- Open System Settings > Privacy & Security > Full Disk Access
- Click +, then drag the
nodefile from the Finder window that just opened - Toggle it on
Stop and wait for the user to confirm before continuing.
Remote Mode (Photon API)
- Set up a Photon account
- Get your server URL and API key
Configure environment
Local mode -- add to .env:
IMESSAGE_ENABLED=true
IMESSAGE_LOCAL=true
Remote mode -- add to .env:
IMESSAGE_LOCAL=false
IMESSAGE_SERVER_URL=https://your-photon-server.com
IMESSAGE_API_KEY=your-api-key
Sync to container: mkdir -p data/env && cp .env data/env/env
Next Steps
If you're in the middle of /setup, return to the setup flow now.
Otherwise, run /manage-channels to wire this channel to an agent group.
Channel Info
- type:
imessage - terminology: iMessage has "conversations." Each conversation is with a contact identified by phone number or email address. Group chats are also supported.
- how-to-find-id: The platform ID is the contact's phone number (e.g.
+15551234567) or email address. For group chats, the ID is assigned by iMessage internally. - supports-threads: no
- typical-use: Interactive 1:1 chat — personal messaging
- default-isolation: Same agent group if you're the only person messaging the bot across iMessage and other channels. Separate agent group if different contacts should have information isolation.
More from qwibitai/nanoclaw
debug
Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.
20add-telegram
Add Telegram channel integration via Chat SDK.
13add-whatsapp
Add WhatsApp channel via native Baileys adapter. Direct connection — no Chat SDK bridge. Uses QR code or pairing code for authentication.
12update-nanoclaw
Efficiently bring upstream NanoClaw updates into a customized install, with preview, selective cherry-pick, and low token usage.
11customize
Add new capabilities or modify NanoClaw behavior. Use when user wants to add channels (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.
10qodo-pr-resolver
Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)
10