···101101 - IRC mentions (`@nick` or `nick:`) are converted to Slack mentions for mapped users
102102 - IRC formatting codes are converted to Slack markdown
103103 - IRC `/me` actions are displayed in a context block with the user's avatar
104104+ - Thread replies: Use `@xxxxx` (5-char thread ID) to reply to a Slack thread from IRC
104105- **Slack → IRC**: Messages from mapped Slack channels are sent to their corresponding IRC channels
105106 - Slack mentions are converted to mapped IRC nicks, or the display name from `<@U123|name>` format
106107 - Slack markdown is converted to IRC formatting codes
107108 - File attachments are uploaded to Hack Club CDN and URLs are shared
109109+ - Thread messages are prefixed with `@xxxxx` (5-char thread ID) to show they're part of a thread
110110+ - First reply in a thread includes a quote of the parent message
108111- **User mappings** allow custom IRC nicknames for specific Slack users and enable proper mentions both ways
112112+113113+#### Thread Support
114114+115115+The bridge supports Slack threads with a simple IRC-friendly syntax:
116116+117117+- **Slack → IRC**: Thread messages appear with a `@xxxxx` prefix (5-character thread ID)
118118+ - First reply in a thread includes a quote: `<user> @xxxxx > original message`
119119+ - Subsequent replies: `<user> @xxxxx message text`
120120+- **IRC → Slack**: Reply to a thread by including the thread ID in your message
121121+ - Example: `@abc12 this is my reply`
122122+ - The bridge removes the `@xxxxx` prefix and sends your message to the correct thread
123123+ - Thread IDs are unique per thread and persist across restarts
109124110125The bridge ignores its own messages and bot messages to prevent loops.
111126