summaryrefslogtreecommitdiff
path: root/external_plugins
AgeCommit message (Collapse)Author
2026-09-30Fix Context7 OAuth fallback (#6333)Tobin South
Remote-Dev: homespace Co-authored-by: Fahreddin Özcan <ozcanfahrettinn@gmail.com>
2026-09-30imessage: surface every inbound image, not just the firstdltn/imessage-multi-imagedltn
An iMessage with several photos arrived with only the first one in the channel tag: handleInbound took the first image attachment and stopped. Collect every image attachment instead (same filters as before) and pass each path in the notification meta as image_path, image_path_2, image_path_3, ... so the model can Read all of them. A single image still produces exactly image_path, so existing behaviour is unchanged. Numbered keys rather than an array or a joined list: Claude Code accepts only string values in channel meta and renders each key as an attribute on the <channel> tag, so keys must be plain identifiers; one key per path also avoids inventing a delimiter for sender-controlled filenames. The attachments query gains ORDER BY a.ROWID so the numbering follows attachment ROWID (creation) order. Instructions and README updated to match; version 0.1.0 -> 0.2.0 in plugin.json and package.json. Known limits, unchanged by this patch: attachments still downloading when the message row is first polled (filename NULL) are skipped and, since the poll watermark has already passed the message, never picked up later; HEIC is passed through unconverted; attachments with a NULL mime_type still pass the image filter; no cap on images per message.
2026-09-08context7: tag the remote MCP URL with client=claude-code-plugin (+ validate ↵jordanecker-ant
path fix) (#5823) * context7: tag the remote MCP URL with client=claude-code-plugin * validate: also trigger on vendored plugins' .mcp.json and hooks changes
2026-09-08greptile: repoint to greptileai/claude-plugin (git-subdir @ ↵jordanecker-ant
greptile--v1.2.3), drop the vendored copy (#5930)
2026-08-12fix(telegram): v0.0.7 reliability rollup — state-dir, PID guard, ppid ↵Noah Zweben
watchdog, install stdout (#1424) * fix(telegram): honor TELEGRAM_STATE_DIR/CLAUDE_CONFIG_DIR in skills and server The server already reads TELEGRAM_STATE_DIR for multi-bot setups, but the /telegram:access and /telegram:configure skills hardcoded ~/.claude/channels/telegram/ in 11 places. So with a custom state dir the skill writes access.json to the default location while the server reads from the override — pairing and allowlist edits silently don't take effect. Skills now resolve the state dir via shell expansion (TELEGRAM_STATE_DIR → CLAUDE_CONFIG_DIR/channels/telegram → ~/.claude/channels/telegram) before any read/write. Server gets the same CLAUDE_CONFIG_DIR fallback. Also adds Bash(echo)/Bash(chmod) to configure skill's allowed-tools (chmod was already documented but not allowlisted). * fix(telegram): verify stale PID is a server.ts process before SIGTERM PID files race with OS PID recycling. The lockfile from #1349 stored only a PID; after enough churn that PID can be reassigned to anything — including the new launch's own bun-run wrapper. SIGTERMing the wrapper closes our stdin and triggers immediate self-shutdown ('replacing stale poller' then 'shutting down' within seconds — matches #1459 item 3). Now check 'ps -p <pid> -o args=' contains 'server.ts' before killing. execFileSync (no shell); whole block already try/catch so Windows/ps-missing falls through to just overwriting the lockfile. * fix(telegram): drop ppid watchdog check; redirect bun install stdout to stderr Two v0.0.5/0.0.6 regressions causing the plugin to fail at startup: 1. The orphan watchdog's process.ppid !== bootPpid check false-fires when the bun-run/shell wrapper exits or execs during normal startup and we get reparented to init — plugin self-terminates ~5s after launch. Stdin-close alone is the correct signal: the kernel closes the MCP pipe on any CLI death regardless of intermediate wrappers, so the ppid check was both unnecessary and harmful. (#1467; also the actual cause of #1459 item 3 and likely #1425.) 2. 'bun install --no-summary' in the start script writes to stdout, which is the MCP JSON-RPC transport. The harness sees non-JSON bytes during the handshake and drops the connection ('Failed to connect'). Redirect install output to stderr. (#1470; also explains #1425 on Windows.) --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Bryan Thompson <238056179+bryan-anthropic@users.noreply.github.com>
2026-08-12Drop the conditional reload note from discord and telegram READMEsreadme-one-command-installMohamed Hegazy
2026-08-12Update install instructions to the one-command plugin installMohamed Hegazy
Claude Code's /plugin install now registers the official marketplace automatically and activates the plugin in the same session, so the /reload-plugins step these READMEs document is no longer needed. discord and telegram keep a conditional note because their MCP servers can't always be activated mid-session.
2026-08-07Update context7 plugin — migrate to remote MCP server (#4985)Bryan Thompson
Replace the npx stdio launch of @upstash/context7-mcp with Context7's hosted remote MCP server (https://mcp.context7.com/mcp), matching the configuration Upstash ships in upstash/context7 (plugins/claude/context7). Adds a README and refreshes the plugin descriptions. Co-Authored-By: Fahreddin Özcan <88107904+fahreddinozcan@users.noreply.github.com> Driver: dir-plugin-add-official
2026-08-06Migrate Asana plugin to V2 MCP server (#4895)Bryan Thompson
* Migrate Asana plugin to V2 MCP server The V1 beta server (https://mcp.asana.com/sse) is deprecated and shuts down on 2026-08-05. Asana's V2 server (https://mcp.asana.com/v2/mcp) requires each user to register their own Asana OAuth app and does not support Dynamic Client Registration. A plugin manifest cannot carry per-user OAuth credentials, so the bundled MCP server entry is removed in favor of a documented one-time `claude mcp add` setup (per Asana's official Claude Code instructions). - Remove dead V1 sse .mcp.json - Add README with V2 OAuth setup + troubleshooting - Add /asana-setup slash command to guide the one-time setup - Update plugin + marketplace descriptions to reference V2 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * plugin-dev: stop using deprecated Asana V1 SSE endpoint in examples The Asana V1 SSE server (https://mcp.asana.com/sse) is deprecated and shuts down on 2026-08-05, and Asana V2 is streamable HTTP with manual OAuth — not SSE with automatic (DCR) OAuth. Replace the Asana SSE examples in the mcp-integration skill with neutral placeholders so the tutorial no longer teaches a dead endpoint or implies Asana is a zero-config SSE/OAuth server. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Greg Dardis <86272347+greg-dardis@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
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-16Point supabase plugin to supabase-community/supabase-plugin (#1442)Dickson Tsai
Remove the in-repo supabase stub; source from the external repo. Co-authored-by: Claude <noreply@anthropic.com>
2026-04-14fix(discord): use cached author.id when DMChannel.recipientId is null (#1365)Daisy S. Hollman
DMChannel.recipientId can be null when client.channels.fetch() returns a DM channel with a cold cache. The inbound gate correctly uses msg.author.id, but fetchAllowedChannel relied on recipientId, so replies to allowlisted DMs intermittently failed with "channel not allowlisted" after session restart. Maintain a channelId→userId map populated during inbound handling and fall back to it when recipientId is null. Fixes anthropics/claude-code#40576 Fixes anthropics/claude-code#41647 :house: Remote-Dev: homespace
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-10Remove hosted slack plugin stub (#1305)Tobin South
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-30Merge pull request #1055 from ↵Kenneth Lien
anthropics/kenneth/imessage-permission-selfchat-only imessage: restrict permission relay to self-chat, fix echo filter & tapback noise
2026-03-27Merge pull request #1008 from anthropics/russell/imessage-conversational-formatrussell-coleman
feat(imessage): conversational format for chat_messages
2026-03-27feat(imessage): add IMESSAGE_DB_PATH env var for testingrussell/imessage-conversational-formatRussell Coleman
Mirrors the existing IMESSAGE_STATE_DIR override. Lets a mock sqlite chat.db stand in for ~/Library/Messages/chat.db so chat_messages can be tested without macOS + Full Disk Access + real iMessage history.
2026-03-26imessage: bump to 0.1.0kenneth/imessage-permission-selfchat-onlyKenneth Lien
2026-03-26imessage: drop SMS/RCS by default, opt-in via IMESSAGE_ALLOW_SMSKenneth Lien
SMS sender IDs are spoofable; iMessage is Apple-ID-authenticated and end-to-end encrypted. The plugin previously treated both identically, so a forged SMS from the owner's own number would match SELF, bypass the access gate, and inherit owner-level trust — including permission approval. handleInbound now drops anything with service != 'iMessage' unless IMESSAGE_ALLOW_SMS=true. Default is the safe path; users who want SMS can opt in after reading the warning in README.
2026-03-26imessage: trim comment cruftKenneth Lien
2026-03-26imessage: harden echo filter normalizationKenneth Lien
The self-chat echo filter matches outbound text against what chat.db stores on round-trip. Three divergence sources caused false negatives and duplicate bubbles: - Signature suffix: "\nSent by Claude" is appended on send, but the \n may not round-trip identically through attributedBody - Emoji variation selectors (U+FE00-FE0F) and ZWJ (U+200D): chat.db can add or drop these on emoji characters - Smart quotes: macOS auto-substitutes straight quotes on the way in Strip/normalize all three in echoKey() before the existing whitespace collapse. Fixes #1024
2026-03-26imessage: drop whitespace-only messages from tapbacks/receiptsKenneth Lien
Tapback reactions and read receipts synced from linked devices arrive as chat.db rows with whitespace-only text. The existing empty-check used falsy comparison which doesn't catch ' ' or invisible chars, causing unsolicited replies to reaction taps. Fixes #1041
2026-03-26imessage: restrict permission relay to self-chat onlyKenneth Lien
Permission prompts were being broadcast to all allowlisted contacts plus every DM resolvable from the SELF address set. Two compounding bugs: 1. SELF was polluted by chat.last_addressed_handle, which on machines with SMS history returns short codes, business handles, and other contacts' numbers — not just the owner's addresses. One reporter's query returned 50 addresses (2 actually theirs) resolving to 148 DM chats, all of which received permission prompts. 2. Even with a clean SELF, the handler sent to allowFrom + SELF, so every allowlisted contact received the prompt and could reply to approve tool execution on the owner's machine. Fix: - Build SELF from message.account WHERE is_from_me=1 only - Send permission prompts to self-chat only, not allowFrom - Accept permission replies from self-chat only Fixes #1048 Fixes #1010
2026-03-26Add terraform plugin files to match marketplace.json entrydickson/add-terraform-pluginDickson Tsai
2026-03-25feat(imessage): conversational format for chat_messagesRussell Coleman
Reformat chat_messages output from flat per-message lines to grouped conversation threads. Each thread gets a header labelling it DM or Group with its participant list, date-separator lines when the calendar day rolls over, and [HH:MM] local-time stamps instead of full ISO. chat_guid is now optional — omit to dump every allowlisted chat at once for a quick multi-thread overview. Default limit raised 20→100 per chat, capped at 500. New queries: qChatParticipants (handle list per chat) and qChatInfo (display_name + style to distinguish DM/group). renderMsg replaced by conversationHeader + renderConversation.
2026-03-23Regenerate imessage bun.lock without artifactory URLskenneth/fix-imessage-lockfileKenneth Lien
The lockfile had 94 artifactory.infra.ant.dev URLs baked in from generation behind a private registry. External users hit 401s on 'bun install' and the server never starts. Regenerated against registry.npmjs.org to match the .npmrc.
2026-03-23Merge pull request #737 from anthropics/add-imessage-channelKenneth Lien
Add imessage channel plugin
2026-03-23Show input_preview only for Bash in permission promptsadd-imessage-channelKenneth Lien
Write/Edit previews are unbearably long over iMessage. Bash is the dangerous one where seeing the command matters; everything else gets tool_name + description only.
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-23Document IMESSAGE_STATE_DIR in READMEKenneth Lien
2026-03-23feat(imessage): port permission-relay + lifecycle fixes from telegramKenneth Lien
Brings the imessage channel to parity with recent telegram/discord hardening: - Permission-relay capability: declare claude/channel/permission, handle inbound permission_request notifications by fanning out to allowlisted DM chats + self-chat, intercept "yes/no <id>" replies after the gate check and emit structured permission events instead of relaying as chat. Groups excluded per single-user-mode policy. - Global unhandledRejection/uncaughtException handlers so the server logs instead of dying silently. - IMESSAGE_STATE_DIR env override for the state directory. - .unref() on both setInterval timers so they don't block shutdown. - stdin EOF / SIGTERM / SIGINT shutdown handler that closes chat.db and exits cleanly instead of leaving a zombie poll loop. Adds zod as a direct dep (already transitively present via the MCP SDK) for the notification handler schema.
2026-03-23Merge remote-tracking branch 'origin/main' into add-imessage-channelKenneth Lien
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 pull request #825 from anthropics/kenneth/channels-rollupKenneth Lien
Channels rollup: resilience + discord port + bucket-1 features
2026-03-20Add IMESSAGE_APPEND_SIGNATURE env var (default true)Kenneth Lien
2026-03-20Merge branch 'main' into add-imessage-channelKenneth Lien
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-resilience' 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-20Remove local stripe external pluginClaude
Now that the stripe plugin sources from the stripe/ai git-subdir, the locally vendored copy under external_plugins/stripe is no longer needed.