5dive-ai

5dive Plugins — Development skill for Claude Code

Development community

Multi-harness plugin marketplace maintained by 5dive — Telegram bridge and related agent-channel integrations.

How to install 5dive Plugins

This entry records only its repository, not the path inside it, so there is no exact command to give. Open 5dive-ai/5dive-plugins and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What 5dive Plugins does

Multi-harness plugin marketplace maintained by 5dive — Telegram bridge and related agent-channel integrations.

Alternatives in Development

IPolloWork — Enterprise-grade, local-first Agent Workbench for people and agent teams 4.9k ★
Oh My Agent — Portable multi-agent harness for .agents-based skills, workflows, and standards-aware agent teams across Antig 786 ★
Claude Code Wechat Channel — Claude Code Channel plugin for WeChat — bridge WeChat messages into Claude Code sessions via the official Claw 255 ★

README

5dive-plugins

Claude Code plugin marketplace maintained by [5dive](https://5dive.ai?utm_source=github&utm_medium=referral&utm_campaign=5dive-plugins-readme).

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	app-server dispatcher	Persistent local dispatcher for Telegram/dashboard; MCP polling remains a fallback.
`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 remaining poll-based forks share one codebase shape and move in lockstep, checked by [`test/parity.test.ts`](./test) and the [`generator/`](./generator) (DIVE-9) — a new poll-based runtime is a config block, not a hand-fork. `telegram-codex` now has an app-server dispatcher in addition to its generated fallback; `telegram-opencode` is a deliberate exception: opencode's headless server makes a relay simpler than an MCP fork (see its README + [the spike](./plugins/telegram-opencode-SPIKE.md)).