[BUG] Novas sessões cortam plugins ativos em sessões ativas

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Starting a brand-new, unrelated claude interactive session (no flags, no --channels, nothing Telegram-related) on the same machine kills the child plugin process (bun.exe running the channel plugin's server.ts) of an already-running, healthy --channels session — while leaving that session's own claude.exe process alive. The affected session looks "alive" in Task Manager but silently stops handling channel messages, since its plugin runtime is gone.

What Should Happen?

The plain session from step 3 should have no effect whatsoever on the independent channel session from step 1 — they should be fully isolated processes.

Error Messages/Logs

Steps to Reproduce

1. Open a dedicated terminal and start a channel session:

claude --permission-mode auto --channels plugin:telegram@claude-plugins-official

1. Confirm it's healthy: send a message through the channel and get a reply (or inspect the process tree — a bun.exe process running server.ts should be a child of this claude.exe).
2. In a separate, unrelated terminal (same user, same machine, same or different working directory), start a plain session:

claude
(no arguments at all — just the normal interactive prompt.)

1. Within ~5-10 seconds, re-inspect the process tree of the channel session from step 1.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.198 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Terminal.app (macOS)

Additional Information

bug_report_telegram_plugin.md