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.
 |
 |
 |
 |
| Direct chat | Image sharing | Group chat | Local demo |
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.
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.
Toxcore transports encrypted packets between peers. Direct messages receive an additional Signal Double Ratchet layer, while identity and history remain in local storage.
Important
OmaQ is not published in the Arch User Repository (AUR) yet. Until an OmaQ package is available, install it through Omarchy's normal plugin command.
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, and enables OmaQ in the selected bar section. It waits for verified IPC and helper readiness without forcing another restart. Pass --section left or --section center to change the section.
If a successful install reports a current helper but OmaQ is still absent, refresh the shell:
omarchy restart shellRun the shell-off updater from the installed Git checkout:
~/.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. It exchanges the checkout while the shell is stopped and verifies the result. Active groups can defer helper activation. See the installation lifecycle for older installations, exact-commit pinning, backups, and recovery.
After an activated or current result, refresh the shell only if the interface has not reappeared:
omarchy restart shellRun the verified wrapper:
~/.config/omarchy/plugins/hancore.omaq/scripts/uninstall-omaq.shInteractive mode offers every remaining OmaQ data directory separately and defaults each answer to No. --yes retains all data. Dependency packages are never removed automatically. The wrapper only prints a non-recursive Pacman command for optional manual cleanup.
- Documentation index
- Illustrated user guide
- Installation lifecycle
- Security and privacy
- Current status
- 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.