[BUG] Cowork scheduled tasks auto-mount telegram connector not configured by user, conflicts with Claude Code Telegram plugin

Resolved 💬 1 comment Opened Apr 26, 2026 by AMX-Claw Closed May 28, 2026

Preflight Checklist

  • [x] I have searched existing issues and this has not been reported yet
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code

What's Wrong?

Cowork scheduled tasks automatically mount a telegram:telegram connector that was never connected or configured by the user in Cowork settings. There is no UI option to remove or disable this connector from individual tasks or from Cowork globally.

When a scheduled task fails and the model (Haiku 4.5) attempts to send a notification via this auto-mounted Telegram connector — even when the task prompt explicitly says "Complete silently, do not retry, do not send messages" — it conflicts with a Claude Code CLI instance running on the same machine that uses the same Telegram bot via --channels plugin:telegram.

The result is that Claude Code's Telegram plugin connection drops (the bot cannot be polled by two clients simultaneously), making CC unresponsive to all Telegram messages until manually restarted.

Steps to Reproduce

  1. Set up Claude Code CLI with --channels plugin:telegram@claude-plugins-official (running in tmux)
  2. Create a Cowork scheduled task (e.g., a weekly script runner)
  3. Observe that telegram:telegram appears in the task's Connectors panel, despite never being connected in Cowork settings
  4. Wait for the scheduled task to run and encounter an error
  5. The model ignores the "complete silently" instruction and attempts to use the Telegram connector
  6. Claude Code CLI's Telegram connection drops immediately

Expected Behavior

  • Cowork should NOT auto-mount connectors that the user has not explicitly connected in Cowork settings
  • If a connector is somehow available, there should be a UI option to remove it from individual tasks or globally
  • Scheduled tasks should respect prompt instructions like "complete silently" and not attempt to use messaging connectors on failure

Actual Behavior

  • telegram:telegram connector appears in scheduled task Connectors panel without user action
  • No settings UI to remove it
  • Haiku ignores "complete silently" instruction and attempts Telegram notification on task failure
  • This kills Claude Code CLI's Telegram connection on the same machine
  • Screenshot shows the connector present and the failed Telegram reply attempt: [Telegram reply failed: chat not allowlisted. Task execution complete.]

Environment

  • OS: macOS (Apple Silicon, Mac mini)
  • Claude Desktop: latest version
  • Claude Code: v2.1.120
  • Model in Cowork task: Haiku 4.5
  • Claude Code model: Opus 4.6
  • Subscription: Max

Impact

This bug causes Claude Code CLI to lose its Telegram connection every time a Cowork scheduled task runs and fails, requiring manual restart. On a machine running both Cowork scheduled tasks and Claude Code with Telegram, this can happen multiple times daily.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗