Conversation
Add packages/telegram/ with Telegram bot integration for opencode, modeled after the existing Slack integration (packages/slack/). Features: - Access control: DM pairing, allowlist, group policies, mention patterns - Session management: chat_id to session mapping for conversation continuity - Message formatting: <channel> tags matching Claude Code's protocol - Auto-splitting for Telegram's 4096 char limit - SSE event subscription for tool execution updates - Support for text, photo, document, voice, video, sticker messages Usage: TELEGRAM_BOT_TOKEN=xxx bun run --cwd packages/telegram dev Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
The following comment was made by an LLM, it may be inaccurate: Potential Duplicates FoundPR #13373 - feat: Adding OpenCode Telegram Bot This is a related PR that also adds Telegram bot integration to OpenCode. You should check if this is addressing a similar or overlapping scope. PR #15742 - docs(ecosystem): add opencode-telegram-bot This is documentation for a Telegram bot integration, which appears related to the above PR. Related integrations (different platforms, but similar pattern):
These follow the same integration pattern but for different messaging platforms. |
NixOS module at nix/module.nix that manages the opencode Telegram bot as a systemd service with: - Configurable package (defaults to nixpkgs opencode with overrideAttrs pointing to Avimitin/opencode source) - Secret management via file paths (botTokenFile, anthropicKeyFile) - Declarative access.json configuration - systemd hardening (NoNewPrivileges, ProtectSystem, etc.) - Auto-created state directories - Example configuration at nix/example.nix Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replace anthropicKeyFile/provider/model options with a single `settings` option that maps directly to opencode.json. All LLM provider config (including API key env vars) goes through settings, matching how opencode is normally configured. API keys are loaded via `environmentFile` (systemd EnvironmentFile=), not through Nix options. Changes: - settings: Nix attrs → serialized to opencode.json - environmentFile: for ANTHROPIC_API_KEY, OPENAI_API_KEY, etc. - Removed anthropicKeyFile, provider, model options - Updated example with placeholder IDs Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
c01a93a to
b9b22ea
Compare
|
this should be using opencode - not inside it |
|
Oh i am sorry it mistakenly open pr to main repo. |
|
Hey! Your PR title Please update it to start with one of:
Where See CONTRIBUTING.md for details. |
editied to avoid polluting future search