README
¶
OmaChat
A Native Omarchy Plugin for Google Messages, WhatsApp, Telegram, and Messenger. Read and reply to conversations in a native panel with separate service sessions, conversation drafts, history, and inline media.
Current stable release: 0.5.4. Release notes.

The preview shows the current QML panel with fictional contacts and messages, all four service tabs, unread badges, and reactions using the Tokyo Night base palette. Connection and delivery states are simulated. Never include private conversations or account details in public screenshots.
More theme examples: Catppuccin Latte and Gruvbox


These demo captures use stock theme base colors with default control styling. See the gallery and reproduction details.
Unified inbox and offline emoji search


These captures use fictional conversations and simulated connection states. The unified example has Google Messages disabled.
Install and build
On an Omarchy desktop with the Quickshell plugin system:
omarchy plugin add https://github.com/onelegdave/omachat --enable
Open OmaChat from the bar. All services use one helper, omachatd, built
locally from vendored source. Building requires Go, Python 3, and a C compiler
(gcc or clang), even if you only use Google Messages or Telegram.
No helper binary is shipped in Git or downloaded by OmaChat.
OmaChat remains an anchored bar panel by default. Select Pop out in the panel header when you want a standalone pop-out. The pop-out includes its own Tiled and Floating choices, which affect only that OmaChat window and do not change your desktop-wide window settings. Select Return to panel to move the same conversation view, including its current drafts and selection, back to the bar.
In Settings > Appearance, enable Always open popped out to make future bar or IPC opens use the standalone window automatically, then choose whether that window should open Floating or Tiled. The preference does not open OmaChat at shell login, and disabling it restores the anchored-panel default.
OmaChat never installs dependencies automatically. Settings includes a dependency checklist with source-review links and optional Install buttons. Installation opens a terminal for your confirmation and keeps the package manager's own confirmation prompt. You decide which tools and features you want. You can also install tools manually. For example:
omarchy pkg add go gcc python
Then select Build helper in the panel. This compiles the included source
with go build -mod=vendor; it does not install packages or download modules.
The first build can take several minutes depending on your hardware. Go may
show no output while compiling. Wait without restarting the Omarchy shell;
the helper starts automatically on success, or the panel displays a build error.
The shell owns the helper as a child process. There is no systemd unit,
installer hook, or automatic privileged step. Only the explicit dependency
Install action can request sudo in a terminal, after your confirmation.
Text fields paste through a separate, bounded clipboard reader. Ctrl+V,
Shift+Insert, the Paste menu action, and middle-click use the same protection.
A paste must finish within 1.5 seconds and contain at most 64 KiB of UTF-8
text; incomplete, oversized, or invalid transfers leave the field unchanged.
Search and credential fields also have smaller length limits. Pasting requires
Python 3 and wl-paste from wl-clipboard; missing tools produce a visible error.
See clipboard safety and verification limits.
See dependencies and optional features for the full tool list. Availability varies by desktop; do not assume a tool is installed.
Updates
Open Settings > Updates to see your installed version, check for a newer release, and read its release notes. Daily checks are optional and off by default. Checks contact GitHub for public release metadata; they do not send messages or account credentials. GitHub can see the request's IP address. You can dismiss a release notice until another release is available.
Select Update to open Omarchy's updater in a terminal. Review its changes and confirm there. You can also run it yourself:
omarchy plugin update onelegdave.omachat
After the plugin reloads, follow any Rebuild helper notice in Settings. Wait for the build and helper restart to finish before treating the update as complete. A failed build keeps the previous executable; review the error and retry after addressing it. Updating does not deliberately remove your paired accounts. Read release notes for any migration or re-pairing requirements.
Omarchy's updater follows the repository's default branch, not a specific
release tag. A canceled or failed update has not installed the release.
If the panel does not reload, run omarchy restart shell, then check Settings
again. If a helper outside this plugin is still running, the app may ask you
to restart the shell rather than claiming the new helper is active. If that
does not resolve it, stop the separately launched omachatd first.
For notifications outside OmaChat, open the GitHub repository, select Watch > Custom > Releases, and follow the release notes.
Connect your services
Each service is optional and pairs only when you request it.
| Service | Setup | Guide |
|---|---|---|
| Google Messages | Sign in to Messages for web in a supported Chromium-family browser, then select Pair with Google and confirm the matching emoji on the phone. | Google Messages |
| Select Use a QR code in the WhatsApp tab and scan it using the phone's Linked devices screen. | ||
| Telegram | Configure your own Telegram API credentials, select Pair with Telegram, and scan the QR code from Telegram's Devices screen. | Telegram |
| Messenger | Sign in to Facebook or Messenger in a supported Chromium-family browser, then select Pair from browser. | Messenger |
The guides include requirements, pairing, supported features, limitations, storage, and recovery. A service losing authentication does not automatically start pairing again.
Features and limits
| Feature | Google Messages | Telegram | Messenger | |
|---|---|---|---|---|
| Conversation list, text, per-chat drafts | Yes | Yes | Yes | Yes |
| Photos and captions | Yes | Yes | Yes | Yes |
| Send GIF files | Yes | Yes (ffmpeg) | No dedicated GIF sending support | Yes |
| Voice recording and playback | Optional ffmpeg/ffplay | Optional ffmpeg/ffplay | Optional ffmpeg/ffplay | Optional ffmpeg/ffplay |
| Reactions | Yes | Yes | Yes (chat-dependent) | Yes |
| Incoming static WebP stickers | No dedicated sticker support | Yes | Yes | Yes |
| Older history | Fetch older pages | Page cached history and request an older phone page | Fetch older pages | Fetch older pages |
| Calling | Unavailable | Unavailable | Unavailable | Unavailable |
Threads open with the latest 60 messages; Load older messages pages back while preserving the reading position. WhatsApp pages cached history offline and can request an older page from the phone at the history boundary when connected; the phone may not provide every requested message. The WhatsApp history cache is configurable at 64, 128, 256, or 512 MB (128 MB by default), with older local messages evicted automatically as space is needed. Telegram animated TGS/video stickers are unsupported, and media references need refreshing after restart. WhatsApp view-once/ephemeral and Telegram self-destructing media are not saved or reopened.
WhatsApp direct-chat and group photos and Telegram user, group, and channel photos load in the background and are cached locally. Refresh picks up changed or removed photos; unavailable photos fall back to initials.
The services use unofficial protocol clients and can stop working when their providers change. Automated checks do not establish live account compatibility for every service. See verification history for dated evidence and its limits.
Everyday use
Choose enabled services in Settings > Services. Apply briefly restarts the shared helper, so enabled services reconnect. Disabled services stop background activity and disappear from the tabs without deleting credentials. You may turn off every service. Fresh installations ask you to choose before connecting; upgrades preserve existing choices. See service opt-outs.
Settings includes text-size choices, service setup guides, optional-tool instructions, and upstream credits. Setup messages wrap and scroll, including at larger text sizes. Popup and message text adapt to the current theme's background for readable contrast.
Switch services with the header tabs, choose a conversation, and press Enter to send. Drafts stay with their service and conversation. Right-click a bubble to copy it. Middle-click the bar icon to refresh; its badge counts unread conversations across active services, and each service tab shows its own unread badge while the app is open.
The optional Unified inbox in Settings > Inbox combines conversations from enabled services in the All tab. It defaults off. Ctrl+Shift+A toggles the preference; the All list keeps each conversation's service badge, message routing, and draft separate. Its connection badge summarizes enabled services, including a connected-service count when only some are online. Hide or show its sidebar with the same header control as an individual inbox. Disabling a service removes its rows.
Use Ctrl+Tab to cycle through visible tabs or Ctrl+1 through Ctrl+9 to select a visible tab by position. Outside text fields, j/k and the arrow keys move through conversations, / searches, u opens the next unread, and i focuses the composer. ? or Ctrl+Shift+P opens searchable keyboard help. Customize app actions in Settings > Keyboard. Escape dismisses the innermost picker, then leaves text entry, then closes the surface; drafts remain.
Ctrl+E opens offline emoji search. Search by English names, keywords, glyphs, or GitHub/JoyPixels-style aliases, with typo tolerance. Search text clears on reopen unless Keep previous emoji search text is enabled in Settings. The bundled metadata and license notices ship with the plugin; emoji search makes no network requests and installs no packages.
Desktop notifications are enabled by default for new incoming messages while OmaChat is running. Open Settings > Notifications to turn them off or send a test notification. Alert text shows only OmaChat, the service, and "New message"; names and message text stay in OmaChat. The icon uses the conversation's cached profile photo when available, with a generic message icon as the fallback. Test notifications use the generic icon. Clicking an alert opens its conversation. The conversation you are actively reading stays quiet; history refreshes, outgoing messages, reactions, and receipt updates do not produce new alerts. Your desktop controls Do Not Disturb and sounds.
Notification previews (removed in 0.5.4)
What was removed. Earlier releases had an optional Show sender and message previews setting, off by default. When it was on, alerts showed the conversation name and the start of the message. OmaChat 0.5.4 removes the setting, and alerts always read "OmaChat · service" and "New message". If you had previews on, the panel turns them off right after the update, and the rebuilt helper deletes the saved setting.
Why. Omarchy's notification service saves each alert to its history by
starting a bash command with the whole notification, text included, as a
command-line argument. Any account on the same computer, including system
service accounts, can normally read other processes' command lines through
/proc, so previews could be read by someone other than you. OmaChat cannot
control what a notification service does with alert text, so it no longer sends
names or message text at all. This was found during
Omarchy Marketplace review.
Previews may return if Omarchy stops passing notification text on command lines.
If you still want previews. The
notification-previews
branch is the current release with the setting restored, still off by default.
It is not part of the Marketplace listing or its review. Use it only if you
accept that other accounts on your computer may be able to read your message
previews. To switch an installed copy:
cd ~/.config/omarchy/plugins/onelegdave.omachat
git fetch origin notification-previews
git switch --track origin/notification-previews
Then use Build helper when the panel asks, and turn on the setting in
Settings > Notifications. The in-app Update button and
omarchy plugin update follow the main release only and will report an error on
this branch, so update with
git -C ~/.config/omarchy/plugins/onelegdave.omachat pull --ff-only and rebuild
the helper. To return to the main release, run
git -C ~/.config/omarchy/plugins/onelegdave.omachat switch main, then rebuild
the helper.
Use the arrow beside the OmaChat title to hide the conversation sidebar; the menu button brings it back. OmaChat remembers this layout, the last service, and the last conversation in each service across shell restarts. Reopening the panel or moving between the panel and pop-out scrolls to the newest messages and focuses the message input so you can type right away. If the remembered conversation is not available, the inbox stays visible so you can choose another chat. Read-only conversations do not focus the composer. Window preferences apply after a confirmed configuration read. If the helper is offline, the anchored panel stays available for recovery. Pop-out layout changes target only the window owned by this shell process; no persistent compositor rule is installed.
Pick an attachment from the composer. Google Messages sends captions separately after the attachment; check the conversation before retrying a caption reported as unconfirmed. WhatsApp, Telegram, and Messenger include captions with images; Messenger sends a document caption as a separate message. Failed media downloads can be retried. Incoming GIFs play inline; video opens in an external player.
For voice notes, choose Rec, record, Play
to preview, then send. Voice needs optional ffmpeg and ffplay. Google
Messages, WhatsApp, and Messenger record M4A; Telegram records OGG/Opus.
WhatsApp uses a standard audio clip instead of native PTT because linked-device
OGG/Opus notes fail to play on iPhone. Google Messages, WhatsApp, and Messenger
send GIF files from your computer through the attachment picker. OmaChat has no
in-app GIF search and sends no search terms or API keys to a third-party GIF
service. WhatsApp uses ffmpeg to convert GIF files to the MP4 playback format
required by its protocol.
Message reactions are available on Google Messages, WhatsApp, Telegram, and Messenger. Telegram supports the standard emoji choices shown by OmaChat; individual chats or channels may restrict which reactions Telegram accepts.
Use Tab to move between controls, arrow keys and Enter to open a conversation, and Space or Enter to activate focused buttons. Pending and failed text sends remain visible when you return to their conversation during the current shell session.
Privacy, storage, and removal
Sessions, chat caches, media, and drafts are separated by service. All four services share the helper process and configuration file. Private files are kept locally; see Security for protections and limitations. Each service limits its downloaded attachment cache to 256 MiB and evicts older files as new downloads complete.
| Location | Contents |
|---|---|
~/.config/omarchy/plugins/onelegdave.omachat/ |
Plugin checkout and locally built helper |
~/.local/share/omachat/session.json |
Google Messages credentials |
~/.local/share/omachat/whatsapp.db |
WhatsApp device credentials |
~/.local/share/omachat/whatsapp_store.json |
WhatsApp conversation index and legacy cache |
~/.local/share/omachat/whatsapp_history.sqlite |
WhatsApp paged message history |
~/.local/share/omachat/telegram.session and telegram_store.json |
Telegram credentials and chat cache |
~/.local/share/omachat/messenger_session.json and messenger.db |
Messenger session cookies and encrypted-device state |
~/.local/share/omachat/config.json |
Service choices, notification preferences, text size, sidebar layout, last service and conversation IDs, browser selection, Telegram API credentials |
~/.cache/omachat/media/, media_whatsapp/, media_telegram/, media_messenger/ |
Service-specific media caches |
$XDG_RUNTIME_DIR/omachat/daemon.sock |
Private plugin/helper control socket |
Before uninstalling, select Unpair this desktop on each connected service tab. This clears that service's local session and cached content. Follow any cleanup or remote-revocation warning, and check the phone's linked-device list for each service. Then run:
omarchy plugin remove onelegdave.omachat
Uninstalling does not erase account data. If you want to remove all remaining
OmaChat data, including API keys, delete ~/.local/share/omachat/ and
~/.cache/omachat/ yourself after unpairing. This affects all four services.
Development and documentation
The QML UI uses Omarchy's qs.Ui and qs.Commons components. Protocol work
runs in the shell-owned Go helper; media capture runs in external processes.
make helper
make test
make lint
make validate
make test-ui
See Contributing for prerequisites and verification, Security for reporting, and the documentation index for service guides, release notes, and historical reviews.
OmaChat 0.4.4 is listed in the Omarchy Marketplace
at snapshot dd77f2ca16e7c701851450578fd9ec51b7eba1a2. Development changes
require fresh validation and marketplace maintainer approval before that
snapshot is updated. See marketplace readiness
for the exact snapshot, review capabilities, and their limits.
Support my work
I build OmaChat as a free, open-source project. If you find it useful, you can buy me a coffee. Contributions are entirely optional and never required to use any feature.
Credits and license
Created and maintained by OneLegDave (GitHub · X).
Community contributors include Andrew Birklid (@tumbleweedlabs), Alex Vlissidis (@alexvlis), Matthias MB (@Hizoul), @ozz1ee-dev, and HANCORE-linux, who reported clipboard, attachment-download, and notification privacy issues. See community contributions and their review status. Codex and Claude have provided AI assistance with code and reviews.
The helper is adapted from Marc Ford's gmessages-omarchy-plugin. Google Messages uses mautrix libgm, WhatsApp uses whatsmeow, Telegram uses gotd/td, and Messenger uses mautrix-meta.
OmaChat v0.4.3 and later is licensed under AGPL-3.0-or-later. Earlier OmaChat releases retain their original MIT grant. Vendored dependencies retain their own terms, including the AGPL terms for libgm and mautrix-meta and the MPL-2.0 license for whatsmeow. See Credits and third-party notices, LICENSE, and NOTICE.
Other plugins: OmaDroid and System QuikView.
Directories
¶
| Path | Synopsis |
|---|---|
|
cmd
|
|
|
omachatd
command
Command omachatd is the protocol helper for OmaChat.
|
Command omachatd is the protocol helper for OmaChat. |
|
internal
|
|
|
boundedfile
Package boundedfile limits the physical extent of a temporary download file.
|
Package boundedfile limits the physical extent of a temporary download file. |
|
browser
Package browser extracts Google session cookies from a local Chromium-family browser profile.
|
Package browser extracts Google session cookies from a local Chromium-family browser profile. |
|
buildinfo
Package buildinfo identifies the sources compiled into the running helper.
|
Package buildinfo identifies the sources compiled into the running helper. |
|
daemon
Package daemon runs the Google Messages client and serves its state to the Quickshell plugin over a Unix socket.
|
Package daemon runs the Google Messages client and serves its state to the Quickshell plugin over a Unix socket. |
|
messenger
Package messenger implements native personal Facebook Messenger access.
|
Package messenger implements native personal Facebook Messenger access. |
|
store
Package store owns on-disk locations and session persistence.
|
Package store owns on-disk locations and session persistence. |
|
wire
Package wire defines the newline-delimited JSON protocol spoken between omachatd and the Quickshell plugin over a Unix socket.
|
Package wire defines the newline-delimited JSON protocol spoken between omachatd and the Quickshell plugin over a Unix socket. |