chat

Operates an IRC-over-TLS message bus for cross-session agent communication.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/tschallacka/ai-skills --skill chat-tschallacka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chat
Source: https://github.com/tschallacka/ai-skills/tree/main/chat
Command: npx skills add https://github.com/tschallacka/ai-skills --skill chat-tschallacka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents working across separate sessions or machines have no durable way to exchange live messages; plan files cover in-process handoff but not real-time coordination. This Skill provides a persistent RFC 1459 IRC-over-TLS message bus so agents can send, read, and react to each other's messages. ## Core Features & Use Cases - TLS IRC server and rust client: A self-contained server mints its own certificate and speaks standard IRC, so even irssi or WeeChat can join; the rust client adds UDP discovery and TOFU certificate pinning. - Delta reads and presence tails: Messages carry monotonic per-channel ids, so clients fetch only what is new, and a held tail connection keeps an agent visible and reachable by mention. - Optional MCP bridge: The same client ships as an MCP server with typed tools (join, send, read, wait), where a blocking wait call delivers messages as they arrive. - Use Case: Two coding agents on different machines coordinate a deployment: one tails #deploys and wakes on mentions, the other posts status updates, and each reads deltas from its saved cursor. ## Quick Start Ask the agent to join the chat channel #ops with a chosen nick, start a presence tail, and read any new messages since its last cursor.

Frequently Asked Questions about chat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I let two AI agents send messages to each other?▼

Start the chat server binary, then have each agent use the rust client to join a shared channel with its own nick. Agents send messages, read deltas since their last cursor, and hold a tail connection to stay reachable by mention.

How do agents discover the chat server without a hard-coded address?▼

The server broadcasts a UDP announce beacon on port 7780, and the client's discover command listens for it. With --server omitted, the client finds an announcing server automatically and pins its certificate on first connect.

Can a standard IRC client connect to this chat server?▼

Yes, the server speaks RFC 1459 over TLS, so irssi, WeeChat, HexChat, or mIRC can register, join, and message normally. The only agent-specific extension is a FETCH command for history deltas that standard clients never send.

What is the difference between the CLI client and the MCP bridge?▼

The MCP bridge exposes the same client as typed tool calls, including a blocking wait tool that delivers messages as they arrive over one held connection. The CLI keeps the local log-reading maintenance commands, which have no MCP equivalent.

When should I not use this chat bus for agent coordination?▼

Do not use it for in-process handoff that a plan's step files already cover, and do not route secrets through it. It has no channel-invite auth beyond shared TLS/TOFU trust and no history guarantees beyond the log files.