OmaQ is invite-only chat for the Omarchy bar: no account, phone number, or public user search. Create your identity locally, then connect with a one-time private invitation link or QR code.
Tox encrypts transport end to end, and direct text messages add the Signal Double Ratchet. OmaQ disables direct UDP discovery and hole punching, so contacts do not receive each other's IP addresses.
OmaQ runs no servers and has no operator access to your identity, contacts, or messages. Public Tox bootstrap and relay nodes can forward encrypted packets but cannot read message contents. Local filesystem permissions protect Ratchet state, avatars, receipts, preferences, and chat history that are not covered by the optional tox.save passphrase.
Use OmaQ only for lawful private communication with people you trust.
Use either one or both. They share one identity, contact list, and history.
The terminal client does not need the bar; it starts OmaQ's helper itself. To use only the terminal, run omarchy plugin disable hancore.omaq after installing. The updater needs the plugin enabled, so run omarchy plugin enable hancore.omaq before an update.
While the bar runs, quitting the terminal client changes nothing. Once the bar is disabled, quitting takes you offline from the next login on, unless you belong to a private group. After updating an older installation, create the command once with ~/.config/omarchy/plugins/hancore.omaq/cli/omaq.py --link.
omarchy plugin add https://github.com/HANCORE-linux/OmaQ.git --yes &&
~/.config/omarchy/plugins/hancore.omaq/install.sh --yesinstall.sh installs dependencies, builds the helper, enables OmaQ in the bar, and creates the omaq-connect command. Pass --section left or --section center to change the bar section. Other Linux distributions are not supported yet.
If a successful install reports a current helper but OmaQ is still absent, refresh the shell:
omarchy restart shell~/.config/omarchy/plugins/hancore.omaq/scripts/update-omaq.sh --yesDo not update OmaQ with omarchy plugin update, including the all-plugins form. It updates the checkout without rebuilding the native helper. When needed, the updater builds outside the monitored plugin tree and verifies the result; the installation lifecycle explains the details.
After an activated or current result, refresh the shell only if the interface has not reappeared:
omarchy restart shell~/.config/omarchy/plugins/hancore.omaq/scripts/uninstall-omaq.shIt asks about each remaining OmaQ data directory, with No as the default; --yes keeps all data. It also removes the omaq-connect command. Dependency packages are never removed automatically.
Project independence and lawful use
OmaQ is general-purpose software intended for lawful use. This policy adds no restrictions to the open-source licenses.
The project answers lawful requests from public authorities truthfully, including when it does not possess the requested data. OmaQ operates no service and cannot provide identities, contacts, messages, or history stored only on your devices.
The project neither cooperates with resellers nor offers reseller, original equipment manufacturer (OEM), white-label, or exclusive distribution arrangements. This policy neither limits open-source redistribution rights nor implies project affiliation or endorsement.
OmaQ keeps one codebase and all security-relevant changes public and reviewable. The project offers no private, privileged, selectively weakened, or organization-specific builds, including for public authorities, companies, or resellers.
- Illustrated user guide, including the terminal client
- Installation lifecycle
- Security and privacy
- Current status
- Documentation index
- Third-party components
The QML plugin is licensed under the MIT License. OmaQ's helper source is GPL-3.0-or-later; the distributed helper binary is GPL-3.0-only because it also links to libsignal-protocol-c. See Third-party components for dependency and asset licenses.



