external_plugins/telegram/.claude-plugin/plugin.json

{
  "name": "telegram",
  "description": "Telegram channel for Claude Code \u2014 messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /telegram:access.",
  "version": "0.0.5",
  "keywords": [
    "telegram",
    "messaging",
    "channel",
    "mcp"
  ],
  "userConfig": {
    "TELEGRAM_BOT_TOKEN": {
      "type": "string",
      "title": "Bot Token",
      "description": "Bot token from @BotFather — format is 123456789:AAH... Stored in keychain (macOS) or ~/.claude/.credentials.json with 0600 permissions elsewhere. Never written to settings.json.",
      "required": true,
      "sensitive": true
    }
  }
}
Revert "Remove telegram, discord, and fakechat plugins (#741)" (#753) This reverts commit d53f6ca4cdb000c671dfdc1c181b021e97c25505. 2026-03-19 13:59:14 -07:00			`{`
			`"name": "telegram",`
			`"description": "Telegram channel for Claude Code \u2014 messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /telegram:access.",`
feat(telegram,discord): migrate to plugin userConfig secrets Closes H1 #3617646 via the proper path — plugin userConfig with sensitive: true routes tokens to keychain (macOS) or .credentials.json 0600 (elsewhere) instead of world-readable .env files. Requires claude-cli-internal#23383 (PLUGIN_OPTIONS ungate + per-server sensitive split). Changes per plugin: - plugin.json: add userConfig.{PLATFORM}_BOT_TOKEN with sensitive: true - .mcp.json: add env block with ${user_config.{PLATFORM}_BOT_TOKEN} - server.ts: update comment + error message to point to /plugin reconfigure instead of .env file The .env read loop stays as a legacy fallback for existing users — process.env wins (injected value takes precedence), so no migration forced. New users get prompted at enable time via CC's built-in dialog; token lands in keychain, never touches settings.json. /telegram:configure and /discord:configure skills are NOT removed in this PR — they still work for the legacy .env path. Follow-up: repurpose or remove after a grace period once cli#23383 is released. :house: Remote-Dev: homespace 2026-03-20 21:48:07 +00:00			`"version": "0.0.5",`
Revert "Remove telegram, discord, and fakechat plugins (#741)" (#753) This reverts commit d53f6ca4cdb000c671dfdc1c181b021e97c25505. 2026-03-19 13:59:14 -07:00			`"keywords": [`
			`"telegram",`
			`"messaging",`
			`"channel",`
			`"mcp"`
feat(telegram,discord): migrate to plugin userConfig secrets Closes H1 #3617646 via the proper path — plugin userConfig with sensitive: true routes tokens to keychain (macOS) or .credentials.json 0600 (elsewhere) instead of world-readable .env files. Requires claude-cli-internal#23383 (PLUGIN_OPTIONS ungate + per-server sensitive split). Changes per plugin: - plugin.json: add userConfig.{PLATFORM}_BOT_TOKEN with sensitive: true - .mcp.json: add env block with ${user_config.{PLATFORM}_BOT_TOKEN} - server.ts: update comment + error message to point to /plugin reconfigure instead of .env file The .env read loop stays as a legacy fallback for existing users — process.env wins (injected value takes precedence), so no migration forced. New users get prompted at enable time via CC's built-in dialog; token lands in keychain, never touches settings.json. /telegram:configure and /discord:configure skills are NOT removed in this PR — they still work for the legacy .env path. Follow-up: repurpose or remove after a grace period once cli#23383 is released. :house: Remote-Dev: homespace 2026-03-20 21:48:07 +00:00			`],`
			`"userConfig": {`
			`"TELEGRAM_BOT_TOKEN": {`
			`"type": "string",`
			`"title": "Bot Token",`
			`"description": "Bot token from @BotFather — format is 123456789:AAH... Stored in keychain (macOS) or ~/.claude/.credentials.json with 0600 permissions elsewhere. Never written to settings.json.",`
			`"required": true,`
			`"sensitive": true`
			`}`
			`}`
Revert "Remove telegram, discord, and fakechat plugins (#741)" (#753) This reverts commit d53f6ca4cdb000c671dfdc1c181b021e97c25505. 2026-03-19 13:59:14 -07:00			`}`