Feature request: Support per-project Telegram bot configuration

Summary

Currently the Telegram plugin uses a single global bot token stored at ~/.claude/channels/telegram/.env, shared across all projects. It would be valuable to support configuring a separate Telegram bot per project.

Motivation

Users working across multiple projects may want distinct bots for:

• Context separation — messages from different projects don't intermingle
• Per-project access policies — different collaborators for different projects
• Routing clarity — messages reach the correct project session automatically

Proposed Behavior

Allow a project-scoped Telegram channel config, e.g. a .claude/channels/telegram/.env within the project directory, that takes precedence over the global config when present. Each project session would connect to its own bot.

Current Workaround

Manually swapping the bot token in the global .env and restarting the session when switching projects, which is cumbersome.

---

🤖 Generated with Claude Code