Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
`OMARCHY_PATH` not loaded when connecting over ssh on `3.4.0`
Reported by Xoorgh · filed Feb 26, 2026Closed upstream on 2026-02-26 by commit 6757b7068a2f (closed by dhh). GitHub close reason: completed.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
MacBook Air 13" mid 2013
What's wrong?
When connecting to my Omarchy machine over ssh, I kept getting:
-bash: /default/bash/fns/*: No such file or directoryClaude (using the Omarchy skill!) identified the issue as being:
OMARCHY_PATH is only set in ~/.config/uwsm/env, which is sourced by the Hyprland/UWSM session (the desktop environment). It's not set in ~/.bashrc, ~/.bash_profile, or ~/.profile.
When you open a terminal locally on the machine, the Hyprland session has already set OMARCHY_PATH in the environment, so every child process (including your terminal) inherits it. But when you SSH in, there's no Hyprland session — bash starts fresh, OMARCHY_PATH is unset, and this line in ~/.local/share/omarchy/default/bash/functions:
for f in $OMARCHY_PATH/default/bash/fns/*; do source "$f"; doneexpands to the literal string /default/bash/fns/* (since $OMARCHY_PATH is empty), which doesn't exist — hence the error.
Adding this to ~/.bash_profile fixed it for me:
export OMARCHY_PATH="$HOME/.local/share/omarchy"
export PATH="$OMARCHY_PATH/bin:$PATH"View raw text
### System details MacBook Air 13" mid 2013 ### What's wrong? When connecting to my Omarchy machine over ssh, I kept getting: ``` -bash: /default/bash/fns/*: No such file or directory ``` Claude (using the Omarchy skill!) identified the issue as being: `OMARCHY_PATH` is only set in `~/.config/uwsm/env`, which is sourced by the Hyprland/UWSM session (the desktop environment). It's not set in `~/.bashrc`, `~/.bash_profile`, or `~/.profile`. When you open a terminal locally on the machine, the Hyprland session has already set `OMARCHY_PATH` in the environment, so every child process (including your terminal) inherits it. But when you SSH in, there's no Hyprland session — bash starts fresh, `OMARCHY_PATH` is unset, and this line in `~/.local/share/omarchy/default/bash/functions`: ```sh for f in $OMARCHY_PATH/default/bash/fns/*; do source "$f"; done ``` expands to the literal string `/default/bash/fns/*` (since `$OMARCHY_PATH` is empty), which doesn't exist — hence the error. Adding this to `~/.bash_profile` fixed it for me: ```sh export OMARCHY_PATH="$HOME/.local/share/omarchy" export PATH="$OMARCHY_PATH/bin:$PATH" ```
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.