Configuration

Make conversations comfortable to read, choose how you share files, and move your network configuration between devices.

Appearance

Use Material You dynamic color or choose a curated editor and terminal palette. Families include Ayu, Catppuccin, Dracula, Everforest, Gruvbox, Kanagawa, Modus, Monokai, Nord, One Dark, Rosé Pine, Solarized, Tokyo Night, and Zenburn. See the full palette variants and attribution table.

Every dark palette can use True black backgrounds. This keeps the palette's accents while making the canvas black and using subtly palette-tinted near-black surfaces. The choice is remembered when you switch to a light theme and takes effect again when you return to a dark theme.

Palette colors are adapted to Material 3 roles and adjusted where needed for readable contrast. The feature overview also covers dynamic color and theming.

Chat and uploads

Choose a conversation layout and adjust chat behavior, previews, and replies. The chat view includes a unified chat list, grouped bubbles, day separators, event pills, inline images, and link previews. The composer supports nick autocomplete, replies, reactions, typing indicators, and slash commands; IRCv3 features depend on what your server supports.

The attachment chooser can share a photo, a file, your current draft as a link, or a new text paste. Review the destination and its privacy and expiry information before uploading. Public uploads must not contain sensitive information; even a secret link can be opened by anyone who has it. A Soju file host uses the connected chat's authenticated network file service, with retention set by that server.

See the documented chat features. Chat preferences and upload backend configuration are included in configuration exports, but uploaded files and upload history are not transferred by a configuration backup.

Configuration backups

Configuration backups do not include messages, drafts, or chat history. A .motdconfig file moves configuration between devices; it is not a backup of your conversations.

Exports include direct networks, bouncer roots and children, their relationships and ordering, connection and identity settings, TLS and proxy configuration, and user-facing preferences such as appearance, chat behavior, replies, upload backends, avatars, and delivery mode.

Choose an export mode

• Without credentials: excludes passwords and private connection links. This configuration-only JSON export is not encrypted.
• Encrypted with credentials: includes saved passwords and private connection links in a password-encrypted file. The payload uses AES-256-GCM encryption with a key derived from the export password. You need that password to import it.

Neither mode transfers Android KeyChain client certificates. Messages, buffers, read markers, drafts, cached previews, upload history and deletion tokens, generated push endpoints and keypairs, certificate pins, STS policy state, diagnostics, history cursors, and other runtime or cache state are excluded.

Choose an import mode carefully

• Merge updates matching networks in place and keeps networks that exist only on the destination device.
• Replace updates matching networks, adds missing networks, and deletes local-only network trees together with their local history. The configuration file does not contain that history to restore later.

The complete document is validated before local state changes. Unsupported versions, invalid configuration, wrong passwords, damaged files, or tampered encrypted data fail without applying the backup.

A credentials-excluded import keeps existing local credentials on matching networks. New networks that need an omitted SASL password, server password, or VLESS link remain disconnected until you provide it. A network that used a client certificate is also imported disconnected: select a certificate on the destination device before connecting.

Read the full configuration backup format specification for the exact included fields, encryption format, exclusions, and import rules.