Your Varlatch sessions in the Omarchy bar: which servers you are signed in to, when each credential expires, and one-click sign-in, renewal, and sign-out.
omarchy plugin add https://github.com/varlatch/omarchy-plugin.git --enableEverything it shows comes from varlatch status --json; see Install.
The Varlatch mark, icon only, with its state told by color:
- theme foreground: at least one live session
- amber: less than 20% of a credential's lifetime remains
- red: signed out, or a credential has expired
- red, dimmed: the
varlatchCLI is missing or too old
A left click opens a panel under the widget with one row per session: a
live countdown, renew (or log in once expired), and ⋯ for the
row's other actions: copy address, other device, log out, and
with several servers dashboard for that server. The host name opens
that server's dashboard too. Above the rows, verify checks every stored
credential and dashboard opens your server (with one server); below
them, add server signs in to one more. A middle click opens
the Varlatch submenu of the Omarchy menu, which SUPER+SPACE also finds.
The widget keeps that submenu in step with your sessions. After a full
sign-out, "Log in" still targets the last server you used, remembered in
~/.local/state/varlatch-omarchy/servers.json.
Without the varlatch CLI, the panel offers install CLI. It opens a
terminal that asks for your server's address, so it can install the CLI
version that server runs (press Enter for the latest release). It then
downloads the release CLI and checks it the same way an update does (see
below), installs it as ~/.local/bin/varlatch once you confirm, and offers
the first sign-in. When ~/.local/bin is not on your PATH, it points the
widget at the file instead. The release CLI needs Node.js 22 or newer; on
Omarchy, omarchy install dev-env node installs it.
With the CLI but no server known yet, the panel asks for the server's address, and connect starts the browser sign-in. The menu's Connect to a server row opens the same form.
"Verify" runs varlatch status --probe: one authenticated request per
stored credential, to check that it is still valid and its server
reachable.
Moving into expiring or expired triggers one desktop notification each, with a Renew now or Log in button.
Renewing means signing in again to the same server. From Varlatch 0.10.0 on, the CLI revokes the credential it replaces only after the new one is verified and saved, so a cancelled or failed browser sign-in never signs you out.
The panel's footer shows the CLI version. With checkUpdates on, it also
shows when a newer release is out, with notes and, when the plugin can
replace your CLI, update. A new release also triggers one notification,
and an Update CLI row appears in the menu.
update opens a terminal and runs varlatch self-update (Varlatch
0.11.0 and newer), using sudo when the CLI's directory is not writable.
For an older CLI, the plugin does the same steps itself. Either way, it
downloads varlatch-cli-<version>.cjs and SHA256SUMS from the release,
checks the signature on SHA256SUMS when the release carries one and
cosign is installed, checks the file against it, shows what it verified,
and replaces the CLI only after you confirm. This works only for the
release build. A CLI built from a source checkout, or a varlatchCommand
with arguments, gets the release notes instead, since you update those
yourself.
Signing in needs no terminal window. The CLI opens your browser for the passkey prompt and the panel closes, so it never covers the browser. While the CLI waits, reopening the panel shows "Signing in to …" with open link, for when the page opens in the wrong browser, other device, and cancel. The result arrives as a notification.
When the browser on this machine has no passkey for your server, sign in
from another device instead: other device on the panel while a sign-in
waits, in a row's ⋯, or next to log in when logged out; Log in
from another device in the menu; or Use another device on a failed
sign-in's notification (the expiry notifications have an Another device
button too). The panel shows an address, a code, and,
with qrencode installed, a QR code of the address for a phone's camera.
Open the address on any device, sign in with your passkey, enter the code,
and approve. The widget collects the new credential, and as with a browser
sign-in, the CLI revokes the credential it replaces only once the new one is
saved. The code lasts 10 minutes. This needs Varlatch CLI 0.14.0 or newer.
The widget polls varlatch status --json on a timer, which reads local
files only (~/.config/varlatch/credentials.json and repository-local
state). It never uses a stored credential on its own; the only network
requests are the ones you start with a click, and, with checkUpdates on,
an anonymous check for the latest release, cached in
~/.local/state/varlatch-omarchy/update.json. That check runs twice a day
in the background, again when you open the panel and the last one is over
an hour old, and when the cache names an older release than the CLI you
have; never more than once an hour.
Set these with omarchy bar set varlatch <key> <value> (add --json for
refreshIntervalSec and sessionHours), or on the widget's entry in
~/.config/omarchy/shell.json:
refreshIntervalSec: how often to poll, in seconds (default 30, minimum 15).varlatchCommand: the CLI to run (defaultvarlatchon yourPATH). For a development build, use for examplenode /path/to/varlatch/apps/cli/dist/main.js.sessionHours: how long a new sign-in lasts, from 1 to 24 hours (default 0: the server's default, 12 hours). Applies to every sign-in the widget starts, renewals included.notifyExpiry:onoroff.showWhenLoggedOut:onoroff. Withoff, the widget hides entirely when no credentials are stored.checkUpdates:onoroff(defaultoff). Withon, the widget looks for new CLI releases on GitHub.showLocalhost:onoroff(defaultoff). Withoff, sessions onlocalhostor127.*are ignored everywhere: the bar color, the panel, the menu, notifications, and the sign-in and dashboard targets.
omarchy plugin add https://github.com/varlatch/omarchy-plugin.git --enableThis clones the plugin into ~/.config/omarchy/plugins/varlatch and puts
the widget on the bar. The widget adds its Varlatch submenu to
~/.config/omarchy/extensions/omarchy-menu.jsonc by itself, as a managed
block between // >>> varlatch plugin and // <<< varlatch plugin that it
rewrites as your sessions change. Leave that block alone; everything
outside it stays yours.
Update with omarchy plugin update varlatch; remove with
omarchy plugin remove varlatch, then delete the managed block.
The shell keeps running the widget code it loaded until it restarts, even
after an update. The widget notices newer code on disk within a minute (or
when you open the panel) and shows "Varlatch for Omarchy 0.5.0 is
installed" with restart, a Restart to load row in the menu, and one
notification with Restart now; all three run omarchy restart shell.
A sign-in under way survives the restart.
Requires jq, python3, and the Varlatch CLI 0.8.0 or newer, which the
panel can install (see First run). With a CLI before 0.10.0,
the widget works out the expiring state itself.
tests/run.sh tests the manifest and bin/varlatch-menu offline, each test
in a throwaway HOME with stand-ins for the CLI (tests/fake-varlatch),
curl, notify-send, and the omarchy commands. It needs jq, python3,
and Node.js 22 or newer, and checks the QR code when qrencode is
installed. CI runs it with shellcheck on every pull request. The QML is
checked by hand on a live bar: omarchy restart shell after editing it,
and omarchy-shell varlatch debugState for the widget's state.
See CHANGELOG.md for what changed in each release.
Copyright © 2026 Robotsson. Licensed under the Apache License 2.0; see
LICENSE.

