Desktop client for Matrix using Qt and C++20.
The motivation behind the project is to provide a native desktop app for [Matrix] that feels more like a mainstream chat app ([Element], Telegram etc) and less like an IRC client.
For other options and details see the Installation section.
Help us with translations so as many people as possible will be able to use nheko!
The current implementation is mostly stable, but it was never audited. If you rely on it for security, we can't make any guarantees.
Most of the features you would expect from a chat application are missing right now but we are getting close to a more feature complete client. Specifically there is support for:
-p name).Releases for Linux (Flatpak), macOS (disk image) & Windows (x64 msix or appinstaller) can be found in the GitHub releases. The appinstaller on Windows will regularly check our servers for updates. The msix won't.
sudo pacman -Syu nhekoThe development version is available in the AUR:
yay -S nheko-git # Or your favorite way of installing AUR packagesNheko requires a secret server to run, so you'll need to install and configure a service such as KDE Wallet or GNOME Keyring if not provided by your desktop environment.
sudo apt install nhekosudo dnf install nhekosudo eselect repository enable guru
sudo emaint sync -r guru
sudo emerge -a nhekoIf you are using Gnome Keyring or KeepassXC as your secrets daemon, ensure that the keyring useflag is enabled on dev-libs/qtkeychain.
sudo urpmi nheko# Imperatively: (not recommended)
nix-env -iA nixpkgs.nheko
# In an ephemeral shell: (recommended if you just want to try it out without committing to a full installation)
nix-shell -p nheko --run nheko
# Note: The above command will both install and run Nheko.
# To stop it from running immediately, just remove the `--run nheko` from the end.Alternatively, add it to your config in one of the following ways: (recommended for long-term installation)
System-wide:
environment.systemPackages = with pkgs; [
# ...
nheko
# ...
];User-specific:
users.users.<user>.packages = with pkgs; [
# ...
nheko
# ...
];via home-manager:
programs.nheko.enable = true;Make sure you have the testing repositories from edge enabled. Note that this is not needed on postmarketOS.
sudo apk add nhekoNote: these instructions have only been tested on Tumbleweed.- First, install nheko:
sudo zypper in nhekoIf you want to add jdenticon support:
sudo zypper install qt-jdenticonflatpak install flathub im.nheko.Nhekoguix install nhekoInstall nheko via the Discover app in Desktop Mode (this installs the flatpak). To also make it work in Game Mode you'll have create a wrapper script that starts kwalletd and then nheko. You can create /home/deck/nheko.sh with the following content and then add this script as a "Non-Steam Game" to Steam.
#!/bin/sh
kwalletd6&
flatpak run --env=XDG_CURRENT_DESKTOP=KDE --env=KDE_SESSION_VERSION=5 --branch=stable --arch=x86_64 --command=im.nheko.Nheko --file-forwarding im.nheko.Nheko @@u @@with homebrew:
brew install --cask nhekowith Chocolatey:
choco install nheko-rebornnheko does not provide binaries for any D-Bus plugins. However, we do provide the following list of known plugins:
Q: Why don't videos run for me on Windows?
A: You're probably missing the required video codecs, download K-Lite Codec Pack.
Q: What commands are supported by nheko?
A: See https://github.com/Nheko-Reborn/nheko/wiki/Commands
Q: Does nheko support end-to-end encryption (EE2E)?
A: Yes, see feature list
Q: Can I test a bleeding edge development version?
A: Checkout nightly builds https://matrix-static.neko.dev/room/!TshDrgpBNBDmfDeEGN:neko.dev/
Q: How do I add stickers and custom emojis?
A: Stickers and custom emojis are organized in image packs. There is one user image pack that only your account has access to and there are room image packs that are accessible by everyone in the room they are defined in. You can activate a room image pack globally to use it in any room.
To manage image packs in nheko, go to the room settings and enter the Sticker & Emote Settings. You will see the Private pack (your user image pack) and can edit it there. The Shortcode is a unique identifier you use to select the image with and the Body is the alternate text that is displayed on clients that don't support images (like the alt tag in HTML images).
If you have the necessary permissions you can create new room packs with the button at the bottom of the image pack list. They are the same as the user pack but you can create as many as you want and everyone in the room can use them. It might be a good idea to create an extra room just for your image packs to make sharing easier.
Q: I can't see some image types!
A: Nheko uses Qt's image plugins to render images. You might need to install
additional packages to display some image types like webp. Usually those
packages are called qt6-image-formats-plugins, qt6-imageformats or similar.
KDE has similar plugins, that can extend the supported image types even more.
-DVOIP=OFF to disable.).-DSCREENSHARE_X11=OFF.-DLIBSECRET_SUPPORT=OFF.)Nheko can use bundled version for most of those libraries automatically, if the versions in your distro are too old.
To use them, you can enable the hunter integration by passing -DHUNTER_ENABLED=ON.
It is probably wise to link those dependencies statically by passing -DBUILD_SHARED_LIBS=OFF
You can select which bundled dependencies you want to use by passing various -DUSE_BUNDLED_* flags. By default all dependencies are bundled if you enable hunter. (The exception to that is OpenSSL, which is always disabled by default.)
If you experience build issues and you are trying to link mtxclient library without hunter, make sure the library version(commit) as mentioned in the CMakeList.txt is used. Sometimes we have to make breaking changes in mtxclient and for that period the master branch of both repos may not be compatible.
The bundle flags are currently:
A note on bundled OpenSSL: You need to explicitly enable it and it will not be using your system certificate directory by default, if you enable it. You need to override that at runtime with the SSL_CERT_FILE variable. On Windows it will still be using your system certificates though, since it loads them from the system store instead of the OpenSSL directory.
If you don't want to install any external dependencies, you can generate an AppImage locally using docker. It is not that well maintained though...
make docker-app-imagesudo pacman -S qt6-base \
qt6-tools \
qt6-multimedia \
qt6-svg \
cmake \
gcc \
fontconfig \
lmdb \
lmdbxx \
cmark \
qtkeychain-qt6 \
nlohmann-json…Build requirements + qml modules needed at runtime (you may not need all of them, but the following seem to work according to reports):
sudo apt install --no-install-recommends g++ cmake make zlib1g-dev libssl-dev libolm-dev liblmdb-dev libcmark-dev nlohmann-json3-dev libspdlog-dev libevent-dev libcurl4-openssl-dev libre2-dev libxcb-ewmh-dev asciidoc-base \
qt{base,declarative,tools,multimedia,quickcontrols2-}5-dev libqt6svg5-dev qt6keychain-dev qml-module-qt{gstreamer,multimedia,quick-extras,-labs-settings,graphicaleffects,quick-controls2,quick-particles2} \
libgstreamer1.0-dev libgstreamer-plugins-{base,bad}1.0-dev qtgstreamer-plugins-qt6 libnice-dev ninja-buildlmdb++-dev is too old so bundled lmdbxx must be used.
libspdlog-dev in debian bullseye is too old (without backporting) so requires using h
No open issues yet, or sync has not completed.