Describe the bug
When running claude --channels plugin:telegram@claude-plugins-official, cloud connectors configured at claude.ai/settings/connectors (Gmail, Google Calendar, Slack, Notion, Granola, Airtable) are not available to the session. The bot correctly receives and responds to Telegram messages, but cannot access any cloud-connected tools.
This makes channels significantly less useful — the bot can read vault files and run skills, but cannot check email, calendar, Slack, or CRM. The same connectors work perfectly in the Claude Desktop app.
To reproduce
- Configure connectors at claude.ai/settings/connectors (Gmail, Calendar, Slack, Notion)
- Confirm they work in Claude Desktop app (Claudian)
- Run
claude --channels plugin:telegram@claude-plugins-official --dangerously-skip-permissions
- Send a Telegram message asking the bot to check email or calendar
- Bot reports connectors are not available
claude mcp list shows only local servers (telegram plugin, perplexity), no cloud connectors
Expected behaviour
Cloud connectors should sync to CLI sessions (including --channels sessions) the same way they sync to the desktop app. The feature flag tengu_claudeai_mcp_connectors is true and claudeAiMcpEverConnected in .claude.json lists all connectors correctly.
Environment
- Claude Code v2.1.81
- macOS Darwin 25.1.0 (Apple Silicon)
- Feature flag
tengu_claudeai_mcp_connectors: true
claudeAiMcpEverConnected lists: Gmail, Slack, Google Calendar, Granola, Airtable, Notion, Excalidraw, Magic Patterns, Fathom, Canva, Mermaid Chart
claude mcp list shows only: telegram plugin, perplexity (local .mcp.json), notion (manually added HTTP), airtable (manually added stdio)
Impact
Running multiple Telegram bots via --channels for different business domains (personal assistant, people management, sales/partnerships) is severely limited without access to Gmail, Calendar, Slack, and Notion. The bots can only access local vault files and Perplexity, making them far less capable than the desktop session.
Related issues
Describe the bug
When running
claude --channels plugin:telegram@claude-plugins-official, cloud connectors configured at claude.ai/settings/connectors (Gmail, Google Calendar, Slack, Notion, Granola, Airtable) are not available to the session. The bot correctly receives and responds to Telegram messages, but cannot access any cloud-connected tools.This makes channels significantly less useful — the bot can read vault files and run skills, but cannot check email, calendar, Slack, or CRM. The same connectors work perfectly in the Claude Desktop app.
To reproduce
claude --channels plugin:telegram@claude-plugins-official --dangerously-skip-permissionsclaude mcp listshows only local servers (telegram plugin, perplexity), no cloud connectorsExpected behaviour
Cloud connectors should sync to CLI sessions (including
--channelssessions) the same way they sync to the desktop app. The feature flagtengu_claudeai_mcp_connectorsistrueandclaudeAiMcpEverConnectedin.claude.jsonlists all connectors correctly.Environment
tengu_claudeai_mcp_connectors: trueclaudeAiMcpEverConnectedlists: Gmail, Slack, Google Calendar, Granola, Airtable, Notion, Excalidraw, Magic Patterns, Fathom, Canva, Mermaid Chartclaude mcp listshows only: telegram plugin, perplexity (local .mcp.json), notion (manually added HTTP), airtable (manually added stdio)Impact
Running multiple Telegram bots via
--channelsfor different business domains (personal assistant, people management, sales/partnerships) is severely limited without access to Gmail, Calendar, Slack, and Notion. The bots can only access local vault files and Perplexity, making them far less capable than the desktop session.Related issues