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

omarchy-mise-install overwrites symlink targets (breaks existing Grok installs)

Reported by JustMrMendez · filed Aug 7, 2026Closed upstream on 2026-08-08 by the merge of PR #6619 (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-mise-install overwrites symlink targets (breaks existing Grok installs)revision 1 · captured 2026-10-04 11:56 UTC via poll

System details

AMD RYZEN AI MAX+ 395 w/ Radeon 8060S · Omarchy 4.0.0.r1541.gfd1034f (Quattro) · mise 2026.7.17 · Linux 7.1.5-arch1-2 x86_64

What's wrong?

I had Grok Build installed before Quattro. After the upgrade, grok never started. It just printed this over and over:

mise ~/.config/mise/config.toml tools: npm:@xai-official/[email protected]

I didn't run any install command myself. Quattro's migration does it:

https://github.com/basecamp/omarchy/blob/fd1034f/migrations/1785846769.sh#L5

omarchy-mise-install npm:@xai-official/grok grok

That helper writes the wrapper with cat >:

https://github.com/basecamp/omarchy/blob/fd1034f/bin/omarchy-mise-install#L17-L21

cat >"$HOME/.local/bin/$command" <<EOF
#!/bin/bash
mise use -g "$package" || exit 1
exec mise x "$package" -- "$bin" "$@"
EOF

My official Grok install already had:

~/.local/bin/grok -> ~/.grok/bin/grok -> ~/.grok/downloads/grok-0.2.114-linux-x86_64

cat > follows that symlink, so the migration replaced the real binary with the mise wrapper. After that, grok goes mise -> npm trampoline -> existing ~/.grok/bin/grok -> stub -> mise again.

This is not #6349 / #6350. Those were PATH self-exec recursion. Here the install step clobbers the previous binary through a symlink.

Steps to reproduce

Reproduce the overwrite with a throwaway symlink:

echo REAL > /tmp/payload
ln -sfn /tmp/payload ~/.local/bin/grok-repro-test
omarchy-mise-install npm:@xai-official/grok grok-repro-test
cat /tmp/payload
rm -f ~/.local/bin/grok-repro-test /tmp/payload

Expected: REAL.
Actual: The mise wrapper script

Suggested fix

In `bin/omarchy-mise-install`, unlink the destination before writing so cat > cannot follow an existing symlink:

 mkdir -p "$HOME/.local/bin"
 
+rm -f "$HOME/.local/bin/$command"
 cat >"$HOME/.local/bin/$command" <<EOF
View raw text
### System details

AMD RYZEN AI MAX+ 395 w/ Radeon 8060S · Omarchy 4.0.0.r1541.gfd1034f (Quattro) · mise 2026.7.17 · Linux 7.1.5-arch1-2 x86_64

### What's wrong?

I had Grok Build installed before Quattro. After the upgrade, `grok` never started. It just printed this over and over:

```
mise ~/.config/mise/config.toml tools: npm:@xai-official/[email protected]
```

I didn't run any install command myself. Quattro's migration does it:

https://github.com/basecamp/omarchy/blob/fd1034f/migrations/1785846769.sh#L5

```bash
omarchy-mise-install npm:@xai-official/grok grok
```

That helper writes the wrapper with `cat >`:

https://github.com/basecamp/omarchy/blob/fd1034f/bin/omarchy-mise-install#L17-L21

```bash
cat >"$HOME/.local/bin/$command" <<EOF
#!/bin/bash
mise use -g "$package" || exit 1
exec mise x "$package" -- "$bin" "$@"
EOF
```

My official Grok install already had:

`~/.local/bin/grok` -> `~/.grok/bin/grok` -> `~/.grok/downloads/grok-0.2.114-linux-x86_64`

`cat >` follows that symlink, so the migration replaced the real binary with the mise wrapper. After that, `grok` goes mise -> npm trampoline -> existing `~/.grok/bin/grok` -> stub -> mise again.

This is not #6349 / #6350. Those were PATH self-exec recursion. Here the install step clobbers the previous binary through a symlink.

### Steps to reproduce

Reproduce the overwrite with a throwaway symlink:

```bash
echo REAL > /tmp/payload
ln -sfn /tmp/payload ~/.local/bin/grok-repro-test
omarchy-mise-install npm:@xai-official/grok grok-repro-test
cat /tmp/payload
rm -f ~/.local/bin/grok-repro-test /tmp/payload
```

Expected: `REAL`.
Actual: The mise wrapper script

### Suggested fix

In [`bin/omarchy-mise-install`](https://github.com/basecamp/omarchy/blob/fd1034f/bin/omarchy-mise-install#L15-L21), unlink the destination before writing so `cat >` cannot follow an existing symlink:


```diff
 mkdir -p "$HOME/.local/bin"
 
+rm -f "$HOME/.local/bin/$command"
 cat >"$HOME/.local/bin/$command" <<EOF
```

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.