Menu
Add Telegram channel integration via Chat SDK.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use Codex (CLI + AppServer) as the full agent provider — planning, tool orchestration, native compaction, MCP tools, session resume — in place of the Claude Agent SDK. ChatGPT subscription or OPENAI_API_KEY. Per-group via agent_provider. Distinct from using OpenAI as an MCP tool (where Claude remains the planner).
Super-easy FamilyClaw family setup — base install (Telegram + native credential proxy) then auto-create a shared-memory family agent with an invite link for the rest of the household. Triggers on "set up family", "family setup", "setup familyclaw for my family".
Efficiently bring upstream FamilyClaw updates into a customized install, with preview, selective cherry-pick, and low token usage.
Add Atomic Chat MCP server so the container agent can call local models served by the Atomic Chat desktop app via its OpenAI-compatible API.
Add a monitoring dashboard to FamilyClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.
Add DeltaChat channel integration via @deltachat/stdio-rpc-server. Native adapter — no Chat SDK bridge. Email-based messaging with end-to-end encryption.
| name | add-telegram |
| description | Add Telegram channel integration via Chat SDK. |
Adds Telegram bot support via the Chat SDK bridge.
Telegram is the primary FamilyClaw channel and ships in trunk — the adapter
(src/channels/telegram.ts + telegram-pairing.ts + telegram-markdown-sanitize.ts),
the pair-telegram setup step, the channel flow, and the @chat-adapter/telegram
dependency are all already present. There is nothing to fetch or copy.
These should all already be true on a fresh FamilyClaw checkout:
src/channels/telegram.ts, telegram-pairing.ts, telegram-markdown-sanitize.ts existsrc/channels/index.ts contains import './telegram.js';setup/pair-telegram.ts exists and setup/index.ts's STEPS map contains 'pair-telegram':@chat-adapter/telegram is listed in package.json dependenciesIf any are missing (e.g. a partial checkout), run pnpm install && pnpm run build
and re-check. Then continue to Credentials.
@BotFather/newbot and follow the prompts:
123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11)Important for group chats: By default, Telegram bots only see @mentions and commands in groups. To let the bot see all messages:
@BotFather > /mybots > select your botAdd to .env:
TELEGRAM_BOT_TOKEN=your-bot-token
Sync to container: mkdir -p data/env && cp .env data/env/env
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.
telegrampnpm exec tsx setup/index.ts --step pair-telegram -- --intent <main|wire-to:folder|new-agent:folder>, show the user the 4-digit CODE from the PAIR_TELEGRAM_ISSUED block (follow the REMINDER_TO_ASSISTANT line in that block), and tell them to send just the 4 digits as a message from the chat they want to register (DM the bot for main, post in the group otherwise). In groups with Group Privacy ON, prefix with the bot handle: @<botname> CODE. Wrong guesses invalidate the code — if a PAIR_TELEGRAM_ATTEMPT block arrives with a mismatched RECEIVED_CODE, a PAIR_TELEGRAM_NEW_CODE block will follow automatically (up to 5 regenerations); show the new code. On PAIR_TELEGRAM STATUS=failed ERROR=max-regenerations-exceeded, ask the user if they want to try again and re-invoke the step — each invocation starts a fresh 5-attempt batch. Success emits PAIR_TELEGRAM STATUS=success with PLATFORM_ID, IS_GROUP, and ADMIN_USER_ID. The service must be running for this to work (the polling adapter is what observes the code).