Give your AI agent the power to read and send messages across Slack, Discord, Teams and more
A unified, agent-friendly CLI for messaging platforms. Zero-config credential extraction from your desktop apps—no OAuth flows, no API keys, no admin approval needed. Works out of the box.
- Why Agent Messenger?
- Installation
- Agent Skills
- Quick Start
- Supported Platforms
- Platform Guides
- Use Cases
- Philosophy
- Contributing
- Thanks
- License
Messaging platforms only offer Bot tokens for API access—your AI agent can never act as you. Agent Messenger extracts user credentials directly from your installed desktop apps, letting your agent operate on your behalf. Bot tokens are fully supported too for server-side and CI/CD use cases.
- Act as yourself, not a bot — Extracted user tokens let your agent operate on your behalf
- No API keys needed — Automatically extracts credentials from your installed desktop apps
- Zero setup — Credentials are auto-extracted on first command. No manual auth step required
- One interface, multiple platforms — Learn once, use everywhere (Slack, Discord, Teams)
- AI-agent friendly — JSON output by default, perfect for LLM tool use
- Agent memory — Remembers workspace IDs, channel names, and preferences across sessions
- Human friendly too — Add
--prettyfor readable output - Token efficient — CLI, not MCP. Load only what you need. (Why not MCP?)
npm install -g agent-messengerOr use your favorite package manager.
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 CLI
Agent Messenger includes Agent Skills that teach your AI agent how to use these CLIs effectively. Five skills are available:
agent-slack— Slack (user token, zero-config)agent-slackbot— Slack Bot (bot token, for server-side/CI/CD)agent-discord— Discordagent-discordbot— Discord Bot (bot token, for server-side/CI/CD)agent-teams— Microsoft Teams
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 skills add devxoul/agent-messengerclaude plugin marketplace add devxoul/agent-messenger
claude plugin install agent-messengerOr within Claude Code:
/plugin marketplace add devxoul/agent-messenger
/plugin install agent-messenger
Add to your opencode.jsonc:
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.
| Feature | Slack | Discord | Teams |
|---|---|---|---|
| Auto credential extraction | ✅ | ✅ | ✅ |
| Send & list messages | ✅ | ✅ | ✅ |
| Search messages | ✅ | ✅ | — |
| Threads | ✅ | ✅ | — |
| Channels & Users | ✅ | ✅ | ✅ |
| Reactions | ✅ | ✅ | ✅ |
| File uploads | ✅ | ✅ | ✅ |
| Workspace snapshots | ✅ | ✅ | ✅ |
| Multi-workspace | ✅ | ✅ | ✅ |
| Activity feed | ✅ | — | — |
| Drafts | ✅ | — | — |
| Saved items | ✅ | — | — |
| Unread messages | ✅ | — | — |
| Sidebar sections | ✅ | — | — |
| Bot support | ✅ | ✅ | — |
⚠️ Teams tokens expire in 60-90 minutes. Re-runagent-teams auth extractto refresh. See Teams Guide for details.
- Slack Guide — Full command reference for Slack
- Slack Bot Guide — Bot token integration for server-side and CI/CD
- Discord Guide — Full command reference for Discord
- Discord Bot Guide — Bot token integration for server-side and CI/CD
- Teams Guide — Full command reference for Microsoft Teams
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, and Teams — 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!
Why not MCP? MCP servers expose all tools at once, bloating context and confusing agents. Agent Skills + agent-friendly CLI offer a better approach—load what you need, when you need it. Fewer tokens, cleaner context, better output.
Why not OAuth? OAuth requires an app and it requires workspace admin approval to install, which can take days. This tool just works—zero setup required. For those who prefer bot tokens (e.g., server-side or CI/CD), see agent-slackbot.
Inspired by agent-browser from Vercel Labs.
bun install # Install dependencies
bun link # Link CLI globally for local testing
bun test # Run tests
bun typecheck # Type check
bun lint # Lint
bun run build # BuildMIT
{ "plugins": ["agent-messenger"], }