pantalk

<p align="center">
  <img src="https://pantalk.dev/icon.svg" alt="Pantalk" width="80" height="80" />
</p>

<h1 align="center">Pantalk</h1>

<p align="center">
  <strong>Give your AI agent a voice on every chat platform.</strong><br/>
  A lightweight daemon that lets AI agents send, receive, and stream messages across Slack, Discord, Mattermost, Telegram, WhatsApp, IRC, Matrix, Twilio, and Zulip through a single interface.
</p>

<p align="center">
  <a href="https://pantalk.dev">Website</a> · <a href="https://pantalk.dev/about">About</a> · <a href="#quick-start">Quick Start</a> · <a href="#platform-setup">Platform Setup</a>
</p>

---

## The Problem

AI agents need to communicate with humans where they already are - Slack, Discord, Mattermost, Telegram, WhatsApp, IRC, Matrix, Twilio, Zulip. But every platform speaks a different protocol. Building an agent that can participate in conversations across all of them means writing and maintaining separate integrations before your agent can even say "hello."

## The Solution

Pantalk gives your AI agent a single, consistent interface to all chat platforms. One daemon (`pantalkd`) handles the upstream complexity - auth, sessions, reconnects, rate limits - while your agent talks through simple CLI commands or a Unix domain socket with a JSON protocol.

```mermaid
graph TD
    Agent["Your AI Agent<br/><em>(any language, any framework)</em>"]
    Agent -->|send| Socket
    Agent -->|history| Socket
    Agent -->|notify| Socket
    Agent -->|stream| Socket
    Socket["Unix Domain Socket<br/><em>(JSON protocol)</em>"]
    Socket --> Daemon["pantalkd<br/><em>(daemon)</em>"]
    Daemon --> Slack
    Daemon --> Discord
    Daemon --> Mattermost
    Daemon --> Telegram
    Daemon --> WhatsApp
    Daemon --> IRC
    Daemon --> Matrix
    Daemon --> Twilio
    Daemon --> Zulip
    Daemon --> More["..."]
```

## Why Pantalk

|                        | Without Pantalk            | With Pantalk                  |
| ----------------------