telegram-opencode

A Telegram connection for the opencode command-line coding agent. It relays messages through opencode's server and supports access control and account pairing.

In plain words
What is it for?
Use it to operate or monitor opencode through Telegram, including pairing users and handling permissions.
Why use it?
It lets people communicate with a long-running opencode session through Telegram while controlling who can connect.

Plugin for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Claude Code
/plugin marketplace add 5dive-ai/5dive-plugins
agentmods
npx agentmods add plugins/5dive-ai/5dive-plugins/telegram-opencode
Clone the repo
git clone --depth 1 https://github.com/5dive-ai/5dive-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

telegram-opencode scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/telegram-opencode/.claude-plugin/plugin.json · 9 lines

What it actually says

{
  "name": "telegram-opencode",
  "description": "Telegram channel for the opencode CLI — a long-running relay over opencode's headless HTTP server (opencode serve) and /event SSE stream, with access control and pairing. Unlike the codex/grok/agy MCP forks it needs no wait_for_message loop, re-arm watchdog, or file-IPC permission bridge (server.heartbeat/session.idle/permission.asked are first-class API). Maintained by 5dive.",
  "version": "0.5.10",
  "author": { "name": "5dive", "email": "[email protected]" },
  "homepage": "https://github.com/5dive-ai/5dive-plugins/tree/main/plugins/telegram-opencode",
  "keywords": ["telegram", "messaging", "channel", "opencode", "relay", "sse"]
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 9 lines scan A b7e0150e5803

Subscribe to this mod's changes

telegram-opencode is a plugin published in the GitHub repository 5dive-ai/5dive-plugins (2 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.