Channel plugin MCP server silently fails to start on restart
Description
When Claude Code is restarted (either manually or via a .bat script), the channel plugin's MCP server (bun process) sometimes fails to start silently. Claude Code launches with the correct --channels plugin:telegram@claude-plugins-official flag, but no bun/MCP process is spawned. Telegram messages stop coming through.
Steps to reproduce
- Install the Telegram channel plugin:
/plugin marketplace add anthropics/claude-plugins-official - Start Claude Code with
--channels plugin:telegram@claude-plugins-official --dangerously-skip-permissions - Verify Telegram channel is working
- Close Claude Code window
- Restart Claude Code with the same command
- Telegram channel no longer works — no bun/MCP processes are running
Observed behavior
- Claude Code process is running with the correct
--channelsargument (confirmed viaWin32_Process.CommandLine) installed_plugins.jsonshows the plugin is installed correctly (version 0.0.4, valid install path)- Plugin is not in
blocklist.json - bun is available and can manually start the MCP server (
bun run --shell=bun --silent startin the plugin directory works fine) - No bun/node/MCP-related processes exist — the plugin's MCP server was never spawned
/pluginUI does not show the installed Telegram/Discord plugins under "Installed" tab — only shows claudeai plugins- No error messages or logs indicating the failure
Workaround
Reinstalling the plugin marketplace resolves the issue:
/plugin marketplace add anthropics/claude-plugins-official
However, this is required after nearly every restart, which is not sustainable for a 24/7 agent setup.
Expected behavior
Channel plugins should reliably start their MCP servers on every Claude Code launch when --channels flag is provided, or at minimum surface an error if initialization fails.
Environment
- Claude Code: v2.1.83
- OS: Windows 11 Pro for Workstations
- Bun: v1.3.11
- Plugin: telegram@claude-plugins-official v0.0.4
- Launch method:
.batscript and Windows Task Scheduler (auto-start on boot)
Additional context
This is a recurring issue on a VM running Claude Code as a 24/7 Telegram agent. The health check script detects Claude Code process as running (since the main process is alive), but the channel plugin is non-functional. This creates a silent failure mode where the agent appears healthy but cannot receive messages.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗