Back to Signal Feed
CodeTracked since May 18, 2026

Switch Telegram remote approval to a native Node Bot API client

This PR replaces the Go-based `cc-connect-clawd` Telegram sidecar with a native Node.js Telegram Bot API client for clawd-on-desk approvals, enabling richer remote approval interactions (allow/deny buttons, suggestion actions, option selection, and text replies) while removing multi-instance polling conflicts that previously broke approval flows.

Node.js Telegram Bot API clientcc-connect-clawd Go sidecargetUpdates pollingTelegram approval UI

What Happened

  • This PR replaces the Go-based `cc-connect-clawd` Telegram sidecar with a native Node.js Telegram Bot API client for clawd-on-desk approvals, enabling richer remote approval interactions (allow/deny buttons, suggestion actions, option selection, and text replies) while removing multi-instance polling conflicts that previously broke approval flows.
  • This PR replaces the Go-based `cc-connect-clawd` Telegram sidecar with a native Node.js Telegram Bot API client for clawd-on-desk approvals, enabling richer remote approval interactions (allow/deny buttons, suggestion actions, option selection, and text replies) while removing multi-instance polling conflicts that previously broke approval flows.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Replaced the approval transport from a Go sidecar process to a native Node.js Telegram client using direct Bot API calls, adding interactive approval UX (inline buttons, suggestion actions, single/multi-select, free-text responses) and eliminating `getUpdates` contention across parallel running instances.

Why Track This

Why It Matters

Operators handling remote approvals via Telegram can expect more reliable and practical approval interactions, because approval prompts no longer rely on a fragile sidecar-only allow/deny path and can now be completed with structured buttons and text replies even as multiple approval workers run. The change removes the previous dependency on the Go sidecar by calling the Telegram Bot API directly from Node.js HTTPS, so approval requests should stop stalling from `getUpdates` conflicts; teams should monitor regression risk in `nativeMode=false` fallback behavior, multi-select UI state handling, and macOS/Linux coverage as validation so far is explicitly incomplete.

Impact

Operators handling remote approvals via Telegram can expect more reliable and practical approval interactions, because approval prompts no longer rely on a fragile sidecar-only allow/deny path and can now be completed with structured buttons and text replies even as multiple approval workers run. The change removes the previous dependency on the Go sidecar by calling the Telegram Bot API directly from Node.js HTTPS, so approval requests should stop stalling from `getUpdates` conflicts; teams should monitor regression risk in `nativeMode=false` fallback behavior, multi-select UI state handling, and macOS/Linux coverage as validation so far is explicitly incomplete.

What To Watch Next

  • Watch whether Node.js Telegram Bot API client becomes a repeated pattern.
  • Track follow-up changes around Human-Agent Collaboration Workspaces.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: native_mode_false_fallback_regression, multi_instance_polling_race_reentry.
Open Topic TimelineOpen Technical EventOpen Original Sourcenative_mode_false_fallback_regression / multi_instance_polling_race_reentry / multi_select_ui_state_drift / platform_coverage_gap_macos_linux

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

rullerzhou-afk/clawd-on-desk PR #301: feat(telegram): native Bot API client with rich approval interactions

Add native Node.js Telegram Bot API client that replaces the Go sidecar and enables inline keyboard, suggestions, single/multi-select, text-input elicitation, and single-poller behavior.