agent-messenger 2.10.2 → 2.11.0

package/examples/slackbot-listen.ts

@@ -0,0 +1,65 @@
+#!/usr/bin/env bun
+import { SlackBotClient } from '../src/platforms/slackbot/client'
+import { SlackBotListener } from '../src/platforms/slackbot/listener'
+
+async function main() {
+  const appToken = process.env.SLACK_APP_TOKEN
+  if (!appToken) {
+    console.error('Set SLACK_APP_TOKEN to an xapp-... token with connections:write scope.')
+    console.error('Create one in your Slack app: Settings → Basic Information → App-Level Tokens.')
+    process.exit(1)
+  }
+
+  const client = await new SlackBotClient().login()
+  const listener = new SlackBotListener(client, { appToken })
+
+  listener.on('connected', (info) => {
+    console.log(`Connected (app: ${info.app_id}, connections: ${info.num_connections})`)
+    console.log('Listening for events. Press Ctrl+C to stop.\n')
+  })
+
+  listener.on('disconnected', () => {
+    console.log('[disconnected] reconnecting...')
+  })
+
+  listener.on('message', ({ ack, event }) => {
+    ack()
+    if (event.subtype || event.bot_id) return
+    const time = new Date(Number(event.ts) * 1000).toLocaleTimeString()
+    console.log(`[${time}] message #${event.channel} <${event.user ?? 'system'}>: ${event.text}`)
+  })
+
+  listener.on('app_mention', ({ ack, event }) => {
+    ack()
+    console.log(`[mention] ${event.user} in #${event.channel}: ${event.text}`)
+  })
+
+  listener.on('reaction_added', ({ ack, event }) => {
+    ack()
+    console.log(`[reaction] :${event.reaction}: by ${event.user} on ${event.item.channel}/${event.item.ts}`)
+  })
+
+  listener.on('slash_commands', ({ ack, body }) => {
+    console.log(`[slash] ${body.command} ${body.text} from ${body.user_id}`)
+    ack({ text: `Got \`${body.command} ${body.text}\`` })
+  })
+
+  listener.on('interactive', ({ ack, body }) => {
+    console.log(`[interactive] ${body.type} from ${body.user?.id}`)
+    ack()
+  })
+
+  listener.on('error', (err) => {
+    console.error(`[error] ${err.message}`)
+  })
+
+  process.on('SIGINT', () => {
+    console.log('\nStopping...')
+    listener.stop()
+    process.exit(130)
+  })
+
+  await listener.start()
+}
+
+main()

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-messenger",
-  "version": "2.10.2",
+  "version": "2.11.0",
   "description": "Multi-platform messaging CLI for AI agents (Slack, Discord, Teams, Webex, Telegram, WhatsApp, LINE, Instagram, KakaoTalk, Channel Talk)",
   "repository": {
     "type": "git",
@@ -36,6 +36,9 @@
       "discord": [
         "./dist/src/platforms/discord/index.d.ts"
       ],
+      "discordbot": [
+        "./dist/src/platforms/discordbot/index.d.ts"
+      ],
       "teams": [
         "./dist/src/platforms/teams/index.d.ts"
       ],
@@ -82,6 +85,10 @@
       "types": "./dist/src/platforms/discord/index.d.ts",
       "default": "./dist/src/platforms/discord/index.js"
     },
+    "./discordbot": {
+      "types": "./dist/src/platforms/discordbot/index.d.ts",
+      "default": "./dist/src/platforms/discordbot/index.js"
+    },
     "./teams": {
       "types": "./dist/src/platforms/teams/index.d.ts",
       "default": "./dist/src/platforms/teams/index.js"
@@ -146,9 +153,15 @@
     "bson": "^7.2.0",
     "classic-level": "^3.0.0",
     "commander": "^11.1.0",
+    "crypto-js": "^4.2.0",
+    "curve25519-js": "^0.0.4",
+    "node-bignumber": "^1.2.2",
+    "node-int64": "^0.4.0",
     "node-jose": "^2.2.0",
     "pino": "^10.3.1",
     "qrcode": "^1.5.4",
+    "thrift": "^0.20.0",
+    "tweetnacl": "^1.0.3",
     "ws": "^8.19.0",
     "zod": "^4.3.6"
   },

package/skills/agent-channeltalk/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-channeltalk
 description: Interact with Channel Talk using extracted desktop app or browser credentials - read chats, send messages, search messages, manage groups
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-channeltalk:*)
 metadata:
   openclaw:
@@ -168,6 +168,10 @@ If a memorized ID returns an error (chat not found, group not found), remove it
 ```bash
 # Extract cookies from Channel Talk desktop app or browser (usually automatic)
 agent-channeltalk auth extract
+agent-channeltalk auth extract --browser-profile ~/browser-data
+agent-channeltalk auth extract --browser-profile "$HOME/work-profile,$HOME/personal-profile"
+
+# --browser-profile accepts repeatable or comma-separated Chromium profile/user-data dirs
 
 # Check auth status
 agent-channeltalk auth status

package/skills/agent-channeltalk/references/authentication.md

@@ -18,12 +18,16 @@ This triggers the extraction flow behind the scenes. You can also extract manual
 
 ```bash
 agent-channeltalk auth extract
+agent-channeltalk auth extract --browser-profile ~/browser-data
+agent-channeltalk auth extract --browser-profile "$HOME/work-profile,$HOME/personal-profile"
 ```
 
+Use `--browser-profile <path>` for agent-browser profiles, custom Chrome user data dirs, or portable browser profiles. The option can be repeated or given comma-separated paths.
+
 ### How It Works
 
 1. Locates the Channel Talk desktop app's SQLite cookie database
-2. If the desktop app isn't found, scans Chromium browser profiles for Channel Talk cookies
+2. Scans Chromium browser profiles for Channel Talk cookies when the desktop app isn't found, or when custom `--browser-profile` paths are provided
 3. Copies the database to a temp file (avoids locking the original)
 4. Reads `x-account` and `ch-session-1` cookies for `*.channel.io`
 5. Decrypts encrypted cookies if needed (macOS Keychain, Linux peanuts, Windows DPAPI)

package/skills/agent-channeltalkbot/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-channeltalkbot
 description: Interact with Channel Talk workspaces using API credentials - send messages, read chats, manage groups and bots
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-channeltalkbot:*)
 metadata:
   openclaw:
@@ -14,7 +14,7 @@ metadata:
         bins: [agent-channeltalkbot]
 ---
 
-# Agent ChannelBot
+# Agent ChannelTalkBot
 
 A TypeScript CLI tool that enables AI agents and humans to interact with Channel Talk workspaces using API credentials (Access Key + Access Secret). Designed for customer support automation, team inbox management, and CI/CD integrations.
 
@@ -364,7 +364,7 @@ Common errors: `No credentials`, `Workspace not found`, `Bot name is required`,
 
 ## Configuration
 
-Credentials stored in `~/.config/agent-messenger/channelbot-credentials.json` (0600 permissions). See [references/authentication.md](references/authentication.md) for format and security details.
+Credentials stored in `~/.config/agent-messenger/channeltalkbot-credentials.json` (0600 permissions). See [references/authentication.md](references/authentication.md) for format and security details.
 
 Config format:
 
@@ -383,6 +383,20 @@ Config format:
 }
 ```
 
+## Key Differences from agent-channeltalk
+
+| Feature              | agent-channeltalk           | agent-channeltalkbot                |
+| -------------------- | --------------------------- | ----------------------------------- |
+| Auth type            | Cookie extraction (browser) | API credentials (access key/secret) |
+| Token source         | Auto-extracted from session | Channel Talk admin Open API         |
+| Acts as              | Manager (you)               | Bot (named identity)                |
+| Send group messages  | Yes                         | Yes (requires bot name)             |
+| Send user-chat reply | Yes                         | Yes                                 |
+| Manage bots          | No                          | Yes (create / delete)               |
+| Workspace snapshot   | Yes                         | Yes                                 |
+| Search messages      | Yes (UI search)             | No (API limitation)                 |
+| CI/CD friendly       | Requires browser session    | Yes (just set access key/secret)    |
+
 ## Limitations
 
 - No real-time events / WebSocket connection

package/skills/agent-channeltalkbot/references/authentication.md

@@ -24,14 +24,14 @@ This command:
 1. Validates the credentials against the Channel Talk API
 2. Retrieves the workspace ID and name
 3. Sets this workspace as the current active workspace
-4. Saves credentials to `~/.config/agent-messenger/channelbot-credentials.json`
+4. Saves credentials to `~/.config/agent-messenger/channeltalkbot-credentials.json`
 
 ## Credential Storage
 
 ### Location
 
 ```
-~/.config/agent-messenger/channelbot-credentials.json
+~/.config/agent-messenger/channeltalkbot-credentials.json
 ```
 
 ### Format
@@ -155,10 +155,12 @@ agent-channeltalkbot auth status
 
 For CI/CD and testing, credentials can be set via environment variables:
 
-- `E2E_CHANNELBOT_ACCESS_KEY` - Access key
-- `E2E_CHANNELBOT_ACCESS_SECRET` - Access secret
+- `E2E_CHANNELTALKBOT_ACCESS_KEY` - Access key (preferred)
+- `E2E_CHANNELTALKBOT_ACCESS_SECRET` - Access secret (preferred)
+- `E2E_CHANNELBOT_ACCESS_KEY` - Legacy fallback, still accepted
+- `E2E_CHANNELBOT_ACCESS_SECRET` - Legacy fallback, still accepted
 
-Environment variables take precedence over stored credentials when no specific workspace is requested.
+Environment variables take precedence over stored credentials when no specific workspace is requested. The newer `E2E_CHANNELTALKBOT_*` names are preferred and override the legacy `E2E_CHANNELBOT_*` names when both are set.
 
 ## Troubleshooting
 

package/skills/agent-discord/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-discord
 description: Interact with Discord servers - send messages, read channels, manage reactions
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-discord:*)
 metadata:
   openclaw:
@@ -137,6 +137,10 @@ If a memorized ID returns an error (channel not found, server not found), remove
 # Extract token from Discord desktop app or browser (usually automatic)
 agent-discord auth extract
 agent-discord auth extract --debug
+agent-discord auth extract --browser-profile ~/browser-data
+agent-discord auth extract --browser-profile "$HOME/work-profile,$HOME/personal-profile"
+
+# --browser-profile accepts repeatable or comma-separated Chromium profile/user-data dirs
 
 # Check auth status
 agent-discord auth status

package/skills/agent-discord/references/authentication.md

@@ -15,6 +15,10 @@ agent-discord auth extract
 
 # Use --debug for troubleshooting extraction issues
 agent-discord auth extract --debug
+
+# Scan custom Chromium profile/user-data dirs (repeatable or comma-separated)
+agent-discord auth extract --browser-profile ~/browser-data
+agent-discord auth extract --browser-profile ~/work-profile --browser-profile ~/personal-profile
 ```
 
 This command:
@@ -22,12 +26,14 @@ This command:
 1. Detects your operating system (macOS, Linux, Windows)
 2. Locates the Discord desktop app data directory
 3. Reads the LevelDB storage containing session data
-4. If the desktop app isn't found, scans Chromium browser profiles for Discord tokens
+4. Scans Chromium browser profiles for Discord tokens when the desktop app isn't found, or when custom `--browser-profile` paths are provided
 5. Extracts user token (handles encrypted tokens on all platforms)
 6. Validates token against Discord API before saving
 7. Discovers ALL joined servers
 8. Stores credentials securely in `~/.config/agent-messenger/discord-credentials.json`
 
+Use `--browser-profile <path>` for agent-browser profiles, custom Chrome user data dirs, or portable browser profiles. The option can be repeated or given comma-separated paths; explicit paths are prioritized so they are not masked by default desktop/browser locations.
+
 ### Platform-Specific Paths
 
 **macOS:**

package/skills/agent-discordbot/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-discordbot
 description: Interact with Discord servers using bot tokens - send messages, read channels, manage reactions
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-discordbot:*)
 metadata:
   openclaw:
@@ -18,6 +18,17 @@ metadata:
 
 A TypeScript CLI tool that enables AI agents and humans to interact with Discord servers using bot tokens. Unlike agent-discord which extracts user tokens from the desktop app, agent-discordbot uses standard Discord Bot tokens for server-side and CI/CD integrations.
 
+## Key Concepts
+
+Before diving in, a few things about Discord Bot integration:
+
+- **Bot tokens** — Issued from the Discord Developer Portal (discord.com/developers/applications). Bots act as the bot application's user, with their own ID and presence.
+- **Server (Guild) preference** — A bot can be in many servers. Use `server switch <id>` to set the active server, or pass `--server <id>` per command.
+- **Privileged intents** — `MessageContent`, `GuildMembers`, and `GuildPresences` are privileged and must be enabled in the Developer Portal before they can be used by the SDK listener.
+- **Permission gates** — Bot capabilities depend on the role's permission flags in each server. Missing permissions return 403 errors.
+- **Real-time events** — Available via the SDK's Gateway listener, not via the CLI.
+- **Channel resolution** — Use channel IDs (snowflake numbers) directly. The CLI does not resolve `#channel-name` syntax.
+
 ## Quick Start
 
 ```bash
@@ -371,7 +382,7 @@ Credentials stored in `~/.config/agent-messenger/discordbot-credentials.json` (0
 
 ## Limitations
 
-- No real-time events / Gateway connection
+- No real-time events in the CLI (real-time Gateway events are available via the SDK — `import { DiscordBotListener } from 'agent-messenger/discordbot'`)
 - No voice channel support
 - No server management (create/delete channels, roles)
 - No slash commands

package/skills/agent-discordbot/references/common-patterns.md

@@ -82,7 +82,7 @@ while true; do
 done
 ```
 
-**Limitations**: Polling-based, not real-time. For production bots, use Discord's Gateway API.
+**Limitations**: This CLI pattern is polling-based. For real-time event delivery, the SDK exposes `DiscordBotListener` (Discord Gateway WebSocket) — `import { DiscordBotListener } from 'agent-messenger/discordbot'`.
 
 ## Pattern 4: Reaction-Based Workflow
 

package/skills/agent-instagram/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-instagram
 description: Interact with Instagram DMs - send messages, read conversations, manage accounts
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-instagram:*)
 metadata:
   openclaw:
@@ -66,8 +66,14 @@ agent-instagram auth extract
 
 # With debug output
 agent-instagram auth extract --debug
+
+# Scan custom Chromium profile/user-data dirs
+agent-instagram auth extract --browser-profile ~/browser-data
+agent-instagram auth extract --browser-profile "$HOME/work-profile,$HOME/personal-profile"
 ```
 
+`--browser-profile` accepts repeatable or comma-separated Chromium profile/user-data directories. Use it for agent-browser profiles, custom Chrome user data dirs, or portable browser profiles.
+
 **How it works**: The CLI reads Instagram cookies (`sessionid`, `csrftoken`, `ds_user_id`) directly from the browser's SQLite cookie database. No browser automation, no password prompts. The session is stored locally in `~/.config/agent-messenger/`.
 
 **When to re-extract**: Browser cookies expire. When your session expires, re-run `agent-instagram auth extract` or let auto-extraction handle it (the CLI attempts extraction automatically when no valid session exists).

package/skills/agent-instagram/references/authentication.md

@@ -23,8 +23,14 @@ agent-instagram auth extract
 
 # With debug output
 agent-instagram auth extract --debug
+
+# Scan custom Chromium profile/user-data dirs (repeatable or comma-separated)
+agent-instagram auth extract --browser-profile ~/browser-data
+agent-instagram auth extract --browser-profile ~/work-profile --browser-profile ~/personal-profile
 ```
 
+Use `--browser-profile <path>` for agent-browser profiles, custom Chrome user data dirs, or portable browser profiles. The option can be repeated or given comma-separated paths.
+
 ### Auto-Extraction
 
 When no valid session exists, the CLI automatically attempts browser extraction before prompting for credentials. This means most users never need to run `auth extract` manually.

package/skills/agent-kakaotalk/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-kakaotalk
 description: Interact with KakaoTalk - send messages, read chats, manage conversations
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-kakaotalk:*)
 metadata:
   openclaw:

package/skills/agent-line/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-line
 description: Interact with LINE - send messages, read chats, manage conversations
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-line:*)
 metadata:
   openclaw:

package/skills/agent-slack/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-slack
 description: Interact with Slack workspaces - send messages, read channels, manage reactions
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-slack:*)
 metadata:
   openclaw:
@@ -140,6 +140,10 @@ If a memorized ID returns an error (channel not found, user not found), remove i
 # Extract tokens from Slack desktop app or browser (usually automatic)
 agent-slack auth extract
 agent-slack auth extract --debug
+agent-slack auth extract --browser-profile ~/browser-data
+agent-slack auth extract --browser-profile ~/work-profile --browser-profile ~/personal-profile
+
+# --browser-profile accepts repeatable or comma-separated Chromium profile/user-data dirs
 
 # Check auth status
 agent-slack auth status

package/skills/agent-slack/references/authentication.md

@@ -15,6 +15,10 @@ agent-slack auth extract
 
 # Use --debug for troubleshooting extraction issues
 agent-slack auth extract --debug
+
+# Scan custom Chromium profile/user-data dirs (repeatable or comma-separated)
+agent-slack auth extract --browser-profile ~/browser-data
+agent-slack auth extract --browser-profile "$HOME/work-profile,$HOME/personal-profile"
 ```
 
 This command:
@@ -22,12 +26,14 @@ This command:
 1. Detects your operating system (macOS, Linux, Windows)
 2. Locates the Slack desktop app data directory (supports both direct download and App Store versions on macOS)
 3. Reads the LevelDB storage containing session data
-4. If the desktop app isn't found, scans Chromium browser profiles for Slack tokens in `localStorage.localConfig_v2` and `d` cookie
+4. Scans Chromium browser profiles for Slack tokens in `localStorage.localConfig_v2` and `d` cookie when the desktop app isn't found, or when custom `--browser-profile` paths are provided
 5. Decrypts cookies using macOS Keychain, Linux keyring, or Windows DPAPI
 6. Validates tokens against Slack API before saving
 7. Extracts xoxc token and xoxd cookie for ALL logged-in workspaces
 8. Stores credentials securely in `~/.config/agent-messenger/slack-credentials.json`
 
+Use `--browser-profile <path>` for agent-browser profiles, custom Chrome user data dirs, or portable browser profiles. The option can be repeated or given comma-separated paths, and explicit paths are included even when desktop credentials are also present.
+
 ### Platform-Specific Paths
 
 **macOS (Direct Download):**

package/skills/agent-slackbot/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-slackbot
 description: Interact with Slack workspaces using bot tokens - send messages, read channels, manage reactions
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-slackbot:*)
 metadata:
   openclaw:
@@ -18,6 +18,17 @@ metadata:
 
 A TypeScript CLI tool that enables AI agents and humans to interact with Slack workspaces using bot tokens (xoxb-). Unlike agent-slack which extracts user tokens from the desktop app, agent-slackbot uses standard Slack Bot tokens for server-side and CI/CD integrations.
 
+## Key Concepts
+
+Before diving in, a few things about Slack Bot integration:
+
+- **Bot tokens (xoxb-)** — Issued from the Slack App config (api.slack.com/apps). Bots act as the bot user, not as you. Different name, different permissions, different identity.
+- **Workspace + Bot hierarchy** — Each workspace can have multiple bot tokens (one per Slack App). The CLI stores bots under their workspace and lets you switch between them.
+- **Channel access requires invitation** — Bots must be invited to private channels with `/invite @YourBotName` before they can read or post.
+- **Bot scopes are immutable per-token** — Token capabilities are baked in at App creation. Adding a new scope means re-installing the App and refreshing the token.
+- **Edit/delete is bot-scoped** — A bot can only edit/delete messages it sent. It cannot modify other users' messages.
+- **Real-time events** — Available via the SDK's Socket Mode listener (separate `xapp-` app-level token required), not via the CLI.
+
 ## Quick Start
 
 ```bash
@@ -200,8 +211,15 @@ agent-slackbot message update <channel> <ts> <new-text>
 
 # Delete a message (bot's own messages only)
 agent-slackbot message delete <channel> <ts> --force
+
+# Show typing/status indicator in an AI Assistant thread
+agent-slackbot message typing <channel> <thread_ts>
+agent-slackbot message typing <channel> <thread_ts> "is analyzing..."
+agent-slackbot message typing <channel> <thread_ts> ""   # clear status
 ```
 
+> **Typing indicators**: `message typing` calls Slack's `assistant.threads.setStatus` API. It only works inside **AI Assistant threads** (not regular channels/DMs) and requires the `chat:write` bot scope. The status auto-clears when your bot posts the next message, or after 2 minutes if no message is sent. Pass an empty string `""` to clear the status manually.
+
 ### Channel Commands
 
 ```bash
@@ -236,6 +254,33 @@ agent-slackbot reaction add C0ACZKTDDC0 1234567890.123456 thumbsup
 agent-slackbot reaction remove <channel> <ts> <emoji>
 ```
 
+### File Commands
+
+```bash
+# Upload a file to a channel (requires files:write scope)
+agent-slackbot file upload <channel> <path>
+agent-slackbot file upload C0ACZKTDDC0 ./report.pdf
+agent-slackbot file upload C0ACZKTDDC0 ./log.txt --filename build-log.txt
+agent-slackbot file upload C0ACZKTDDC0 ./screenshot.png --thread 1234567890.123456 --comment "FYI"
+
+# List files visible to the bot (requires files:read scope)
+agent-slackbot file list
+agent-slackbot file list --channel C0ACZKTDDC0
+agent-slackbot file list --user U123 --limit 50
+
+# Show file details
+agent-slackbot file info <file-id>
+
+# Download a file by ID (saves to current dir or given path)
+agent-slackbot file download <file-id>
+agent-slackbot file download F0123ABC ./downloads/
+
+# Delete a file (bot's own files only)
+agent-slackbot file delete <file-id> --force
+```
+
+> **File scopes**: `file upload` requires `files:write`; `file list`, `file info`, and `file download` require `files:read`. Add these to your Slack App's bot token scopes and reinstall the app. The bot can only delete files it uploaded.
+
 ## Output Format
 
 ### JSON (Default)
@@ -258,6 +303,13 @@ Use `--pretty` flag for formatted output:
 agent-slackbot channel list --pretty
 ```
 
+## Global Options
+
+| Option       | Description                                          |
+| ------------ | ---------------------------------------------------- |
+| `--pretty`   | Human-readable output instead of compact JSON        |
+| `--bot <id>` | Use a specific bot for this command (workspace/bot)  |
+
 ## Common Patterns
 
 See `references/common-patterns.md` for typical AI agent workflows.
@@ -298,7 +350,7 @@ Credentials stored in `~/.config/agent-messenger/slackbot-credentials.json` (060
 | Token type           | User token (xoxc-)              | Bot token (xoxb-)            |
 | Token source         | Auto-extracted from desktop app | Manual from Slack App config |
 | Message search       | Yes                             | No (requires user token)     |
-| File operations      | Yes                             | No                           |
+| File operations      | Yes                             | Upload/list/info/download/delete (with scopes) |
 | Snapshot             | Yes                             | No                           |
 | Edit/delete messages | Any message                     | Bot's own messages only      |
 | Workspace management | Multi-workspace                 | Multi-bot, multi-workspace   |
@@ -306,9 +358,9 @@ Credentials stored in `~/.config/agent-messenger/slackbot-credentials.json` (060
 
 ## Limitations
 
-- No real-time events / Socket Mode
+- No real-time events in the CLI (real-time Socket Mode events are available via the SDK — see the README's "Real-time Events (Slack Bot)" section)
 - No message search (requires user token scope)
-- No file upload/download
+- File operations require `files:read` / `files:write` scopes; bot can only delete files it uploaded
 - No workspace snapshot
 - Bot can only edit/delete its own messages
 - Bot must be invited to private channels

package/skills/agent-slackbot/references/authentication.md

@@ -29,6 +29,8 @@ Add these **Bot Token Scopes**:
 | `users:read.email` | Access user email addresses            |
 | `reactions:write`  | Add and remove emoji reactions         |
 | `reactions:read`   | List reactions on messages             |
+| `files:read`       | List, inspect, and download files      |
+| `files:write`      | Upload and delete files                |
 
 ### Installing the App
 
@@ -246,6 +248,8 @@ oauth_config:
       - users:read.email
       - reactions:write
       - reactions:read
+      - files:read
+      - files:write
 
 settings:
   org_deploy_enabled: false

package/skills/agent-teams/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-teams
 description: Interact with Microsoft Teams - send messages, read channels, manage reactions
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-teams:*)
 metadata:
   openclaw:
@@ -148,6 +148,10 @@ If a memorized ID returns an error (channel not found, team not found), remove i
 # Extract token from Teams desktop app or browser (usually automatic)
 agent-teams auth extract
 agent-teams auth extract --debug
+agent-teams auth extract --browser-profile ~/browser-data
+agent-teams auth extract --browser-profile ~/work-profile --browser-profile ~/personal-profile
+
+# --browser-profile accepts repeatable or comma-separated Chromium profile/user-data dirs
 
 # Check auth status (includes token expiry info)
 agent-teams auth status

package/skills/agent-teams/references/authentication.md

@@ -49,6 +49,10 @@ agent-teams auth extract
 
 # Use --debug for troubleshooting extraction issues
 agent-teams auth extract --debug
+
+# Scan custom Chromium profile/user-data dirs (repeatable or comma-separated)
+agent-teams auth extract --browser-profile ~/browser-data
+agent-teams auth extract --browser-profile "$HOME/work-profile,$HOME/personal-profile"
 ```
 
 This command:
@@ -56,12 +60,14 @@ This command:
 1. Detects your operating system (macOS, Linux, Windows)
 2. Locates the Teams desktop app data directory
 3. Reads the **Cookies SQLite database** containing session data
-4. If the desktop app isn't found, scans Chromium browser profiles for Teams cookies
+4. Scans Chromium browser profiles for Teams cookies when the desktop app isn't found, or when custom `--browser-profile` paths are provided
 5. Extracts `skypetoken_asm` cookie value
 6. Validates token against Teams API before saving
 7. Discovers ALL joined teams
 8. Stores credentials securely in `~/.config/agent-messenger/teams-credentials.json`
 
+Use `--browser-profile <path>` for agent-browser profiles, custom Chrome user data dirs, or portable browser profiles. The option can be repeated or given comma-separated paths.
+
 ### Platform-Specific Paths
 
 **macOS:**

package/skills/agent-telegram/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-telegram
 description: Interact with Telegram through TDLib - authenticate, inspect chats, and send messages
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-telegram:*)
 ---
 

package/skills/agent-webex/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-webex
 description: Interact with Cisco Webex - send messages, read spaces, manage memberships
-version: 2.10.2
+version: 2.11.0
 allowed-tools: Bash(agent-webex:*)
 metadata:
   openclaw:
@@ -54,8 +54,14 @@ agent-webex auth extract
 
 # With debug output
 agent-webex auth extract --debug
+
+# Scan custom Chromium profile/user-data dirs
+agent-webex auth extract --browser-profile ~/browser-data
+agent-webex auth extract --browser-profile ~/work-profile --browser-profile ~/personal-profile
 ```
 
+`--browser-profile` accepts repeatable or comma-separated Chromium profile/user-data directories. Use it for agent-browser profiles, custom Chrome user data dirs, or portable browser profiles.
+
 **Supported browsers**: Chrome, Chrome Canary, Edge, Arc, Brave, Vivaldi, Chromium
 
 **How it works**: The Webex web client stores its authentication token in the browser's localStorage. This CLI reads it directly from the browser's LevelDB files — no browser automation, no password prompts. The token is stored locally in `~/.config/agent-messenger/`.