Back to Signal Feed
ProductionTracked since May 17, 2026

Telegram remote approval for Clawd permission prompts

v0.8.0 adds a Telegram-based approval path for AI agent permission requests, letting users approve actions like Claude Code, CodeBuddy, Codex, and Pi prompts from a phone while keeping local approval bubbles as the default surface.

Telegram approvalcc-connect-clawdClawd Settingspermission request workflow

What Happened

  • v0.8.0 adds a Telegram-based approval path for AI agent permission requests, letting users approve actions like Claude Code, CodeBuddy, Codex, and Pi prompts from a phone while keeping local approval bubbles as the default surface.
  • v0.8.0 adds a Telegram-based approval path for AI agent permission requests, letting users approve actions like Claude Code, CodeBuddy, Codex, and Pi prompts from a phone while keeping local approval bubbles as the default surface.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Added a mobile-first remote approval flow in Clawd: users can configure Telegram bot credentials and pairing in a dedicated settings tab, receive permission prompts in Telegram for approval/rejection, and continue using local bubbles as the primary path when Telegram is disabled or unavailable.

Why Track This

Why It Matters

Teams can now approve AI coding-agent permission requests from their phone, so remote operators are no longer forced to keep a desktop UI open to keep work moving during approval gates. The feature introduces a Telegram transport via a sidecar-backed approval relay and an opt-in fallback so request handling remains available when Telegram is offline, disabled, or in do-not-disturb; the next watch points are reliability and operator clarity. In practice, release notes already flag that in-flight Telegram approvals cannot yet be canceled, Telegram-side timeouts can leave local bubbles pending without timeout feedback, and broader macOS/Linux runtime checks were not fully completed.

Impact

Teams can now approve AI coding-agent permission requests from their phone, so remote operators are no longer forced to keep a desktop UI open to keep work moving during approval gates. The feature introduces a Telegram transport via a sidecar-backed approval relay and an opt-in fallback so request handling remains available when Telegram is offline, disabled, or in do-not-disturb; the next watch points are reliability and operator clarity. In practice, release notes already flag that in-flight Telegram approvals cannot yet be canceled, Telegram-side timeouts can leave local bubbles pending without timeout feedback, and broader macOS/Linux runtime checks were not fully completed.

What To Watch Next

  • Watch whether Telegram approval becomes a repeated pattern.
  • Track follow-up changes around Computer Use Agents.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: remote_approval_inflight_requests_not_cancelable, telegram_timeout_cards_no_toast_feedback.
Open Topic TimelineOpen Technical EventOpen Original Sourceremote_approval_inflight_requests_not_cancelable / telegram_timeout_cards_no_toast_feedback / remote_approval_requires_bot_and_sidecar_connectivity / macos_linux_runtime_verification_gaps

Supporting Evidence

GITHUB RELEASEHigh Trust

v0.8.0

A new Remote Approval tab enables Telegram bot setup and recipient pairing so approval cards can be handled on mobile, with automatic fallback to local bubbles when Telegram is not available.