\n
\n\n### 4๏ธโฃ Subscribe to Events\n\n**Features โ Event Subscriptions** โ enable โ **Subscribe to bot events** โ add `app_mention` and `message.im` โ **Save Changes**.\n\n### 5๏ธโฃ Install the app\n\n**OAuth & Permissions** โ **Install to Workspace** (or **Reinstall** if you added scopes after an earlier install) โ **Allow**.\n\n### 6๏ธโฃ Collect your credentials\n\n| Value | Where to find it | Goes in |\n| --------------------------------- | ----------------------------------- | ---------------------- |\n| Bot User OAuth Token (`xoxb-...`) | OAuth & Permissions โ top of page | `SLACK_BOT_TOKEN` |\n| Signing Secret | Basic Information โ App Credentials | `SLACK_SIGNING_SECRET` |\n| App-Level Token (`xapp-...`) | From step 2 | `SLACK_APP_TOKEN` |\n\n### 7๏ธโฃ Say hello ๐\n\n`/invite @your-bot-name` in a channel, or just DM it directly โ no invite needed for that.\n\n---\n\n\n\n## โ๏ธ Creating Your Telegram Bot\n\n### 1๏ธโฃ Talk to BotFather\n\nOpen [@BotFather](https://t.me/BotFather) in Telegram โ `/newbot` โ follow the prompts (name, then a unique username ending in `bot`).\n\n### 2๏ธโฃ Copy the token\n\nBotFather replies with a token like `123456789:AAExampleTokenHere`. That's your `TELEGRAM_BOT_TOKEN`.\n\n### 3๏ธโฃ (Optional) tune group behavior\n\nBy default, Telegram's **group privacy mode** means the bot only sees, in groups: commands (`/help`), replies to its own messages, and `@mentions` of it โ DMs are unaffected. To have it read every group message instead, message BotFather with `/setprivacy` โ select your bot โ **Disable**. Most setups should leave this on default (**Enabled**).\n\n### 4๏ธโฃ Say hello ๐\n\nSearch for your bot's username in Telegram and start a private chat, or add it to a group.\n\n---\n\n\n\n## ๐ฎ Creating Your Discord Bot\n\nYou'll need a Discord application with a bot user, two **privileged gateway intents**, and the right invite scopes.\n\n### 1๏ธโฃ Create the application\n\nGo to the [Discord Developer Portal](https://discord.com/developers/applications) โ **New Application** โ name it (e.g. `Agent Connect`) โ **Bot** in the sidebar โ **Add Bot** if it isn't already there.\n\n### 2๏ธโฃ Enable Privileged Gateway Intents\n\nStill on the **Bot** page, scroll to **Privileged Gateway Intents** and turn on:\n\n| Intent | Why |\n| ----------------- | ---------------------------------------------------------------------------------------------- |\n| `MESSAGE CONTENT` | Without it, every message arrives with empty text |\n| `SERVER MEMBERS` | Not required for a fresh setup, but harmless to enable if you plan to extend the adapter later |\n\n### 3๏ธโฃ Copy the token\n\n**Bot** page โ **Reset Token** (if none is shown yet) โ copy it. That's your `DISCORD_BOT_TOKEN`. Treat it like a password โ anyone with it can control your bot.\n\n### 4๏ธโฃ Invite the bot to a server\n\n**OAuth2 โ URL Generator** โ **Scopes**: check `bot` โ **Bot Permissions**: check `Send Messages`, `Read Message History`, and `Attach Files` (if you want attachment support) โ open the generated URL and pick a server.\n\n### 5๏ธโฃ Say hello ๐\n\n`@your-bot-name` in a server channel it's in, or DM it directly โ no invite needed for a DM.\n\n---\n\n\n\n## ๐ง Setting Up Your Agents\n\nAt least one agent must be enabled. You can enable more than one โ each user picks their active one with `agent Optional: respond to plain messages in channels (not just mentions)
\n\nAdd `channels:history` (public channels), `groups:history` (private channels), and/or `mpim:history` (group DMs), and subscribe to the matching event(s) below (`message.channels`, `message.groups`, `message.mpim`). โ ๏ธ Noisy โ every message becomes a potential command/prompt.\n![\"Buy](\"https://img.buymeacoffee.com/button-api/?text=Buy)
\n\nThank you for using Agent Connect โ truly. ๐\n","readmeFilename":"README.md"}