Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-4267GitHub issuePublicReceived

omarchy-theme-install should lowercase directory name to match omarchy-theme-set

Reported by limehawk · filed Apr 7, 2026Closed upstream on 2026-04-22 by the merge of PR #5392 (closed by dhh). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

omarchy-theme-install should lowercase directory name to match omarchy-theme-setrevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

N/A — code-level issue in bin/omarchy-theme-install, reproducible on any system

What's wrong?

omarchy-theme-set normalizes theme names to lowercase:

THEME_NAME=$(echo "$1" | sed -E 's/<[^>]+>//g' | tr '[:upper:]' '[:lower:]' | tr ' ' '-')

omarchy-theme-install does not:

THEME_NAME=$(basename "$REPO_URL" .git | sed -E 's/^omarchy-//; s/-theme$//')

Since theme-install calls theme-set at the end, any repo with uppercase letters in the name will clone into a mixed-case directory, then theme-set lowercases when looking it up and fails with "does not exist."

The lowercasing was added to theme-set in 7514ae7 but theme-install was never updated to match.

Steps to reproduce:

  1. omarchy-theme-install any repo with uppercase in the name
  2. Directory is created with original casing
  3. omarchy-theme-set lowercases → can't find directory → "Theme does not exist"

Suggested fix — bin/omarchy-theme-install, line 18:

THEME_NAME=$(basename "$REPO_URL" .git | sed -E 's/^omarchy-//; s/-theme$//' | tr '[:upper:]' '[:lower:]')
View raw text
### System details

N/A — code-level issue in `bin/omarchy-theme-install`, reproducible on any system

### What's wrong?

`omarchy-theme-set` normalizes theme names to lowercase:

```bash
THEME_NAME=$(echo "$1" | sed -E 's/<[^>]+>//g' | tr '[:upper:]' '[:lower:]' | tr ' ' '-')
```

`omarchy-theme-install` does not:

```bash
THEME_NAME=$(basename "$REPO_URL" .git | sed -E 's/^omarchy-//; s/-theme$//')
```

Since `theme-install` calls `theme-set` at the end, any repo with uppercase letters in the name will clone into a mixed-case directory, then `theme-set` lowercases when looking it up and fails with "does not exist."

The lowercasing was added to `theme-set` in 7514ae7 but `theme-install` was never updated to match.

**Steps to reproduce:**

1. `omarchy-theme-install` any repo with uppercase in the name
2. Directory is created with original casing
3. `omarchy-theme-set` lowercases → can't find directory → "Theme does not exist"

**Suggested fix** — `bin/omarchy-theme-install`, line 18:

```bash
THEME_NAME=$(basename "$REPO_URL" .git | sed -E 's/^omarchy-//; s/-theme$//' | tr '[:upper:]' '[:lower:]')
```

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.