summaryrefslogtreecommitdiff
path: root/external_plugins/telegram
AgeCommit message (Collapse)Author
2026-04-23telegram: gate /start, /help, /status behind dmPolicy (#894)Noah Zweben
The bot command handlers bypassed access control — they responded to any DM user regardless of dmPolicy, leaking bot presence and contradicting ACCESS.md's "Drop silently. No reply." contract for allowlist mode. Add dmCommandGate() that applies the same disabled/allowlist checks as gate() without the pairing side effects, and route all three handlers through it. Also prune expired pending codes before /status iterates them. Fixes #854 Co-authored-by: Claude <noreply@anthropic.com>
2026-04-14fix(telegram): retry polling on all transient errors, not just 409 (#1397)Noah Zweben
A single ETIMEDOUT/ECONNRESET/DNS failure during long-polling rejected bot.start(); the catch block returned and polling stopped permanently. The MCP server process stayed alive (stdin keeps it running), so outbound reply/react tools kept working — but the bot was deaf to inbound messages until a full restart. Users see 'typing...' then nothing, indistinguishable from the harness-side gate bug. Now all errors retry with the same capped backoff (max 15s). attempt resets to 0 in onStart so backoff doesn't accumulate across a long-running session. Co-authored-by: Claude <noreply@anthropic.com>
2026-04-10fix(telegram): prevent zombie pollers from blocking new sessions with 409 ↵Noah Zweben
Conflict (#1349) * fix(telegram): prevent zombie pollers from blocking new sessions The MCP server runs as a grandchild of the CLI (via `bun run start` → shell → `bun server.ts`). When the CLI is killed uncleanly (SIGKILL, crash, terminal close), the grandchild survives as an orphan and keeps long-polling getUpdates indefinitely. Telegram allows only one consumer per token, so every subsequent session sees 409 Conflict and the existing retry loop spins forever. Three layered mitigations: - PID lockfile (STATE_DIR/bot.pid): on startup, SIGTERM any stale holder before claiming the slot, so a fresh session always wins. - Orphan watchdog: every 5s check for parent reparenting (POSIX ppid change) or a dead stdin pipe, and self-terminate. Covers cases where the existing stdin end/close events never fire through the wrapper. - 409 retry cap: give up after 8 attempts (~28s) instead of looping forever, and bail immediately if shutdown has begun. Also adds a SIGHUP handler and removes the pidfile on clean shutdown (only if still owned by this process). * chore(telegram): bump version to 0.0.5 --------- Co-authored-by: Claude <noreply@anthropic.com>
2026-04-03Merge pull request #885 from anthropics/sarah/restore-reload-plugins-readmeSarah Deaton
Restore /reload-plugins step in telegram/discord READMEs
2026-03-23feat(telegram,discord): compact permission messages with expandable details ↵Noah Zweben
(#952) * feat(telegram,discord): compact permission messages with expandable details Replace verbose permission request messages with a compact format showing only the tool name. Adds a "See more" button that expands inline to show tool_name, description, and pretty-printed input_preview JSON. Yes/No buttons replace Allow/Deny. Bump plugin versions to 0.0.4. * revert: restore Allow/Deny button labels
2026-03-23feat(telegram,discord): inline buttons for permission approval (#945)Daisy S. Hollman
Replace "Reply 'yes abcde' to allow" text instruction with native inline buttons (Telegram InlineKeyboard, Discord ButtonBuilder). One tap to approve/deny instead of typing a 5-char ID. - Telegram: callback_query handler with allowFrom gate, edits message to show outcome and remove buttons after decision - Discord: interactionCreate handler with allowFrom gate, updates interaction with outcome and clears components - Text-reply path (PERMISSION_REPLY_RE) kept as fallback - Bump both plugins to v0.0.3 :house: Remote-Dev: homespace
2026-03-23feat(telegram,discord): permission-relay capability + bidirectional handlersdaisy/plugin-7/channel-permissionsDaisy Hollman
Complete the plugin side of anthropics/claude-cli-internal#23061 (permission prompts over channels). Capability: both servers now declare experimental["claude/channel/permission"] which tells CC they can relay permission requests. This capability asserts the server authenticates the replier — gate()/access.allowFrom filters non-allowlisted senders before handleInbound runs. Outbound (CC → user): setNotificationHandler for notifications/claude/channel/permission_request formats the tool name, description, and input preview into a human-readable message and sends it to every allowlisted DM. Groups are excluded — the security thread resolution was "single-user mode for official plugins." Inbound (user → CC): PERMISSION_REPLY_RE intercept in handleInbound catches "yes xxxxx" / "no xxxxx" replies, emits the structured notifications/claude/channel/permission event with {request_id, behavior}, reacts with checkmark/cross, and returns without relaying the text to Claude as a chat message. The regex is inlined from channelPermissions.ts (no cross-repo dep). IDs are lowercased at the plugin boundary per the case-insensitive spec. Version bumped 0.0.1 → 0.0.2 so the plugin reconciler picks up the change. :house: Remote-Dev: homespace
2026-03-21Drop tab-complete check, keep just /reload-plugins linesarah/restore-reload-plugins-readmeSarah Deaton
2026-03-21Restore /reload-plugins step in telegram/discord READMEsSarah Deaton
Partially reverts #758. The reload step is not redundant: the configure skill runs before the restart step, so it is not loaded yet when the user types /telegram:configure. CLI prints 'Run /reload-plugins to activate.' after install (pluginInstallationHelpers.ts:529). Mintlify reports confirm users hit 'Unknown skill: discord:configure' at step 3.
2026-03-20Merge remote-tracking branch 'origin/kenneth/telegram-all-file-types' into ↵kenneth/channels-rollupKenneth Lien
kenneth/channels-rollup
2026-03-20Merge remote-tracking branch 'origin/kenneth/telegram-bot-commands-795' into ↵Kenneth Lien
kenneth/channels-rollup # Conflicts: # external_plugins/telegram/server.ts
2026-03-20Merge remote-tracking branch 'origin/kenneth/telegram-bot-commands' into ↵Kenneth Lien
kenneth/channels-rollup
2026-03-20Merge remote-tracking branch 'origin/kenneth/discord-edit-notif-guidance' ↵Kenneth Lien
into kenneth/channels-rollup
2026-03-20Merge remote-tracking branch 'origin/kenneth/channels-state-dir' into ↵Kenneth Lien
kenneth/channels-rollup
2026-03-20Merge remote-tracking branch 'origin/kenneth/telegram-409' into ↵Kenneth Lien
kenneth/channels-rollup # Conflicts: # external_plugins/telegram/server.ts
2026-03-20Merge remote-tracking branch 'origin/kenneth/telegram-shutdown' into ↵Kenneth Lien
kenneth/channels-rollup
2026-03-20Sanitize user-controlled filenames and download path componentskenneth/telegram-all-file-typesKenneth Lien
- safeName() strips <>[]\r\n; from file_name/title before they hit the <channel> notification — delimiter chars would let an uploader break out of the tag or forge meta entries - download_attachment strips ext/uniqueId to alphanumeric before join() — defense-in-depth against path traversal (file_unique_id is Telegram-controlled so this is belt-and-braces)
2026-03-20Tighten /start and /help copykenneth/telegram-bot-commands-795Kenneth Lien
Less chatty, more precise. Explicitly mentions the /telegram:access skill and the 6-char code format.
2026-03-20Restrict bot commands to DMs (security)Kenneth Lien
- /status in a group would leak the sender's pending pairing code to other group members, who could then pair as that user - Commands in non-allowlisted groups confirm bot presence and enable spam - /start now acknowledges dmPolicy === 'disabled' instead of lying - setMyCommands scoped to private chats so the / menu only shows in DMs
2026-03-20telegram: handle all inbound file types + download_attachment toolKenneth Lien
2026-03-20telegram: add /start /help /status bot commandsKenneth Lien
2026-03-20telegram: add MarkdownV2 parse_mode to reply/edit_messagekenneth/telegram-bot-commandsKenneth Lien
2026-03-20discord/telegram: guide assistant to send new reply on completionkenneth/discord-edit-notif-guidanceKenneth Lien
Message edits don't trigger push notifications on the user's device. Update system instructions and edit_message tool description to steer the assistant toward edit-for-progress + new-reply-on-completion. Fixes #786
2026-03-20Silently return when bot.stop() aborts the setup phasekenneth/telegram-409Kenneth Lien
If bot.stop() is called while bot.start() is still in setup (deleteWebhook/ getMe), grammy rejects with 'Aborted delay'. Expected, not an error.
2026-03-20telegram/discord: make state dir configurable via env varkenneth/channels-state-dirKenneth Lien
Hardcoded ~/.claude/channels/<name>/ meant only one bot per machine. Respect TELEGRAM_STATE_DIR / DISCORD_STATE_DIR so users can run multiple bots with separate tokens and allowlists. Also fixed README path ('in your project' -> '~/...') to match the code. Fixes #792
2026-03-20telegram: retry on 409 Conflict instead of crashingKenneth Lien
During /mcp reload or when a zombie from a previous session still holds the polling slot, the new process gets 409 Conflict on its first getUpdates and dies immediately. Retry with backoff until the slot frees — typically within a second or two. Also handles the two-sessions case: the second Claude Code instance keeps retrying (with a clear message about what's happening) and takes over when the first one exits. Fixes #804 #794, partial #788 (issue 4)
2026-03-20telegram: exit when Claude Code closes the connectionkenneth/telegram-shutdownKenneth Lien
When the MCP stdio transport closes, the bot kept polling Telegram as a zombie process — holding the token and causing 409 Conflict for the next session. - Listen for stdin end/close and SIGTERM/SIGINT -> bot.stop() + exit - Force-exit after 2s if bot.stop() stalls on the long-poll timeout - unref the approval-check interval so it doesn't keep us alive Fixes #793, partial #788 (issue 3)
2026-03-20telegram: add error handlers to stop silent polling deathkenneth/telegram-resilienceKenneth Lien
The bot would silently stop delivering messages after the first error: grammy's default handler calls bot.stop() on any middleware throw, and void bot.start() / void mcp.notification() swallow rejections with no log. - bot.catch(): log and keep polling on handler errors - bot.start().catch(): log when polling dies (bad token, 409, network) - mcp.notification().catch(): log when inbound delivery to Claude fails - process-level unhandledRejection/uncaughtException as a safety net Fixes #756 #759 #761 #777 #809, partial #788
2026-03-20Merge pull request #811 from anthropics/kenneth/chmod-env-filesKenneth Lien
Lock telegram/discord .env files to owner (chmod 600)
2026-03-20Lock telegram/discord .env files to owner (chmod 600)kenneth/chmod-env-filesKenneth Lien
The bot token is a credential. Tighten perms on load so hand-written or pre-existing .env files get locked down, and update the configure skill to chmod after writing. No-op on Windows.
2026-03-19README clarifications from docs walkthrough testingdocs/readme-clarificationsSarah Deaton
- Drop /reload-plugins (redundant, you restart with --channels next) - Fix token save path: .claude/channels/ not ~/.claude/channels/ - Clarify bot only responds once channel is running (pairing step)
2026-03-19Add Bun prerequisite to discord and telegram plugin READMEskenneth/add-bun-prereqKenneth Lien
Both MCP servers run on Bun, but this wasn't documented. Add a Prerequisites section with the install command so users don't hit a missing-runtime error on first setup.
2026-03-19Revert "Remove telegram, discord, and fakechat plugins (#741)" (#753)Kenneth Lien
This reverts commit d53f6ca4cdb000c671dfdc1c181b021e97c25505.
2026-03-18Remove telegram, discord, and fakechat plugins (#741)Noah Zweben
Remove the three chat bridge plugins from external_plugins/ and their corresponding entries in marketplace.json. Co-authored-by: Claude <noreply@anthropic.com>
2026-03-18Add telegram channel plugin (#735)Kenneth Lien
Telegram messaging bridge for Claude Code. Runs a local MCP server that connects to the Telegram Bot API via a user-created bot token. Built-in access control: inbound messages are gated by an allowlist (default: pairing mode), outbound sends are scoped to the same allowlist. The /telegram:access skill manages pairing, allowlists, and policy. Ships full source — server.ts runs locally via bun, started by the .mcp.json command. First external_plugins entry to bundle source rather than point at a hosted MCP endpoint.