Skip to content

v0.1.36 — opencode telegram channel

Choose a tag to compare

View all tags
@lodar lodar released this 02 Jun 04:12
· 110 commits to main since this release
v0.1.36
aec54af

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 seeds access.json (0600).
  • 5dive-agent-start launches the relay via bun run --cwd <plugin> start for opencode+telegram (the TUI still runs for channels=none), exporting OPENCODE_BIN + OPENCODE_PROJECT_DIR.
  • OPENCODE_SERVE_PORT is 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.

Assets 2
Loading