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.
Terminal not showing active python virtual environment
Reported by AurelienBoland · filed Nov 4, 2025Closed upstream on 2025-11-05 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
System details
Omarchy 3.15
What's wrong?
Short version
Python virtual environment not showing in the terminal prompt because of starship config
More details
Unexpected Behavior
When a python virtual environment get activated using*:source venv/bin/activate
a python developer usually expect "(venv)" to be added to the terminal prompt to indicate that the venv environment is activated. This is actually what happen when using bash (or zsh) with default config. However in omarchy, despite the environment being activated nothing is added to the terminal prompt.
Root cause
Omarchy is using starship (https://starship.rs/) to overwrite the terminal prompt. Despite the code in "venv/bin/activate" overwriting $PS1 to add "(venv)" (PS1="(venv) ${PS1:-}"), starship overwrite the terminal prompt.
Solution (see PR)
I modified starship.toml to add the the python virtual environment to the prompt
Additional comment
Starship being used for the bash prompt, I don't see the point of customizing $PS1 in "default/bash/prompt". I removed that file and the reference to it in "default/bash/prompt" as it seems to be outdated.
*assuming the user is in a folder with a venv folder containing a python virtual environment)
View raw text
### System details
Omarchy 3.15
### What's wrong?
## Short version
Python virtual environment not showing in the terminal prompt because of starship config
## More details
### Unexpected Behavior
When a python virtual environment get activated using*:
`source venv/bin/activate`
a python developer usually expect "(venv)" to be added to the terminal prompt to indicate that the venv environment is activated. This is actually what happen when using bash (or zsh) with default config. However in omarchy, despite the environment being activated nothing is added to the terminal prompt.
### Root cause
Omarchy is using starship (https://starship.rs/) to overwrite the terminal prompt. Despite the code in "venv/bin/activate" overwriting `$PS1` to add "(venv)" (`PS1="(venv) ${PS1:-}"`), starship overwrite the terminal prompt.
### Solution (see PR)
I modified starship.toml to add the the python virtual environment to the prompt
### Additional comment
Starship being used for the bash prompt, I don't see the point of customizing `$PS1` in "default/bash/prompt". I removed that file and the reference to it in "default/bash/prompt" as it seems to be outdated.
*assuming the user is in a folder with a venv folder containing a python virtual environment)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.