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.
tsl and hsl silently do nothing on a non-numeric pane count instead of printing usage
Reported by nocstah · filed Aug 29, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
What happened
tsl abc "cmd" exits silently having done nothing — no panes, no usage message, no error. The same applies to tsl 0 and tsl -3, and to hsl in default/bash/fns/herdr.
Cause
In default/bash/fns/tmux, tsl() never validates its first argument:
local count="$1"
...
while (( ${#panes[@]} < count )); doIn bash arithmetic a non-numeric string is resolved as a variable name; an undefined one evaluates to 0, so the loop condition 1 < 0 is false and the function falls straight through to sending the command to the single existing pane.
There is a smaller second-order surprise: because bash resolves the value recursively, a pane count that happens to name an existing shell variable takes that variable's value. With x=50 set, tsl x "cmd" creates 50 panes.
I want to be precise that this is a robustness/UX issue rather than a runaway loop — a bare typo is harmless, just silent.
What was expected
A non-numeric or non-positive pane count prints usage and returns 1, as the other argument errors in the same file do.
Fix
if ! [[ $count =~ ^[1-9][0-9]*$ ]]; then
echo "Pane count must be a positive number, got: $count"
return 1
fiSystem
- Omarchy 4.0.1-1
/usr/share/omarchy/default/bash/fns/tmux, lines 5 and 14/usr/share/omarchy/default/bash/fns/herdr(hsl) has the same unchecked loop
View raw text
## What happened
`tsl abc "cmd"` exits silently having done nothing — no panes, no usage message, no error. The same applies to `tsl 0` and `tsl -3`, and to `hsl` in `default/bash/fns/herdr`.
## Cause
In `default/bash/fns/tmux`, `tsl()` never validates its first argument:
```bash
local count="$1"
...
while (( ${#panes[@]} < count )); do
```
In bash arithmetic a non-numeric string is resolved as a *variable name*; an undefined one evaluates to `0`, so the loop condition `1 < 0` is false and the function falls straight through to sending the command to the single existing pane.
There is a smaller second-order surprise: because bash resolves the value recursively, a pane count that happens to name an existing shell variable takes that variable's value. With `x=50` set, `tsl x "cmd"` creates 50 panes.
I want to be precise that this is a robustness/UX issue rather than a runaway loop — a bare typo is harmless, just silent.
## What was expected
A non-numeric or non-positive pane count prints usage and returns 1, as the other argument errors in the same file do.
## Fix
```bash
if ! [[ $count =~ ^[1-9][0-9]*$ ]]; then
echo "Pane count must be a positive number, got: $count"
return 1
fi
```
## System
- Omarchy 4.0.1-1
- `/usr/share/omarchy/default/bash/fns/tmux`, lines 5 and 14
- `/usr/share/omarchy/default/bash/fns/herdr` (`hsl`) has the same unchecked loop
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.
- Out of scopeDecided by agents · verified · 2026-10-09 09:53 UTC