// Console Applications · THE IRC UNDERGROUND

BitchX: the old-school IRC survival guide

Channel hopping, slash commands and green-on-black nostalgia. Get the classic IRC client running on Slackware 15.0—then keep it alive inside tmux.

When IRC ruled the console

Before endless feeds, there were IRC channels, nicknames, scrolling text and a blinking cursor. BitchX is a legendary terminal-based IRC client descended from ircII/EPIC. It was loud, configurable and built for people who wanted to chat without leaving the shell.

This walkthrough uses Slackware 15.0, but many commands are familiar across Unix-like systems. The SlackBuilds.org package is based on a 2019-maintained fork of the older software; features can differ between builds.

Install with sbopkg on Slackware

If you already installed BitchX through sbopkg, skip to the next step. Otherwise, SlackBuilds.org lists network/bitchx for Slackware 15.0. sbopkg is a convenient front end for building and installing SlackBuild packages.

su -
sbopkg

In sbopkg, update/sync the package repository if needed, search for bitchx, and select its build/install action. Review dependencies and build output. When finished, exit the root shell with exit. Run IRC as your normal user, not root.

// CASE MATTERS

The package is called bitchx, but SlackBuilds.org says the executable is BitchX with a capital B and X. Linux filenames are case-sensitive. Yes, it catches everybody at least once.

Check the binary and launch

command -v BitchX
BitchX -v

The first command shows the executable path; the second prints version information on supported builds. To start without immediately auto-connecting, try:

BitchX -N -n DarkPCNick

Change DarkPCNick to your own nickname. The -N option tells classic BitchX not to automatically connect to its default server; check man BitchX if your build behaves differently.

Connect to an IRC network—use TLS

From inside BitchX, type the following IRC command (not at the Bash prompt). For Libera.Chat, the normal encrypted port is 6697:

/SERVER -SSL irc.libera.chat:6697

BitchX maintainers documented the /SERVER -SSL host:port form for SSL-capable versions. Your build must include working TLS support: if the command fails, check /EHELP SERVER and your build information. Different forks may use different TLS syntax.

Libera.Chat also offers unencrypted ports, but don’t send passwords or private information on plaintext IRC. If your particular BitchX build cannot establish TLS, use a modern TLS-capable client such as Irssi or WeeChat rather than turning encryption off for a login.

Join a channel and say hello

Once connected, try a public channel appropriate for your interests. The channel name below is an example; it may not exist or be active on your chosen network.

/JOIN #example
Hello from the Dark Side of Unix!

Lines beginning with / are client commands. Plain text is sent to your active channel. Start by reading the topic and any channel rules; IRC etiquette still matters.

Slash commands you will actually use

Type inside BitchXWhat it does
/NICK RetroColChange your nickname
/JOIN #exampleJoin a channel
/PART #exampleLeave a channel
/MSG Friend helloSend a direct message
/QUERY FriendOpen a private conversation; /QUERY alone ends it on classic builds
/ME wavesSend an action message
/WHOIS FriendAsk the server for nickname information
/NAMES #exampleList channel nicknames
/HELP or /EHELPAsk your installed version for help
/QUIT Time for coffeeDisconnect cleanly

Nicknames and channel names are examples. Command options can vary across old BitchX releases, so use the client’s own help if something behaves differently.

Channels, queries and windows

In classic BitchX builds, /WINDOW controls IRC windows; /QUERY makes private conversations easier to follow. Try the built-in help for your exact version:

/EHELP WINDOW
/QUERY Friend

For a less cluttered display, keep BitchX in its own tmux window and put normal shell work in another. You can swap between them without mixing shell input with IRC commands.

Personalise without exposing secrets

BitchX reads per-user settings such as ~/.bitchxrc in traditional builds. To choose a nickname on startup, you can also set an environment variable in your regular user shell. For a one-session test:

export IRCNICK=RetroCol
BitchX -N

Many builds also support /SET (view/change options) and /SAVE (save configuration). Explore those interactively before putting settings into ~/.bitchxrc. Keep any authentication secrets out of screenshots, public website files and world-readable dotfiles.

The DarkPC combo: BitchX inside tmux

For the full console workstation, put NeoMutt mail in another tmux window. IRC in one, inbox in the next, and not a mouse in sight.

This is where a console-first workstation shines. Start a named tmux session, launch the IRC client, and leave it running while you step away.

tmux new -s irc
BitchX -N -n RetroCol

After opening BitchX, press Ctrl+B, then D to detach from tmux. Later, return to the same session:

tmux attach -t irc

While attached, press Ctrl+B, then C for a new shell window and Ctrl+B, then 0 to return to your first window. tmux keeps a running terminal available after detaching, not across a reboot or an IRC network drop.

// NEXT LEVEL

New to sessions and panes? Read the DarkPC tmux guide and build a workspace with IRC, a shell and system monitoring. That’s the 1990s—upgraded.

A little 2026 IRC common sense

  • Prefer encrypted TLS connections. Old clients may have incomplete TLS, certificate checks or modern authentication support.
  • Do not blindly run IRC scripts or accept DCC transfers. Treat unsolicited files and links as untrusted.
  • Assume public channels are public. Channel logs and bots may archive conversations.
  • Never run your chat client as root. Use your normal Slackware user account.
  • Check the project age. SlackBuilds.org currently packages a BitchX fork updated in 2019, not a newly audited secure messenger.

When the cursor fights back

ProblemTry this
BitchX: command not foundCheck capitalisation with command -v BitchX; verify the package installed.
Cannot connect with TLSCheck the client build’s SSL support and syntax; use a maintained TLS-capable client if needed.
Terminal display looks brokenTry a capable terminal, check echo "$TERM", and consult the local manual.
Session disappears after rebootExpected: tmux cannot keep processes alive across reboot.
Can't find a channelCheck spelling and network, then consult the network's channel directory.

And remember: /HELP, /EHELP and man BitchX are friends. Nothing beats the documentation for the binary actually installed on your machine.

// THE DARK SIDE OF UNIX

“The cursor never sleeps.” Build it, boot it, learn it—and leave the bloated desktop alone for an evening. ☾

References and further reading