The hosts in your ~/.ssh/config, in the bar — with the answers to why isn't
it connecting next to each one. For Omarchy.
▣ SSH ● agent · 1 key (◉)
╭──────────────────────────────────────────────────────────────────╮
│ ⌕ Type to filter hosts │
╰──────────────────────────────────────────────────────────────────╯
╭ ! devbox is declared 2 times ────────────────────────────────────╮
│ ssh reads ~/.ssh/config:12 first; config.d/work:3 never wins │
╰──────────────────────────────────────────────────────────────────╯
HOSTS
╭──────────────────────────────────────────────────────────────────╮
│ [✓] omarchy │
│ shilai_li@192.168.10.175 │
│ [–] server │
│ user@10.0.0.20 │
│ [✗] devbox Unreachable │
│ dev@example.com │
╰──────────────────────────────────────────────────────────────────╯
PATTERNS
╭──────────────────────────────────────────────────────────────────╮
│ [*] * │
│ Applies to every host it matches │
╰──────────────────────────────────────────────────────────────────╯
enter connect → details ^n new esc close
- It runs the real ssh client.
ssh -Gfor the effective configuration,ssh -o BatchMode=yesfor authentication,ssh-add -lfor the agent. Nothing about SSH is reimplemented here. - It never handles a credential. Every probe runs with
BatchMode=yes,PasswordAuthentication=noandKbdInteractiveAuthentication=no: ssh fails where it would otherwise prompt. No password is read, stored, forwarded or cached — by design, not by policy. - Your file stays your file. Edits rewrite the lines they must and copy every other line — comments included — through untouched, and an edit made against a copy someone else has since changed is refused rather than applied.
- No Electron. QML running inside the
omarchy-shellprocess you are already running. - Themed. No hardcoded colors or sizes; it repaints itself when you run
omarchy theme set.
omarchy plugin add https://github.com/shilai-li/omarchy-ssh-manager.git --enableOr by hand, from a clone:
cp -r . ~/.config/omarchy/plugins/shilai_li.ssh-manager
omarchy-shell shell rescanPlugins
omarchy plugin enable shilai_li.ssh-managerThe widget lands on the right of the bar. Move it with omarchy bar move.
Plugins run unsandboxed inside your shell. Read the code before you enable it — this one reads and writes
~/.ssh/config, so that goes double.
omarchy plugin remove shilai_li.ssh-managerThe one thing it keeps of its own is the last test result of each host, in
~/.local/state/shilai_li.ssh-manager/ — remove that directory too if you want
it gone.
Every Host entry ssh reads, including the ones in Included files, in the
order ssh reads them. Wildcard entries (Host *) sort to the bottom and are
marked as patterns — they are not somewhere to connect, but they are usually
where a surprising value came from.
Each row starts with a square that says what the last test found. The glyph differs for every state, so it reads the same on a theme whose warning color is its accent color.
| Mark | |
|---|---|
– on a quiet square |
not tested yet |
✓ filled with the accent |
answered and authenticated |
! on a tinted square |
answered, but refused the key |
✗ filled with the urgent color |
unreachable |
Nothing is tested until you ask. Opening the panel makes no network connection.
The list keeps to what you need to pick a host: its status square, its name and
user@address, and words only when something is wrong (Unreachable, Key refused). ↑↓, ^t and ^h work without being listed.
The last result of each test is remembered, so restarting the shell does not
turn every host back into "not tested". How old it is shows in the host's
details, on the Test tile (Authenticated · 2 h ago), and it is never
refreshed on its own: press t to ask the host again. Results are dropped after 30 days, and forgotten when you edit
or remove the host. What is kept is only the alias, the outcome and the time,
in a 0600 file in a 0700 directory under ~/.local/state.
| Key | |
|---|---|
↑ ↓ |
move |
enter |
connect in a terminal |
→ |
details |
^t |
test the selected host |
^n |
new host |
^e |
edit the selected host |
delete |
remove the selected host (asks first) |
| anything else | filters the list |
^h |
hide or show users, addresses and key paths |
^, |
settings |
esc |
clear the filter, then close |
Left click a row to connect, right click for details.
‹ omarchy ● AUTHENTICATED
╭──────────────────────────────────────────────────────────────╮
│ ( ▣ ) │
│ Connect │
│ shilai_li@192.168.10.175 │
╰──────────────────────────────────────────────────────────────╯
╭──────────────────────────────────────────────────────────────╮
│ (✓) (✓) (✓) (✓) │
│ Reachable Key Auth Config │
│ on disk │
╰──────────────────────────────────────────────────────────────╯
╭ (∿) Test ───────────────────╮ ╭ (✎) Edit ────────────────────╮
│ Authenticated │ │ Five fields, nothing else│
╰─────────────────────────────╯ ╰──────────────────────────────╯
WHAT SSH WILL USE ssh -G
╭──────────────────────────────────────────────────────────────╮
│ HostName 192.168.10.175 │
│ User shilai_li │
│ Port 22 │
╰──────────────────────────────────────────────────────────────╯
IDENTITIES SSH WILL TRY
╭──────────────────────────────────────────────────────────────╮
│ [⚿] ~/.ssh/id_ed25519 │
│ On disk │
╰──────────────────────────────────────────────────────────────╯
╭──────────────────────────────────────────────────────────────╮
│ [⌦] Remove host › │
╰──────────────────────────────────────────────────────────────╯
Defined in ~/.ssh/config:4. Nothing here touches the network until you test.
The values come from ssh -G <host>, so they are what ssh will actually use —
Includes, Match blocks and wildcards already resolved.
Identities ssh will try is the part ssh -G cannot tell you on its own: it
lists the six default key names whether or not they exist and says nothing
about the agent. This list is the keys that are really there, in the order ssh
will offer them, each marked on disk, in agent, or missing.
A dash in the checklist means not asked, never fine. Host reachable and
Authentication stay dashed until you press t, or until a remembered result
from an earlier session fills them in.
An ssh-agent is optional, and not running one is not a fault. The agent counts
only where it is the source of a host's key, and that shows in Key available.
It is mentioned on its own only for a host with ForwardAgent yes and no agent
to forward. A host whose IdentityAgent names another socket is never credited
with the keys in SSH_AUTH_SOCK's agent; its Key available stays a dash,
because nothing here asks that agent what it holds.
| Key | |
|---|---|
c / enter |
connect |
t |
test this host |
e |
edit |
n |
new host |
x |
remove (asks first) |
esc / ← |
back to the list |
For a screen someone else can see — a call, a stream, a recording — the eye
button in the header (or ^h, in any view) takes off the screen what says
where a host is and who you are on it: users, addresses, ports, key paths, the
agent socket, and those values wherever a warning or ssh's own message quotes
them. Host names stay, as do test results and the file and line, so the panel
still works. A host whose name is an address is shown as host 3.
While hidden, the filter matches host names only, and the editor masks
HostName, User, Port and IdentityFile like password fields — typing still
works, and ^h shows them before you save. Connecting and testing use the
real values; only the screen changes. The terminal a connection opens is ssh's
own, and may print the address.
Two settings, behind the gear in the list header (or ^,):
| Setting | |
|---|---|
| Start hidden | hide every time the shell starts (off by default) |
| Hide while recording | on while the screen is being recorded (gpu-screen-recorder or wf-recorder, which Omarchy records with), and locked until it stops (on by default) |
Only those two recorders can be seen from here; a browser or meeting app sharing the screen cannot, which is what Start hidden is for.
Five fields — Host, HostName, User, Port, IdentityFile — because
those are the five this plugin claims to manage. Everything else in a block is
preserved exactly: ProxyJump, ForwardAgent, a keyword this plugin has
never heard of, and every comment inside and around the entry.
The fields edit the way you expect — type, backspace and delete (with ^
for a word), arrows, home / end, shift to select, ^a, ^c, ^x — and
^v pastes. What they do not do is read the clipboard on their own: a Qt text
field normally fetches whatever another program copied, every time anything
copies, just to know whether a paste would be possible. Here the clipboard is
read only when you press ^v, through wl-paste, cut off at 4 KiB and five
seconds; a larger clipboard is refused rather than pasted. The cost is that
there is no undo, and no input method or compose key inside these five fields.
A new entry is written above the first wildcard block. ssh takes the first
value it obtains for each keyword, so an entry appended after Host * would
silently lose every keyword that block sets — the most common way a
hand-edited ssh_config stops doing what it looks like it does.
A save is a transaction. The new text is written to a fresh file in ~/.ssh at
mode 0600 before it holds anything, and renamed over the old one; a reader
sees one version or the other and never a half-written file, and there is no
moment where the new one is readable by anyone else. ~/.ssh itself is created
0700 if it is not there, one directory at a time, and is checked before every
write — not created with mkdir -p, which would follow a symlink anybody could
have put on the way. If the file changed on disk between being read and being
saved, the save is refused and the panel reloads: whoever edited it in the
meantime keeps their edit.
| Finding | Where it comes from |
|---|---|
Missing IdentityFile |
a path your config names that is not on disk |
Duplicate Host entries |
the same name declared in two places, with both files and line numbers |
| Overridden values | a keyword set in a file that lost to an earlier one — ssh takes the first, not the last |
| Unreachable host | a TCP connection to the effective hostname:port |
| Authentication failure | ssh -o BatchMode=yes <host> true, classified by ssh's own message |
| Which key ssh will use | ssh -G identity list, filtered by what exists, cross-referenced with ssh-add -l fingerprints |
| Broken config | ssh -G refusing to parse, quoting its own error |
A Host * block losing to a host that names itself is not reported: that is
ssh working as intended, and reporting it would bury the real conflicts.
A host behind a ProxyJump is not called unreachable — the jump host is what
reaches it, so the TCP check is skipped rather than failed.
omarchy-shell shilai_li.ssh-manager toggle
omarchy-shell shilai_li.ssh-manager refresh
omarchy-shell shilai_li.ssh-manager connect <host>
omarchy-shell shilai_li.ssh-manager test <host> # opens the panel and asks
omarchy-shell shilai_li.ssh-manager status # JSON
omarchy-shell shilai_li.ssh-manager hideDetails # hide users and addressesThat socket is reachable by anything running as you, and unlike the panel there is nobody at a keyboard behind it, so it is deliberately narrower than the panel:
connectandtesttake only aHostalias that is in your config right now, spelled exactly, and not a pattern. Neither will accept an arbitrary destination.testopens a TCP connection and offers a key to whatever answers, so it does not do it on its own: it raises the panel on that host and asks. Presston a host yourself and it just runs — that keystroke is the answer.hideDetailscan only hide. Putting users and addresses back on a screen that may be shared is for the person at the keyboard (^h), so there is no socket call that shows them.statusreports which aliases exist, how many hosts and files there are, and whether an agent is running. It does not report hostnames, usernames, ports, key paths, file paths, key fingerprints or agent key comments. An inventory of where your infrastructure is and which keys open it is worth a great deal to somebody who should not have it and very little to a shell script.
A Hyprland bind:
bindd = SUPER CTRL, S, SSH manager, exec, omarchy-shell shilai_li.ssh-manager toggle
The scripts in bin/ are the whole backend and run fine on their own:
bin/scan.sh ~/.ssh/config # the config as ssh reads it, includes expanded
bin/effective.sh myhost # ssh -G, plus which identity files exist
bin/probe.sh myhost # TCP reachability and authentication
bin/agent.sh # what the ssh-agent is holding
bin/config-read.sh ~/.ssh/config # the file, if it is safe to read
bin/config-write.sh ~/.ssh/config <digest> # replace it, against that digest
bin/results.sh read ~/.local/state/shilai_li.ssh-manager/results # remembered testseffective.sh and probe.sh take an optional trailing config path (-F),
which is how the test suite points them at a fixture instead of your real
~/.ssh. bin/guard.sh is sourced by all of them and holds the two things
none of them may get wrong: what has to be true about a path before it is
opened, and the ceilings on how much any of them may read, spawn or spend.
~/.ssh/config, everything it Includes, and the socket this plugin listens
on are all reachable by anything else running as you. It is written on that
assumption.
| Open a config file by name and trust it | Every path is checked before it is opened: not a symlink, no symlink on the way to it, a regular file rather than a FIFO or a device, owned by you or by root, and small enough to be a config. |
| Read without a ceiling | Bytes, lines, line length, file count, Include depth and wall-clock all have a limit, and an Include cycle is not walked twice. Hitting a limit is a note in the panel saying the view is partial. |
| Run without a deadline | Every helper is one of this plugin's scripts, started by an absolute /usr/bin/bash with a fixed PATH, in its own process group, under a deadline that kills the group — a ProxyCommand outliving the ssh that spawned it does not get to outlive the test. |
Resolve a tool through your PATH |
ssh, ssh-add, ssh-keygen, setsid and the rest come from a fixed /usr/bin:/bin. Your terminal still gets your own environment when you connect. |
| Read the clipboard behind your back | The editor's fields are read-only to Qt, which is what stops them fetching every copy made anywhere on the desktop. ^v reads it once, in a separate process, at most 4 KiB, within five seconds. |
| Touch the network without you | Opening the panel runs the config scan and ssh-add -l, and nothing else. A probe happens on a keystroke, or on a confirmation you clicked. |
No password storage, no SFTP browser, no SCP GUI, no remote file editing, no
remote monitoring, no built-in terminal. Connecting hands the host to your
default terminal running the system ssh; everything after that is between you
and the host.
omarchy plugin validate .
QT_FORCE_STDERR_LOGGING=1 /usr/lib/qt6/bin/qmllint -I /usr/share/omarchy/shell BarWidget.qml
bash test/test.shSshConfig.js (parsing and file surgery) and Diagnostics.js (reading ssh's
answers) are Qt-free so the suite runs under plain node. The shell scripts
are tested by running them against a throwaway ~/.ssh; no test connects to a
host that exists.
See AGENTS.md for the plugin contract, architecture notes and house style.
MIT. See LICENSE.

