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-theme-set-pi` themes `~/.pi/agent` even when `PI_CODING_AGENT_DIR` points elsewhere
Reported by Susensio · filed Sep 28, 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
System details
Omarchy 4.0.4, Intel Core i7-1195G7, Intel Iris Xe
What's wrong?
omarchy-theme-set-pi writes the theme into ~/.pi/agent regardless of where pi keeps its config, so on a machine that sets PI_CODING_AGENT_DIR the theme file and the theme setting both land in a directory pi never reads and pi keeps its previous theme.
Its siblings honour their agent's variable — omarchy-theme-set-claude reads ${CLAUDE_CONFIG_DIR:-$HOME/.claude}, omarchy-theme-set-hermes reads ${HERMES_HOME:-$HOME/.hermes} — while line 11 hardcodes PI_AGENT_DIR="$HOME/.pi/agent".
PI_CODING_AGENT_DIR is pi's documented variable for this (pi --help lists PI_CODING_AGENT_DIR - Config directory (default: ~/.pi/agent)).
PI_CODING_AGENT_DIR=/tmp/pi-agent omarchy-theme-set-pi --activate
ls /tmp/pi-agent # not created
jq -r .theme ~/.pi/agent/settings.json # omarchy-system, written anywayThe test/cli pi-theme assertions run the script with HOME="$PI_TMPDIR" only, so they cover the default path and pass either way.
Maybe line 11 becomes PI_AGENT_DIR="${PI_CODING_AGENT_DIR:-$HOME/.pi/agent}", matching the other two.
omarchy-provision-user and omarchy-upgrade-to-quattro hardcode $HOME/.pi/agent the same way for the skill symlinks; there the effect is that pi sees none of them.
View raw text
### System details
Omarchy 4.0.4, Intel Core i7-1195G7, Intel Iris Xe
### What's wrong?
`omarchy-theme-set-pi` writes the theme into `~/.pi/agent` regardless of where pi keeps its config, so on a machine that sets `PI_CODING_AGENT_DIR` the theme file and the `theme` setting both land in a directory pi never reads and pi keeps its previous theme.
Its siblings honour their agent's variable — `omarchy-theme-set-claude` reads `${CLAUDE_CONFIG_DIR:-$HOME/.claude}`, `omarchy-theme-set-hermes` reads `${HERMES_HOME:-$HOME/.hermes}` — while [line 11](https://github.com/omacom/omarchy/blob/e332dc975d5f635294c497ebb54feb98dc3d89eb/bin/omarchy-theme-set-pi#L11) hardcodes `PI_AGENT_DIR="$HOME/.pi/agent"`.
`PI_CODING_AGENT_DIR` is pi's documented variable for this (`pi --help` lists `PI_CODING_AGENT_DIR - Config directory (default: ~/.pi/agent)`).
```bash
PI_CODING_AGENT_DIR=/tmp/pi-agent omarchy-theme-set-pi --activate
ls /tmp/pi-agent # not created
jq -r .theme ~/.pi/agent/settings.json # omarchy-system, written anyway
```
The `test/cli` pi-theme assertions run the script with `HOME="$PI_TMPDIR"` only, so they cover the default path and pass either way.
Maybe line 11 becomes `PI_AGENT_DIR="${PI_CODING_AGENT_DIR:-$HOME/.pi/agent}"`, matching the other two.
`omarchy-provision-user` and `omarchy-upgrade-to-quattro` hardcode `$HOME/.pi/agent` the same way for the skill symlinks; there the effect is that pi sees none of them.
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 20:05 UTC