irc

the irc crate is a thread-safe and async-friendly IRC client library written in Rust. It implements the IRC protocol as specified in RFC 2812 along with IRCv3.1 and IRCv3.2 extensions and several common features from popular IRC daemons, exposing a high-level async API for connecting to servers, joining channels, and reacting to messages.

Built on Tokio and futures, it provides a stream of incoming messages and ergonomic sending helpers, with configuration via structs or TOML/JSON/YAML files. It powers a range of Rust IRC software including terminal clients, bouncers, and bot frameworks.

What You Get

• An async Client with a message Stream and Sender for reading and writing IRC protocol events.
• Compliance with RFC 2812 plus IRCv3.1/3.2 capabilities and CTCP support.
• Flexible configuration via a Config struct or TOML/JSON/YAML files behind cargo features.
• Pluggable TLS backends (native-tls or rustls) and optional SOCKS proxy support.
• The separate irc-proto crate for low-level message parsing and command types.

Common Use Cases

• Writing IRC bots that listen for commands and respond in channels.
• Building terminal IRC clients or bouncers on top of a reliable async protocol layer.
• Integrating IRC connectivity into a Rust service for notifications or chat bridging.

Under The Hood

Architecture - The crate is a Cargo workspace split into the high-level irc client and the low-level irc-proto protocol crate. src/client/ holds the async client: conn.rs/transport.rs manage the TCP/TLS connection and framing, mod.rs builds a Client that exposes an incoming message Stream and an outgoing Sender, and data/config.rs handles configuration (including proxy and user data). irc-proto supplies message parsing, command enums, and IRCv3 capability handling that the client layer drives.

Tech Stack - Rust 2018 edition (MSRV 1.80) built on Tokio and the futures ecosystem. TLS is feature-selected between native-tls and rustls (with webpki/rustls-native-certs), config parsing uses serde with toml/json/yaml backends, and tokio-socks provides optional proxy support.

Code Quality - The codebase includes a mock.rs client for testing, numerous runnable examples/, and CI workflows, and it is a long-standing, well-documented crate that many downstream projects depend on. Errors are consolidated in error.rs, and feature flags keep optional dependencies isolated.

API Design - The high-level API is intentionally approachable: importing irc::client::prelude gives you everything needed to connect, and the async/await stream model (introduced in v0.14) reads naturally with while let Some(message) = stream.next().await. Configuration via struct or file lowers the barrier to a first working bot, while the separate protocol crate is available when finer control is needed.