Proof Portal

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-4587GitHub issuePublicReceived

Agent setup for OpenCode fails on Quattro: mise resolves to deprecated aqua:sst/opencode

Reported by alvarosaavedra · filed Aug 14, 2026Closed upstream on 2026-08-15 by dhh, as not planned.

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

Agent setup for OpenCode fails on Quattro: mise resolves to deprecated aqua:sst/opencoderevision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

After updating to Quattro (Omarchy 4.0.0.alpha), the agent setup flow fails for OpenCode. Omarchy's omarchy-mise-install generates ~/.local/bin/opencode with:

mise use -g "opencode" || exit 1
exec mise x "opencode" -- "opencode" "$@"

The bare opencode package name resolves through mise's registry to aqua:sst/opencode, and opencode has since moved from the sst org to the anomalyco org. The install fails with:

mise ERROR Failed to install aqua:sst/opencode@latest:
   0: <asset resolution failure — lists opencode-desktop-* assets, no linux CLI match>

(Running mise use -g opencode directly reproduces it.)

Workaround (confirmed working)

mise use -g github:anomalyco/opencode

Suggested fix

In install/user/mise.sh, change:

omarchy-mise-install opencode

to:

omarchy-mise-install github:anomalyco/opencode opencode

so the generated wrapper pins the tool to the current GitHub repo instead of relying on the stale registry/aqua name.

Environment

  • Omarchy version: 4.0.0.alpha
  • OS: Arch Linux (Omarchy)
  • mise backend in failure: aqua:sst/opencode
View raw text
## What happened

After updating to Quattro (Omarchy 4.0.0.alpha), the agent setup flow fails for OpenCode. Omarchy's `omarchy-mise-install` generates `~/.local/bin/opencode` with:

```bash
mise use -g "opencode" || exit 1
exec mise x "opencode" -- "opencode" "$@"
```

The bare `opencode` package name resolves through mise's registry to `aqua:sst/opencode`, and opencode has since moved from the `sst` org to the `anomalyco` org. The install fails with:

```
mise ERROR Failed to install aqua:sst/opencode@latest:
   0: <asset resolution failure — lists opencode-desktop-* assets, no linux CLI match>
```

(Running `mise use -g opencode` directly reproduces it.)

## Workaround (confirmed working)

```bash
mise use -g github:anomalyco/opencode
```

## Suggested fix

In `install/user/mise.sh`, change:

```bash
omarchy-mise-install opencode
```

to:

```bash
omarchy-mise-install github:anomalyco/opencode opencode
```

so the generated wrapper pins the tool to the current GitHub repo instead of relying on the stale registry/aqua name.

## Environment

- Omarchy version: 4.0.0.alpha
- OS: Arch Linux (Omarchy)
- mise backend in failure: `aqua:sst/opencode`

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.