agent-messenger
Advanced tools
Multi-platform messaging CLI for AI agents (Slack, Discord, Teams, Webex, Telegram, WhatsApp, LINE, Instagram, KakaoTalk, Channel Talk)
Your agent messages as you — not as a bot
One CLI for Slack, Discord, Teams, Webex, Telegram, WhatsApp, LINE, Instagram, KakaoTalk, and Channel Talk. Credentials extracted from desktop apps or authenticated in seconds — no API keys, no OAuth, no admin approval. TypeScript SDK included.
You shouldn't need a bot token to send a message.
Every platform gates API access behind OAuth apps that need admin approval — days of waiting just to send a message. And even then, your agent is a bot, not you. Different name, different permissions, different context.
Agent Messenger reads session tokens from your Slack, Discord, Teams, KakaoTalk, or Channel Talk desktop app — zero config. If the desktop app isn't installed, it falls back to extracting from Chromium browsers. Webex and Instagram tokens are extracted directly from browsers. Telegram authenticates with a one-time phone code, and WhatsApp with a QR code or pairing code. Either way, your agent operates as you — same name, same permissions, same context. Bot tokens are fully supported too for server-side and CI/CD use cases.
--pretty for human-readable. Structured output your agent can parse and act onCLI (global install for terminal / AI agent use):
npm install -g agent-messenger
SDK (project dependency for programmatic use):
npm install agent-messenger
The global install gives you all platform CLIs. The project install gives you both CLIs and the TypeScript SDK.
This installs:
agent-slack — Slack CLI (user token, zero-config)agent-slackbot — Slack Bot CLI (bot token, for server-side/CI/CD)agent-discord — Discord CLIagent-discordbot — Discord Bot CLI (bot token, for server-side/CI/CD)agent-teams — Microsoft Teams CLIagent-webex — Cisco Webex CLI (browser token extraction with e2e encryption + OAuth Device Grant, zero-config)agent-telegram — Telegram CLI (user account via TDLib)agent-whatsapp — WhatsApp CLI (user account via Baileys, QR code or pairing code auth)agent-whatsappbot — WhatsApp Bot CLI (Cloud API, for server-side/CI/CD)agent-line — LINE CLI (QR code login, Thrift protocol)agent-wechatbot — WeChat Bot CLI (Official Account API, for server-side/CI/CD)agent-instagram — Instagram DM CLI (browser cookie extraction + username/password auth)agent-kakaotalk — KakaoTalk CLI (sub-device login, LOCO protocol)agent-channeltalk — Channel Talk CLI (beta, zero-config, extracted cookies)agent-channeltalkbot — Channel Talk Bot CLI (beta, API credentials, for server-side/CI/CD)Agent Messenger includes Agent Skills that teach your AI agent how to use each CLI above. One skill per CLI — install only what you need.
SkillPad is a GUI app for Agent Skills. See skillpad.dev for more details.
Skills CLI is a CLI tool for Agent Skills. See skills.sh for more details.
npx -y skills add agent-messenger/agent-messenger
claude plugin marketplace add agent-messenger/agent-messenger
claude plugin install agent-messenger
Or within Claude Code:
/plugin marketplace add agent-messenger/agent-messenger
/plugin install agent-messenger
Add to your opencode.jsonc:
{
"plugins": ["agent-messenger"],
}
Get up and running in 30 seconds:
# 1. See your workspace at a glance
agent-slack snapshot --pretty
# 2. Send a message
agent-slack message send general "Hello from the CLI!"
That's it. Credentials are extracted automatically from your Slack desktop app on first run. No OAuth flows. No API tokens. No configuration files.
Get up and running with Telegram in a minute:
bunx --package agent-messenger agent-telegram auth login
# Send a message
bunx --package agent-messenger agent-telegram message send <chat-id-or-@username> "Hello from the CLI!"
The CLI automatically provisions API credentials via my.telegram.org if needed. For CI/CD, set AGENT_TELEGRAM_API_ID and AGENT_TELEGRAM_API_HASH environment variables.
Use Agent Messenger as a TypeScript library. Each platform exports a typed client, credential manager, types, and Zod schemas.
import { SlackClient } from 'agent-messenger/slack'
const slack = await new SlackClient().login()
const channels = await slack.listChannels()
await slack.sendMessage(channels[0].id, 'Hello from the SDK!')
Credentials are resolved the same way as the CLI — auto-extracted from your desktop apps. Call .login() with no arguments for auto-extraction, or pass credentials explicitly:
const slack = await new SlackClient().login({ token: 'xoxc-...', cookie: 'xoxd-...' })
| Import Path | Client |
|---|---|
agent-messenger/slack | SlackClient |
agent-messenger/slackbot | SlackBotClient |
agent-messenger/discord | DiscordClient |
agent-messenger/discordbot | DiscordBotClient |
agent-messenger/teams | TeamsClient |
agent-messenger/webex | WebexClient |
agent-messenger/whatsapp | WhatsAppClient |
agent-messenger/whatsappbot | WhatsAppBotClient |
agent-messenger/line | LineClient |
agent-messenger/wechatbot | WeChatBotClient |
agent-messenger/instagram | InstagramClient |
agent-messenger/kakaotalk | KakaoTalkClient |
agent-messenger/channeltalk | ChannelClient |
agent-messenger/channeltalkbot | ChannelBotClient |
Each module also exports its credential manager, Zod schemas, and TypeScript types:
import { SlackClient, SlackCredentialManager, SlackMessageSchema } from 'agent-messenger/slack'
import type { SlackMessage, SlackChannel } from 'agent-messenger/slack'
Every client supports .login() with explicit credentials for advanced use cases:
import { SlackClient } from 'agent-messenger/slack'
const client = await new SlackClient().login({ token: 'xoxc-...', cookie: 'xoxd-...' })
const messages = await client.getMessages('C01234567')
import { SlackClient, SlackListener } from 'agent-messenger/slack'
const client = await new SlackClient().login()
const listener = new SlackListener(client)
listener.on('message', (event) => {
console.log(`New message in ${event.channel}: ${event.text}`)
})
await listener.start()
import { KakaoTalkClient, KakaoTalkListener } from 'agent-messenger/kakaotalk'
const client = await new KakaoTalkClient().login()
const listener = new KakaoTalkListener(client)
listener.on('message', (event) => {
console.log(`New message in ${event.chat_id}: ${event.message}`)
})
await listener.start()
A unified terminal interface for all your messaging platforms in one screen. Navigate between Slack, Discord, Teams, Webex, Telegram, WhatsApp, LINE, Instagram, KakaoTalk, and Channel Talk — all from your terminal.
Note: The TUI is a showcase of what's possible with Agent Messenger's SDK. It demonstrates the power of having a unified adapter layer across all platforms.
agent-messenger tui
Key features:
Ctrl+K for channels, Ctrl+W for workspacesSee the TUI docs for keybindings, architecture, and more.
| Feature | Slack | Discord | Teams | Webex | Telegram | LINE | KakaoTalk | Channel Talk (beta) | ||
|---|---|---|---|---|---|---|---|---|---|---|
| Auto credential extraction | ✅ | ✅ | ✅ | ✅ | — | — | — | ✅ | ✅ | ✅ |
| Send & list messages | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Direct messages | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Search messages | ✅ | ✅ | — | — | — | ✅ | — | ✅ | — | ✅ |
| Threads | ✅ | ✅ | — | — | — | — | — | — | — | — |
| Channels & Users | ✅ | ✅ | ✅ | ✅ | partial | — | ✅ | — | — | ✅ |
| Reactions | ✅ | ✅ | ✅ | — | — | ✅ | — | — | — | — |
| File uploads | ✅ | ✅ | ✅ | — | — | — | — | — | — | — |
| File downloads | ✅ | — | — | — | — | — | — | — | — | — |
| Workspace snapshots | ✅ | ✅ | ✅ | ✅ | — | — | — | — | — | ✅ |
| Multi-workspace / account | ✅ | ✅ | ✅ | — | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Activity feed | ✅ | — | — | — | — | — | — | — | — | — |
| Drafts | ✅ | — | — | — | — | — | — | — | — | — |
| Saved items | ✅ | — | — | — | — | — | — | — | — | — |
| Unread messages | ✅ | — | — | — | — | — | — | — | — | — |
| Sidebar sections | ✅ | — | — | — | — | — | — | — | — | — |
| Pins & bookmarks | ✅ | — | — | — | — | — | — | — | — | — |
| Scheduled messages | ✅ | — | — | — | — | — | — | — | — | — |
| Channel management | ✅ | — | — | — | — | — | — | — | — | — |
| Reminders | ✅ | — | — | — | — | — | — | — | — | — |
| User groups | ✅ | — | — | — | — | — | — | — | — | — |
| Real-time events (SDK) | ✅ | ✅ | — | — | — | — | ✅ | ✅ | ✅ | — |
| Bot support | ✅ | ✅ | — | — | — | ✅ | — | — | — | ✅ |
⚠️ Teams tokens expire in 60-90 minutes. Re-run
agent-teams auth extractto refresh. See Teams Guide for details.
Pull context from conversations before you start working — no tab-switching, no skimming.
"Read the #incident-api-outage thread in Slack and summarize the root cause, timeline, and action items so I can write the postmortem."
"Search our Discord #architecture channel for any previous discussion about event sourcing before I write a proposal."
"Check my unread messages across all Slack channels and tell me if anything needs my attention."
"Look through #frontend in Slack for messages about the login page redesign from the past two weeks and summarize the decisions made."
"Search Teams for any messages mentioning 'API deprecation' so I know if this was discussed before."
Send updates, file reports, and notify your team — all from a prompt.
"Post a deployment summary to #releases in Slack with the commit hash, changelog, and deploy status."
"Send a message to the #standup channel with what I worked on yesterday, what I'm doing today, and any blockers."
"Cross-post this announcement to #general in Slack, the announcements channel in Discord, and the General channel in Teams."
"Upload the latest test coverage report to #ci-results in Slack."
"React with ✅ to the last message in #deploy-requests to confirm I've handled it."
Wire messaging into your CI, scripts, or agent workflows.
"After every CI run, post the build status and test results to #builds in Slack — include the branch name and commit link."
"When a long-running migration finishes, notify me in Discord with the final row count and elapsed time."
"Every morning at 9am, snapshot my Slack workspace and post a summary of active channels to #team-pulse."
"Send an alert to #oncall in Slack whenever the error rate exceeds 1% — include the service name and a link to the dashboard."
"Read the latest message in #releases, then cross-post it to our Discord announcements channel."
These are just starting points. Your agent has full read/write access to Slack, Discord, Teams, Telegram, WhatsApp, LINE, Instagram, KakaoTalk, and Channel Talk — anything you'd do manually in a chat app, it can handle for you. If you build something cool with Agent Messenger, let me know!
MCP servers expose all tools at once, bloating context and confusing agents.
| MCP Approach | Agent Skills + CLI |
|---|---|
| All tools loaded at once | Load only what you need |
| Bloated context window | Minimal token usage |
| Agent confused by options | Focused, relevant tools |
| Requires a running server | One shell command per action |
With Agent Messenger, your agent loads the skill it needs, uses the CLI, and moves on. No wasted tokens. The SDK complements the CLI for when you need programmatic access—same credentials, same platform coverage, full type safety.
OAuth requires creating an app and workspace admin approval—days of waiting just to send a message. Agent Messenger skips all of that. Your desktop apps already have valid session tokens; Agent Messenger extracts them directly so you can start messaging immediately. For platforms like Telegram, WhatsApp, and LINE, a one-time authentication flow gets you in fast.
For server-side bots and CI/CD, bot tokens are fully supported via agent-slackbot, agent-discordbot, agent-whatsappbot, agent-wechatbot, and agent-channeltalkbot.
Inspired by agent-browser from Vercel Labs.
bun install # Install dependencies
bun link # Link CLI globally for local testing
bun test # Run tests
bun test:e2e # Run e2e tests
bun typecheck # Type check
bun lint # Lint
bun lint:fix # Lint with autofix
bun format # Format
bun run build # Build
MIT
FAQs
Multi-platform messaging CLI for AI agents (Slack, Discord, Teams, Webex, Telegram, WhatsApp, LINE, Instagram, KakaoTalk, Channel Talk)
The npm package agent-messenger receives a total of 858 weekly downloads. As such, agent-messenger popularity was classified as not popular.
We found that agent-messenger demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.
Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.