IRC Documentation · Beginner
QUIT command: terminate an IRC connection
QUIT requests the closure of the IRC connection concerned. In an ordinary connection, other members see their departure from shared channels. Stopping a connection does not erase accounts or copies of messages already distributed.
Dialova Team · Verified on
Syntax and Parameters #
QUIT [:<raison>]| Parameter | Meaning |
|---|---|
| Reason | Optional departure message; it can be broadcast and logged. |
Commented Example #
C: QUIT :À bientôt
S: :Alice!alice@cloak.example QUIT :À bientôtNicknames, hosts, and text in this exchange are fictional. The client may display responses in a more readable format than the presented frames.
Possible Responses and Errors #
| Response | Understanding |
|---|---|
| QUIT | Departure announced to concerned clients; the sender's link closes. |
| Error | Typical Cause |
|---|---|
| No universal disconnection acknowledgement | Closing the transport terminates the exchange; do not assume a final success message displayed to the client. |
Rights, Compatibility, and Precautions #
With a bouncer or a persistent account, closing the interface may detach a session while leaving the IRC presence in place. Multi-client operation is the responsibility of the service used; QUIT therefore does not always mean account disappearance on all devices.
On Dialova, the 'Keep Connection Alive' option should be distinguished from the Web tab's state. Messages already recorded on the site remain in the history according to its retention rules.
Frequently Asked Questions #
Should I use PART or QUIT? PART is suitable for leaving a channel; QUIT terminates the concerned connection.
Is a QUIT reason private? No. Avoid sensitive information, even if the text seems innocuous.
Sources & Verification
Examples use pseudonyms and fictional domains, except for explicitly documented connection points. Network-specific extensions and settings are noted in the text.
- Modern IRC — spécification du protocole client ↗Source Specification · consulted on 2026-10-29
- RFC 2812 — Client Protocol (2000) ↗Source Historical · consulted on 2026-10-29