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-2042GitHub issuePublicDecided· Out of scope

mise activate hook overwritten by starship/zoxide - PATH not updated automatically

Reported by plgonzalezrx8 · filed Nov 29, 2025 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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

mise activate hook overwritten by starship/zoxide - PATH not updated automaticallyrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Ryzen 3800, 64gb ram, Omarchy latest

What's wrong?

mise activate hook overwritten by starship/zoxide - PATH not updated automatically

Problem

When using mise to manage Python (or other tools), the mise-managed versions are not used by default in new terminal sessions. The system Python takes precedence even though mise is activated.

For example:

$ python --version
Python 3.13.7  # System version, not mise-managed 3.14.0

$ which python
/bin/python  # Should be ~/.local/share/mise/installs/python/...

Root Cause

In ~/.local/share/omarchy/default/bash/init, mise is activated before starship and zoxide:

eval "$(mise activate bash)"    # Line 2
# ...
eval "$(starship init bash)"    # Line 6
# ...
eval "$(zoxide init bash)"      # Line 10

Mise relies on a PROMPT_COMMAND hook (_mise_hook) to dynamically update the PATH. However, starship and zoxide overwrite PROMPT_COMMAND when they initialize, removing mise's hook.

You can verify this by checking PROMPT_COMMAND in a new terminal:

$ echo $PROMPT_COMMAND
__zoxide_hook;starship_precmd   # Notice: _mise_hook is missing

Workaround

Add the following to the end of ~/.bashrc:

# Re-activate mise at end so its hook isn't overwritten by starship/zoxide
eval "$(mise activate bash)"

Optionally, also add this before the Omarchy rc is sourced to ensure mise paths take priority:

export MISE_ACTIVATE_AGGRESSIVE=1

Suggested Fix

Move the mise activation to the end of ~/.local/share/omarchy/default/bash/init, after starship and zoxide:

if command -v starship &> /dev/null; then
  eval "$(starship init bash)"
fi

if command -v zoxide &> /dev/null; then
  eval "$(zoxide init bash)"
fi

# Activate mise LAST so its PROMPT_COMMAND hook isn't overwritten
if command -v mise &> /dev/null; then
  eval "$(mise activate bash)"
fi

Environment

  • Omarchy version: 3.2.1
  • mise version: 2025.11.3
View raw text
### System details

Ryzen 3800, 64gb ram, Omarchy latest

### What's wrong?

# mise activate hook overwritten by starship/zoxide - PATH not updated automatically

## Problem

When using mise to manage Python (or other tools), the mise-managed versions are not used by default in new terminal sessions. The system Python takes precedence even though mise is activated.

For example:
```bash
$ python --version
Python 3.13.7  # System version, not mise-managed 3.14.0

$ which python
/bin/python  # Should be ~/.local/share/mise/installs/python/...
```

## Root Cause

In `~/.local/share/omarchy/default/bash/init`, mise is activated **before** starship and zoxide:

```bash
eval "$(mise activate bash)"    # Line 2
# ...
eval "$(starship init bash)"    # Line 6
# ...
eval "$(zoxide init bash)"      # Line 10
```

Mise relies on a `PROMPT_COMMAND` hook (`_mise_hook`) to dynamically update the PATH. However, starship and zoxide overwrite `PROMPT_COMMAND` when they initialize, removing mise's hook.

You can verify this by checking `PROMPT_COMMAND` in a new terminal:
```bash
$ echo $PROMPT_COMMAND
__zoxide_hook;starship_precmd   # Notice: _mise_hook is missing
```

## Workaround

Add the following to the **end** of `~/.bashrc`:

```bash
# Re-activate mise at end so its hook isn't overwritten by starship/zoxide
eval "$(mise activate bash)"
```

Optionally, also add this **before** the Omarchy rc is sourced to ensure mise paths take priority:

```bash
export MISE_ACTIVATE_AGGRESSIVE=1
```

## Suggested Fix

Move the mise activation to the end of `~/.local/share/omarchy/default/bash/init`, after starship and zoxide:

```bash
if command -v starship &> /dev/null; then
  eval "$(starship init bash)"
fi

if command -v zoxide &> /dev/null; then
  eval "$(zoxide init bash)"
fi

# Activate mise LAST so its PROMPT_COMMAND hook isn't overwritten
if command -v mise &> /dev/null; then
  eval "$(mise activate bash)"
fi
```

## Environment

- Omarchy version: 3.2.1
- mise version: 2025.11.3

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 00:02 UTC