This release adds 3 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+4 more
Affected surfaces
Summary
AI summaryAdded Telegram bridge support for opencode agents via --channels telegram flag.
Full changelog
v0.1.36 — opencode telegram channel
Enable --channels telegram for --type opencode (DIVE-42). TYPE_CHANNELS[opencode] flipped on.
opencode's telegram bridge is a standalone relay (telegram-opencode/server.ts) — a third run-model distinct from claude (--channels flag) and codex/grok/antigravity (MCP server wired into the runtime's config). The relay IS the agent's main process and itself spawns opencode serve over loopback HTTP.
5dive agent create <name> --type opencode --channels telegram --telegram-token <t> [--telegram-allowed-users <csv>]now provisions the bridge: writes the token into~/.opencode/channels/telegram/.env(0600) and seedsaccess.json(0600).5dive-agent-startlaunches the relay viabun run --cwd <plugin> startfor opencode+telegram (the TUI still runs forchannels=none), exportingOPENCODE_BIN+OPENCODE_PROJECT_DIR.OPENCODE_SERVE_PORTis left unset so the bridge (telegram-opencode v0.1.2) auto-picks a free loopback port — multiple opencode agents on one box never collide.
Requires the telegram-opencode plugin (v0.1.2+) deployed (/usr/local/lib/5dive/telegram-opencode or the 5dive-plugins checkout) and bun on the agent user's PATH.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About 5dive
All releases →Related context
Related tools
Beta — feedback welcome: [email protected]