5dive-plugins
5dive-ai/5dive-plugins
Conecte agents Claude ao Telegram com múltiplos runtimes e protocolos
Ver no GitHubClaude Code plugin marketplace maintained by 5dive — Telegram bridge and related agent-channel integrations.
Instalação
npx convez-ai 5dive-ai/5dive-plugins1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Integrar Claude Code com Telegram para responder mensagens diretas
- Estender Telegram bridge para runtimes alternativos (Codex, Grok, Antigravity)
- Automatizar aprovação de permissões via botões inline no Telegram
- Manter codebase unificada entre forks poll-based de diferentes runtimes
Veredito

Solução técnica robusta para operadores de agent CLIs que precisam de bridge Telegram em escala. A arquitetura multi-runtime com gerador de parity-tests é engenharia séria, mas o setup em Teams requer coordenação admin — não é plug-and-play para usuários casual.
README
A tradução para o português deste README ainda está na fila.
5dive-plugins
Claude Code plugin marketplace maintained by 5dive.
The telegram plugin pairs an agent CLI with a Telegram bot — DM the bot, the
agent answers. The original targets Claude Code; the runtime forks below
bring the same bridge to other agent CLIs that lack Claude Code's channel
push protocol.
| Plugin | Runtime | Inbound model | Notes |
|---|---|---|---|
telegram | Claude Code | channel push | The baseline. Fork of Anthropic's telegram plugin, extended with 5dive auto-relay, stop-reply gating, and ask-user-question routing. |
telegram-codex | OpenAI Codex | wait_for_message poll | MCP server. Adds a PermissionRequest-hook → inline-button approval bridge. |
telegram-grok | xAI Grok | wait_for_message poll | MCP server. Runs --always-approve (no permission bridge). |
telegram-agy | Google Antigravity | wait_for_message poll | MCP server. Plugin manifest + MCP wired global+absolute in ~/.gemini/config. |
telegram-opencode | opencode | HTTP + /event SSE | Not an MCP fork — a long-running relay over opencode serve. No watchdog/hooks/file-IPC needed (the server pushes events). |
The four poll-based forks share one codebase shape and move in lockstep, checked
by test/parity.test.ts and the generator/ (DIVE-9) —
a new poll-based runtime is a config block, not a hand-fork. telegram-opencode
is a deliberate exception: opencode's headless server makes a relay simpler than
an MCP fork (see its README + the spike).
Install
/plugin marketplace add 5dive-ai/5dive-plugins
/plugin install telegram@5dive-plugins
Anthropic Teams accounts
On an Anthropic Teams account, the channel-plugin allowlist is controlled by your org admin via remote managed-settings — local /etc/claude-code/managed-settings.json is ignored. Without an admin-set allowlist, claude silently drops inbound Telegram messages and the startup log shows:
Channel notifications skipped: plugin telegram@5dive-plugins is not on the approved channels allowlist
Fix: your org admin opens claude.ai and navigates to Admin Settings → Claude Code → Managed settings (settings.json) → click "Manage", then pastes the JSON below into the Managed settings textarea and saves:
{
"channelsEnabled": true,
"allowedChannelPlugins": [
{ "plugin": "telegram", "marketplace": "5dive-plugins" },
{ "plugin": "telegram", "marketplace": "claude-plugins-official" },
{ "plugin": "discord", "marketplace": "claude-plugins-official" }
]
}
Notes:
channelsEnabled: trueis required on Claude Code 2.1.150+. Without it the allowlist is silently inert.- Once any org-level allowlist exists, Claude Code stops reading Anthropic's default ledger — so include every channel plugin your team uses, not just
5dive-plugins. Drop any you don't need. - Single-user (non-Teams) installs don't hit this —
5dive'sinstall.shwrites/etc/claude-code/managed-settings.jsonlocally and that's all Claude Code needs.
Attribution
The telegram plugin is forked from Anthropic's
claude-plugins-official
under Apache License 2.0. See NOTICE and
plugins/telegram/LICENSE.