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.
opencode --auto doesn't seem to exist
Reported by phlawlessDevelopment · filed Aug 25, 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
CPU: 12-core (2-mt/10-st) Intel Core Ultra 7 255U (-MST AMCP-) speed/min/max: 1400/400/5200:4200:2400 MHz Kernel: 7.1.9-arch1-2 x86_64 Up: 7m Mem: 3.73/15.01 GiB (24.8%) Storage: 953.87 GiB (36.4% used) Procs: 358 Shell: Bash inxi: 3.3.41 Omarchy 4.0.1-1
What's wrong?
I was getting a blank terminal window when trying to launch the "default agent" with opencode selected. (gh copilot worked fine)
I narrowed it down to this part of "bin/omarchy-agent"
case "$agent" in
opencode)
command=(opencode --auto)
[[ -n ${prompt:-} ]] && command+=(--prompt "$prompt")
;;
I ran opencode manually and --auto is not listed as a flag
removed the --auto from that line and it launched perfectly.
If this is affecting many users, I'd be happy to send a PR but i couldn't see anyone else complaining about it in issues so maybe it's something stupid that I'm doing.
Also from context is seems like that flag was for skipping all permission prompts, which i'm sure is the intended behaviou here, I had a quick look at the opencode docs, couldn't really see anything about that, removing the flag is probably not the right move unless there is a replacement.
Let me know what I can do to help :)
View raw text
### System details
CPU: 12-core (2-mt/10-st) Intel Core Ultra 7 255U (-MST AMCP-) speed/min/max: 1400/400/5200:4200:2400 MHz Kernel: 7.1.9-arch1-2 x86_64 Up: 7m Mem: 3.73/15.01 GiB (24.8%) Storage: 953.87 GiB (36.4% used) Procs: 358 Shell: Bash inxi: 3.3.41 Omarchy 4.0.1-1
### What's wrong?
I was getting a blank terminal window when trying to launch the "default agent" with opencode selected. (gh copilot worked fine)
I narrowed it down to this part of "bin/omarchy-agent"
case "$agent" in
opencode)
command=(opencode --auto)
[[ -n ${prompt:-} ]] && command+=(--prompt "$prompt")
;;
I ran opencode manually and --auto is not listed as a flag
removed the --auto from that line and it launched perfectly.
If this is affecting many users, I'd be happy to send a PR but i couldn't see anyone else complaining about it in issues so maybe it's something stupid that I'm doing.
Also from context is seems like that flag was for skipping all permission prompts, which i'm sure is the intended behaviou here, I had a quick look at the opencode docs, couldn't really see anything about that, removing the flag is probably not the right move unless there is a replacement.
Let me know what I can do to help :)
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 08:46 UTC