v0.1.11

Added

• grok --channels=telegram — 5dive agent create <name> --type=grok --channels=telegram --telegram-token=<bot> now wires the telegram-grok plugin into the agent's ~/.grok/. End-to-end mirrors the codex provisioning shipped in 0.1.8/0.1.9:
  • install_channel_for_grok_agent writes the bot token into ~/.grok/channels/telegram/.env and seeds access.json from --telegram-allowed-users.
  • 5dive-agent-start writes [mcp_servers.telegram] into ~/.grok/config.toml (absolute paths — ${GROK_PLUGIN_ROOT} isn't expanded for MCP command/args in grok 0.1.x) AND ~/.grok/hooks/5dive-telegram.json with the silence-watchdog / notify-stop / notification-relay hooks. Grok ignores [[hooks.*]] inside config.toml, so the split is intentional.
  • --always-approve (already in the grok launcher ARGS) auto-trusts MCP and hook commands.
• install.sh stages the telegram-grok plugin into /usr/local/lib/5dive/telegram-grok on customer VMs (same shape as the telegram-codex staging in 0.1.9).

Plugin built and handed off by agent-dev.

Verified live: grok mcp doctor reports ✓ server started, ✓ handshake OK, ✓ 5 tools discovered, 1 healthy; grok inspect confirms Hooks (3) loaded.